From: Fabio Estevam <festevam@gmail.com>
To: thierry.reding@gmail.com
Cc: u.kleine-koenig@pengutronix.de,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
robh+dt@kernel.org, linux-pwm@vger.kernel.org,
devicetree@vger.kernel.org, Fabio Estevam <festevam@denx.de>
Subject: [PATCH 3/3] dt-bindings: pwm: mxs: Allow passing #pwm-cells = <2>
Date: Thu, 21 Sep 2023 15:43:48 -0300 [thread overview]
Message-ID: <20230921184348.290261-3-festevam@gmail.com> (raw)
In-Reply-To: <20230921184348.290261-1-festevam@gmail.com>
From: Fabio Estevam <festevam@denx.de>
All the in-tree imx23 and imx28 devicetrees use #pwm-cells = <2>.
Allow it in the schema to avoid warnings.
It is still possible for a devicetree to pass the third cell with the
PWM polarity though.
This is similar to imx-pwm.yaml that allows #pwm-cells to be 2 or 3.
Signed-off-by: Fabio Estevam <festevam@denx.de>
---
Documentation/devicetree/bindings/pwm/mxs-pwm.yaml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/pwm/mxs-pwm.yaml b/Documentation/devicetree/bindings/pwm/mxs-pwm.yaml
index 8f50e23ca8c9..405c6412dd5f 100644
--- a/Documentation/devicetree/bindings/pwm/mxs-pwm.yaml
+++ b/Documentation/devicetree/bindings/pwm/mxs-pwm.yaml
@@ -29,7 +29,9 @@ properties:
maxItems: 1
"#pwm-cells":
- const: 3
+ enum:
+ - 2
+ - 3
fsl,pwm-number:
$ref: /schemas/types.yaml#/definitions/uint32
--
2.34.1
next prev parent reply other threads:[~2023-09-21 18:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 18:43 [PATCH 1/3] dt-bindings: pwm: mxs: Document fsl,imx28-pwm Fabio Estevam
2023-09-21 18:43 ` [PATCH 2/3] dt-bindings: pwm: mxs: Document the clocks property Fabio Estevam
2023-09-21 20:07 ` Uwe Kleine-König
2023-09-22 11:31 ` Conor Dooley
2023-09-21 18:43 ` Fabio Estevam [this message]
2023-09-21 19:59 ` [PATCH 3/3] dt-bindings: pwm: mxs: Allow passing #pwm-cells = <2> Uwe Kleine-König
2023-09-22 21:17 ` Rob Herring
2023-09-21 19:59 ` [PATCH 1/3] dt-bindings: pwm: mxs: Document fsl,imx28-pwm Uwe Kleine-König
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=20230921184348.290261-3-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh+dt@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).