From: Michael Walle <michael@walle.cc>
To: Leo Li <leoyang.li@nxp.com>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>
Subject: Re: [PATCH v2 5/5] arm64: dts: lx2160a: fix FlexSPI clock
Date: Fri, 06 Nov 2020 15:04:08 +0100 [thread overview]
Message-ID: <8c96e34b3139c99f0946b62767b8cfdd@walle.cc> (raw)
In-Reply-To: <639fa8e62e0b98bedf4077f76fd75e83@walle.cc>
Am 2020-11-06 09:11, schrieb Michael Walle:
> Am 2020-11-06 03:00, schrieb Leo Li:
>>> -----Original Message-----
>>> From: Michael Walle <michael@walle.cc>
>>> Sent: Thursday, November 5, 2020 1:35 PM
>>> To: linux-clk@vger.kernel.org; devicetree@vger.kernel.org; linux-
>>> kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org
>>> Cc: Michael Turquette <mturquette@baylibre.com>; Stephen Boyd
>>> <sboyd@kernel.org>; Rob Herring <robh+dt@kernel.org>; Shawn Guo
>>> <shawnguo@kernel.org>; Leo Li <leoyang.li@nxp.com>; Michael Walle
>>> <michael@walle.cc>
>>> Subject: [PATCH v2 5/5] arm64: dts: lx2160a: fix FlexSPI clock
>>>
>>> Now that we have a proper driver for the FlexSPI interface use it.
>>> This will fix
>>> SCK frequency switching on Layerscape SoCs.
>>>
>>> This was only compile time tested.
>>>
>>> Signed-off-by: Michael Walle <michael@walle.cc>
>>> ---
>>> Changes since v1:
>>> - none
>>>
>>> arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi | 15 +++++++++++++--
>>> 1 file changed, 13 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi
>>> b/arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi
>>> index 83072da6f6c6..6e375e80bd35 100644
>>> --- a/arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi
>>> +++ b/arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi
>>> @@ -659,9 +659,20 @@
>>> };
>>>
>>> dcfg: syscon@1e00000 {
>>> - compatible = "fsl,lx2160a-dcfg", "syscon";
>>> + #address-cells = <1>;
>>> + #size-cells = <1>;
>>> + compatible = "fsl,lx2160a-dcfg", "syscon", "simple-
>>> mfd";
>>> reg = <0x0 0x1e00000 0x0 0x10000>;
>>> + ranges = <0x0 0x0 0x1e00000 0x10000>;
>>> little-endian;
>>> +
>>> + fspi_clk: clock-controller@900 {
>>> + compatible = "fsl,lx2160a-flexspi-clk";
>>> + reg = <0x900 0x4>;
>>> + #clock-cells = <0>;
>>> + clocks = <&clockgen 4 0>;
>>
>> This is different from the current <&clockgen 4 3>, is it an intended
>> change?
>
> Yes, this change was intended. At least on the LS1028A this clock
> divider is
> connected to the platform base clock. I don't know why there was
> "<&clockgen 4 3>" in the first place. But because the clkgen clock
> cannot
> be changed it didn't matter before this commit. The flexspi driver only
> calls clk_set_rate(), never clk_get_rate(). On the LS1028A I actually
> meassured the resulting SCK frequency.
> Looking at Figure 7. (Clock subsystem block diagram) in the LX2160A RM,
> this
> seems to be the case here, too.
Btw on the LS1028A this should be "<&clockgen 2 0>;" Will be fixed in
the
new version.
And because there so much difference between LS1028A and LX2160A, I'll
mark
the last patch (this one, for the LX2160A) as RFC until someone will
test it.
-michael
prev parent reply other threads:[~2020-11-06 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 19:35 [PATCH v2 0/5] clk: add fsl-flexspi driver Michael Walle
2020-11-05 19:35 ` [PATCH v2 1/5] clk: divider: add devm_clk_hw_register_divider_table() Michael Walle
2020-11-05 19:35 ` [PATCH v2 2/5] dt-bindings: clock: document the fsl-flexspi-clk driver Michael Walle
2020-11-05 19:35 ` [PATCH v2 3/5] clk: fsl-flexspi: new driver Michael Walle
2020-11-05 19:35 ` [PATCH v2 4/5] arm64: dts: ls1028a: fix FlexSPI clock Michael Walle
2020-11-05 19:35 ` [PATCH v2 5/5] arm64: dts: lx2160a: " Michael Walle
2020-11-06 2:00 ` Leo Li
2020-11-06 8:11 ` Michael Walle
2020-11-06 14:04 ` Michael Walle [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=8c96e34b3139c99f0946b62767b8cfdd@walle.cc \
--to=michael@walle.cc \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=shawnguo@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).