Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: computersforpeace@gmail.com (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH for v3.15 0/2] ARM: mvebu Specificy ECC scheme for A375/385 boards
Date: Sun, 25 May 2014 14:35:09 -0700	[thread overview]
Message-ID: <20140525213509.GA5241@norris-Latitude-E6410> (raw)
In-Reply-To: <20140525172906.GL8664@titan.lakedaemon.net>

On Sun, May 25, 2014 at 01:29:06PM -0400, Jason Cooper wrote:
> On Sat, May 24, 2014 at 11:17:08AM -0300, Ezequiel Garcia wrote:
> > Last minute fixes, which help prevent any inconsistencies between the ECC
> > scheme expected by the bootloader, and the one expected by the kernel.
> > 
> > Until now, the kernel was using the ONFI-provided "datasheet ECC requirement",
> > and assume the bootloader did the same thing. However, this is not the case
> > for these boards, where the vendor provided a bootloader with an ECC strength
> > that's weaker than the required.
> > 
> > After the introduction of the NAND ECC devicetree binding, and its support
> > in the pxa3xx-nand driver, we can set these values and expect them to work.
> > 
> > I hope it's not too late for v3.15 already.
> > 
> > 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(+)

For the series:

Acked-by: Brian Norris <computersforpeace@gmail.com>

> As discussed on irc, I'm pushing this for v3.16 right now.  If we later
> determine that it needs to be in v3.15, we can send a stable request for
> these patches.

Not sure what went into the discussion, but for one, the binding is only
used in the pxa3xx_nand driver in the for-3.16 development branch, so it
doesn't quite seem urgent to me.

Regards,
Brian

      reply	other threads:[~2014-05-25 21:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-24 14:17 [PATCH for v3.15 0/2] ARM: mvebu Specificy ECC scheme for A375/385 boards Ezequiel Garcia
2014-05-24 14:17 ` [PATCH 1/2] ARM: dts: Specify the NAND ECC scheme explicitly on Armada 375 DB board Ezequiel Garcia
2014-05-24 14:17 ` [PATCH 2/2] ARM: dts: Specify the NAND ECC scheme explicitly on Armada 385 " Ezequiel Garcia
2014-05-25 17:29 ` [PATCH for v3.15 0/2] ARM: mvebu Specificy ECC scheme for A375/385 boards Jason Cooper
2014-05-25 21:35   ` Brian Norris [this message]

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=20140525213509.GA5241@norris-Latitude-E6410 \
    --to=computersforpeace@gmail.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