From: Benjamin Zores <hidden> Date: 2007-01-22 21:44:02
Hi,
This question is mainly intended to Freescale's MPC8349ITX board maintainer
but the issue/resolution is probably the same for other boards.
I'm trying to boot the MPC8349ITX card with Linux 2.6.19 using old PPC
architecture (and not the new PowerPC one).
I've ported patches from Freescale's BSP from 2.6.13 to 2.6.19 and
it works pretty well but USB doesn't init properly.
Switching to PowerPC arch of course works fine and USB is well inited
but due to other feature i use that only exist on PPC right now, I can't
make use of it.
So I've added the attached patched to my PPC kernel in order to initialize
the USB controller the same way it is done in DTS file for PowerPC arch.
The goal is of course to use the regular EHCI-FSL driver.
I've noticed that PowerPC arch starts by initing the DR controller than MPH one.
On PPC it's the opposite way. Although I have to not initialize the DR one, which
seems to completely hang the card at USB controller probe.
Initializing the MPH controller seems to work fine but then
USB stack has a lot of errors which seem to come from bad EHCI-FSL init.
(see below)
fsl-ehci fsl-ehci.1: No platform data for fsl-ehci.1.
fsl-ehci fsl-ehci.2: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.2: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.2: irq 39, io base 0xe0022000
fsl-ehci fsl-ehci.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: Product: Freescale On-Chip EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.19.2-fsl ehci_hcd
usb usb1: SerialNumber: fsl-ehci.2
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
USB Universal Host Controller Interface driver v3.0
Initializing USB Mass Storage driver...
usb 1-1: new high speed USB device using fsl-ehci and address 2
usb 1-1: device descriptor read/64, error -32
usb 1-1: device descriptor read/64, error -32
usb 1-1: new high speed USB device using fsl-ehci and address 3
usb 1-1: device descriptor read/64, error -32
usb 1-1: device descriptor read/64, error -32
usb 1-1: new high speed USB device using fsl-ehci and address 4
usb 1-1: device not accepting address 4, error -32
usb 1-1: new high speed USB device using fsl-ehci and address 5
usb 1-1: device not accepting address 5, error -32
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
Of course, the USB controller isn't working afterwards
and no USB device can be used.
Does anyone has an idea where the problem might come from and how to solve it
(once again, switching to PowerPC arch is ok but i don't want to).
Thx in advance,
Regards,
Ben
From: Kumar Gala <hidden> Date: 2007-01-22 22:20:08
On Jan 22, 2007, at 11:10 AM, Benjamin Zores wrote:
Hi,
This question is mainly intended to Freescale's MPC8349ITX board
maintainer
but the issue/resolution is probably the same for other boards.
I'm trying to boot the MPC8349ITX card with Linux 2.6.19 using old PPC
architecture (and not the new PowerPC one).
I've ported patches from Freescale's BSP from 2.6.13 to 2.6.19 and
it works pretty well but USB doesn't init properly.
Switching to PowerPC arch of course works fine and USB is well inited
but due to other feature i use that only exist on PPC right now, I
can't
make use of it.
What are these features?
So I've added the attached patched to my PPC kernel in order to
initialize
the USB controller the same way it is done in DTS file for PowerPC
arch.
The goal is of course to use the regular EHCI-FSL driver.
I've noticed that PowerPC arch starts by initing the DR controller
than MPH one.
On PPC it's the opposite way. Although I have to not initialize the
DR one, which
seems to completely hang the card at USB controller probe.
Initializing the MPH controller seems to work fine but then
USB stack has a lot of errors which seem to come from bad EHCI-FSL
init.
(see below)
fsl-ehci fsl-ehci.1: No platform data for fsl-ehci.1.
fsl-ehci fsl-ehci.2: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.2: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.2: irq 39, io base 0xe0022000
fsl-ehci fsl-ehci.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: Product: Freescale On-Chip EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.19.2-fsl ehci_hcd
usb usb1: SerialNumber: fsl-ehci.2
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
USB Universal Host Controller Interface driver v3.0
Initializing USB Mass Storage driver...
usb 1-1: new high speed USB device using fsl-ehci and address 2
usb 1-1: device descriptor read/64, error -32
usb 1-1: device descriptor read/64, error -32
usb 1-1: new high speed USB device using fsl-ehci and address 3
usb 1-1: device descriptor read/64, error -32
usb 1-1: device descriptor read/64, error -32
usb 1-1: new high speed USB device using fsl-ehci and address 4
usb 1-1: device not accepting address 4, error -32
usb 1-1: new high speed USB device using fsl-ehci and address 5
usb 1-1: device not accepting address 5, error -32
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
Of course, the USB controller isn't working afterwards
and no USB device can be used.
Does anyone has an idea where the problem might come from and how
to solve it
(once again, switching to PowerPC arch is ok but i don't want to).
If you are forward porting the Freescale patches and not using the in
kernel driver that would explain the issue. There are bugs in the
Freescale driver that have been fixed in the driver that is in the
kernel.
- kumar
From: Benjamin Zores <hidden> Date: 2007-01-23 08:22:29
On Mon, 22 Jan 2007 16:19:06 -0600
Kumar Gala [off-list ref] wrote:
What are these features?
External RT patch that only supports PPC arch atm.
Also I've encountered some stability issues with PowerPC branch
(card hangs after some time for undetermined reason).
If you are forward porting the Freescale patches and not using the in
kernel driver that would explain the issue. There are bugs in the
Freescale driver that have been fixed in the driver that is in the
kernel.
I only ported what needs to be i.e. the platform initialization part.
I'm using the regular USB drivers (EHCI-FSL) from vanilla 2.6.19, this part
hasn't be ported from old 2.6.13 BSP code (which would have been useless).
The goal of the patch i've sent early is to init the USB bus the same way
it is done by OF device tree in arch/powerpc/sysdev/fsl_soc.c (but for PPC).
Does it sounds ok to you ?
Regards,
Ben
From: Kumar Gala <hidden> Date: 2007-01-23 16:19:31
On Jan 23, 2007, at 2:18 AM, Benjamin Zores wrote:
On Mon, 22 Jan 2007 16:19:06 -0600
Kumar Gala [off-list ref] wrote:
quoted
What are these features?
External RT patch that only supports PPC arch atm.
Also I've encountered some stability issues with PowerPC branch
(card hangs after some time for undetermined reason).
Do you get an oops on the hang? would be useful to know if we have
an issue in arch/powerpc
quoted
If you are forward porting the Freescale patches and not using the in
kernel driver that would explain the issue. There are bugs in the
Freescale driver that have been fixed in the driver that is in the
kernel.
I only ported what needs to be i.e. the platform initialization part.
I'm using the regular USB drivers (EHCI-FSL) from vanilla 2.6.19,
this part
hasn't be ported from old 2.6.13 BSP code (which would have been
useless).
The goal of the patch i've sent early is to init the USB bus the
same way
it is done by OF device tree in arch/powerpc/sysdev/fsl_soc.c (but
for PPC).
Does it sounds ok to you ?
From: Timur Tabi <hidden> Date: 2007-01-23 16:33:00
Benjamin Zores wrote:
Hi,
This question is mainly intended to Freescale's MPC8349ITX board maintainer
but the issue/resolution is probably the same for other boards.
I'm the maintainer, although I don't think I can help you with this specific
problem.
I'm trying to boot the MPC8349ITX card with Linux 2.6.19 using old PPC
architecture (and not the new PowerPC one).
I've ported patches from Freescale's BSP from 2.6.13 to 2.6.19 and
it works pretty well but USB doesn't init properly.
Switching to PowerPC arch of course works fine and USB is well inited
but due to other feature i use that only exist on PPC right now, I can't
make use of it.
What feature is that? I would think it would be easier to port that feature to
the powerpc architecture, then it would be to port ITX support to the ppc
architecture.
--
Timur Tabi
Linux Kernel Developer @ Freescale
Thanks for the hint.
I've seen the part that was missing in my own patch and now the MPH is well detected (though the DR one still hangs the card but it's useless to me atm).
Ben