From: Mikko Perttunen <mperttunen@nvidia.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Thierry Reding <thierry.reding@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jon Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: pwm: Document Tegra194 and Tegra264 controllers
Date: Wed, 25 Mar 2026 10:13:44 +0900 [thread overview]
Message-ID: <9168919.NyiUUSuA9g@senjougahara> (raw)
In-Reply-To: <acJLwYEfJVX4MseT@orome>
On Tuesday, March 24, 2026 5:32 PM Thierry Reding wrote:
> On Tue, Mar 24, 2026 at 08:02:04AM +0100, Krzysztof Kozlowski wrote:
> > On 24/03/2026 05:24, Mikko Perttunen wrote:
> > > On Monday, March 23, 2026 4:23 PM Krzysztof Kozlowski wrote:
> > >> On 23/03/2026 03:45, Mikko Perttunen wrote:
> > >>> On Saturday, March 21, 2026 7:49 PM Krzysztof Kozlowski wrote:
> > >>>> On Sat, Mar 21, 2026 at 12:40:55AM +0100, Thierry Reding wrote:
> > >>>>> From: Thierry Reding <treding@nvidia.com>
> > >>>>>
> > >>>>> The PWM controller found on Tegra264 is largely compatible with the
> > >>>>> one
> > >>>>> on prior generations, but it comes with some extra features, hence a
> > >>>>> new
> > >>>>> compatible string is needed.
> > >>>>>
> > >>>>> Signed-off-by: Thierry Reding <treding@nvidia.com>
> > >>>>> ---
> > >>>>>
> > >>>>> Documentation/devicetree/bindings/pwm/nvidia,tegra20-pwm.yaml | 2
> > >>>>> ++
> > >>>>> 1 file changed, 2 insertions(+)
> > >>>>
> > >>>> Where is the driver patch? Why this is not being part of driver
> > >>>> submission (see also submitting bindings DT in description how
> > >>>> patches
> > >>>> should be sent)?
> > >>>>
> > >>>> Best regards,
> > >>>> Krzysztof
> > >>>
> > >>> Just posted:
> > >>> https://lore.kernel.org/linux-tegra/20260323-t264-pwm-v1-0-4c4ff743050
> > >>> f@n
> > >>> vidia.com/T/#mfb40392e07d7ac9cedbaf853442eed822da7671e
> > >>
> > >> so this is completely misplaced. Please read submitting patches in DT
> > >> dir and follow standard style of sending patches upstream. Just like
> > >> every other contributor. You don't get any exceptions here.
> > >
> > > You asked to see patches, so I thought I'd be helpful and clean up my
> > > work in progress and respond. I'm not looking for any exceptions.
> > > Please do not make such accusations.
> >
> > I asked where are the patches. The non-existing cover letter of this
> > patchset explained nothing in this regard. After my question where are
> > the patches, you sent them without explanation why, so don't assume I
> > can read your intentions that you posted them just so I can see the
> > patches and you do not intend to merge them.
>
> Alright, alright. I'll take the blame for this. I should've coordinated
> better with Mikko and made my intentions clearer in the cover letter.
> Let's move forward by integrating both series.
>
> Mikko, can you please integrate the DT bindings and DT patches into your
> driver series?
Will do.
Mikko
>
> Thanks,
> Thierry
next prev parent reply other threads:[~2026-03-25 1:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 23:40 [PATCH 1/2] dt-bindings: pwm: Document Tegra194 and Tegra264 controllers Thierry Reding
2026-03-20 23:40 ` [PATCH 2/2] arm64: tegra: Add PWM controllers on Tegra264 Thierry Reding
2026-03-21 10:47 ` [PATCH 1/2] dt-bindings: pwm: Document Tegra194 and Tegra264 controllers Krzysztof Kozlowski
2026-03-23 14:45 ` Thierry Reding
2026-03-23 15:00 ` Krzysztof Kozlowski
2026-03-24 8:30 ` Thierry Reding
2026-03-21 10:49 ` Krzysztof Kozlowski
2026-03-23 2:45 ` Mikko Perttunen
2026-03-23 7:23 ` Krzysztof Kozlowski
2026-03-24 4:24 ` Mikko Perttunen
2026-03-24 7:02 ` Krzysztof Kozlowski
2026-03-24 8:32 ` Thierry Reding
2026-03-25 1:13 ` Mikko Perttunen [this message]
2026-03-23 14:50 ` Thierry Reding
2026-03-23 15:04 ` Krzysztof Kozlowski
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=9168919.NyiUUSuA9g@senjougahara \
--to=mperttunen@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@kernel.org \
/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