public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ismael Luceno Cortes <ismael.luceno@silicon-gears.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] usb: host: Print device name when scanning
Date: Thu, 14 Mar 2019 16:19:43 +0000	[thread overview]
Message-ID: <20190314161943.GD3468@kiki> (raw)
In-Reply-To: <d476b77b-ad04-f017-e6bd-7e8810a5b1e2@gmail.com>

On 14/Mar/2019 16:09, Marek Vasut wrote:
> On 3/14/19 1:57 PM, Ismael Luceno Cortes wrote:
> > On 14/Mar/2019 12:55, Marek Vasut wrote:
> >> On 3/14/19 12:44 PM, Ismael Luceno Cortes wrote:
> >>> On 18/Feb/2019 09:23, Ismael Luceno Cortes wrote:
> >>>> Signed-off-by: Ismael Luceno <ismael.luceno@silicon-gears.com>
> >>>> ---
> >>>>  drivers/usb/host/usb-uclass.c | 2 +-
> >>>>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>>>
> >>>> diff --git a/drivers/usb/host/usb-uclass.c b/drivers/usb/host/usb-uclass.c
> >>>> index 611ea97a72..0575f5393b 100644
> >>>> --- a/drivers/usb/host/usb-uclass.c
> >>>> +++ b/drivers/usb/host/usb-uclass.c
> >>>> @@ -255,7 +255,7 @@ int usb_init(void)
> >>>>  
> >>>>  	uclass_foreach_dev(bus, uc) {
> >>>>  		/* init low_level USB */
> >>>> -		printf("USB%d:   ", count);
> >>>> +		printf("USB%d(%s):   ", count, bus->name);
> >>>>  		count++;
> >>>>  
> >>>>  #ifdef CONFIG_SANDBOX
> >>>> -- 
> >>>> 2.19.1
> >>>
> >>> Ping.
> >>
> >> What is this patch doing ? The commit description doesn't explain
> >> anything about it.
> > 
> > It prints the host device name. I'm not sure the count is at all useful
> > given there's a name...
> 
> If you could share the log before and after to better illustrate the
> difference, that'd be nice.

unpatched:

=> usb reset
resetting USB...
USB0:   USB EHCI 1.10
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found

patched:

=> usb reset
resetting USB...
USB0(usb at ee080100):   USB EHCI 1.10
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found

> However, shouldn't the same approach be applied to 'usb tree' subcommand
> and possibly others ?

The number shown during usb scanning is not used nor saved anywhere
else, so seems pretty useless and a special case.

OTOH the number used in the usb tree command is taken from struct
usb_device, and is used for lookups.

The name is only relevant to non-discoverable devices at the moment.

dm tree shows:
... ehci_generic          |   |-- usb at ee080100
... usb_hub               |   |   `-- usb_hub
... usb_mass_storage      |   |       `-- usb_mass_storage
... usb_storage_blk       |   |           `-- usb_mass_storage.lun0

  reply	other threads:[~2019-03-14 16:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-18  9:23 [U-Boot] [PATCH] usb: host: Print device name when scanning Ismael Luceno Cortes
2019-03-14 11:44 ` Ismael Luceno Cortes
2019-03-14 11:55   ` Marek Vasut
2019-03-14 12:57     ` Ismael Luceno Cortes
2019-03-14 15:09       ` Marek Vasut
2019-03-14 16:19         ` Ismael Luceno Cortes [this message]
2019-03-15 17:34           ` Marek Vasut
2019-03-15 19:50             ` Ismael Luceno Cortes
2019-03-16  1:41               ` Marek Vasut
2019-03-18 12:02                 ` Ismael Luceno Cortes
2019-03-18 12:04                   ` Marek Vasut
  -- strict thread matches above, loose matches on Subject: below --
2019-02-12 14:56 Ismael Luceno Cortes

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=20190314161943.GD3468@kiki \
    --to=ismael.luceno@silicon-gears.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