From: Rob Herring <robh@kernel.org>
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: linux-kernel@vger.kernel.org,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"open list:PWM SUBSYSTEM" <linux-pwm@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list:BROADCOM BCM7XXX ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
justin.chen@broadcom.com
Subject: Re: [PATCH 1/2] dt-bindings: pwm: brcm,bcm7038: Document the 'open-drain' property
Date: Tue, 15 Oct 2024 11:32:00 -0500 [thread overview]
Message-ID: <20241015163200.GA1220909-robh@kernel.org> (raw)
In-Reply-To: <20241012025603.1644451-2-florian.fainelli@broadcom.com>
On Fri, Oct 11, 2024 at 07:56:02PM -0700, Florian Fainelli wrote:
> Document the 'open-drain' property that allows configuring the PWM
> controller outputs in open drain versus totem pole.
>
> Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com>
> ---
> Documentation/devicetree/bindings/pwm/brcm,bcm7038-pwm.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/pwm/brcm,bcm7038-pwm.yaml b/Documentation/devicetree/bindings/pwm/brcm,bcm7038-pwm.yaml
> index 119de3d7f9dd..12851c43a612 100644
> --- a/Documentation/devicetree/bindings/pwm/brcm,bcm7038-pwm.yaml
> +++ b/Documentation/devicetree/bindings/pwm/brcm,bcm7038-pwm.yaml
> @@ -25,6 +25,12 @@ properties:
> clocks:
> maxItems: 1
>
> + open-drain:
> + type: boolean
> + description:
> + Configure the outputs with open-drain structure, if omitted totem pole
> + structure is used.
> +
There's one other PWM with 'open-drain' so move the definition to
pwm.yaml.
Alternatively, 'drive-open-drain' is a much more commonly used
variation.
Another thing to consider is for any PWM controller with more than
1 output, you might want this to be per output and therefore should be
a flag in the cells.
Rob
next prev parent reply other threads:[~2024-10-15 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 2:56 [PATCH 0/2] pwm: brcmstb: Support configurable open-drain mode Florian Fainelli
2024-10-12 2:56 ` [PATCH 1/2] dt-bindings: pwm: brcm,bcm7038: Document the 'open-drain' property Florian Fainelli
2024-10-15 16:32 ` Rob Herring [this message]
2024-10-15 17:07 ` Florian Fainelli
2024-10-29 10:44 ` Uwe Kleine-König
2024-10-29 16:03 ` Florian Fainelli
2024-11-28 11:35 ` Uwe Kleine-König
2024-10-12 2:56 ` [PATCH 2/2] pwm: brcmstb: Do not assume open drain configuration Florian Fainelli
2024-10-14 20:05 ` [PATCH 0/2] pwm: brcmstb: Support configurable open-drain mode Uwe Kleine-König
2024-10-16 7:09 ` 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=20241015163200.GA1220909-robh@kernel.org \
--to=robh@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=justin.chen@broadcom.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).