From: khilman@kernel.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v2 2/4] ARM: imx: soc updates for 4.2
Date: Wed, 10 Jun 2015 16:58:53 -0700 [thread overview]
Message-ID: <7hk2vbi08y.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20150604023903.GB17189@dragon> (Shawn Guo's message of "Thu, 4 Jun 2015 10:39:03 +0800")
Shawn Guo <shawnguo@kernel.org> writes:
> Changes since v1:
> - Rebase to only share imx7d clock ID header with imx/dt branch
> - Fix gpt timer issues found by linux-next testing
>
> The following changes since commit b787f68c36d49bb1d9236f403813641efa74a031:
>
> Linux 4.1-rc1 (2015-04-26 17:59:10 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-soc-4.2
>
> for you to fetch changes up to 0be5da9dc249391e3310cc2351e7af5ce211ac49:
>
> ARM: imx: imx7d requires anatop (2015-06-03 14:52:31 +0800)
>
> ----------------------------------------------------------------
> The i.MX SoC updates for 4.2:
> - Add new SoC i.MX7D support, which integrates two Cortex-A7 and one
> Cortex-M4 cores.
> - Support suspend from IRAM on i.MX53, so that DDR pins can be set to
> high impedance for more power saving during suspend.
> - Move i.MX clock drivers from arch/arm/mach-imx to drivers/clk/imx.
> - Move i.MX GPT timer driver from arch/arm/mach-imx into
> drivers/clocksource.
> - A couple of clock driver update for VF610 and i.MX6Q.
> - A few random code correction and improvement.
>
> ----------------------------------------------------------------
Applied to next/soc, but...
This had a minor conflict with "ARM: vf610: enable Cortex-M4
configuration on Vybrid SoC" already in next/soc. Please make sure
that my resolution of arch/arm/mach-imx/Kconfig looks right.
Thanks,
Kevin
next prev parent reply other threads:[~2015-06-10 23:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 2:39 [GIT PULL v2 2/4] ARM: imx: soc updates for 4.2 Shawn Guo
2015-06-10 23:58 ` Kevin Hilman [this message]
2015-06-11 0:34 ` 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=7hk2vbi08y.fsf@deeprootsystems.com \
--to=khilman@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 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.