From: Michael Walle <michael@walle.cc>
To: Shawn Guo <shawnguo@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Li Yang <leoyang.li@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] arm64: dts: ls1028a: fix reboot node
Date: Mon, 09 Dec 2019 10:02:02 +0100 [thread overview]
Message-ID: <67346b48fa7e236ea31e3ecb1a108f28@walle.cc> (raw)
In-Reply-To: <20191209034722.GZ3365@dragon>
Am 2019-12-09 04:47, schrieb Shawn Guo:
> On Sat, Nov 23, 2019 at 01:07:09AM +0100, Michael Walle wrote:
>> The reboot register isn't located inside the DCFG controller, but in
>> its
>> own RST controller. Fix it.
>>
>> Signed-off-by: Michael Walle <michael@walle.cc>
>> ---
>> arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi | 8 +++++++-
>> 1 file changed, 7 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
>> b/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
>> index 72b9a75976a1..dc75534a4754 100644
>> --- a/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
>> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
>> @@ -102,7 +102,7 @@
>>
>> reboot {
>> compatible ="syscon-reboot";
>> - regmap = <&dcfg>;
>> + regmap = <&rst>;
>> offset = <0xb0>;
>> mask = <0x02>;
>> };
>> @@ -161,6 +161,12 @@
>> big-endian;
>> };
>>
>> + rst: syscon@1e60000 {
>> + compatible = "fsl,ls1028a-rst", "syscon";
>
> Compatible "fsl,ls1028a-rst" seems undocumented?
it is the same with fsl,ls1028a-scfg and fsl,ls1028a-dcfg. So maybe I
should just drop the "fsl,ls1028a-rst". What do you think?
-michael
>
> Shawn
>
>> + reg = <0x0 0x1e60000 0x0 0x10000>;
>> + little-endian;
>> + };
>> +
>> scfg: syscon@1fc0000 {
>> compatible = "fsl,ls1028a-scfg", "syscon";
>> reg = <0x0 0x1fc0000 0x0 0x10000>;
>> --
>> 2.20.1
>>
next prev parent reply other threads:[~2019-12-09 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 0:07 [PATCH] arm64: dts: ls1028a: fix reboot node Michael Walle
2019-12-09 3:46 ` Shawn Guo
2019-12-09 3:47 ` Shawn Guo
2019-12-09 9:02 ` Michael Walle [this message]
2019-12-11 2:17 ` Shawn Guo
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=67346b48fa7e236ea31e3ecb1a108f28@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-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).