From: Adrian Ambrozewicz <aambrozewicz@nvidia.com>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Donald Shannon" <donalds@nvidia.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-usb@vger.kernel.org, llvm@lists.linux.dev,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Johan Hovold" <johan@kernel.org>,
"Oliver Neukum" <oneukum@suse.com>
Subject: Re: [PATCH 10/11] tty: Add NVIDIA LSTP UART driver
Date: Fri, 16 Oct 2026 11:19:15 +0300 [thread overview]
Message-ID: <20261016081917.1958681-3-aambrozewicz@nvidia.com> (raw)
In-Reply-To: <558332ed-b93e-4f0d-abb0-942ca63b0cd6@kernel.org>
Hi Jiri,
Thanks for the review.
On 13. 10. 26, 7:49, Jiri Slaby wrote:
>> +static speed_t lstp_baud_to_speed(u32 baud)
>
> Maybe implement this in drivers/tty/tty_baudrate.c on the top of
> baud_table + baud_bits?
tty_termios_encode_baud_rate() already does that lookup on those
tables, including the sparc variant the kernel test robot tripped over
on this patch, and falls back to BOTHER for a rate without a Bxxx
constant (the posted code turns such a rate into B0). So rather than a
new helper, the next version keeps a struct ktermios for the line
settings the device reports and sets its speed with
tty_termios_encode_baud_rate(). Does that work for you, or would you
prefer a helper in tty_baudrate.c that returns only the Bxxx bits?
>> + dev_info(ch->dev, "%s: ch_%d: Started as %s\n", __func__, ch->ch_id, ch->display_name);
>
> We usually print nothing in case everything went well.
Will drop it, here and in the other LSTP drivers.
>> + tty_vhangup(tty);
>> + tty_kref_put(tty);
>
> tty_port_tty_vhangup()?
Yes, will use it.
Thanks,
Adrian
next prev parent reply other threads:[~2026-10-16 8:19 UTC|newest]
Thread overview: 34+ 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-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-13 6:11 ` Krzysztof Kozlowski
2026-10-12 17:36 ` [PATCH 03/11] dt-bindings: spi: Add NVIDIA LSTP SPI Adrian Ambrozewicz
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-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:36 ` [PATCH 06/11] gpio: Add NVIDIA LSTP GPIO driver Adrian Ambrozewicz
2026-10-13 23:25 ` Linus Walleij
2026-10-16 8:19 ` Adrian Ambrozewicz
2026-10-16 21:14 ` Linus Walleij
2026-10-12 17:36 ` [PATCH 07/11] leds: Add NVIDIA LSTP LED driver Adrian Ambrozewicz
2026-10-12 17:36 ` [PATCH 08/11] i2c: Add NVIDIA LSTP I2C driver Adrian Ambrozewicz
2026-10-12 17:36 ` [PATCH 09/11] spi: Add NVIDIA LSTP SPI driver Adrian Ambrozewicz
2026-10-12 17:36 ` [PATCH 10/11] tty: Add NVIDIA LSTP UART driver Adrian Ambrozewicz
2026-10-13 5:49 ` Jiri Slaby
2026-10-16 8:19 ` Adrian Ambrozewicz [this message]
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 21:10 ` Corey Minyard
2026-10-16 8:19 ` Adrian Ambrozewicz
2026-10-16 12:26 ` Corey Minyard
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=20261016081917.1958681-3-aambrozewicz@nvidia.com \
--to=aambrozewicz@nvidia.com \
--cc=donalds@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=johan@kernel.org \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=oneukum@suse.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®