From: Rob Herring <robh@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: Johan Jonker <jbx6244@gmail.com>,
hjc@rock-chips.com, heiko@sntech.de, andy.yan@rock-chips.com,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
airlied@gmail.com, daniel@ffwll.ch,
maarten.lankhorst@linux.intel.com, tzimmermann@suse.de,
mripard@kernel.org, markyao0591@gmail.com,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/6] dt-bindings: display: rockchip: rockchip,dw-hdmi: deprecate port property
Date: Wed, 31 Jan 2024 08:15:02 -0600 [thread overview]
Message-ID: <20240131141502.GB966672-robh@kernel.org> (raw)
In-Reply-To: <20240130-denim-capacity-e1617595ac9f@spud>
On Tue, Jan 30, 2024 at 06:18:49PM +0000, Conor Dooley wrote:
> On Tue, Jan 30, 2024 at 03:55:43PM +0100, Johan Jonker wrote:
> > The hdmi-connector nodes are now functional and the new way to model
> > hdmi nodes with, so deprecate the port property and
>
> This doesn't really explain what makes having hdmi-connector nodes
> replace the usecase for "port".
>
> > make port@0 and
> > port@1 a requirement.
>
> Why?
That means the deprecated way will always have warnings which makes
documenting the deprecated stuff a bit pointless. Technically, new
required properties are ABI break and something I'm working on making
the tools check (by comparing 2 versions of schemas). That said, if all
the upstream dts files are fixed already, then I don't care too much.
> > Also update example.
>
> "Also do x" is a red flag when it comes to commit messages, as it
> immediately makes me think that this should be more than one commit.
> I'd probably write this as "Update the example to avoid use of the
> deprecated property" or something to avoid bad gut reactions.
> That's not worth resending for though obviously...
>
> >
> > Signed-off-by: Johan Jonker <jbx6244@gmail.com>
> > ---
> > .../display/rockchip/rockchip,dw-hdmi.yaml | 27 ++++++++++++++++---
> > 1 file changed, 23 insertions(+), 4 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/display/rockchip/rockchip,dw-hdmi.yaml b/Documentation/devicetree/bindings/display/rockchip/rockchip,dw-hdmi.yaml
> > index 7e59dee15a5f..cd0a42f35f24 100644
> > --- a/Documentation/devicetree/bindings/display/rockchip/rockchip,dw-hdmi.yaml
> > +++ b/Documentation/devicetree/bindings/display/rockchip/rockchip,dw-hdmi.yaml
> > @@ -97,8 +97,11 @@ properties:
> > ports:
> > $ref: /schemas/graph.yaml#/properties/ports
> >
> > - patternProperties:
> > - "^port(@0)?$":
> > + properties:
> > + port:
> > + $ref: /schemas/graph.yaml#/properties/port
> > + deprecated: true
>
> This change makes the deprecated property's description incomplete,
> since it doesn't cover the endpoints any more. It also doesn't make
> port@0 and port mutually exclusive.
graph.yaml has a check that effectively does that.
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-01-31 14:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 14:55 [PATCH v1 1/6] dt-bindings: display: rockchip: rockchip,dw-hdmi: deprecate port property Johan Jonker
2024-01-30 14:57 ` [PATCH v1 2/6] dt-bindings: display: rockchip,dw-hdmi: add power-domains property Johan Jonker
2024-01-30 18:05 ` Conor Dooley
2024-01-31 13:59 ` Rob Herring
2024-01-30 14:57 ` [PATCH v1 3/6] ARM: dts: rockchip: fix rk3288 hdmi ports node Johan Jonker
2024-01-30 14:57 ` [PATCH v1 4/6] ARM: dts: rockchip: fix rk322x " Johan Jonker
2024-01-30 14:58 ` [PATCH v1 5/6] arm64: dts: rockchip: fix rk3328 " Johan Jonker
2024-01-30 14:58 ` [PATCH v1 6/6] arm64: dts: rockchip: fix rk3399 " Johan Jonker
2024-01-30 18:18 ` [PATCH v1 1/6] dt-bindings: display: rockchip: rockchip,dw-hdmi: deprecate port property Conor Dooley
2024-01-31 14:15 ` Rob Herring [this message]
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=20240131141502.GB966672-robh@kernel.org \
--to=robh@kernel.org \
--cc=airlied@gmail.com \
--cc=andy.yan@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=jbx6244@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=markyao0591@gmail.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.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).