Home
last modified time | relevance | path

Searched full:mx6q (Results 1 – 24 of 24) sorted by relevance

/linux-5.10/Documentation/devicetree/bindings/display/imx/
Dldb.txt16 - gpr : should be <&gpr> on i.MX53 and i.MX6q.
29 On i.MX6q the following additional clocks are needed:
37 - pinctrl-names : should be "default" on i.MX53, not used on i.MX6q
39 not used on i.MX6q
/linux-5.10/Documentation/devicetree/bindings/arm/
Dfsl.yaml111 - description: i.MX6Q based Boards
116 - emtrion,emcon-mx6 # emCON-MX6D or emCON-MX6Q SoM
117 - emtrion,emcon-mx6-avari # emCON-MX6D or emCON-MX6Q SoM on Avari Base
126 - technexion,imx6q-pico-dwarf # TechNexion i.MX6Q Pico-Dwarf
127 - technexion,imx6q-pico-hobbit # TechNexion i.MX6Q Pico-Hobbit
128 - technexion,imx6q-pico-nymph # TechNexion i.MX6Q Pico-Nymph
129 - technexion,imx6q-pico-pi # TechNexion i.MX6Q Pico-Pi
139 - description: i.MX6Q Gateworks Ventana Boards
160 - description: i.MX6Q PHYTEC phyBOARD-Mira
169 - description: i.MX6Q PHYTEC phyFLEX-i.MX6
/linux-5.10/Documentation/admin-guide/media/
Dimx.rst108 The following shows the media topologies for the i.MX6Q SabreSD and
109 i.MX6Q SabreAuto. Refer to these diagrams in the entity descriptions
123 :alt: Diagram of the i.MX6Q SabreSD media pipeline topology
126 Media pipeline graph on i.MX6Q SabreSD
129 :alt: Diagram of the i.MX6Q SabreAuto media pipeline topology
132 Media pipeline graph on i.MX6Q SabreAuto
409 i.MX6Q SabreLite with OV5642 and OV5640
463 i.MX6Q SabreAuto with ADV7180 decoder
466 On the i.MX6Q SabreAuto, an on-board ADV7180 SD decoder is connected to the
579 i.MX6Q SabreSD with MIPI CSI-2 OV5640
[all …]
/linux-5.10/Documentation/devicetree/bindings/thermal/
Dimx-thermal.yaml22 The interrupt output of the controller, i.MX6Q has IRQ_HIGH which
24 i.MX6SX and i.MX7S/D have two more IRQs than i.MX6Q, one is IRQ_LOW
/linux-5.10/Documentation/devicetree/bindings/bus/
Dimx-weim.txt32 register, e.g. IOMUXC_GPR1 on i.MX6Q. IOMUXC_GPR1[11:0]
62 i.MX51 ("fsl,imx51-weim") and i.MX6Q ("fsl,imx6q-weim")
/linux-5.10/Documentation/usb/
Dchipidea.rst9 with 2 Freescale i.MX6Q sabre SD boards.
35 1) Power up 2 Freescale i.MX6Q sabre SD boards with gadget class driver loaded
/linux-5.10/Documentation/devicetree/bindings/media/
Dfsl-vdoa.txt4 The Video Data Order Adapter (VDOA) is present on the i.MX6q. Its sole purpose
Dcoda.txt12 (d) "fsl,imx6q-vpu" for CODA960 present in i.MX6q
/linux-5.10/drivers/clocksource/
Dtimer-imx-gpt.c25 * - MX25, MX31, MX35, MX37, MX51, MX6Q(rev1.0)
26 * - MX6DL, MX6SX, MX6Q(rev1.1+)
497 * We were using the same compatible string for i.MX6Q/D and i.MX6DL/S in imx31_timer_init_dt()
/linux-5.10/Documentation/devicetree/bindings/nvmem/
Dimx-ocotp.yaml14 i.MX6Q/D, i.MX6DL/S, i.MX6SL, i.MX6SX, i.MX6UL, i.MX6ULL/ULZ, i.MX6SLL,
/linux-5.10/Documentation/devicetree/bindings/power/
Dfsl,imx-gpc.yaml58 The following DOMAIN_INDEX values are valid for i.MX6Q:
/linux-5.10/drivers/soc/imx/
Dsoc-imx.c90 soc_id = "i.MX6Q"; in imx_soc_device_init()
/linux-5.10/drivers/mtd/nand/raw/gpmi-nand/
Dgpmi-nand.h16 #define GPMI_CLK_MAX 5 /* MX6Q needs five clocks */
Dgpmi-nand.c635 * is 16000ps, but in mx6q, we use 12000ps.
/linux-5.10/arch/arm/mach-imx/
Dhardware.h79 * mx6q:
Dmach-imx6q.c251 imx_print_silicon_rev(cpu_is_imx6dl() ? "i.MX6DL" : "i.MX6Q", in imx6q_init_machine()
/linux-5.10/drivers/cpufreq/
Dimx6q-cpufreq.c245 * 2b'01: 852000000Hz; -- i.MX6Q Only, exclusive with 996MHz. in imx6q_opp_check_speed_grading()
548 MODULE_DESCRIPTION("Freescale i.MX6Q cpufreq driver");
/linux-5.10/drivers/gpu/drm/imx/
Dimx-ldb.c595 * i.MX6q: ipu1_di0_sel, ipu1_di1_sel, ipu2_di0_sel, ipu2_di1_sel in imx_ldb_bind()
/linux-5.10/arch/arm/
DKconfig.debug454 bool "i.MX6Q/DL Debug UART"
458 on i.MX6Q/DL.
/linux-5.10/drivers/clk/imx/
Dclk-imx6q.c468 /* Audio/video PLL post dividers do not work on i.MX6q revision 1.0 */ in imx6q_clocks_init()
913 * The gpt_3m clock is not available on i.MX6Q TO1.0. Let's point it in imx6q_clocks_init()
/linux-5.10/drivers/tty/serial/
Dimx.c178 /* i.MX21 type uart runs on all i.mx except i.MX1 and i.MX6q */
1136 * There are two kinds of RX DMA interrupts(such as in the MX6Q):
/linux-5.10/drivers/mmc/host/
Dsdhci-esdhc-imx.c1329 * erratum ESDHC_FLAG_ERR004536 fix for MX6Q TO1.2 and MX6DL in sdhci_esdhc_imx_hwinit()
/linux-5.10/drivers/gpu/drm/bridge/synopsys/
Ddw-hdmi.c2080 * (and possibly on the platform). So far i.MX6Q (v1.30a), i.MX6DL in dw_hdmi_clear_overflow()
/linux-5.10/drivers/net/ethernet/freescale/
Dfec_main.c2103 * Reference Manual has an error on this, and gets fixed on i.MX6Q in fec_enet_mii_init()