This moves the two instances from the big node into two child nodes. The
glue layer ontop does almost nothing.
There is one devices containing the control module for USB (2) phy,
(2) usb and later the dma engine. The usb device is the glue device
which contains the musb device as a child. This is
On Fri, Jul 05, 2013 at 03:32:57PM +0200, Sebastian Andrzej Siewior wrote:
This moves the two instances from the big node into two child nodes. The
glue layer ontop does almost nothing.
This could be two indepentant child nodes but I have no idea how
'ti,hwmods = usb_otg_hs;' affects the two
This moves the two instances from the big node into two child nodes. The
glue layer ontop does almost nothing.
This could be two indepentant child nodes but I have no idea how
'ti,hwmods = usb_otg_hs;' affects the two musb controler.
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
Hi Sebastian,
2013/7/5 Sebastian Andrzej Siewior bige...@linutronix.de:
This moves the two instances from the big node into two child nodes. The
glue layer ontop does almost nothing.
This could be two indepentant child nodes but I have no idea how
'ti,hwmods = usb_otg_hs;' affects the two
On 07/05/2013 05:08 PM, Enric Balletbo Serra wrote:
Hi Sebastian,
Hi Enric,
I'm trying to test these patches but I've problems, I've following error,
[ 10.096492] musb-dsps 4740.usb: failed to get memory for instance 0
[ 10.103481] musb-dsps 4740.usb: failed to create child
2013/7/5 Sebastian Andrzej Siewior bige...@linutronix.de:
On 07/05/2013 05:08 PM, Enric Balletbo Serra wrote:
Hi Sebastian,
Hi Enric,
I'm trying to test these patches but I've problems, I've following error,
[ 10.096492] musb-dsps 4740.usb: failed to get memory for instance 0
[
On 07/05/2013 05:22 PM, Enric Balletbo Serra wrote:
Fixed, I didn't update my DT for my custom board properly. Thanks.
Good. I hate breaking the compatibility for DT but unfortunately it is
beyond repair.
Sebastian
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the
