mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH 4/4] ARM: i.MX7: Add PSCI support
Date: Thu, 9 Feb 2017 11:13:25 -0800	[thread overview]
Message-ID: <CAHQ1cqGbbzkMn3cm7RjhNECMewBZDWt3WkHpGrKs6dxe8k-6gA@mail.gmail.com> (raw)
In-Reply-To: <20170207084327.7691-5-s.hauer@pengutronix.de>

On Tue, Feb 7, 2017 at 12:43 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> ---
>  arch/arm/cpu/psci.c      | 13 +++++++++
>  arch/arm/mach-imx/imx7.c | 76 ++++++++++++++++++++++++++++++++++++++++++++++++
>  2 files changed, 89 insertions(+)
>
> diff --git a/arch/arm/cpu/psci.c b/arch/arm/cpu/psci.c
> index 745b8495e..d650c23ea 100644
> --- a/arch/arm/cpu/psci.c
> +++ b/arch/arm/cpu/psci.c
> @@ -22,6 +22,17 @@
>  #include <magicvar.h>
>
>  #ifdef CONFIG_ARM_PSCI_DEBUG
> +
> +/*
> + * PSCI debugging functions. Board code can specify a putc() function
> + * which is used for debugging output. Beware that this function is
> + * called while the kernel is running. This means the kernel could have
> + * turned off clocks, configured other baudrates and other stuff that
> + * might confuse the putc function. So it can well be that the debugging
> + * code itself is the problem when somethings not working. You have been
> + * warned.
> + */
> +
>  static void (*__putc)(void *ctx, int c);
>  static void *putc_ctx;
>
> @@ -220,6 +231,8 @@ int psci_cpu_entry_c(void)
>         if (bootm_arm_security_state() == ARM_STATE_HYP)
>                 armv7_switch_to_hyp();
>
> +       psci_printf("core #%d enter function 0x%p\n", cpu, entry);
> +
>         entry(context_id);
>
>         while (1);
> diff --git a/arch/arm/mach-imx/imx7.c b/arch/arm/mach-imx/imx7.c
> index 1cd27a0db..c4b9b2815 100644
> --- a/arch/arm/mach-imx/imx7.c
> +++ b/arch/arm/mach-imx/imx7.c
> @@ -92,6 +92,80 @@ static void imx7_init_csu(void)
>                 writel(CSU_INIT_SEC_LEVEL0, csu + i * 4);
>  }
>
> +#define GPC_CPU_PGC_SW_PDN_REQ 0xfc
> +#define GPC_CPU_PGC_SW_PUP_REQ 0xf0
> +#define GPC_PGC_C1             0x840

Maybe convert this to something like:

#define PGC_C(n) (0x800 + (n) * 0x40)

... more domain offsets if needed ...

#define GPC_PGC_nCTRL(d)   ((d) + 0x00)

and use as:

GPC_PGC_nCTRL(PGC_C(1))

?

> +
> +#define BM_CPU_PGC_SW_PDN_PUP_REQ_CORE1_A7     0x2
> +
> +/* below is for i.MX7D */
> +#define SRC_GPR1_MX7D          0x074
> +#define SRC_A7RCR0             0x004

This constant doesn't seem to be used anywhere, is that intentional?

> +#define SRC_A7RCR1             0x008
> +
> +static void imx_gpcv2_set_core1_power(bool pdn)
> +{

Did you not make this function more generic and take core number as a
parameter on purpose? It just seems like it would be trivial code
change, but maybe I am mistaken

> +       void __iomem *gpc = IOMEM(MX7_GPC_BASE_ADDR);
> +
> +       u32 reg = pdn ? GPC_CPU_PGC_SW_PUP_REQ : GPC_CPU_PGC_SW_PDN_REQ;
> +       u32 val;
> +
> +       writel(1, gpc + GPC_PGC_C1);

GPC_PGC_nCTRL_PCR instead of "1"?

> +
> +       val = readl(gpc + reg);
> +       val |= BM_CPU_PGC_SW_PDN_PUP_REQ_CORE1_A7;
> +       writel(val, gpc + reg);
> +
> +       while ((readl(gpc + reg) &
> +              BM_CPU_PGC_SW_PDN_PUP_REQ_CORE1_A7) != 0)
> +               ;
> +
> +       writel(0, gpc + GPC_PGC_C1);
> +}
> +
> +static int imx7_cpu_on(u32 cpu_id)
> +{
> +       void __iomem *src = IOMEM(MX7_SRC_BASE_ADDR);
> +       u32 val;
> +
> +       writel(psci_cpu_entry, src + cpu_id * 8 + SRC_GPR1_MX7D);
> +       imx_gpcv2_set_core1_power(true);
> +
> +       val = readl(src + SRC_A7RCR1);
> +       val |= 1 << cpu_id;

BIT(cpu_id)?

> +       writel(val, src + SRC_A7RCR1);

Hmm, this function doesn't look like it supports turning on CPU 0, am
I missing something? If not shouldn't it return NOT_SUPPORTED in case
cpu_id is 0?

> +
> +       return 0;
> +}
> +
> +static int imx7_cpu_off(void)
> +{
> +       void __iomem *src = IOMEM(MX7_SRC_BASE_ADDR);
> +       u32 val;
> +       int cpu_id = 1;
> +

I have only a very brief familiarity with PCSI, so pleasw bear with me
if what I am asking is dumb, but isn't CPU_OFF operation supposed to
power off current CPU? This function looks like it will power down
core 1 regardless of who's executing the code.

> +       val = readl(src + SRC_A7RCR1);
> +       val &= ~(1 << cpu_id);

BIT(cpu_id)?

> +       writel(val, src + SRC_A7RCR1);
> +
> +       /*
> +        * FIXME: This reads nice and symmetrically to cpu_on above,
> +        * but of course this will never be reached as we have just
> +        * put the CPU we are currently running on into reset.
> +        */
> +
> +       imx_gpcv2_set_core1_power(false);
> +
> +       while (1);
> +
> +       return 0;
> +}
> +
> +static struct psci_ops imx7_psci_ops = {
> +       .cpu_on = imx7_cpu_on,
> +       .cpu_off = imx7_cpu_off,
> +};
> +
>  int imx7_init(void)
>  {
>         const char *cputypestr;
> @@ -107,6 +181,8 @@ int imx7_init(void)
>
>         imx7_silicon_revision = imx7_cpu_revision();
>
> +       psci_set_ops(&imx7_psci_ops);
> +
>         switch (imx7_cpu_type()) {
>         case IMX7_CPUTYPE_IMX7D:
>                 cputypestr = "i.MX7d";
> --
> 2.11.0
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2017-02-09 19:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07  8:43 Sascha Hauer
2017-02-07  8:43 ` [PATCH 1/4] ARM: Add UNWIND macro Sascha Hauer
2017-02-07  8:43 ` [PATCH 2/4] ARM: Add smc call support Sascha Hauer
2017-02-07  8:43 ` [PATCH 3/4] ARM: Add PSCI support Sascha Hauer
2017-02-07  8:43 ` [PATCH 4/4] ARM: i.MX7: " Sascha Hauer
2017-02-09 19:13   ` Andrey Smirnov [this message]
2017-02-13  7:45     ` Sascha Hauer
2017-02-13 18:38       ` Andrey Smirnov

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=CAHQ1cqGbbzkMn3cm7RjhNECMewBZDWt3WkHpGrKs6dxe8k-6gA@mail.gmail.com \
    --to=andrew.smirnov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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