From: Rob Herring <robh@kernel.org>
To: Johan Jonker <jbx6244@gmail.com>
Cc: tzimmermann@suse.de, markyao0591@gmail.com,
andy.yan@rock-chips.com, dri-devel@lists.freedesktop.org,
conor+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
mripard@kernel.org, devicetree@vger.kernel.org,
airlied@gmail.com, heiko@sntech.de,
maarten.lankhorst@linux.intel.com, daniel@ffwll.ch,
hjc@rock-chips.com, linux-arm-kernel@lists.infradead.org,
robh+dt@kernel.org, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/6] dt-bindings: display: rockchip: rockchip,dw-hdmi: remove port property
Date: Thu, 1 Feb 2024 16:58:37 -0600 [thread overview]
Message-ID: <170682831660.1899746.18090191904658752173.robh@kernel.org> (raw)
In-Reply-To: <a493c65e-7cf9-455f-95d5-8c98cad35710@gmail.com>
On Wed, 31 Jan 2024 22:14:29 +0100, Johan Jonker wrote:
> The hdmi-connector nodes are now functional and the new way to model
> hdmi ports nodes with both in and output port subnodes. Unfortunately
> with the conversion to YAML the old method with only an input port node
> was used. Later the new method was also added to the binding.
> A binding must be unambiguously, so remove the old port property
> entirely and make port@0 and port@1 a requirement as all
> upstream dts files are updated as well and because checking
> deprecated stuff is a bit pointless.
> Update the example to avoid use of the removed property.
>
> Signed-off-by: Johan Jonker <jbx6244@gmail.com>
> ---
>
> Changed V2:
> rename title from deprecate to remove
> reword
> ---
> .../display/rockchip/rockchip,dw-hdmi.yaml | 24 +++++++++++++++----
> 1 file changed, 20 insertions(+), 4 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-02-01 22:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 21:14 [PATCH v2 1/6] dt-bindings: display: rockchip: rockchip,dw-hdmi: remove port property Johan Jonker
2024-01-31 21:16 ` [PATCH v2 2/6] dt-bindings: display: rockchip,dw-hdmi: add power-domains property Johan Jonker
2024-01-31 21:16 ` [PATCH v2 3/6] ARM: dts: rockchip: fix rk3288 hdmi ports node Johan Jonker
2024-01-31 21:16 ` [PATCH v2 4/6] ARM: dts: rockchip: fix rk322x " Johan Jonker
2024-01-31 21:17 ` [PATCH v2 5/6] arm64: dts: rockchip: fix rk3328 " Johan Jonker
2024-01-31 21:17 ` [PATCH v2 6/6] arm64: dts: rockchip: fix rk3399 " Johan Jonker
2024-02-01 19:47 ` [PATCH v2 1/6] dt-bindings: display: rockchip: rockchip,dw-hdmi: remove port property Conor Dooley
2024-02-01 22:58 ` Rob Herring [this message]
2024-02-13 19:20 ` (subset) " Heiko Stuebner
2024-02-13 19:37 ` Heiko Stuebner
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=170682831660.1899746.18090191904658752173.robh@kernel.org \
--to=robh@kernel.org \
--cc=airlied@gmail.com \
--cc=andy.yan@rock-chips.com \
--cc=conor+dt@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=linux-rockchip@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=markyao0591@gmail.com \
--cc=mripard@kernel.org \
--cc=robh+dt@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