[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9a1d75a2-66c0-46b6-91a1-4922b892dfb1@kernel.org>
Date: Fri, 28 Feb 2025 10:37:48 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: David Jander <david@...tonic.nl>
Cc: linux-kernel@...r.kernel.org, linux-iio@...r.kernel.org,
Jonathan Corbet <corbet@....net>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, devicetree@...r.kernel.org,
linux-doc@...r.kernel.org, Nuno Sa <nuno.sa@...log.com>,
Jonathan Cameron <jic23@...nel.org>, Oleksij Rempel <o.rempel@...gutronix.de>
Subject: Re: [RFC PATCH 7/7] dt-bindings: motion: Add motion-simple-pwm
bindings
On 28/02/2025 10:22, David Jander wrote:
>
>>> +
>>> + motion,pwm-inverted:
>>> + $ref: /schemas/types.yaml#/definitions/flag
>>
>> And PWM flag does not work?
>
> I have seen PWM controllers that don't seem to support the
> PWM_POLARITY_INVERTED flag and those where it just doesn't work. Should all
Shouldn't the controllers be fixed? Or let's rephrase the question: why
only this PWM consumer needs this property and none of others need it?
Best regards,
Krzysztof
Powered by blists - more mailing lists