Re: [linux-usb-devel] hub.c port power handling on over-current

2007-05-29 Thread Engelmayer Christian
]); + } + } + } /* FIXME autosuspend idle root hubs */ spin_unlock_irqrestore (ehci-lock, flags); - Christian -Original Message- From: David Brownell [mailto:[EMAIL PROTECTED] Sent: Saturday, May 26, 2007 6:18 AM To: linux-usb-devel@lists.sourceforge.net Cc: Engelmayer Christian

[linux-usb-devel] hub.c port power handling on over-current

2007-05-25 Thread Engelmayer Christian
Hi all, If I am not mistaken the current policy is to leave port power enabled at all times during over-current situations and let the power provider handle current limitation. I experienced problems with the EHCI on an MPC8343E, which after some over-current situations no longer asserts the

[linux-usb-devel] [PATCH 2.6.20.2 1/1] ehci-fsl: change SI_CTRL, PRI_CTRL register offsets according to errata

2007-03-12 Thread Engelmayer Christian
From: Christian Engelmayer [EMAIL PROTECTED] Correct the offsets of the SI_CTRL, PRI_CTRL registers according to the Reference Manual errata sheet in order to prevent unwanted settings regarding burst transactions and priority states. Signed-off-by: Christian Engelmayer [EMAIL PROTECTED] ---

[linux-usb-devel] Freescale MPC8343 EHCI USB over-current behaviour

2007-03-12 Thread Engelmayer Christian
Hello all, I encountered some strange behaviour using EHCI support on an MPC8343: In case there is an over-current reported to the USB controller while no device is actually attached (due to a faulty board or by test creating a short at an extension cord) it seems as if no device is recognized