Re: [PATCH v6 0/7] Tegra264 PWM support

Jon Hunter <[email protected]>
Newsgroups org.kernel.vger.linux-pwm,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel,org.kernel.vger.linux-tegra
Message-ID <[email protected]>
On 01/07/2026 04:20, 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.
> 
> Thanks,
> Mikko

...

> 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                            | 160 ++++++++++++++-------
>   3 files changed, 181 insertions(+), 52 deletions(-)
> ---
> base-commit: 8cd9520d35a6c38db6567e97dd93b1f11f185dc6
> change-id: 20260303-t264-pwm-57e10d039df1
> 

For the series ...

Tested-by: Jon Hunter <[email protected]>
Reviewed-by: Jon Hunter <[email protected]>

Thanks
Jon

-- 
nvpublic
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.