From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/6] ARM: dts: rockchip: add basic dtsi file for RK3229 SoC
Date: Mon, 19 Jun 2017 14:30:47 +0200 [thread overview]
Message-ID: <25831201.s5BUplWuV7@diego> (raw)
In-Reply-To: <7e8e2097-d5ca-a594-cb87-1b7b221fd58a@rock-chips.com>
Hi Frank,
Am Montag, 19. Juni 2017, 18:34:27 CEST schrieb Frank Wang:
> On 2017/6/18 2:12, Heiko Stuebner wrote:
> > Am Donnerstag, 15. Juni 2017, 15:16:15 CEST schrieb Frank Wang:
> >> Due to some tiny differences between RK3228 and RK3229, this patch
> >> adds a basic dtsi file which includes a new CPU opp table and PSCI
> >> brought up support for RK3229.
> >>
> >> Signed-off-by: Frank Wang <frank.wang@rock-chips.com>
[...]
> >> + psci {
> >> + compatible = "arm,psci-1.0", "arm,psci-0.2";
> >> + method = "smc";
> >> + };
> >> +};
> >> +
> >> +&cpu0 {
> >> + enable-method = "psci";
> >> +};
> >
> > Hmm, I don't really understand this.
> > What method of core-bringup does the rk3228 use? In the current
> > rk322x.dtsi there is no enable-method at all defined.
>
> For non-security, the same with rk3036 SoC, we use rk3036-smp method to
> bring-up cores, and for security, we use arm-psci method.
> As security become more and more important and required, we would prefer
> using arm-psci method, and it is also an easy way to use.
>
> > So is the rk3228 firmware using a different method than the rk3229?
>
> No, they are the same. How about I move these changes to rk322x.dtsi?
yep, that is what I was getting at with my question ;-)
> > And out of curiosity as this is a arm32 without atf, is the psci
> > implementation (for uboot?) you're using available somewhere?
>
> Ah, it is included in op-tee :-)
Is that super secret or will this be part of the official op-tee [0]
at some point (Similar to the ATF stuff on arm64)?
Heiko
[0] https://github.com/OP-TEE/optee_os/tree/master/core/arch/arm
next prev parent reply other threads:[~2017-06-19 12:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 7:16 [PATCH 0/6] add some device nodes support for rk322x SoC Frank Wang
2017-06-15 7:16 ` [PATCH 1/6] ARM: dts: rockchip: add basic dtsi file for RK3229 SoC Frank Wang
2017-06-17 18:12 ` Heiko Stuebner
2017-06-19 10:34 ` Frank Wang
2017-06-19 12:30 ` Heiko Stübner [this message]
2017-06-20 7:13 ` Frank Wang
2017-06-20 10:48 ` Heiko Stübner
[not found] ` <CAFLEztTZPeqbE++uRS-jXYUb7KzSik7=5v8+p07L788HWvwQqg@mail.gmail.com>
2017-06-21 7:29 ` Huang, Tao
2017-06-21 8:55 ` Heiko Stübner
2017-06-15 7:16 ` [PATCH 2/6] Documentation: rockchip-dw-mshc: add description for rk3228 Frank Wang
2017-06-15 7:51 ` Heiko Stübner
2017-06-15 7:16 ` [PATCH 3/6] ARM: dts: rockchip: fix compatible string for eMMC node of rk3228 SoC Frank Wang
2017-06-15 7:16 ` [PATCH 4/6] ARM: dts: rockchip: add sdmmc and sdio nodes for " Frank Wang
2017-06-15 7:21 ` [PATCH 5/6] ARM: dts: rockchip: Add io-domain node for rk3228 Frank Wang
2017-06-15 7:23 ` [PATCH 6/6] ARM: dts: rockchip: add efuse device " Frank Wang
2017-06-15 15:10 ` Heiko Stuebner
2017-06-16 9:24 ` Frank Wang
2017-06-16 9:35 ` Heiko Stübner
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=25831201.s5BUplWuV7@diego \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.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).