From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: DT fix for v3.16-rc1
Date: Sun, 25 May 2014 13:36:37 -0400 [thread overview]
Message-ID: <20140525173637.GM8664@titan.lakedaemon.net> (raw)
Guys,
This is a small fix for some new code going in to v3.16. Apparently,
there's a mis-match between what the bootloader assumes wrt NAND ECC
settings and what the ONFI spec says. To prevent woe and discontent, we
need to explicitly state the ECC settings in the dts files.
At the time of this writing, this hasn't been in -next yet. I imagine
it'll be a few days before you pull this, so I wanted you to be aware
asap. These changes are set to be in -next from tonight onwards.
As usual, this is an incremental pull request from tags/mvebu-dt-3.16-2
up to tags/mvebu-dt-3.16-3 in the mvebu/dt branch.
Please pull.
thx,
Jason.
The following changes since commit 599a136e5f4a7c3ca324fb2749ca235cd90c9d51:
ARM: dts: kirkwood: add kirkwood-km_fixedeth DTS file (2014-05-16 17:57:27 +0000)
are available in the git repository at:
git://git.infradead.org/linux-mvebu.git tags/mvebu-dt-3.16-3
for you to fetch changes up to 54aab8845c46b0f87947107cdc67c8ed7062a5bb:
ARM: dts: Specify the NAND ECC scheme explicitly on Armada 385 DB board (2014-05-25 17:14:37 +0000)
----------------------------------------------------------------
mvebu DT changes for v3.16 (incremental #3)
- Armada 375/38x NAND ECC fix for v3.16-rc1
----------------------------------------------------------------
Ezequiel Garcia (2):
ARM: dts: Specify the NAND ECC scheme explicitly on Armada 375 DB board
ARM: dts: Specify the NAND ECC scheme explicitly on Armada 385 DB board
arch/arm/boot/dts/armada-375-db.dts | 2 ++
arch/arm/boot/dts/armada-385-db.dts | 2 ++
2 files changed, 4 insertions(+)
next reply other threads:[~2014-05-25 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 17:36 Jason Cooper [this message]
2014-06-13 20:23 ` [GIT PULL] ARM: mvebu: DT fix for v3.16-rc1 Jason Cooper
2014-06-13 20:57 ` 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=20140525173637.GM8664@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