Re: [PATCH 1/2] dt-bindings: pwm: Document Tegra194 and Tegra264 controllers

[Thierry Reding <thierry.reding@kernel.org>]

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

On Sat, Mar 21, 2026 at 11:49:08AM +0100, 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)?

I don't see anything in the documentation about a requirement for driver
patches to be included. It does indicate what the ordering of patches
should be if driver code is included, but doesn't specifically say that
driver code must accompany binding updates.

Nor do I understand why it should be needed. I do understand why you
would want to have driver code to go along with a completely new binding
but in cases like this where we're really only adding a new compatible
string to an otherwise unmodified binding, I don't see any advantage in
having to put both together.

Thierry

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