From: Stephen Boyd <sboyd@kernel.org>
To: Jorge Ramirez <jorge.ramirez-ortiz@linaro.org>,
Niklas Cassel <niklas.cassel@linaro.org>
Cc: andy.gross@linaro.org, david.brown@linaro.org,
jassisinghbrar@gmail.com, mark.rutland@arm.com,
mturquette@baylibre.com, robh+dt@kernel.org, will.deacon@arm.com,
bjorn.andersson@linaro.org, vkoul@kernel.org,
sibis@codeaurora.org, georgi.djakov@linaro.org, arnd@arndb.de,
horms+renesas@verge.net.au, heiko@sntech.de,
enric.balletbo@collabora.com, jagan@amarulasolutions.com,
olof@lixom.net, amit.kucheria@linaro.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH 05/13] clk: qcom: apcs-msm8916: get parent clock names from DT
Date: Fri, 28 Dec 2018 14:28:54 -0800 [thread overview]
Message-ID: <154603613437.179992.1170701312259011363@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <72bc192f-b60a-1209-7818-78a2fed07831@linaro.org>
Quoting Jorge Ramirez (2018-12-26 01:20:07)
> On 12/18/18 15:35, Niklas Cassel wrote:
> > On Mon, Dec 17, 2018 at 03:37:43PM -0800, Stephen Boyd wrote:
> >> Quoting Jorge Ramirez-Ortiz (2018-12-17 01:46:22)
> >>> Allow accessing the parent clock names required for the driver
> >>> operation by using the device tree node.
> >>>
> >>> This permits extending the driver to other platforms without having to
> >>> modify its source code.
> >>>
> >>> For backwards compatibility leave previous values as default.
> >>
> >> Why do we need to maintain backwards compatibility? Isn't is required
> >> that the nodes have clocks properties?
> >>
> >
> > Hello Stephen,
> >
> >
> > This is the existing DT nodes for msm8916:
> >
> > a53pll: clock@b016000 {
> > compatible = "qcom,msm8916-a53pll";
> > reg = <0xb016000 0x40>;
> > #clock-cells = <0>;
> > };
> >
> > apcs: mailbox@b011000 {
> > compatible = "qcom,msm8916-apcs-kpss-global", "syscon";
> > reg = <0xb011000 0x1000>;
> > #mbox-cells = <1>;
> > clocks = <&a53pll>;
> > #clock-cells = <0>;
> > };
> >
> >
> > This is the (suggested) DT nodes for qcs404:
> >
> > apcs_hfpll: clock-controller@0b016000 {
> > compatible = "qcom,hfpll";
> > reg = <0x0b016000 0x30>;
> > #clock-cells = <0>;
> > clock-output-names = "apcs_hfpll";
> > clocks = <&xo_board>;
> > clock-names = "xo";
> > };
> >
> > apcs_glb: mailbox@b011000 {
> > compatible = "qcom,qcs404-apcs-apps-global", "syscon";
> > reg = <0x0b011000 0x1000>;
> > #mbox-cells = <1>;
> > clocks = <&gcc GCC_GPLL0_AO_OUT_MAIN>, <&apcs_hfpll>;
> > clock-names = "aux", "pll";
> > #clock-cells = <0>;
> > };
> >
> > qcs404 specifies two clocks, with an accompanied clock-name for each clock.
> >
> > msm8916 specifies a single clock, without an accompanied clock-name.
> >
> > It is possible to append clock-names = "pll" for the existing clock,
> > as well as to define the aux clock in the apcs node in the msm8916 DT:
> > clocks = <&gcc GPLL0_VOTE>;
> > clock-names = "aux";
> >
> > However, since the DT is treated as an ABI, the existing DT for msm8916 must
> > still work, so I don't think that it is possible to ignore having backwards
> > compability in the apcs clock driver.
>
>
> so where are we with this?
>
> do we remove backwards compatibility (see below] for v2 or is the DT
> really an ABI and therefore the patch under review is good as is?
>
Breaking compatibility is up to the platform maintainers. If anything, I
would make the DTS and driver changes in parallel and then remove the
driver's backwards compatibility logic later on.
next prev parent reply other threads:[~2018-12-28 22:28 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 9:46 [PATCH 00/13] Support CPU frequency scaling on QCS404 Jorge Ramirez-Ortiz
2018-12-17 9:46 ` [PATCH 01/13] clk: qcom: gcc: limit GPLL0_AO_OUT operating frequency Jorge Ramirez-Ortiz
2018-12-21 11:19 ` Taniya Das
2018-12-21 12:36 ` Jorge Ramirez
2018-12-21 17:58 ` Taniya Das
2018-12-21 19:28 ` Bjorn Andersson
2018-12-21 19:45 ` Jorge Ramirez
2018-12-21 21:40 ` Stephen Boyd
2018-12-21 21:45 ` Jorge Ramirez
2018-12-21 21:51 ` Stephen Boyd
2018-12-17 9:46 ` [PATCH 02/13] mbox: qcom: add APCS child device for QCS404 Jorge Ramirez-Ortiz
2019-01-17 6:25 ` Bjorn Andersson
2018-12-17 9:46 ` [PATCH 03/13] mbox: qcom: replace integer with valid macro Jorge Ramirez-Ortiz
2019-01-17 6:25 ` Bjorn Andersson
2018-12-17 9:46 ` [PATCH 04/13] dt-bindings: mailbox: qcom: Add clock-name optional property Jorge Ramirez-Ortiz
2018-12-20 21:37 ` Rob Herring
2019-01-17 6:44 ` Bjorn Andersson
2019-01-28 16:57 ` Jorge Ramirez
2019-01-28 17:46 ` Jorge Ramirez
2018-12-17 9:46 ` [PATCH 05/13] clk: qcom: apcs-msm8916: get parent clock names from DT Jorge Ramirez-Ortiz
2018-12-17 23:37 ` Stephen Boyd
2018-12-18 8:37 ` Jorge Ramirez
2018-12-18 14:35 ` Niklas Cassel
2018-12-26 9:20 ` Jorge Ramirez
2018-12-28 22:28 ` Stephen Boyd [this message]
2018-12-31 8:42 ` Jorge Ramirez
2019-01-17 6:54 ` Bjorn Andersson
2018-12-28 22:27 ` Stephen Boyd
2018-12-17 9:46 ` [PATCH 06/13] clk: qcom: hfpll: " Jorge Ramirez-Ortiz
2019-01-17 6:27 ` Bjorn Andersson
2018-12-17 9:46 ` [PATCH 07/13] clk: qcom: hfpll: register as clock provider Jorge Ramirez-Ortiz
2019-01-17 6:28 ` Bjorn Andersson
2018-12-17 9:46 ` [PATCH 08/13] clk: qcom: hfpll: CLK_IGNORE_UNUSED Jorge Ramirez-Ortiz
2019-01-17 6:33 ` Bjorn Andersson
2019-01-17 8:38 ` Jorge Ramirez
2019-01-17 10:08 ` Viresh Kumar
2019-01-17 10:46 ` Jorge Ramirez
2019-01-22 18:47 ` Stephen Boyd
2019-01-22 19:35 ` Jorge Ramirez
2018-12-17 9:46 ` [PATCH 09/13] arm64: dts: qcom: qcs404: Add OPP table Jorge Ramirez-Ortiz
2019-01-17 6:35 ` Bjorn Andersson
2018-12-17 9:46 ` [PATCH 10/13] arm64: dts: qcom: qcs404: Add HFPLL node Jorge Ramirez-Ortiz
2018-12-17 19:39 ` Stephen Boyd
2019-01-17 6:38 ` Bjorn Andersson
2019-01-22 18:49 ` Stephen Boyd
2018-12-17 9:46 ` [PATCH 11/13] arm64: dts: qcom: qcs404: Add the clocks for APCS mux/divider Jorge Ramirez-Ortiz
2019-01-17 6:35 ` Bjorn Andersson
2018-12-17 9:46 ` [PATCH 12/13] arm64: dts: qcom: qcs404: Add cpufreq support Jorge Ramirez-Ortiz
2019-01-17 6:36 ` Bjorn Andersson
2018-12-17 9:46 ` [PATCH 13/13] arm64: defconfig: Enable HFPLL Jorge Ramirez-Ortiz
2019-01-17 6:36 ` Bjorn Andersson
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=154603613437.179992.1170701312259011363@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=amit.kucheria@linaro.org \
--cc=andy.gross@linaro.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=georgi.djakov@linaro.org \
--cc=heiko@sntech.de \
--cc=horms+renesas@verge.net.au \
--cc=jagan@amarulasolutions.com \
--cc=jassisinghbrar@gmail.com \
--cc=jorge.ramirez-ortiz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=niklas.cassel@linaro.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=sibis@codeaurora.org \
--cc=vkoul@kernel.org \
--cc=will.deacon@arm.com \
/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).