From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Francesco Lavra <flavra@baylibre.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Kartik Rajput <kkartik@nvidia.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Robert Marko <robert.marko@sartura.hr>,
Thierry Bultel <thierry.bultel.yh@bp.renesas.com>,
Douglas Anderson <dianders@chromium.org>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH] serial: tegra: remove Kconfig dependency on APB DMA controller
Date: Wed, 26 Nov 2025 13:20:50 +0200 [thread overview]
Message-ID: <aSbikmpzkADKkna6@smile.fi.intel.com> (raw)
In-Reply-To: <20251126090759.4042709-1-flavra@baylibre.com>
On Wed, Nov 26, 2025 at 10:07:59AM +0100, Francesco Lavra wrote:
> This driver runs also on SoCs without a Tegra20 APB DMA controller (e.g.
> Tegra234).
> Remove the Kconfig dependency on TEGRA20_APB_DMA, and remove reference to
> the APB DMA controller from the Kconfig help text.
...
> help
> Support for the on-chip UARTs on the NVIDIA Tegra series SOCs
> providing /dev/ttyTHS0, 1, 2, 3 and 4 (note, some machines may not
> provide all of these ports, depending on how the serial port
> - are enabled). This driver uses the APB DMA to achieve higher baudrate
> - and better performance.
> + are enabled).
I think this removes a good piece of information. Perhaps rephrase?
This driver may use the APB DMA when available to achieve
higher baudrate and better performance.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-11-26 11:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 9:07 [PATCH] serial: tegra: remove Kconfig dependency on APB DMA controller Francesco Lavra
2025-11-26 11:20 ` Andy Shevchenko [this message]
2025-11-26 12:08 ` Francesco Lavra
2025-11-26 16:25 ` Andy Shevchenko
2025-11-26 16:45 ` Francesco Lavra
2025-11-26 17:44 ` Andy Shevchenko
2026-02-25 11:35 ` Francesco Lavra
2026-03-12 13:43 ` Greg Kroah-Hartman
2026-03-13 7:56 ` Francesco Lavra
2026-02-26 10:04 ` Jon Hunter
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=aSbikmpzkADKkna6@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dianders@chromium.org \
--cc=flavra@baylibre.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kkartik@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robert.marko@sartura.hr \
--cc=thierry.bultel.yh@bp.renesas.com \
--cc=wsa+renesas@sang-engineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.