From: Corey Minyard <corey@minyard.net>
To: Adrian Ambrozewicz <aambrozewicz@nvidia.com>
Cc: Donald Shannon <donalds@nvidia.com>,
linux-kernel@vger.kernel.org,
openipmi-developer@lists.sourceforge.net,
linux-usb@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Quan Nguyen <quan@os.amperecomputing.com>,
Andrew Jeffery <andrew@codeconstruct.com.au>
Subject: Re: [PATCH 11/11] ipmi: Add NVIDIA LSTP IPMI BMC driver
Date: Fri, 16 Oct 2026 07:26:53 -0500 [thread overview]
Message-ID: <atIYDWk8CNlWOUZk@mail.minyard.net> (raw)
In-Reply-To: <20261016081917.1958681-2-aambrozewicz@nvidia.com>
On Fri, Oct 16, 2026 at 11:19:14AM +0300, Adrian Ambrozewicz wrote:
> Hi Corey,
>
> Thanks for the review.
>
> On Mon, Oct 12, 2026 at 04:10:32PM -0500, Corey Minyard wrote:
> > Can you name the file usb_lstp.c, or something like that, to match
> > the other BMC side devices?
>
> Sure. Would lstp_bmc.c work, next to ssif_bmc.c and kcs_bmc.c?
> Otherwise usb_lstp.c it is.
Either name works. Just want it to be consistent, and your suggestion
is better than mine.
>
> >> +static DEFINE_IDA(lstp_ipmi_ida);
> >
> > Wouldn't you want to assign the numbers in the device tree so they
> > always have the same number?
>
> I'd rather keep them out of DT. The binding rules ask not to add
> instance index properties or custom aliases
> (Documentation/devicetree/bindings/writing-bindings.rst): DT describes
> the hardware, not how Linux numbers its device nodes. Our out-of-tree
> driver used to take the node name from a "label" property, and we
> dropped it for that reason.
>
> A stable name comes from udev instead. The node's parent is the
> channel's auxiliary device under the USB device, so a rule matching the
> USB port path and the channel can add a symlink with whatever name the
> BMC userspace expects.
Yes, that's the right way to do this, since udev has something to
differentiate the device.
>
> > It seems a little strange to set this up here and then register it in
> > the next section. Why not set it up right before the register?
> >
> > The breakup of the probe function seems a little unnatural. Not a
> > bit deal, but it makes the code a little harder to follow.
>
> Agreed. The next version fills in the miscdevice right before
> misc_register() and folds the init and start helpers into one probe
> function.
Going a little higher level, I'm wondering if there is any advantage to
having this in the kernel. Since it's USB you could do this all in
userland. There's no kernel subsystem that this would tie in to.
I suppose the big advantage is it looks like the other BMC interfaces.
But you can maintain it more easily if it's in userland. I don't know a
lot about USB, though, and how all that works. Just something to
think about, perhaps.
-corey
>
> Thanks,
> Adrian
next prev parent reply other threads:[~2026-10-16 12:27 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 17:35 [PATCH 00/11] Add NVIDIA LSTP USB adapter drivers Adrian Ambrozewicz
2026-10-12 17:35 ` [PATCH 01/11] dt-bindings: gpio: Add NVIDIA LSTP GPIO Adrian Ambrozewicz
2026-10-12 17:43 ` sashiko-bot
2026-10-16 9:28 ` Adrian Ambrozewicz
2026-10-13 6:09 ` Krzysztof Kozlowski
2026-10-16 8:44 ` Adrian Ambrozewicz
2026-10-12 17:36 ` [PATCH 02/11] dt-bindings: i2c: Add NVIDIA LSTP I2C Adrian Ambrozewicz
2026-10-12 17:41 ` sashiko-bot
2026-10-16 9:28 ` Adrian Ambrozewicz
2026-10-13 6:11 ` Krzysztof Kozlowski
2026-10-12 17:36 ` [PATCH 03/11] dt-bindings: spi: Add NVIDIA LSTP SPI Adrian Ambrozewicz
2026-10-12 17:46 ` sashiko-bot
2026-10-13 6:11 ` Krzysztof Kozlowski
2026-10-12 17:36 ` [PATCH 04/11] dt-bindings: usb: Add NVIDIA LSTP USB adapter Adrian Ambrozewicz
2026-10-12 17:47 ` sashiko-bot
2026-10-16 9:28 ` Adrian Ambrozewicz
2026-10-13 6:13 ` Krzysztof Kozlowski
2026-10-13 6:17 ` Krzysztof Kozlowski
2026-10-12 17:36 ` [PATCH 05/11] usb: misc: Add NVIDIA LSTP USB adapter driver Adrian Ambrozewicz
2026-10-12 17:51 ` sashiko-bot
2026-10-16 9:28 ` Adrian Ambrozewicz
2026-10-12 17:36 ` [PATCH 06/11] gpio: Add NVIDIA LSTP GPIO driver Adrian Ambrozewicz
2026-10-12 17:53 ` sashiko-bot
2026-10-16 9:28 ` Adrian Ambrozewicz
2026-10-13 23:25 ` Linus Walleij
2026-10-16 8:19 ` Adrian Ambrozewicz
2026-10-12 17:36 ` [PATCH 07/11] leds: Add NVIDIA LSTP LED driver Adrian Ambrozewicz
2026-10-12 17:46 ` sashiko-bot
2026-10-16 9:28 ` Adrian Ambrozewicz
2026-10-12 17:36 ` [PATCH 08/11] i2c: Add NVIDIA LSTP I2C driver Adrian Ambrozewicz
2026-10-12 17:49 ` sashiko-bot
2026-10-12 17:36 ` [PATCH 09/11] spi: Add NVIDIA LSTP SPI driver Adrian Ambrozewicz
2026-10-12 17:45 ` sashiko-bot
2026-10-16 9:28 ` Adrian Ambrozewicz
2026-10-12 17:36 ` [PATCH 10/11] tty: Add NVIDIA LSTP UART driver Adrian Ambrozewicz
2026-10-12 17:50 ` sashiko-bot
2026-10-16 9:28 ` Adrian Ambrozewicz
2026-10-13 5:49 ` Jiri Slaby
2026-10-16 8:19 ` Adrian Ambrozewicz
2026-10-15 1:25 ` kernel test robot
2026-10-16 7:43 ` kernel test robot
2026-10-12 17:36 ` [PATCH 11/11] ipmi: Add NVIDIA LSTP IPMI BMC driver Adrian Ambrozewicz
2026-10-12 17:51 ` sashiko-bot
2026-10-16 9:28 ` Adrian Ambrozewicz
2026-10-12 21:10 ` Corey Minyard
2026-10-16 8:19 ` Adrian Ambrozewicz
2026-10-16 12:26 ` Corey Minyard [this message]
2026-10-13 11:37 ` [PATCH 00/11] Add NVIDIA LSTP USB adapter drivers Greg Kroah-Hartman
2026-10-16 8:44 ` Adrian Ambrozewicz
2026-10-13 11:39 ` Greg Kroah-Hartman
2026-10-14 3:38 ` Jeremy Kerr
2026-10-14 4:53 ` Greg Kroah-Hartman
2026-10-16 8:19 ` Adrian Ambrozewicz
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=atIYDWk8CNlWOUZk@mail.minyard.net \
--to=corey@minyard.net \
--cc=aambrozewicz@nvidia.com \
--cc=andrew@codeconstruct.com.au \
--cc=donalds@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=quan@os.amperecomputing.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