public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: imx: fixes for 4.1, 3rd round
Date: Wed, 27 May 2015 19:39:56 +0800	[thread overview]
Message-ID: <20150527113952.GF16165@dragon> (raw)

The following changes since commit e46b5a6470a5e2c8e1096f8f60887ac19949055b:

  ARM: dts: fix imx27 dtb build rule (2015-05-19 22:06:41 +0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-fixes-4.1-3

for you to fetch changes up to b17c70cd9211e9bbcd77a489f9c60f3d1bd4c392:

  ARM: imx6: gpc: don't register power domain if DT data is missing (2015-05-27 16:33:46 +0800)

----------------------------------------------------------------
The i.MX fixes for 4.1, 3rd round:

It includes a couple of fixes for i.MX6 GPC code to let the new kernel
be able to boot with old DTBs:

 - Booting v4.1-rc kernel with old DTBs will fail with a fat warning
   (require low-level debug to be seen), due to the adoption of stacked
   IRQ domain.  The first fix improves the situation by allowing kernel
   boot up with old DTBs, although suspend/resume still breaks.

 - Booting new kernel with old DTBs that do not have power-domain info
   will result in a hang.  The second patch fixes the hang by skipping
   the kernel power-domain registration if DTB has no power-domain info.

----------------------------------------------------------------
Lucas Stach (2):
      ARM: imx6: allow booting with old DT
      ARM: imx6: gpc: don't register power domain if DT data is missing

 arch/arm/mach-imx/gpc.c | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)

             reply	other threads:[~2015-05-27 11:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 11:39 Shawn Guo [this message]
2015-05-29 12:31 ` [GIT PULL] ARM: imx: fixes for 4.1, 3rd round Arnd Bergmann

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=20150527113952.GF16165@dragon \
    --to=shawn.guo@linaro.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