summaryrefslogtreecommitdiffstats
path: root/drivers/spi/spidev.c
diff options
context:
space:
mode:
authorGregory CLEMENT <gregory.clement@free-electrons.com>2015-05-26 11:44:42 +0200
committerMark Brown <broonie@kernel.org>2015-05-26 11:35:10 +0100
commitce2f6ea1cbd41d78224f703af980a6ceeb0eb56a (patch)
tree632b8057399f954fb12ec9a2923a08efc1401963 /drivers/spi/spidev.c
parentb787f68c36d49bb1d9236f403813641efa74a031 (diff)
downloadtalos-obmc-linux-ce2f6ea1cbd41d78224f703af980a6ceeb0eb56a.tar.gz
talos-obmc-linux-ce2f6ea1cbd41d78224f703af980a6ceeb0eb56a.zip
spi: orion: Fix maximum baud rates for Armada 370/XP
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>
Diffstat (limited to 'drivers/spi/spidev.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud