devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott Shu <scott.shu@mediatek.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
	wsd_upstream@mediatek.com, loda.chou@mediatek.com,
	jades.shih@mediatek.com, Mars.Cheng@mediatek.com,
	scott.shu@gmail.com, djkurtz@chromium.org
Subject: Re: [PATCH v3 3/8] soc: Mediatek: Add SCPSYS CPU power domain driver
Date: Fri, 7 Aug 2015 09:56:58 +0800	[thread overview]
Message-ID: <1438912618.1900.31.camel@mtkswgap22> (raw)
In-Reply-To: <20150806100311.GP18700@pengutronix.de>

On Thu, 2015-08-06 at 12:03 +0200, Sascha Hauer wrote:
> On Thu, Aug 06, 2015 at 10:59:02AM +0800, Scott Shu wrote:
> > On Wed, 2015-08-05 at 10:50 +0200, Sascha Hauer wrote:
> > > don't do this then it indeed doesn't make much sense to put it into the
> > > same file.
> > > 
> > > From what I see we would need to change the prototype to something like
> > > 
> > > static int __scpsys_power_on(struct scp_domain_data *)
> > > 
> > > (maybe with some additional base addresses and stuff)
> > > 
> > > struct scp_domain_data would additionally need sram_isoint_b and sram_ckiso
> > > members.
> > > 
> > > Sascha
> > > 
> > Hi Sascha,
> >    The CPU power sequence is quite different with the others, as
> > described below.
> > 
> > * Non-CPU
> >    1) Set PWR_ON_BIT, PWR_ON_2ND_BIT
> >    2) Wait PWR_ACK
> >    3) Clear PWR_CLK_DIS_BIT
> >    4) Clear PWR_ISO_BIT
> >    5) Set PWR_RST_B_BIT
> >    6) Clear SRAM_PDN
> >    7) Wait SRAM_PDN_ACK
> > * CPU
> >    1) Set PWR_ON_BIT, PWR_ON_2ND_BIT
> >    2) Wait PWR_ACK
> >    3) Clear PWR_ISO_BIT
> >    4) Clear L1_PDN to power on L1
> >    5) Wait L1_PDN_ACK
> >    6) Set SRAM_ISOINT_B
> >    7) Clear SRAM_CKISO
> >    8) Clear PWR_CLK_DIS
> >    9) Set PWR_RST_B
> > For multi-cluster SoC, the cluster power sequence is also different.
> > 
> > Please think if this is a good idea if we integrate the CPU support into
> > the scpsys_power_on()? Based on the readability and compatible
> > considerations, we provide this patch.
> 
> Maybe it's best if you go back to the v1 layout and put your scpsys code
> to arch/arm/mach-mediatek/. While I think it's possible to share some
> more code I am not sure anymore if this buys us something. We'll know in
> the future.
> 
> Sascha
> 
> 
Thanks Sascha. If you agree, we prefer to keep v3 layout. It's good to
put all scpsys related code and definitions in the same place (your
driver) and limit the CPU MTCMOS code are all located in button half of
the file. We may also change the function name, for example, rename
spm_cpu_mtcmos_on/off to scpsys_cpu_power_on/off, to make a better
overall sense. 

Scott

  reply	other threads:[~2015-08-07  1:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04 13:54 [PATCH v3 0/8] This series adds SMP support for the MediaTek MT6580 Scott Shu
2015-08-04 13:54 ` [PATCH v3 1/8] Document: bindings: DT: Add SMP enable method for MT6580 SoC platform Scott Shu
     [not found] ` <1438696464-59858-1-git-send-email-scott.shu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-08-04 13:54   ` [PATCH v3 2/8] dt-bindings: soc: Add SCPSYS compatible support for mt6580 Scott Shu
2015-08-04 13:54   ` [PATCH v3 3/8] soc: Mediatek: Add SCPSYS CPU power domain driver Scott Shu
2015-08-05  8:50     ` Sascha Hauer
2015-08-06  2:59       ` Scott Shu
2015-08-06 10:03         ` Sascha Hauer
2015-08-07  1:56           ` Scott Shu [this message]
2015-08-04 13:54   ` [PATCH v3 4/8] ARM: multi_v7_defconfig: enable INFRACFG and SCPSYS modules Scott Shu
2015-08-04 13:54   ` [PATCH v3 5/8] ARM: mediatek: add smp bringup code for MT6580 Scott Shu
     [not found]     ` <1438696464-59858-6-git-send-email-scott.shu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-08-05  9:44       ` Russell King - ARM Linux
     [not found]         ` <20150805094429.GU7557-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2015-08-07  2:28           ` Scott Shu
2015-08-05 16:47     ` Matthias Brugger
2015-08-06  6:19       ` Sascha Hauer
     [not found]         ` <20150806061918.GK18700-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2015-08-07  1:59           ` Scott Shu
2015-08-06 14:00       ` Scott Shu
2015-08-04 13:54 ` [PATCH v3 6/8] ARM: Mediatek: enable GPT6 on boot up to make arch timer working " Scott Shu
2015-08-04 13:54 ` [PATCH v3 7/8] ARM: dts: mt6580: Add device nodes to the MT6580 dtsi file Scott Shu
2015-08-04 13:54 ` [PATCH v3 8/8] ARM: dts: mt6580: enable basic SMP bringup for MT6580 Scott Shu

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=1438912618.1900.31.camel@mtkswgap22 \
    --to=scott.shu@mediatek.com \
    --cc=Mars.Cheng@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=djkurtz@chromium.org \
    --cc=jades.shih@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=loda.chou@mediatek.com \
    --cc=mark.rutland@arm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=s.hauer@pengutronix.de \
    --cc=scott.shu@gmail.com \
    --cc=wsd_upstream@mediatek.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).