From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Conor Dooley <conor@kernel.org>
Cc: Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Liu Ying <victor.liu@nxp.com>,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/1] dt-bindings: phy: mixel, mipi-dsi-phy: Remove assigned-clock* properties
Date: Thu, 08 Jun 2023 09:31:57 +0200 [thread overview]
Message-ID: <1855461.tdWV9SEqCh@steina-w> (raw)
In-Reply-To: <20230606-implement-canning-0353ca9afddb@spud>
Hi Conor,
Am Dienstag, 6. Juni 2023, 20:21:02 CEST schrieb Conor Dooley:
> * PGP Signed by an unknown key
>
> On Tue, Jun 06, 2023 at 04:44:46PM +0200, Alexander Stein wrote:
> > These properties are allowed anyway and some SoC (e.g. imx8mq) configure
> > more than just one clock using these properties.
>
> What does "allowed anyway" mean?
> And following from that, why not modify the min/maxItems to suit
> reality, rather than remove them. Is there enforcement from elsewhere?
As Liu pointed out, assigned-clock* were considered a generic property added
by default at that time. With that support added there is no need to specify
these properties in this bindings again.
Despite that you never know in advance how many items you will have to add to
assigned-clock* properties, that's totally different to 'clocks', it may even
depend on board specific clock setups.
> > Fixes: f9b0593dd4fc6 ("dt-bindings: phy: Convert mixel,mipi-dsi-phy to
> > json-schema") Signed-off-by: Alexander Stein
> > <alexander.stein@ew.tq-group.com>
> > ---
> > I can't reproduce the mentioned mis-matches in commit f9b0593dd4fc6
> > ("dt-bindings: phy: Convert mixel,mipi-dsi-phy to json-schema").
>
> I suspect that meant that the property was in the dt but not in the
> binding at the time of the conversion.
You are right, given the commit [1]. Which, from today's perspective, is also
a rationale for this patch.
Best regards,
Alexander
[1] https://github.com/devicetree-org/dt-schema/commit/
c3424745f900e8cf0a0e3acebffeeda83a82f6d4
> Cheers,
> Conor.
>
> > Since commit 62270eeb2b639 ("arm64: dts: imx8mq: Add clock parents for
> > mipi dphy") imx8mq.dtsi configures several clocks using assigned-clocks*
> > properties.
> >
> > .../devicetree/bindings/phy/mixel,mipi-dsi-phy.yaml | 9 ---------
> > 1 file changed, 9 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/phy/mixel,mipi-dsi-phy.yaml
> > b/Documentation/devicetree/bindings/phy/mixel,mipi-dsi-phy.yaml index
> > 786cfd71cb7eb..3c28ec50f0979 100644
> > --- a/Documentation/devicetree/bindings/phy/mixel,mipi-dsi-phy.yaml
> > +++ b/Documentation/devicetree/bindings/phy/mixel,mipi-dsi-phy.yaml
> >
> > @@ -32,15 +32,6 @@ properties:
> > clock-names:
> > const: phy_ref
> >
> > - assigned-clocks:
> > - maxItems: 1
> > -
> > - assigned-clock-parents:
> > - maxItems: 1
> > -
> > - assigned-clock-rates:
> > - maxItems: 1
> > -
> >
> > "#phy-cells":
> > const: 0
>
> * Unknown Key
> * 0xA08262D2
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
next prev parent reply other threads:[~2023-06-08 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 14:44 [PATCH 1/1] dt-bindings: phy: mixel,mipi-dsi-phy: Remove assigned-clock* properties Alexander Stein
2023-06-06 18:21 ` Conor Dooley
2023-06-08 7:31 ` Alexander Stein [this message]
2023-06-08 7:59 ` [PATCH 1/1] dt-bindings: phy: mixel, mipi-dsi-phy: " Conor Dooley
2023-06-08 8:07 ` Alexander Stein
2023-06-07 2:45 ` [PATCH 1/1] dt-bindings: phy: mixel,mipi-dsi-phy: " Ying Liu
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=1855461.tdWV9SEqCh@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-phy@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=victor.liu@nxp.com \
--cc=vkoul@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).