From: Alan Stern <stern@rowland.harvard.edu>
To: Mihai Sain <mihai.sain@microchip.com>
Cc: gregkh@linuxfoundation.org, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com, claudiu.beznea@tuxon.dev,
linux-usb@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: ohci-at91: Use dynamic device name for OHCI HCD creation
Date: Wed, 11 Jun 2025 10:08:41 -0400 [thread overview]
Message-ID: <afaf4c79-ccec-46ad-889c-e8347454c065@rowland.harvard.edu> (raw)
In-Reply-To: <20250611075414.4239-2-mihai.sain@microchip.com>
On Wed, Jun 11, 2025 at 10:54:15AM +0300, Mihai Sain wrote:
> Use the dynamic device name instead of the hardcoded string "at91"
> when creating the OHCI host controller driver.
> This ensures that the device name is more flexible
> and correctly reflects the actual device in the system.
> This will be in sync with ehci at91 driver.
>
> [root@sam9x75eb ~]$ dmesg | grep usb
> [ 1.464487] usb usb1: Manufacturer: Linux 6.16.0-rc1 ehci_hcd
> [ 1.470210] usb usb1: SerialNumber: 700000.usb-ehci
> [ 1.595683] usb usb2: Manufacturer: Linux 6.16.0-rc1 ohci_hcd
> [ 1.601406] usb usb2: SerialNumber: 600000.usb-ohci
>
> [root@sam9x75eb ~]$ cat /proc/iomem | grep usb
> 00600000-006fffff : 600000.usb-ohci usb-ohci@600000
> 00700000-007fffff : 700000.usb-ehci usb-ehci@700000
Are these two outputs supposed to make some sort of point? It would be
better to have a before-and-after comparison, so we can see what the
effect of the patch is.
Alan Stern
next prev parent reply other threads:[~2025-06-11 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 7:54 Mihai Sain
2025-06-11 14:08 ` Alan Stern [this message]
[not found] ` <PH3PPF37F43E35DF7E5350AEBBB079073748274A@PH3PPF37F43E35D.namprd11.prod.outlook.com>
2025-06-12 16:32 ` Alan Stern
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=afaf4c79-ccec-46ad-889c-e8347454c065@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mihai.sain@microchip.com \
--cc=nicolas.ferre@microchip.com \
/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
all inboxes | Powered by JetHome®