From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] ARM: mvebu: fix bus width handling in mvebu-devbus
Date: Wed, 16 Apr 2014 10:17:54 +0200 [thread overview]
Message-ID: <534E3CB2.3010505@free-electrons.com> (raw)
In-Reply-To: <1397489361-5833-1-git-send-email-thomas.petazzoni@free-electrons.com>
Hi Thomas,
On 14/04/2014 17:29, Thomas Petazzoni wrote:
> Jason, Greg, Andrew, Sebastian,
>
> This set of patches fix a bug in the mvebu-devbus driver, which was
> leading to a misinterpretation of Device Tree provided value: a NOR
> bus width declared as 8 bits in the Device Tree was in fact configured
> as 16 bits at the hardware level.
>
> This bug was not noticed until now, because it was compensated by a
> symetric mistake in the Device Tree files.
>
> This set of commits therefore fix both the driver itself, and the
> incorrect Device Tree files. The patches for the Device Tree files
> have been separated, because some of them should apply all the way to
> v3.10, while some of them apply only up to v3.11.
>
> Changes since v1:
>
> * Added patches to fix the Device Tree files to indicate the correct
> bus width, as documented in the board schematics. Noticed by
> Ezequiel Garcia.
>
> * Changed the bus_width conversion logic in the driver to only accept
> valid values: 8 bits and 16 bits. All other values lead to an error
> being returned. Suggested by Sebastian Hesselbarth.
>
> * Rebased on top of v3.15-rc1.
Everything looks good so for the whole series:
Acked-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
Thanks,
Gregory
>
> Thanks,
>
> Thomas
>
> Thomas Petazzoni (4):
> memory: mvebu-devbus: fix the conversion of the bus width
> ARM: mvebu: fix NOR bus-width in Armada XP GP Device Tree
> ARM: mvebu: fix NOR bus-width in Armada XP DB Device Tree
> ARM: mvebu: fix NOR bus-width in Armada XP OpenBlocks AX3 Device Tree
>
> arch/arm/boot/dts/armada-xp-db.dts | 2 +-
> arch/arm/boot/dts/armada-xp-gp.dts | 2 +-
> arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts | 2 +-
> drivers/memory/mvebu-devbus.c | 15 +++++++++++++--
> 4 files changed, 16 insertions(+), 5 deletions(-)
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2014-04-16 8:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 15:29 [PATCH v2 0/4] ARM: mvebu: fix bus width handling in mvebu-devbus Thomas Petazzoni
2014-04-14 15:29 ` [PATCH v2 1/4] memory: mvebu-devbus: fix the conversion of the bus width Thomas Petazzoni
2014-04-16 21:09 ` Jason Cooper
2014-04-16 21:28 ` Thomas Petazzoni
2014-04-17 4:48 ` Jason Cooper
2014-04-14 15:29 ` [PATCH v2 2/4] ARM: mvebu: fix NOR bus-width in Armada XP GP Device Tree Thomas Petazzoni
2014-04-17 5:08 ` Jason Cooper
2014-04-17 7:09 ` Thomas Petazzoni
2014-04-17 14:23 ` Jason Cooper
2014-04-14 15:29 ` [PATCH v2 3/4] ARM: mvebu: fix NOR bus-width in Armada XP DB " Thomas Petazzoni
2014-04-14 15:29 ` [PATCH v2 4/4] ARM: mvebu: fix NOR bus-width in Armada XP OpenBlocks AX3 " Thomas Petazzoni
2014-04-14 17:00 ` [PATCH v2 0/4] ARM: mvebu: fix bus width handling in mvebu-devbus Ezequiel Garcia
2014-04-16 8:17 ` Gregory CLEMENT [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=534E3CB2.3010505@free-electrons.com \
--to=gregory.clement@free-electrons.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 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.