From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Marek Vasut <marex@denx.de>
Cc: Tom Rini <trini@konsulko.com>,
u-boot@lists.denx.de, Kevin Hilman <khilman@baylibre.com>,
Lukasz Majewski <lukma@denx.de>, Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH v4 1/4] cmd: bind: Add unbind command with driver filter
Date: Fri, 4 Aug 2023 19:24:09 +0200 [thread overview]
Message-ID: <20230804192409.45e650f8@xps-13> (raw)
In-Reply-To: <0eb7f3fe-42da-6252-3b77-50eb3276f2ee@denx.de>
Hi Marek,
marex@denx.de wrote on Fri, 4 Aug 2023 17:40:07 +0200:
> On 8/4/23 17:12, Miquel Raynal wrote:
> > Hi,
> >
> > marex@denx.de wrote on Fri, 4 Aug 2023 17:05:01 +0200:
> >
> >> On 8/4/23 17:01, Tom Rini wrote:
> >>> On Fri, Aug 04, 2023 at 04:42:13PM +0200, Marek Vasut wrote:
> >>>> On 8/4/23 09:00, Miquel Raynal wrote:
> >>>>> Hi Marek,
> >>>>>
> >>>>> marex@denx.de wrote on Wed, 2 Aug 2023 14:46:54 +0200:
> >>>>> >>>>>> Extend the driver core to perform lookup by both OF node and driver
> >>>>>> bound to the node. Use this to look up specific device instances to
> >>>>>> unbind from nodes in the unbind command. One example where this is
> >>>>>> needed is USB peripheral controller, which may have multiple gadget
> >>>>>> drivers bound to it. The unbind command has to select that specific
> >>>>>> gadget driver instance to unbind from the controller, not unbind the
> >>>>>> controller driver itself from the controller.
> >>>>>>
> >>>>>> USB ethernet gadget usage looks as follows with this change. Notice
> >>>>>> the extra 'usb_ether' addition in the 'unbind' command at the end.
> >>>>>> "
> >>>>>> bind /soc/usb-otg@49000000 usb_ether
> >>>>>> setenv ethact usb_ether
> >>>>>> setenv loadaddr 0xc2000000
> >>>>>> setenv ipaddr 10.0.0.2
> >>>>>> setenv serverip 10.0.0.1
> >>>>>> setenv netmask 255.255.255.0
> >>>>>> tftpboot 0xc2000000 10.0.0.1:test.file
> >>>>>> unbind /soc/usb-otg@49000000 usb_ether
> >>>>>
> >>>>> This extra parameter does not seem to work on the BBBW. I cannot select
> >>>>> the "usb_ether" driver like you do.
> >>>>>
> >>>>> Good news though, I am now able to use fastboot, but it is not
> >>>>> straightforward:
> >>>>>
> >>>>> Here is my sequence right after the boot (reducing the dm tree output
> >>>>> to the usb nodes for clarity):
> >>>>> >>>>> => dm tree
> >>>>> misc 0 [ + ] ti-musb-wrapper | |-- usb@47400000
> >>>>> usb 0 [ + ] ti-musb-peripheral | | |-- usb@47401000
> >>>>> ethernet 1 [ + ] usb_ether | | | `-- usb_ether
> >>>>> bootdev 3 [ ] eth_bootdev | | | `-- usb_ether.bootdev
> >>>>> usb 0 [ ] ti-musb-host | | `-- usb@47401800
> >>>>> => fastboot usb 0
> >>>>> couldn't find an available UDC
> >>>>> g_dnl_register: failed!, error: -19
> >>>>
> >>>> That is expected and not a bug, since the beagle explicitly binds USB
> >>>> ethernet to MUSB gadget in board file, which is legacy deprecated way.
> >>>
> >>> So, we should do away with, probably all of arch_misc_init() in
> >>> arch/arm/mach-omap2/am33xx/board.c for the non-SPL case.
> >>
> >> Yes
> >>
> >>>>> exit not allowed from main input shell.
> >>>>> => unbind /ocp/usb@47400000/usb@47401000 usb_ether
> >>>>
> >>>> Does
> >>>> >>>> => unbind ethernet 0
> >>>>
> >>>> work ?
> >>>>
> >>>> If so, 1/4 in this series can be skipped altogether.
> >>>>
> >>>> You likely won't even need the rebinding of ti-musb-peripheral anymore.
>
> Did you test this yet ?
Unfortunately it does not work. Indeed it would be much simpler than
using the node path. Any idea why?
Thanks,
Miquèl
next prev parent reply other threads:[~2023-08-04 17:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 12:46 [PATCH v4 1/4] cmd: bind: Add unbind command with driver filter Marek Vasut
2023-08-02 12:46 ` [PATCH v4 2/4] usb: gadget: ether: Inline functions used once Marek Vasut
2023-08-02 12:46 ` [PATCH v4 3/4] usb: gadget: ether: Move probe function above driver structure Marek Vasut
2023-08-02 12:46 ` [PATCH v4 4/4] usb: gadget: ether: Handle gadget driver registration in probe and remove Marek Vasut
2023-08-02 21:31 ` [PATCH v4 1/4] cmd: bind: Add unbind command with driver filter Simon Glass
2023-08-02 22:04 ` Marek Vasut
2023-08-04 7:00 ` Miquel Raynal
2023-08-04 14:42 ` Marek Vasut
2023-08-04 15:01 ` Tom Rini
2023-08-04 15:05 ` Marek Vasut
2023-08-04 15:12 ` Miquel Raynal
2023-08-04 15:40 ` Marek Vasut
2023-08-04 16:00 ` Miquel Raynal
2023-08-04 16:15 ` Tom Rini
2023-08-04 17:01 ` Miquel Raynal
2023-08-04 17:18 ` Marek Vasut
2023-08-04 17:20 ` Tom Rini
2023-08-04 18:01 ` Miquel Raynal
2023-08-04 18:51 ` Tom Rini
2023-08-04 19:38 ` Miquel Raynal
2023-08-04 16:37 ` Tom Rini
2023-08-04 17:04 ` Miquel Raynal
2023-08-04 17:19 ` Marek Vasut
2023-08-04 17:23 ` Tom Rini
2023-08-04 17:24 ` Miquel Raynal [this message]
2023-08-04 17:31 ` Marek Vasut
2023-08-04 17:46 ` Miquel Raynal
2023-08-04 17:54 ` Marek Vasut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230804192409.45e650f8@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=khilman@baylibre.com \
--cc=lukma@denx.de \
--cc=marex@denx.de \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox