From: "Heiko Stübner" <heiko@sntech.de>
To: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>, kishon@ti.com
Cc: mark.rutland@arm.com, bivvy.bi@rock-chips.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
christoph.muellner@theobroma-systems.com
Subject: Re: [PATCH 1/2] dt-bindings: phy: drop #clock-cells from rockchip, px30-dsi-dphy
Date: Mon, 09 Dec 2019 10:27:28 +0100 [thread overview]
Message-ID: <2785558.xRCxUMSmLi@diego> (raw)
In-Reply-To: <20191108000640.8775-1-heiko.stuebner@theobroma-systems.com>
Hi Kishon,
Am Freitag, 8. November 2019, 01:06:39 CET schrieb Heiko Stuebner:
> Further review of the dsi components for the px30 revealed that the
> phy shouldn't expose the pll as clock but instead handle settings
> via phy parameters.
>
> As the phy binding is new and not used anywhere yet, just drop them
> so they don't get used.
>
> Fixes: 3817c7961179 ("dt-bindings: phy: add yaml binding for rockchip,px30-dsi-dphy")
> Signed-off-by: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
> ---
> Hi Kishon,
>
> this should ideally get into 5.5 as a fix for the previous change
> so that the binding doesn't accidentially get used.
Could you take a look at these 2 changes for the newly added dsi-phy
for some Rockchip SoCs? From a dt-binding-hardliner standpoint, it should
ideally get fixed in 5.5, so that the (wrong) binding doesn't get released
with a full kernel release.
But as it is very much Rockchip-specific and doesn't touch other part,
5.6 would also be ok I guess ;-)
Thanks
Heiko
> .../devicetree/bindings/phy/rockchip,px30-dsi-dphy.yaml | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/phy/rockchip,px30-dsi-dphy.yaml b/Documentation/devicetree/bindings/phy/rockchip,px30-dsi-dphy.yaml
> index bb0da87bcd84..476c56a1dc8c 100644
> --- a/Documentation/devicetree/bindings/phy/rockchip,px30-dsi-dphy.yaml
> +++ b/Documentation/devicetree/bindings/phy/rockchip,px30-dsi-dphy.yaml
> @@ -13,9 +13,6 @@ properties:
> "#phy-cells":
> const: 0
>
> - "#clock-cells":
> - const: 0
> -
> compatible:
> enum:
> - rockchip,px30-dsi-dphy
> @@ -49,7 +46,6 @@ properties:
>
> required:
> - "#phy-cells"
> - - "#clock-cells"
> - compatible
> - reg
> - clocks
> @@ -66,7 +62,6 @@ examples:
> reg = <0x0 0xff2e0000 0x0 0x10000>;
> clocks = <&pmucru 13>, <&cru 12>;
> clock-names = "ref", "pclk";
> - #clock-cells = <0>;
> resets = <&cru 12>;
> reset-names = "apb";
> #phy-cells = <0>;
>
_______________________________________________
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:[~2019-12-09 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 0:06 [PATCH 1/2] dt-bindings: phy: drop #clock-cells from rockchip, px30-dsi-dphy Heiko Stuebner
2019-11-08 0:06 ` [PATCH 2/2] phy/rockchip: inno-dsidphy: generalize parameter handling Heiko Stuebner
2019-11-14 1:53 ` [PATCH 1/2] dt-bindings: phy: drop #clock-cells from rockchip,px30-dsi-dphy Rob Herring
2019-12-09 9:27 ` Heiko Stübner [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=2785558.xRCxUMSmLi@diego \
--to=heiko@sntech.de \
--cc=bivvy.bi@rock-chips.com \
--cc=christoph.muellner@theobroma-systems.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko.stuebner@theobroma-systems.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.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).