From: Jon Hunter <jonathanh@nvidia.com>
To: "Mikko Perttunen" <mperttunen@nvidia.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Uwe Kleine-König" <ukleinek@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: linux-pwm@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Thierry Reding <treding@nvidia.com>,
Yi-Wei Wang <yiweiw@nvidia.com>
Subject: Re: [PATCH v5 0/7] Tegra264 PWM support
Date: Tue, 2 Jun 2026 10:16:26 +0100 [thread overview]
Message-ID: <e7b0d66e-ef2f-47d8-8844-38ae63eaf7fb@nvidia.com> (raw)
In-Reply-To: <20260529-t264-pwm-v5-0-7bf9e405a96a@nvidia.com>
On 29/05/2026 03:47, Mikko Perttunen wrote:
> Hello,
>
> this adds support for the PWM controller on Tegra264. The controller
> is similar to previous generations, but the register fields are
> widened, the depth is made configurable, and the enable bit moves
> to a different spot.
>
> This series adds only basic support with fixed depth -- configurable
> depth will come later.
>
> Patch 1 adds device tree bindings for Tegra264 PWM (compatible
> string).
>
> Patch 2 prefixes driver-local macros and static helpers with
> tegra_/TEGRA_ to make their scoping clear.
>
> Patches 3 to 6 contain the PWM driver changes for Tegra264.
>
> Patch 7 adds device tree nodes for the PWM controllers on Tegra264.
...
> Mikko Perttunen (4):
> pwm: tegra: Prefix driver-local macros and functions
> pwm: tegra: Modify read/write accessors for multi-register channel
> pwm: tegra: Parametrize duty and scale field widths
> pwm: tegra: Add support for Tegra264
>
> Thierry Reding (2):
> dt-bindings: pwm: Document Tegra264 controller
> arm64: tegra: Add PWM controllers on Tegra264
>
> Yi-Wei Wang (1):
> pwm: tegra: Avoid hard-coded max clock frequency
>
> .../bindings/pwm/nvidia,tegra20-pwm.yaml | 1 +
> arch/arm64/boot/dts/nvidia/tegra264.dtsi | 72 ++++++++++
> drivers/pwm/pwm-tegra.c | 155 ++++++++++++++-------
> 3 files changed, 176 insertions(+), 52 deletions(-)
For the series ...
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Uwe, if you are OK with the version, we would like to get this into -next.
Thanks!
Jon
--
nvpublic
prev parent reply other threads:[~2026-06-02 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 2:47 [PATCH v5 0/7] Tegra264 PWM support Mikko Perttunen
2026-05-29 2:47 ` [PATCH v5 1/7] dt-bindings: pwm: Document Tegra264 controller Mikko Perttunen
2026-05-29 2:47 ` [PATCH v5 2/7] pwm: tegra: Prefix driver-local macros and functions Mikko Perttunen
2026-05-29 2:47 ` [PATCH v5 3/7] pwm: tegra: Avoid hard-coded max clock frequency Mikko Perttunen
2026-05-29 2:47 ` [PATCH v5 4/7] pwm: tegra: Modify read/write accessors for multi-register channel Mikko Perttunen
2026-05-29 2:47 ` [PATCH v5 5/7] pwm: tegra: Parametrize duty and scale field widths Mikko Perttunen
2026-05-29 2:47 ` [PATCH v5 6/7] pwm: tegra: Add support for Tegra264 Mikko Perttunen
2026-05-29 2:47 ` [PATCH v5 7/7] arm64: tegra: Add PWM controllers on Tegra264 Mikko Perttunen
2026-06-02 9:16 ` Jon Hunter [this message]
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=e7b0d66e-ef2f-47d8-8844-38ae63eaf7fb@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=treding@nvidia.com \
--cc=ukleinek@kernel.org \
--cc=yiweiw@nvidia.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