From: "Andreas Färber" <afaerber@suse.de> To: linux-realtek-soc@lists.infradead.org, Cheng-Yu Lee <cylee12@realtek.com>, James Tai <james.tai@realtek.com> Cc: Mark Rutland <mark.rutland@arm.com>, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>, linux-arm-kernel@lists.infradead.org Subject: Re: [RFC 5/5] arm64: dts: realtek: rtd139x: Add SB2 sem nodes Date: Tue, 3 Dec 2019 00:12:57 +0100 [thread overview] Message-ID: <15898d07-ba67-f790-723d-33b0fe5363c8@suse.de> (raw) In-Reply-To: <20191202220535.6208-6-afaerber@suse.de> Am 02.12.19 um 23:05 schrieb Andreas Färber: > Add DT nodes to SB2 for hardware semaphores in RTD1395 SoC family. > > Signed-off-by: Andreas Färber <afaerber@suse.de> > --- > arch/arm64/boot/dts/realtek/rtd139x.dtsi | 14 ++++++++++++++ > 1 file changed, 14 insertions(+) > > diff --git a/arch/arm64/boot/dts/realtek/rtd139x.dtsi b/arch/arm64/boot/dts/realtek/rtd139x.dtsi > index a3c10ceeb586..586b05350274 100644 > --- a/arch/arm64/boot/dts/realtek/rtd139x.dtsi > +++ b/arch/arm64/boot/dts/realtek/rtd139x.dtsi > @@ -191,3 +191,17 @@ > status = "disabled"; > }; > }; > + > +&sb2 { > + sb2_hd_sem: hwspinlock@0 { > + compatible = "realtek,rtd1195-sb2-sem"; > + reg = <0x0 0x4>; > + #hwlock-cells = <0>; > + }; > + > + sb2_hd_sem_new: hwspinlock@620 { > + compatible = "realtek,rtd1195-sb2-sem"; > + reg = <0x620 0x20>; > + #hwlock-cells = <1>; > + }; Forgot to mention: These last 8 registers (0x20) are a guess, untested. @Realtek: Can someone please check whether RTD1395 has the same nine sem registers as RTD1295? Similarly, this series is lacking a patch for RTD1619 because - same as for RTD1295/RTD1395 - BSP DT only shows the first one (cf. coverletter). Same issue for RTD1319 while at it. Thanks, Andreas > +}; -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)
WARNING: multiple messages have this Message-ID (diff)
From: "Andreas Färber" <afaerber@suse.de> To: linux-realtek-soc@lists.infradead.org, Cheng-Yu Lee <cylee12@realtek.com>, James Tai <james.tai@realtek.com> Cc: Mark Rutland <mark.rutland@arm.com>, devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [RFC 5/5] arm64: dts: realtek: rtd139x: Add SB2 sem nodes Date: Tue, 3 Dec 2019 00:12:57 +0100 [thread overview] Message-ID: <15898d07-ba67-f790-723d-33b0fe5363c8@suse.de> (raw) In-Reply-To: <20191202220535.6208-6-afaerber@suse.de> Am 02.12.19 um 23:05 schrieb Andreas Färber: > Add DT nodes to SB2 for hardware semaphores in RTD1395 SoC family. > > Signed-off-by: Andreas Färber <afaerber@suse.de> > --- > arch/arm64/boot/dts/realtek/rtd139x.dtsi | 14 ++++++++++++++ > 1 file changed, 14 insertions(+) > > diff --git a/arch/arm64/boot/dts/realtek/rtd139x.dtsi b/arch/arm64/boot/dts/realtek/rtd139x.dtsi > index a3c10ceeb586..586b05350274 100644 > --- a/arch/arm64/boot/dts/realtek/rtd139x.dtsi > +++ b/arch/arm64/boot/dts/realtek/rtd139x.dtsi > @@ -191,3 +191,17 @@ > status = "disabled"; > }; > }; > + > +&sb2 { > + sb2_hd_sem: hwspinlock@0 { > + compatible = "realtek,rtd1195-sb2-sem"; > + reg = <0x0 0x4>; > + #hwlock-cells = <0>; > + }; > + > + sb2_hd_sem_new: hwspinlock@620 { > + compatible = "realtek,rtd1195-sb2-sem"; > + reg = <0x620 0x20>; > + #hwlock-cells = <1>; > + }; Forgot to mention: These last 8 registers (0x20) are a guess, untested. @Realtek: Can someone please check whether RTD1395 has the same nine sem registers as RTD1295? Similarly, this series is lacking a patch for RTD1619 because - same as for RTD1295/RTD1395 - BSP DT only shows the first one (cf. coverletter). Same issue for RTD1319 while at it. Thanks, Andreas > +}; -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg) _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-02 23:13 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-12-02 22:05 [RFC 0/5] ARM: dts: realtek: SB2 semaphores Andreas Färber 2019-12-02 22:05 ` Andreas Färber 2019-12-02 22:05 ` [RFC 1/5] dt-bindings: hwlock: Add Realtek RTD1195 SB2 Andreas Färber 2019-12-02 22:05 ` Andreas Färber 2019-12-13 23:40 ` Rob Herring 2019-12-13 23:40 ` Rob Herring 2019-12-13 23:40 ` Rob Herring 2019-12-02 22:05 ` [RFC 2/5] hwspinlock: " Andreas Färber 2019-12-02 22:05 ` Andreas Färber 2019-12-03 8:46 ` Fabien DESSENNE 2019-12-03 8:46 ` Fabien DESSENNE 2019-12-03 8:46 ` Fabien DESSENNE 2019-12-03 8:58 ` Andreas Färber 2019-12-03 8:58 ` Andreas Färber 2019-12-03 8:58 ` Andreas Färber 2019-12-03 9:50 ` Fabien DESSENNE 2019-12-03 9:50 ` Fabien DESSENNE 2019-12-03 9:50 ` Fabien DESSENNE 2019-12-02 22:05 ` [RFC 3/5] ARM: dts: rtd1195: Add SB2 sem nodes Andreas Färber 2019-12-02 22:05 ` Andreas Färber 2019-12-02 22:05 ` [RFC 4/5] arm64: dts: realtek: rtd129x: " Andreas Färber 2019-12-02 22:05 ` Andreas Färber 2019-12-02 22:05 ` [RFC 5/5] arm64: dts: realtek: rtd139x: " Andreas Färber 2019-12-02 22:05 ` Andreas Färber 2019-12-02 23:12 ` Andreas Färber [this message] 2019-12-02 23:12 ` Andreas Färber
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=15898d07-ba67-f790-723d-33b0fe5363c8@suse.de \ --to=afaerber@suse.de \ --cc=cylee12@realtek.com \ --cc=devicetree@vger.kernel.org \ --cc=james.tai@realtek.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-realtek-soc@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.