All of lore.kernel.org
 help / color / mirror / Atom feed
From: leonard.crestez@nxp.com (Leonard Crestez)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] ARM: imx6ull: Make suspend/resume work like on 6ul
Date: Tue, 6 Jun 2017 20:50:41 +0300	[thread overview]
Message-ID: <cover.1496771145.git.leonard.crestez@nxp.com> (raw)

Suspend and resume on imx6ull is currenty not working because of some
missed checks where behavior should match imx6ul.

Looking at the reference manual I don't think BM_CLPCR_BYP_MMDC_CH0_LPM_HS
needs to be set, it's just that BM_CLPCR_BYP_MMDC_CH1_LPM_HS should not be set
like on imx6qdl. But this would be an unrelated cleanup and affect other chips
as well (everything other that imx6qdl).

Changes since v1 https://lkml.org/lkml/2017/5/30/584 :
 * Split adding MXC_CPU_IMX6ULL into a separate patch
 * While we're at it fix soc_id reading "Unknown"

Leonard Crestez (2):
  ARM: imx: Add MXC_CPU_IMX6ULL and cpu_is_imx6ull
  ARM: imx6ull: Make suspend/resume work like on 6ul

 arch/arm/mach-imx/cpu.c     | 3 +++
 arch/arm/mach-imx/mxc.h     | 6 ++++++
 arch/arm/mach-imx/pm-imx6.c | 6 ++++--
 3 files changed, 13 insertions(+), 2 deletions(-)

-- 
2.7.4

WARNING: multiple messages have this Message-ID (diff)
From: Leonard Crestez <leonard.crestez@nxp.com>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Peter Chen <peter.chen@nxp.com>,
	Anson Huang <Anson.Huang@nxp.com>, <linux-kernel@vger.kernel.org>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	<linux-arm-kernel@lists.infradead.org>,
	Lucas Stach <l.stach@pengutronix.de>
Subject: [PATCH v2 0/2] ARM: imx6ull: Make suspend/resume work like on 6ul
Date: Tue, 6 Jun 2017 20:50:41 +0300	[thread overview]
Message-ID: <cover.1496771145.git.leonard.crestez@nxp.com> (raw)

Suspend and resume on imx6ull is currenty not working because of some
missed checks where behavior should match imx6ul.

Looking at the reference manual I don't think BM_CLPCR_BYP_MMDC_CH0_LPM_HS
needs to be set, it's just that BM_CLPCR_BYP_MMDC_CH1_LPM_HS should not be set
like on imx6qdl. But this would be an unrelated cleanup and affect other chips
as well (everything other that imx6qdl).

Changes since v1 https://lkml.org/lkml/2017/5/30/584 :
 * Split adding MXC_CPU_IMX6ULL into a separate patch
 * While we're at it fix soc_id reading "Unknown"

Leonard Crestez (2):
  ARM: imx: Add MXC_CPU_IMX6ULL and cpu_is_imx6ull
  ARM: imx6ull: Make suspend/resume work like on 6ul

 arch/arm/mach-imx/cpu.c     | 3 +++
 arch/arm/mach-imx/mxc.h     | 6 ++++++
 arch/arm/mach-imx/pm-imx6.c | 6 ++++--
 3 files changed, 13 insertions(+), 2 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-06-06 17:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 17:50 Leonard Crestez [this message]
2017-06-06 17:50 ` [PATCH v2 0/2] ARM: imx6ull: Make suspend/resume work like on 6ul Leonard Crestez
2017-06-06 17:50 ` [PATCH v2 1/2] ARM: imx: Add MXC_CPU_IMX6ULL and cpu_is_imx6ull Leonard Crestez
2017-06-06 17:50   ` Leonard Crestez
2017-06-06 18:38   ` Fabio Estevam
2017-06-06 18:38     ` Fabio Estevam
2017-06-06 17:50 ` [PATCH v2 2/2] ARM: imx6ull: Make suspend/resume work like on 6ul Leonard Crestez
2017-06-06 17:50   ` Leonard Crestez
2017-06-06 18:38   ` Fabio Estevam
2017-06-06 18:38     ` Fabio Estevam
2017-06-07  3:40 ` [PATCH v2 0/2] " Shawn Guo
2017-06-07  3:40   ` Shawn Guo

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=cover.1496771145.git.leonard.crestez@nxp.com \
    --to=leonard.crestez@nxp.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.