From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
TAKESHI KIHARA <takeshi.kihara.df@renesas.com>
Subject: Re: [PATCH 3/4] soc: renesas: rcar-sysc: Add support for R-Car E3 power areas
Date: Fri, 13 Apr 2018 10:46:20 +0200 [thread overview]
Message-ID: <CAMuHMdVXm52gCOx9KL+0Nn2pw507ansPVFGtAjN8sTTwEKWtdg@mail.gmail.com> (raw)
In-Reply-To: <TY1PR06MB09922C1E3B83DF01EB084714D8BC0@TY1PR06MB0992.apcprd06.prod.outlook.com>
Hi Shimoda-san,
On Thu, Apr 12, 2018 at 10:25 AM, Yoshihiro Shimoda
<yoshihiro.shimoda.uh@renesas.com> wrote:
>> From: Simon Horman <horms@verge.net.au>, Sent: Thursday, April 12, 2018 4:55 PM
>> On Wed, Apr 11, 2018 at 05:10:02PM +0200, Geert Uytterhoeven wrote:
>> > On Wed, Apr 11, 2018 at 11:36 AM, Yoshihiro Shimoda
>> > <yoshihiro.shimoda.uh@renesas.com> wrote:
>> > > From: Takeshi Kihara <takeshi.kihara.df@renesas.com>
>> > >
>> > > This patch adds Cortex-A53 CPU{0,1}, Cortex-A53 SCU, Cortex-R7, A3VC,
>> > > A2VC1 and 3DG-{A,B} power domain areas for the R8A77990 SoC.
>> >
>> > > - The 3DG power domain resume order of R-Car E3 is [3DG-B] -> [3DG-A],
>> >
>> > So 3DG-B is the parent of 3DG-A?
>> > I have to take your word on this, as I cannot find this in the documentation.
>
> Geert-san, you're correct. the documentation doesn't have any description about this.
> So, software team are asking HW guys about this.
> This means, should we drop 3DGs (or always on these domains) at initial support?
Using always-on is an acceptable solution, for now.
But let's wait and see the response from the HW guys. The v4.18 deadline is
sufficiently far in the future...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2018-04-13 8:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 9:36 [PATCH 0/4] soc: renesas: Add support for R-Car E3 Yoshihiro Shimoda
2018-04-11 9:36 ` [PATCH 1/4] soc: renesas: identify " Yoshihiro Shimoda
2018-04-11 13:26 ` Geert Uytterhoeven
2018-04-12 7:48 ` Simon Horman
2018-04-11 9:36 ` [PATCH 2/4] soc: renesas: Add r8a77990 SYSC PM Domain Binding Definitions Yoshihiro Shimoda
2018-04-11 14:55 ` Geert Uytterhoeven
2018-04-12 7:50 ` Simon Horman
2018-04-11 9:36 ` [PATCH 3/4] soc: renesas: rcar-sysc: Add support for R-Car E3 power areas Yoshihiro Shimoda
2018-04-11 15:10 ` Geert Uytterhoeven
2018-04-12 7:55 ` Simon Horman
2018-04-12 8:25 ` Yoshihiro Shimoda
2018-04-13 8:46 ` Geert Uytterhoeven [this message]
2018-04-11 9:36 ` [PATCH 4/4] soc: renesas: rcar-rst: Add support for R-Car E3 Yoshihiro Shimoda
2018-04-11 15:18 ` Geert Uytterhoeven
2018-04-12 7:54 ` Simon Horman
2018-04-12 8:11 ` Yoshihiro Shimoda
2018-04-13 8:09 ` Simon Horman
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=CAMuHMdVXm52gCOx9KL+0Nn2pw507ansPVFGtAjN8sTTwEKWtdg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=takeshi.kihara.df@renesas.com \
--cc=yoshihiro.shimoda.uh@renesas.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).