From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: stable fix for v3.13
Date: Tue, 14 Jan 2014 10:41:41 -0500 [thread overview]
Message-ID: <20140114154141.GO19878@titan.lakedaemon.net> (raw)
arm-soc folks,
Sorry for the lateness in the window on this one. I'd like to see it
get into v3.13 if possible, but if it doesn't get there till v3.13.1, I
understand.
This fixes a boot hang experienced on some Openblocks AX3-4 boards.
Once i2c transaction support was added, it was discovered that the A0
revision of the Armada XP had broken offload support which causes the
kernel to hang at boot. The only way to detect this situation is to
read the PCI config register to get the SoC revision, then disable
offload if we are on an A0 SoC.
Unfortunately, this makes for a rather large patch series against
stable. Doing the fix in a smaller patch would create a runtime
dependency between i2c and PCI which we prefer to avoid.
I'm Cc'ing Greg and linux-stable as a heads-up, and so they can comment
or ask questions.
thx,
Jason.
The following changes since commit 6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae:
Linux 3.13-rc1 (2013-11-22 11:30:55 -0800)
are available in the git repository at:
git://git.infradead.org/linux-mvebu.git tags/mvebu-fixes-3.13
for you to fetch changes up to f8b94beb7e6a374cb0de531b72377c49857b35ca:
i2c: mv64xxx: Document the newly introduced Armada XP A0 compatible (2014-01-14 02:09:17 +0000)
----------------------------------------------------------------
mvebu late fixes for v3.13
- mvebu
- fix boot hang on Armada XP due to broken i2c offloading in A0 SoC revision
(specifically experienced on some early OpenBlocks AX3-4 boards)
----------------------------------------------------------------
Gregory CLEMENT (4):
ARM: mvebu: Add support to get the ID and the revision of a SoC
ARM: mvebu: Add quirk for i2c for the OpenBlocks AX3-4 board
i2c: mv64xxx: Fix bus hang on A0 version of the Armada XP SoCs
i2c: mv64xxx: Document the newly introduced Armada XP A0 compatible
.../devicetree/bindings/i2c/i2c-mv64xxx.txt | 6 +-
arch/arm/mach-mvebu/Makefile | 2 +-
arch/arm/mach-mvebu/armada-370-xp.c | 32 ++++++
arch/arm/mach-mvebu/mvebu-soc-id.c | 119 +++++++++++++++++++++
arch/arm/mach-mvebu/mvebu-soc-id.h | 32 ++++++
drivers/i2c/busses/i2c-mv64xxx.c | 5 +
6 files changed, 194 insertions(+), 2 deletions(-)
create mode 100644 arch/arm/mach-mvebu/mvebu-soc-id.c
create mode 100644 arch/arm/mach-mvebu/mvebu-soc-id.h
next reply other threads:[~2014-01-14 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 15:41 Jason Cooper [this message]
2014-02-04 1:30 ` [GIT PULL] ARM: mvebu: stable fix for v3.13 Greg KH
-- strict thread matches above, loose matches on Subject: below --
2014-01-14 15:44 Jason Cooper
2014-01-14 19:14 ` Kevin Hilman
2014-01-14 19:17 ` Jason Cooper
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=20140114154141.GO19878@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--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