From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Matt Ranostay <mranostay@ti.com>
Cc: <lee@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: mfd: ti,am3359-tscadc: change clock-names property to enum
Date: Mon, 24 Oct 2022 13:34:20 +0200 [thread overview]
Message-ID: <20221024133420.72c2d8ed@xps-13> (raw)
In-Reply-To: <20221024100706.386286-1-mranostay@ti.com>
Hi Matt,
mranostay@ti.com wrote on Mon, 24 Oct 2022 03:07:06 -0700:
> Several J7 platforms use adc_tsc_fck instead of fck for clock naming. To
> avoid warnings from dt-schema on invalid clock naming; create an enum with
> both fck, and adc_tsc_fck options.
Looks like I've missed this definition when introducing the bindings.
But in practice this property looks very k3 specific and is not used
anywhere else so would it be worth considering renaming the properties
in the DT instead? There won't be any backward compatibility issue
apparently.
> Signed-off-by: Matt Ranostay <mranostay@ti.com>
> ---
> Documentation/devicetree/bindings/mfd/ti,am3359-tscadc.yaml | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/mfd/ti,am3359-tscadc.yaml b/Documentation/devicetree/bindings/mfd/ti,am3359-tscadc.yaml
> index 34bf6a01436f..fbb44531ed88 100644
> --- a/Documentation/devicetree/bindings/mfd/ti,am3359-tscadc.yaml
> +++ b/Documentation/devicetree/bindings/mfd/ti,am3359-tscadc.yaml
> @@ -28,7 +28,9 @@ properties:
> maxItems: 1
>
> clock-names:
> - const: fck
> + enum:
> + - fck
> + - adc_tsc_fck
>
> dmas:
> items:
Thanks,
Miquèl
next prev parent reply other threads:[~2022-10-24 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 10:07 [PATCH] dt-bindings: mfd: ti,am3359-tscadc: change clock-names property to enum Matt Ranostay
2022-10-24 11:34 ` Miquel Raynal [this message]
2022-10-24 12:36 ` Matt Ranostay
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=20221024133420.72c2d8ed@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=mranostay@ti.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).