diff options
author | Gregory CLEMENT <gregory.clement@free-electrons.com> | 2015-05-26 11:44:42 +0200 |
---|---|---|
committer | Sasha Levin <sasha.levin@oracle.com> | 2015-07-03 23:02:19 -0400 |
commit | 2e4e4d17a62b3a06e87e0ca4383c70e14ebbbcdd (patch) | |
tree | 7bd1514f65e4f7c124b57926c094b1e4565f593a /virt | |
parent | d1e78f3cdb81d9eab27247d234242c09a859114b (diff) |
spi: orion: Fix maximum baud rates for Armada 370/XP
[ Upstream commit ce2f6ea1cbd41d78224f703af980a6ceeb0eb56a ]
The commit df59fa7f4bca "spi: orion: support armada extended baud
rates" was too optimistic for the maximum baud rate that the Armada
SoCs can support. According to the hardware datasheet the maximum
frequency supported by the Armada 370 SoC is tclk/4. But for the
Armada XP, Armada 38x and Armada 39x SoCs the limitation is 50MHz and
for the Armada 375 it is tclk/15.
Currently the armada-370-spi compatible is only used by the Armada 370
and the Armada XP device tree. On Armada 370, tclk cannot be higher
than 200MHz. In order to be able to handle both SoCs, we can take the
minimum of 50MHz and tclk/4.
A proper solution is adding a compatible string for each SoC, but it
can't be done as a fix for compatibility reason (we can't modify
device tree that have been already released) and it will be part of a
separate patch.
Fixes: df59fa7f4bca (spi: orion: support armada extended baud rates)
Reported-by: Kostya Porotchkin <kostap@marvell.com>
Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
Cc: <stable@vger.kernel.org>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions