Searched full:mx23 (Results 1 – 25 of 36) sorted by relevance
12
| /Linux-v5.10/Documentation/devicetree/bindings/clock/ |
| D | imx23-clock.yaml | 7 title: Clock bindings for Freescale i.MX23
14 ID in its "clocks" phandle cell. The following is a full list of i.MX23
|
| /Linux-v5.10/Documentation/devicetree/bindings/mfd/ |
| D | mxs-lradc.txt | 4 - compatible: Should be "fsl,imx23-lradc" for i.MX23 SoC and "fsl,imx28-lradc"
23 Example for i.MX23 SoC:
|
| /Linux-v5.10/Documentation/devicetree/bindings/display/ |
| D | mxsfb.txt | 6 - compatible: Should be "fsl,imx23-lcdif" for i.MX23.
42 - compatible: Should be "fsl,imx23-lcdif" for i.MX23.
|
| /Linux-v5.10/drivers/clocksource/ |
| D | mxs_timer.c | 22 * The v1 on MX23 only gets 16 bits counter, while v2 on MX28
26 * another for clocksource. MX28 uses timrot 0 and 1, while MX23
43 * on MX28 while timrot2 on MX23.
|
| /Linux-v5.10/drivers/i2c/busses/ |
| D | i2c-mxs.c | 107 * @dev_type: distinguish i.MX23/i.MX28 features
350 * Start WRITE transaction on the I2C bus. By studying i.MX23 datasheet,
382 * MX23 idea: in mxs_i2c_pio_setup_xfer()
386 * WARNING! The MX23 is broken in some way, even if it claims in mxs_i2c_pio_setup_xfer()
550 /* Clear the PIO_MODE on i.MX23 */ in mxs_i2c_pio_setup_xfer()
615 * The i.MX23 is strange. After each and every operation, it's I2C IP in mxs_i2c_xfer_msg()
619 * DEBUG0 register. This bit is not documented in the i.MX23 datasheet in mxs_i2c_xfer_msg()
|
| /Linux-v5.10/arch/arm/mach-mxs/ |
| D | Kconfig | 17 bool "Freescale MXS (i.MX23, i.MX28) support"
|
| D | mach-mxs.c | 297 return "i.MX23"; in mxs_get_soc_id()
|
| /Linux-v5.10/drivers/gpu/drm/mxsfb/ |
| D | Kconfig | 19 Those devices are found in various i.MX SoC (including i.MX23,
|
| D | mxsfb_drv.h | 5 * i.MX23/i.MX28/i.MX6SX MXSFB LCD controller driver.
|
| D | mxsfb_regs.h | 6 * i.MX23/i.MX28/i.MX6SX MXSFB LCD controller driver.
|
| /Linux-v5.10/Documentation/devicetree/bindings/nvmem/ |
| D | mxs-ocotp.yaml | 7 title: On-Chip OTP Memory for Freescale i.MX23/i.MX28
|
| /Linux-v5.10/Documentation/devicetree/bindings/media/ |
| D | fsl-pxp.txt | 7 i.MX SoCs from i.MX23 to i.MX7.
|
| /Linux-v5.10/Documentation/devicetree/bindings/crypto/ |
| D | fsl-dcp.yaml | 7 title: Freescale DCP (Data Co-Processor) found on i.MX23/i.MX28
|
| /Linux-v5.10/drivers/mfd/ |
| D | mxs-lradc.c | 175 fallthrough; /* to an error message for i.MX23 */ in mxs_lradc_probe()
258 MODULE_DESCRIPTION("Freescale i.MX23/i.MX28 LRADC driver");
|
| /Linux-v5.10/arch/arm/boot/dts/ |
| D | imx23-olinuxino.dts | 13 model = "i.MX23 Olinuxino Low Cost Board";
|
| D | imx23-evk.dts | 9 model = "Freescale i.MX23 Evaluation Kit";
|
| D | imx23-pinfunc.h | 2 * Header providing constants for i.MX23 pinctrl bindings.
|
| /Linux-v5.10/drivers/watchdog/ |
| D | stmp3xxx_rtc_wdt.c | 3 * Watchdog driver for the RTC based watchdog in STMP3xxx and i.MX23/28
|
| /Linux-v5.10/drivers/mtd/nand/raw/gpmi-nand/ |
| D | gpmi-regs.h | 175 /* MX23 uses this to detect READY. */
|
| D | gpmi-nand.c | 66 * But in MX23, there is a hardware bug in the BCH block (see erratum #2847).
161 * See later BCH reset for explanation of MX23 and MX28 handling in gpmi_init()
243 /* The mx23/mx28 only support the GF13. */ in gpmi_check_ecc()
550 * Due to erratum #2847 of the MX23, the BCH cannot be soft reset on this in bch_set_geometry()
551 * chip, otherwise it will lock up. So we skip resetting BCH on the MX23. in bch_set_geometry()
|
| /Linux-v5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | fsl,mxs-pinctrl.txt | 124 Valid values for i.MX28/i.MX23 pinmux-id are defined in
|
| /Linux-v5.10/drivers/nvmem/ |
| D | mxs-ocotp.c | 196 MODULE_DESCRIPTION("driver for OCOTP in i.MX23/i.MX28");
|
| D | Kconfig | 94 on the Freescale i.MX23/i.MX28 processor.
|
| /Linux-v5.10/drivers/clk/mxs/ |
| D | clk-imx23.c | 157 pr_err("i.MX23 clk %d: register failed with %ld\n", in mx23_clocks_init()
|
| /Linux-v5.10/drivers/pinctrl/freescale/ |
| D | pinctrl-imx23.c | 3 // Freescale i.MX23 pinctrl driver
|
12
