devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Sandipan Patra <spatra@nvidia.com>
Cc: jonathanh@nvidia.com, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	bbasu@nvidia.com, kyarlagadda@nvidia.com
Subject: Re: [PATCH v5 2/3] arm64: tegra: Add PWM controllers on Tegra234
Date: Thu, 3 Nov 2022 12:50:46 +0100	[thread overview]
Message-ID: <Y2OrFj8sLbzaFCgE@orome> (raw)
In-Reply-To: <20220919141455.31084-2-spatra@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 486 bytes --]

On Mon, Sep 19, 2022 at 07:44:54PM +0530, Sandipan Patra wrote:
> Tegra234 has eight single-channel PWM controllers, one of them in the
> AON block.
> 
> Signed-off-by: Sandipan Patra <spatra@nvidia.com>
> ---
> V4->V5: Update compatable with Tegra234 and fallback
> 
>  arch/arm64/boot/dts/nvidia/tegra234.dtsi | 88 +++++++++++++++++++++++-
>  1 file changed, 86 insertions(+), 2 deletions(-)

I've merged this with Jon's changes that also added these.

Thanks,
Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2022-11-03 11:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19 14:14 [PATCH v5 1/3] dt-bindings: pwm: tegra: Document Tegra234 pwm binding Sandipan Patra
2022-09-19 14:14 ` [PATCH v5 2/3] arm64: tegra: Add PWM controllers on Tegra234 Sandipan Patra
2022-09-20 16:00   ` Krzysztof Kozlowski
2022-11-03 11:50   ` Thierry Reding [this message]
2022-09-19 14:14 ` [PATCH v5 3/3] arm64: tegra: Add user PWM support on Jetson Orin Sandipan Patra
2022-11-03 11:53   ` Thierry Reding
2022-09-20 16:00 ` [PATCH v5 1/3] dt-bindings: pwm: tegra: Document Tegra234 pwm binding Krzysztof Kozlowski
2022-11-03 11:49 ` Thierry Reding

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=Y2OrFj8sLbzaFCgE@orome \
    --to=thierry.reding@gmail.com \
    --cc=bbasu@nvidia.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kyarlagadda@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=spatra@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;
as well as URLs for NNTP newsgroup(s).