Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
	Sascha Hauer <kernel@pengutronix.de>,
	NXP Linux Team <linux-imx@nxp.com>,
	stable <stable@vger.kernel.org>
Subject: Re: [PATCH] ARM: imx: cpuidle-imx6sx: Restrict the SW2ISO increase to i.MX6SX
Date: Mon, 13 May 2019 11:01:06 +0800	[thread overview]
Message-ID: <20190513030105.GR15856@dragon> (raw)
In-Reply-To: <CAOMZO5BMpwqQUYQ==MRowu62SboL7ikFztUVA2ODkRtONU6gsg@mail.gmail.com>

On Thu, May 02, 2019 at 09:54:16AM -0300, Fabio Estevam wrote:
> On Thu, May 2, 2019 at 9:33 AM Fabio Estevam <festevam@gmail.com> wrote:
> >
> > On Thu, May 2, 2019 at 9:26 AM Sasha Levin <sashal@kernel.org> wrote:
> > >
> > > Hi,
> > >
> > > [This is an automated email]
> > >
> > > This commit has been processed because it contains a "Fixes:" tag,
> > > fixing commit: 1e434b703248 ARM: imx: update the cpu power up timing setting on i.mx6sx.
> > >
> > > The bot has tested the following trees: v5.0.10, v4.19.37, v4.14.114, v4.9.171, v4.4.179.
> > >
> > > v5.0.10: Build OK!
> > > v4.19.37: Build OK!
> > > v4.14.114: Build OK!
> > > v4.9.171: Build OK!
> > > v4.4.179: Failed to apply! Possible dependencies:
> > >     6ae44aa651d0 ("ARM: imx: enable WAIT mode hardware workaround for imx6sx")
> > >
> > >
> > > How should we proceed with this patch?
> >
> > I can submit a version for 4.4 stable tree once this hits mainline.
> > The conflict resolution is very simple.
> 
> Or maybe I can send a simpler version that applies all the way to 4.4:
> 
> --- a/arch/arm/mach-imx/cpuidle-imx6sx.c
> +++ b/arch/arm/mach-imx/cpuidle-imx6sx.c
> @@ -15,6 +15,7 @@
> 
>  #include "common.h"
>  #include "cpuidle.h"
> +#include "hardware.h"
> 
>  static int imx6sx_idle_finish(unsigned long val)
>  {
> @@ -110,7 +111,7 @@ int __init imx6sx_cpuidle_init(void)
>   * except for power up sw2iso which need to be
>   * larger than LDO ramp up time.
>   */
> - imx_gpc_set_arm_power_up_timing(0xf, 1);
> + imx_gpc_set_arm_power_up_timing(cpu_is_imx6sx() ? 0xf: 0x2, 1);
                                                         ^ missing space

>   imx_gpc_set_arm_power_down_timing(1, 1);
> 
>   return cpuidle_register(&imx6sx_cpuidle_driver, NULL);
> 
> Would this be preferred?

Yes, please.

Shawn

  reply	other threads:[~2019-05-13  3:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-02 11:30 [PATCH] ARM: imx: cpuidle-imx6sx: Restrict the SW2ISO increase to i.MX6SX Fabio Estevam
2019-05-02 12:13 ` Sébastien Szymanski
     [not found] ` <20190502122645.C5FD52081C@mail.kernel.org>
2019-05-02 12:33   ` Fabio Estevam
2019-05-02 12:54     ` Fabio Estevam
2019-05-13  3:01       ` Shawn Guo [this message]
2019-05-03  8:23 ` [PATCH] ARM: imx: cpuidle-imx6sx: Restrict the SW2ISO increase to i.MX6SX [Klartext] Christoph Niedermaier

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=20190513030105.GR15856@dragon \
    --to=shawnguo@kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-imx@nxp.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.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: 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