Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: patrice.chotard@st.com (Patrice Chotard)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND GIT PULL] STi DT fixes for v4.8-rcs
Date: Thu, 8 Sep 2016 17:21:00 +0200	[thread overview]
Message-ID: <f2d83529-3ab1-fe8e-c599-cf5dfbb1f17b@st.com> (raw)

Hi Arnd, Olof, Kevin

I resend this pull request as i got issue with the local IT infrastructure.

Please consider this set for inclusion into the v4.8-rcs.

The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc:

  Linux 4.8-rc1 (2016-08-07 18:18:00 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/pchotard/sti.git tags/sti-dt-fixes-for-v4.8-rcs

for you to fetch changes up to 78567f135d9bbbaf4538f63656d3e4d957c35fe9:

  ARM: dts: STiH407-family: Provide interconnect clock for consumption in ST SDHCI (2016-09-08 15:51:12 +0200)

----------------------------------------------------------------
Handle STiH410 interconnect clock required for EHCI/OHCI and SDHCI

With the introduction of critical-clock support in v4.8, our developers'
default configuration is to run with 'clk_ignore_unused' removed.  This
patch-set ensures they can achieve successful boot when a) booting from
an SD Card and when b) booting using USB->Eth adaptors for NFS booting.

----------------------------------------------------------------
Lee Jones (2):
      ARM: dts: STiH410: Handle interconnect clock required by EHCI/OHCI (USB)
      ARM: dts: STiH407-family: Provide interconnect clock for consumption in ST SDHCI

 arch/arm/boot/dts/stih407-family.dtsi | 10 ++++++----
 arch/arm/boot/dts/stih410.dtsi        | 12 ++++++++----
 2 files changed, 14 insertions(+), 8 deletions(-)

             reply	other threads:[~2016-09-08 15:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08 15:21 Patrice Chotard [this message]
2016-09-09 15:59 ` [RESEND GIT PULL] STi DT fixes for v4.8-rcs 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=f2d83529-3ab1-fe8e-c599-cf5dfbb1f17b@st.com \
    --to=patrice.chotard@st.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox