From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Mark Brown <broonie@kernel.org>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Gregory CLEMENT <gregory.clement@free-electrons.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Boris BREZILLON <boris.brezillon@free-electrons.com>,
Lior Amsalem <alior@marvell.com>,
Tawfik Bayouk <tawfik@marvell.com>,
Nadav Haklai <nadavh@marvell.com>,
devicetree@vger.kernel.org
Subject: [PATCH 0/3] Fix baud rate for Armada SoCs
Date: Tue, 26 May 2015 11:44:41 +0200 [thread overview]
Message-ID: <1432633484-18758-1-git-send-email-gregory.clement@free-electrons.com> (raw)
Hi,
The commit df59fa7f4bca "spi: orion: support armada extended baud
rates" was too optimistic for the maximum baud rate that the Armada
SoCs can support. Fixing it is the purpose of the 1st patch.
Actually the Armada SoCs do not have the same constraints, some of
them have maximum absolute values whereas for the other it is linked
to the TCLK value. The second patch takes care of managing all these
cases.
Then the third patch updates the dtsi in order to use the accurate
value.
Only the first patch fixes a bug observed on the board by using a too
high frequency on the SPI bus. The other ones allow using the best
maximum frequency available.
Thanks,
Gregory
Gregory CLEMENT (3):
spi: orion: Fix maximum baud rates for Armada 370/XP
spi: orion: Fix extended baud rates for each Armada SoCs
ARM: mvebu: use improved armada spi device tree compatible name for
each SoC
.../devicetree/bindings/spi/spi-orion.txt | 8 ++-
arch/arm/boot/dts/armada-370-xp.dtsi | 2 -
arch/arm/boot/dts/armada-370.dtsi | 4 ++
arch/arm/boot/dts/armada-375.dtsi | 6 +-
arch/arm/boot/dts/armada-38x.dtsi | 6 +-
arch/arm/boot/dts/armada-39x.dtsi | 6 +-
arch/arm/boot/dts/armada-xp.dtsi | 8 +++
drivers/spi/spi-orion.c | 70 ++++++++++++++++++++--
8 files changed, 96 insertions(+), 14 deletions(-)
--
2.1.0
next reply other threads:[~2015-05-26 9:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 9:44 Gregory CLEMENT [this message]
2015-05-26 9:44 ` [PATCH 1/3] spi: orion: Fix maximum baud rates for Armada 370/XP Gregory CLEMENT
2015-05-26 10:36 ` Mark Brown
2015-05-26 12:08 ` Gregory CLEMENT
2015-05-26 9:44 ` [PATCH 2/3] spi: orion: Fix extended baud rates for each Armada SoCs Gregory CLEMENT
2015-05-26 10:38 ` Mark Brown
2015-05-26 12:08 ` Andrew Lunn
2015-05-26 12:20 ` Gregory CLEMENT
2015-05-27 17:45 ` Mark Brown
2015-05-27 17:47 ` Gregory CLEMENT
2015-05-27 18:39 ` Mark Brown
2015-05-26 9:44 ` [PATCH 3/3] ARM: mvebu: use improved armada spi device tree compatible name for each SoC Gregory CLEMENT
2015-05-27 10:04 ` Gregory CLEMENT
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=1432633484-18758-1-git-send-email-gregory.clement@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=boris.brezillon@free-electrons.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=nadavh@marvell.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tawfik@marvell.com \
--cc=thomas.petazzoni@free-electrons.com \
/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
all inboxes | Powered by JetHome®