RE: USB OTG support on mx27pdk
Sun, 20 Apr 2014 00:48:28 + от Peter Chen peter.c...@freescale.com: -Original Message- From: Fabio Estevam [mailto:feste...@gmail.com] Sent: Sunday, April 20, 2014 1:10 AM To: Chen Peter-B29397 Cc: Michael Grzeschik; Alexander Shiyan; linux-arm- ker...@lists.infradead.org; linux-usb@vger.kernel.org; Sascha Hauer; chris.ru...@gtsys.com.hk; Guo Shawn-R65073 Subject: Re: USB OTG support on mx27pdk On Sat, Apr 19, 2014 at 4:32 AM, Peter Chen peter.c...@freescale.com wrote: The below patch is intended to fix above issues for all platforms, I have tested it at imx6 platform, if possible, have a test at imx25/imx27 please. I don't see any patch below, but anyway I have managed to fix the issue on mx27 at dts level. https://github.com/hzpeterchen/linux- usb/commit/c1f42ea27ed3f5d988c63da7849d2e6b445b4fbc Your problem is different with sasche's, which hang the system due to no phy clk. The chris's patch should not cause the oops. For me, nothing has changed. The driver works on i.MX27 PCM970 RDK with the patch as well as without it. Thanks for testing. This patch does not change the flow for ulpi, it changes pts at portsc first, and call ulpi_init if it exists, your results prove that the patch works ok if the kernel does not touch ulpi. Peter N�r��yb�X��ǧv�^�){.n�+{��^n�r���z���h����G���h�(�階�ݢj���m��z�ޖ���f���h���~�m�
RE: USB OTG support on mx27pdk
On Wed, Apr 16, 2014 at 09:53:34AM -0300, Fabio Estevam wrote: On Wed, Apr 16, 2014 at 8:58 AM, Alexander Shiyan shc_w...@mail.ru wrote: I can tell immediately without further testing, this will not work without the USB support in the bootoader because we do not have DT support for ULPI. The generic nop usb phy should work just fine. I have tried Uwe's suggestion from a previous post and reverted: commit cd0b42c2a6d2a74244f0053f8960f5dad5842278 Author: Chris Ruehl chris.ru...@gtsys.com.hk Date: Fri Jan 10 13:51:30 2014 +0800 usb: chipidea: put hw_phymode_configure before ci_usb_phy_init hw_phymode_configure configures the PORTSC registers and allow the following phy_inits to operate on the right parameters. This fix a problem where the UPLI (ISP1504) could not be detected, because the Viewport was not available and read the viewport return 0's only. Signed-off-by: Chris Ruehl chris.ru...@gtsys.com.hk Signed-off-by: Peter Chen peter.c...@freescale.com Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org Then USB OTG port detected the USB pen driver fine: usbcore: registered new interface driver usb-storage 10024000.usb supply vbus not found, using dummy regulator ci_hdrc ci_hdrc.0: EHCI Host Controller ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1 ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected ... scsi 0:0:0:0: Direct-Access ChipsBnk Flash Disk 2.00 PQ: 0 ANSI: 2 sd 0:0:0:0: [sda] 1035200 512-byte logical blocks: (530 MB/505 MiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] No Caching mode page found sd 0:0:0:0: [sda] Assuming drive cache: write through sda: sda1 sd 0:0:0:0: [sda] Attached SCSI removable disk If I understand correctly commit cd0b42c2a was only needed because Chris was trying to add DT support for ULPI, which never got merged into mainline. If we use the generic nop usb phy instead, we should just revert this commit. Any objections? Yes, when this patch got reverted it will probably break usb support on mx6 machines. We have seen different behaviour on several mxc/mxs machines regarding the order of PORTSC and phy configuration. We will probably need to test all platforms before reordering this function call again and again for every machine using this driver. The below patch is intended to fix above issues for all platforms, I have tested it at imx6 platform, if possible, have a test at imx25/imx27 please. Peter -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: USB OTG support on mx27pdk
On Sat, Apr 19, 2014 at 4:32 AM, Peter Chen peter.c...@freescale.com wrote: The below patch is intended to fix above issues for all platforms, I have tested it at imx6 platform, if possible, have a test at imx25/imx27 please. I don't see any patch below, but anyway I have managed to fix the issue on mx27 at dts level. -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: USB OTG support on mx27pdk
-Original Message- From: Fabio Estevam [mailto:feste...@gmail.com] Sent: Sunday, April 20, 2014 1:10 AM To: Chen Peter-B29397 Cc: Michael Grzeschik; Alexander Shiyan; linux-arm- ker...@lists.infradead.org; linux-usb@vger.kernel.org; Sascha Hauer; chris.ru...@gtsys.com.hk; Guo Shawn-R65073 Subject: Re: USB OTG support on mx27pdk On Sat, Apr 19, 2014 at 4:32 AM, Peter Chen peter.c...@freescale.com wrote: The below patch is intended to fix above issues for all platforms, I have tested it at imx6 platform, if possible, have a test at imx25/imx27 please. I don't see any patch below, but anyway I have managed to fix the issue on mx27 at dts level. https://github.com/hzpeterchen/linux-usb/commit/c1f42ea27ed3f5d988c63da7849d2e6b445b4fbc Your problem is different with sasche's, which hang the system due to no phy clk. The chris's patch should not cause the oops. Peter N�r��yb�X��ǧv�^�){.n�+{��^n�r���z���h����G���h�(�階�ݢj���m��z�ޖ���f���h���~�m�
Re: USB OTG support on mx27pdk
Sun, 20 Apr 2014 00:48:28 + от Peter Chen peter.c...@freescale.com: -Original Message- From: Fabio Estevam [mailto:feste...@gmail.com] Sent: Sunday, April 20, 2014 1:10 AM To: Chen Peter-B29397 Cc: Michael Grzeschik; Alexander Shiyan; linux-arm- ker...@lists.infradead.org; linux-usb@vger.kernel.org; Sascha Hauer; chris.ru...@gtsys.com.hk; Guo Shawn-R65073 Subject: Re: USB OTG support on mx27pdk On Sat, Apr 19, 2014 at 4:32 AM, Peter Chen peter.c...@freescale.com wrote: The below patch is intended to fix above issues for all platforms, I have tested it at imx6 platform, if possible, have a test at imx25/imx27 please. I don't see any patch below, but anyway I have managed to fix the issue on mx27 at dts level. https://github.com/hzpeterchen/linux-usb/commit/c1f42ea27ed3f5d988c63da7849d2e6b445b4fbc Your problem is different with sasche's, which hang the system due to no phy clk. The chris's patch should not cause the oops. For me, nothing has changed. The driver works on i.MX27 PCM970 RDK with the patch as well as without it. --- N�r��yb�X��ǧv�^�){.n�+{��^n�r���z���h����G���h�(�階�ݢj���m��z�ޖ���f���h���~�m�
Re: USB OTG support on mx27pdk
On Wed, Apr 16, 2014 at 2:55 AM, Alexander Shiyan shc_w...@mail.ru wrote: ci_hdrc ci_hdrc.0: EHCI Host Controller ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1 ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00 usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: EHCI Host Controller usb usb1: Manufacturer: Linux 3.15.0-rc1-next-20140415-dirty ehci_hcd usb usb1: SerialNumber: ci_hdrc.0 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected Thanks for testing, Alexander. Does your bootloader have USB support? If so, would it be possible to remove the USB support from the bootloader, please? I am wondering if the bootloader is doing some USB related init that the kernel is missing. Thanks, Fabio Estevam -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: USB OTG support on mx27pdk
Wed, 16 Apr 2014 08:32:55 -0300 от Fabio Estevam feste...@gmail.com: On Wed, Apr 16, 2014 at 2:55 AM, Alexander Shiyan shc_w...@mail.ru wrote: ci_hdrc ci_hdrc.0: EHCI Host Controller ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1 ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00 usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: EHCI Host Controller usb usb1: Manufacturer: Linux 3.15.0-rc1-next-20140415-dirty ehci_hcd usb usb1: SerialNumber: ci_hdrc.0 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected Thanks for testing, Alexander. Does your bootloader have USB support? If so, would it be possible to remove the USB support from the bootloader, please? I am wondering if the bootloader is doing some USB related init that the kernel is missing. I can tell immediately without further testing, this will not work without the USB support in the bootoader because we do not have DT support for ULPI. ---
Re: USB OTG support on mx27pdk
On Wed, Apr 16, 2014 at 8:58 AM, Alexander Shiyan shc_w...@mail.ru wrote: I can tell immediately without further testing, this will not work without the USB support in the bootoader because we do not have DT support for ULPI. The generic nop usb phy should work just fine. I have tried Uwe's suggestion from a previous post and reverted: commit cd0b42c2a6d2a74244f0053f8960f5dad5842278 Author: Chris Ruehl chris.ru...@gtsys.com.hk Date: Fri Jan 10 13:51:30 2014 +0800 usb: chipidea: put hw_phymode_configure before ci_usb_phy_init hw_phymode_configure configures the PORTSC registers and allow the following phy_inits to operate on the right parameters. This fix a problem where the UPLI (ISP1504) could not be detected, because the Viewport was not available and read the viewport return 0's only. Signed-off-by: Chris Ruehl chris.ru...@gtsys.com.hk Signed-off-by: Peter Chen peter.c...@freescale.com Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org Then USB OTG port detected the USB pen driver fine: usbcore: registered new interface driver usb-storage 10024000.usb supply vbus not found, using dummy regulator ci_hdrc ci_hdrc.0: EHCI Host Controller ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1 ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected ... scsi 0:0:0:0: Direct-Access ChipsBnk Flash Disk 2.00 PQ: 0 ANSI: 2 sd 0:0:0:0: [sda] 1035200 512-byte logical blocks: (530 MB/505 MiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] No Caching mode page found sd 0:0:0:0: [sda] Assuming drive cache: write through sda: sda1 sd 0:0:0:0: [sda] Attached SCSI removable disk If I understand correctly commit cd0b42c2a was only needed because Chris was trying to add DT support for ULPI, which never got merged into mainline. If we use the generic nop usb phy instead, we should just revert this commit. Any objections? Regards, Fabio Estevam -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: USB OTG support on mx27pdk
Hi, On Wed, Apr 16, 2014 at 09:53:34AM -0300, Fabio Estevam wrote: On Wed, Apr 16, 2014 at 8:58 AM, Alexander Shiyan shc_w...@mail.ru wrote: I can tell immediately without further testing, this will not work without the USB support in the bootoader because we do not have DT support for ULPI. The generic nop usb phy should work just fine. I have tried Uwe's suggestion from a previous post and reverted: commit cd0b42c2a6d2a74244f0053f8960f5dad5842278 Author: Chris Ruehl chris.ru...@gtsys.com.hk Date: Fri Jan 10 13:51:30 2014 +0800 usb: chipidea: put hw_phymode_configure before ci_usb_phy_init hw_phymode_configure configures the PORTSC registers and allow the following phy_inits to operate on the right parameters. This fix a problem where the UPLI (ISP1504) could not be detected, because the Viewport was not available and read the viewport return 0's only. Signed-off-by: Chris Ruehl chris.ru...@gtsys.com.hk Signed-off-by: Peter Chen peter.c...@freescale.com Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org Then USB OTG port detected the USB pen driver fine: usbcore: registered new interface driver usb-storage 10024000.usb supply vbus not found, using dummy regulator ci_hdrc ci_hdrc.0: EHCI Host Controller ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1 ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected ... scsi 0:0:0:0: Direct-Access ChipsBnk Flash Disk 2.00 PQ: 0 ANSI: 2 sd 0:0:0:0: [sda] 1035200 512-byte logical blocks: (530 MB/505 MiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] No Caching mode page found sd 0:0:0:0: [sda] Assuming drive cache: write through sda: sda1 sd 0:0:0:0: [sda] Attached SCSI removable disk If I understand correctly commit cd0b42c2a was only needed because Chris was trying to add DT support for ULPI, which never got merged into mainline. If we use the generic nop usb phy instead, we should just revert this commit. Any objections? Yes, when this patch got reverted it will probably break usb support on mx6 machines. We have seen different behaviour on several mxc/mxs machines regarding the order of PORTSC and phy configuration. We will probably need to test all platforms before reordering this function call again and again for every machine using this driver. Regards, Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: USB OTG support on mx27pdk
On Wed, Apr 16, 2014 at 12:03 PM, Michael Grzeschik m...@pengutronix.de wrote: Yes, when this patch got reverted it will probably break usb support on mx6 machines. We have seen different behaviour on several mxc/mxs machines regarding the order of PORTSC and phy configuration. We will probably need to test all platforms before reordering this function call again and again for every machine using this driver. Ok, I managed to fix the issue on mx27 without touching the chipidea driver. Will submit the fix later today. Regards, Fabio Estevam -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: USB OTG support on mx27pdk
Hi, I am trying to add USBOTG support to mx27pdk with the following dts patch: --- a/arch/arm/boot/dts/imx27-pdk.dts +++ b/arch/arm/boot/dts/imx27-pdk.dts @@ -78,6 +78,14 @@ status = okay; }; +usbotg { + pinctrl-names = default; + pinctrl-0 = pinctrl_usbotg; + dr_mode = otg; + phy_type = ulpi; + status = okay; +}; + iomuxc { imx27-pdk { pinctrl_cspi2: cspi2grp { @@ -121,5 +129,22 @@ MX27_PAD_UART1_RTS__UART1_RTS 0x0 ; }; + + pinctrl_usbotg: usbotggrp { + fsl,pins = + MX27_PAD_USBOTG_NXT__USBOTG_NXT 0x0 + MX27_PAD_USBOTG_STP__USBOTG_STP 0x0 + MX27_PAD_USBOTG_DIR__USBOTG_DIR 0x0 + MX27_PAD_USBOTG_CLK__USBOTG_CLK 0x0 + MX27_PAD_USBOTG_DATA0__USBOTG_DATA0 0x0 + MX27_PAD_USBOTG_DATA1__USBOTG_DATA1 0x0 + MX27_PAD_USBOTG_DATA2__USBOTG_DATA2 0x0 + MX27_PAD_USBOTG_DATA3__USBOTG_DATA3 0x0 + MX27_PAD_USBOTG_DATA4__USBOTG_DATA4 0x0 + MX27_PAD_USBOTG_DATA5__USBOTG_DATA5 0x0 + MX27_PAD_USBOTG_DATA6__USBOTG_DATA6 0x0 + MX27_PAD_USBOTG_DATA7__USBOTG_DATA7 0x0 + ; + }; }; } However on kernel boot the following is seen: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-mxc: Freescale On-Chip EHCI Host driver usbcore: registered new interface driver usb-storage 10024000.usb supply vbus not found, using dummy regulator Unhandled fault: external abort on non-linefetch (0x808) at 0xf4424184 Internal error: : 808 [#1] PREEMPT ARM Modules linked in: CPU: 0 PID: 1 Comm: swapper Not tainted 3.15.0-rc1-26325-g971f9fd-dirty #64 task: c7829aa0 ti: c7836000 task.ti: c7836000 PC is at ci_hdrc_probe+0x3a4/0x634 LR is at ci_hdrc_probe+0x100/0x634 pc : [c036cc78]lr : [c036c9d4]psr: 6013 sp : c7837d48 ip : 0001 fp : r10: r9 : r8 : c791b6c0 r7 : c7945000 r6 : f4424000 r5 : c7945010 r4 : c794e010 r3 : f4424184 r2 : r1 : 8c04 r0 : 0c04 Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel Control: 0005317f Table: a0004000 DAC: 0017 Process swapper (pid: 1, stack limit = 0xc78361c0) Stack: (0xc7837d48 to 0xc7838000) 7d40: c012e294 c7945010 c06f471c c073dc90 c06f471c 7d60: c02b9d84 c02b9d6c c7945010 c02b8874 c02b8a1c 7d80: c7945010 c02b8a1c c78bc010 c02b6fcc c7828c7c c7a150d4 c7945010 c7945044 7da0: c7945010 c02b8744 c7945010 c06e6780 c7945010 c02b7e58 c7945010 7dc0: c7945018 c02b6440 c7829aa0 c06cd748 c791b6c0 c7945010 0002 7de0: c7945000 c7945010 c7945000 0002 c7893340 c02b9f28 10024000 7e00: c7837e34 c7945000 c036d1d4 c78bc010 c78bc000 7e20: 0091 c7875670 c036e358 c7836000 c78a8aa0 0100 7e40: c7881b90 0003 000a 0003 c793b9c0 c78bc010 7e60: c06f48c4 c073dc90 c06f48c4 c7836000 c06a4aa0 c02b9d84 c02b9d6c c78bc010 7e80: c02b8874 c78bc010 c06f48c4 c78bc044 c02b8a18 7ea0: c06f48c4 c02b898c c02b7070 c7828c6c c78905b0 c06f48c4 c7943ee0 7ec0: c06e6780 c02b8050 c05ff4b8 c024a414 c06f48c4 c06f48c4 0006 c06b21c4 7ee0: c0707240 c02b9088 c06bdd8c 0006 c0008974 c7866280 c01236c0 7f00: c070f434 c7866280 c04c9900 004f c01239f4 7f20: 6053 c06cec64 c7ffc890 c04ec5c0 0091 c0034300 c064db3c 0006 7f40: c7ffc897 0006 c06cec3c c06bdd8c 0006 c06b21c4 c0707240 c0679480 7f60: 0091 c06b21d0 c0679af0 0006 0006 c0679480 7f80: c7837f9c c003f8c0 c04b8dd0 7fa0: c04b8dd8 c00095b0 7fc0: 7fe0: 0013 [c036cc78] (ci_hdrc_probe) from [c02b9d84] (platform_drv_probe+0x18/0x48) [c02b9d84] (platform_drv_probe) from [c02b8874] (driver_probe_device+0x104/) [c02b8874] (driver_probe_device) from [c02b6fcc] (bus_for_each_drv+0x48/0x9) [c02b6fcc] (bus_for_each_drv) from [c02b8744] (device_attach+0x74/0x80) [c02b8744] (device_attach) from [c02b7e58] (bus_probe_device+0x88/0xb0) [c02b7e58] (bus_probe_device) from [c02b6440] (device_add+0x3e0/0x4e4) [c02b6440] (device_add) from [c02b9f28] (platform_device_add+0xac/0x20c) [c02b9f28] (platform_device_add) from
Re: USB OTG support on mx27pdk
On Wed, Apr 16, 2014 at 12:23 AM, Peter Chen peter.c...@freescale.com wrote: Please check if below patch is existed commit 3b5d3e6845bfe68777d069886b0d1cd5f23b9d58 Author: Chris Ruehl chris.ru...@gtsys.com.hk Date: Fri Jan 10 13:51:29 2014 +0800 usb: chipidea: Fix Internal error: : 808 [#1] ARM related to STS flag * init the sts flag to 0 (missed) * fix write the real bit not sts value * Set PORTCS_STS and DEVLC_STS only if sts = 1 I cced chris who has imx27 hardware. Yes, this patch is applied in 3.15-rc1, but does not help here. Regards, Fabio Estevam -- To unsubscribe from this list: send the line unsubscribe linux-usb in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: USB OTG support on mx27pdk
On Wed, Apr 16, 2014 at 12:23 AM, Peter Chen peter.c...@freescale.com wrote: Please check if below patch is existed commit 3b5d3e6845bfe68777d069886b0d1cd5f23b9d58 Author: Chris Ruehl chris.ru...@gtsys.com.hk Date: Fri Jan 10 13:51:29 2014 +0800 usb: chipidea: Fix Internal error: : 808 [#1] ARM related to STS flag * init the sts flag to 0 (missed) * fix write the real bit not sts value * Set PORTCS_STS and DEVLC_STS only if sts = 1 I cced chris who has imx27 hardware. Yes, this patch is applied in 3.15-rc1, but does not help here. Just tried one imx6dl board, it works well. Have a look if it is related to phy_type at dts or phy driver please. Peter
Re: USB OTG support on mx27pdk
Wed, 16 Apr 2014 03:23:54 + от Peter Chen peter.c...@freescale.com: Hi, I am trying to add USBOTG support to mx27pdk with the following dts patch: ... I cced chris who has imx27 hardware. Loading OS arm Linux zImage '/dev/nor0.kernel' using internal devicetree commandline: console=ttymxc0,115200n8 earlyprintk root=/dev/mtdblock3 ro booting kernel with devicetree Uncompressing Linux... done, booting the kernel. Booting Linux on physical CPU 0x0 Linux version 3.15.0-rc1-next-20140415-dirty (s...@shc.zet) (gcc version 4.7.3 (GCC) ) #11 PREEMPT Wed Apr 16 09:40:14 MSK 2014 CPU: ARM926EJ-S [41069264] revision 4 (ARMv5TEJ), cr=00053177 CPU: VIVT data cache, VIVT instruction cache Machine model: Phytec pcm970 bootconsole [earlycon0] enabled Memory policy: Data cache writeback Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 Kernel command line: console=ttymxc0,115200n8 earlyprintk root=/dev/mtdblock3 ro PID hash table entries: 512 (order: -1, 2048 bytes) Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 123364K/131072K available (4601K kernel code, 256K rwdata, 1244K rodata, 170K init, 143K bss, 7708K reserved) Virtual kernel memory layout: vector : 0x - 0x1000 ( 4 kB) fixmap : 0xfff0 - 0xfffe ( 896 kB) vmalloc : 0xc880 - 0xff00 ( 872 MB) lowmem : 0xc000 - 0xc800 ( 128 MB) .text : 0xc0008000 - 0xc05bd8c0 (5847 kB) .init : 0xc05be000 - 0xc05e8970 ( 171 kB) .data : 0xc05ea000 - 0xc062a260 ( 257 kB) .bss : 0xc062a26c - 0xc064e104 ( 144 kB) Preemptible hierarchical RCU implementation. NR_IRQS:16 nr_irqs:16 16 MXC IRQ initialized Switching to timer-based delay loop sched_clock: 32 bits at 14MHz, resolution 67ns, wraps every 290636879804ns CPU identified as i.MX27, silicon rev 2.1 Console: colour dummy device 80x30 Calibrating delay loop (skipped), value calculated using timer frequency.. 29.55 BogoMIPS (lpj=14) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) CPU: Testing write buffer coherency: ok Setting up static identity map for 0xa045f2c8 - 0xa045f328 devtmpfs: initialized pinctrl core: initialized pinctrl subsystem regulator-dummy: no parameters NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations cpuidle: using governor ladder cpuidle: using governor menu imx27-pinctrl 10015000.iomuxc: initialized IMX pinctrl driver 3V3: 3300 mV 5V0: 5000 mV SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb platform 0.usbphy: Driver usb_phy_gen_xceiv requests probe deferral platform 2.usbphy: Driver usb_phy_gen_xceiv requests probe deferral i2c i2c-0: IMX I2C adapter registered i2c i2c-1: IMX I2C adapter registered Linux video capture interface: v2.00 pps_core: LinuxPPS API ver. 1 registered pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti giome...@linux.it PTP clock support registered Advanced Linux Sound Architecture Driver Initialized. Switched to clocksource mxc_timer1 NET: Registered protocol family 2 TCP established hash table entries: 1024 (order: 0, 4096 bytes) TCP bind hash table entries: 1024 (order: 0, 4096 bytes) TCP: Hash tables configured (established 1024 bind 1024) TCP: reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. futex hash table entries: 256 (order: -1, 3072 bytes) jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. msgmni has been set to 240 Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251) io scheduler noop registered (default) imx-weim d8002000.weim: Driver registered. imx-fb 10021000.fb: i.MX Framebuffer driver Console: switching to colour frame buffer device 30x40 Serial: IMX driver 1000a000.serial: ttymxc0 at MMIO 0x1000a000 (irq = 36, base_baud = 923611) is a IMX console [ttymxc0] enabled bootconsole [earlycon0] disabled 1000b000.serial: ttymxc1 at MMIO 0x1000b000 (irq = 35, base_baud = 923611) is a IMX [drm] Initialized drm 1.1.0 20060810 at24 1-0052: 4096 byte 24c32 EEPROM, writable, 32 bytes/write physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x89 Chip ID 0x00891c Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Intel/Sharp Extended Query Table at 0x010A Using buffer write method Using auto-unlock on power-up/resume