From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: imx6: add missing BM_CLPCR_BYPASS_PMIC_READY setting for imx6sx
Date: Tue, 30 Aug 2016 19:26:21 +0800 [thread overview]
Message-ID: <20160830112621.GB8363@tiger> (raw)
In-Reply-To: <AM3PR04MB1315B37C3A91FFF7F3A374B0F5E10@AM3PR04MB1315.eurprd04.prod.outlook.com>
On Mon, Aug 29, 2016 at 11:37:27PM +0000, Yongcai Huang wrote:
> Ping..
>
> Just a kind reminder in case this patch is missed, without this patch, i.MX6SX latest suspend/resume can NOT work.
>
> Best Regards!
> Anson Huang
>
>
>
> > -----Original Message-----
> > From: linux-arm-kernel [mailto:linux-arm-kernel-bounces at lists.infradead.org]
> > On Behalf Of Anson Huang
> > Sent: 2016-08-22 11:53 PM
> > To: linux-arm-kernel at lists.infradead.org
> > Cc: Fabio Estevam <fabio.estevam@nxp.com>; Peter Chen
> > <peter.chen@nxp.com>; shawnguo at kernel.org; kernel at pengutronix.de
> > Subject: [PATCH] ARM: imx6: add missing BM_CLPCR_BYPASS_PMIC_READY
> > setting for imx6sx
> >
> > i.MX6SX has bypass PMIC ready function, as this function is normally NOT
> > enabled on the board design, so we need to bypass the PMIC ready pin check
> > during DSM mode resume flow, otherwise, the internal DSM resume logic will
> > be waiting for this signal to be ready forever and cause resume fail.
> >
> > Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
Applied as a fix and Cc-ed stable as requested by Peter.
Shawn
prev parent reply other threads:[~2016-08-30 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 15:53 [PATCH] ARM: imx6: add missing BM_CLPCR_BYPASS_PMIC_READY setting for imx6sx Anson Huang
2016-08-22 8:26 ` Peter Chen
2016-08-29 23:37 ` Yongcai Huang
2016-08-30 11:26 ` Shawn Guo [this message]
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=20160830112621.GB8363@tiger \
--to=shawnguo@kernel.org \
--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