From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: imx: fixes for 4.2
Date: Tue, 14 Jul 2015 23:39:51 +0800 [thread overview]
Message-ID: <20150714153951.GJ4119@tiger> (raw)
The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-fixes-4.2
for you to fetch changes up to d438462c20a300139c2e5e65b96cadaa21b58d9a:
ARM: imx6: gpc: always enable PU domain if CONFIG_PM is not set (2015-07-08 22:52:08 +0800)
----------------------------------------------------------------
The i.MX fixes for 4.2:
- Correct compatible string for i.MX27 GPT which actually shares the
same programming model as i.MX21 GPT rather than i.MX1 one.
- Add missing #io-channel-cells property for i.MX23 LRADC device, which
is required for the device to be an IIO provider.
- Correct HSYNC/VSYNC pins and add ddc-i2c-bus property for TVE device
on imx53-qsb to work properly.
- Always enable PU domain if CONFIG_PM is not set. This fixes a couple
of failure scenarios which will hang the system if one of the devices
in the PU domain is accessed.
----------------------------------------------------------------
Fabio Estevam (1):
ARM: dts: imx27: Adjust the GPT compatible string
Lucas Stach (1):
ARM: imx6: gpc: always enable PU domain if CONFIG_PM is not set
Philipp Zabel (1):
ARM: dts: imx53-qsb: fix TVE entry
Stefan Wahren (1):
ARM: dts: mx23: fix iio-hwmon support
arch/arm/boot/dts/imx23.dtsi | 1 +
arch/arm/boot/dts/imx27.dtsi | 12 ++++++------
arch/arm/boot/dts/imx53-qsb-common.dtsi | 5 +++--
arch/arm/mach-imx/gpc.c | 27 ++++++---------------------
4 files changed, 16 insertions(+), 29 deletions(-)
next reply other threads:[~2015-07-14 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 15:39 Shawn Guo [this message]
2015-07-15 9:30 ` [GIT PULL] ARM: imx: fixes for 4.2 Olof Johansson
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=20150714153951.GJ4119@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;
as well as URLs for NNTP newsgroup(s).