From: sr@denx.de (Stefan Roese)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: mvebu: armada-370-xp: Add MBus mappings for all SPI devices
Date: Thu, 7 Apr 2016 14:02:17 +0200 [thread overview]
Message-ID: <1460030537-10054-2-git-send-email-sr@denx.de> (raw)
In-Reply-To: <1460030537-10054-1-git-send-email-sr@denx.de>
This patch adds the static MBus mappings for all supported SPI devices
(8 per controller) for the direct access SPI mode. They can be configured
and enabled by setting these MBus mapping in the 'ranges' property of the
per-board 'soc' node. If nothing is changed here, the default 'normal'
(indirect) SPI mode is used.
Signed-off-by: Stefan Roese <sr@denx.de>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Gregory CLEMENT <gregory.clement@free-electrons.com>
Cc: Andrew Lunn <andrew@lunn.ch>
Cc: Jason Cooper <jason@lakedameon.net>
Cc: Mark Brown <broonie@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>
---
arch/arm/boot/dts/armada-370-xp.dtsi | 20 ++++++++++++++++++--
1 file changed, 18 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/armada-370-xp.dtsi b/arch/arm/boot/dts/armada-370-xp.dtsi
index a0903cd..c3ebf88 100644
--- a/arch/arm/boot/dts/armada-370-xp.dtsi
+++ b/arch/arm/boot/dts/armada-370-xp.dtsi
@@ -302,7 +302,15 @@
};
spi0: spi at 10600 {
- reg = <MBUS_ID(0xf0, 0x01) 0x10600 0x28>;
+ reg = <MBUS_ID(0xf0, 0x01) 0x10600 0x28 /* control */
+ MBUS_ID(0x01, 0x1e) 0 0x100000 /* CS0 */
+ MBUS_ID(0x01, 0x5e) 0 0x100000 /* CS1 */
+ MBUS_ID(0x01, 0x9e) 0 0x100000 /* CS2 */
+ MBUS_ID(0x01, 0xde) 0 0x100000 /* CS3 */
+ MBUS_ID(0x01, 0x1f) 0 0x100000 /* CS4 */
+ MBUS_ID(0x01, 0x5f) 0 0x100000 /* CS5 */
+ MBUS_ID(0x01, 0x9f) 0 0x100000 /* CS6 */
+ MBUS_ID(0x01, 0xdf) 0 0x100000>; /* CS7 */
#address-cells = <1>;
#size-cells = <0>;
cell-index = <0>;
@@ -312,7 +320,15 @@
};
spi1: spi at 10680 {
- reg = <MBUS_ID(0xf0, 0x01) 0x10680 0x28>;
+ reg = <MBUS_ID(0xf0, 0x01) 0x10680 0x28 /* control */
+ MBUS_ID(0x01, 0x1a) 0 0x100000 /* CS0 */
+ MBUS_ID(0x01, 0x5a) 0 0x100000 /* CS1 */
+ MBUS_ID(0x01, 0x9a) 0 0x100000 /* CS2 */
+ MBUS_ID(0x01, 0xda) 0 0x100000 /* CS3 */
+ MBUS_ID(0x01, 0x1b) 0 0x100000 /* CS4 */
+ MBUS_ID(0x01, 0x5b) 0 0x100000 /* CS5 */
+ MBUS_ID(0x01, 0x9b) 0 0x100000 /* CS6 */
+ MBUS_ID(0x01, 0xdb) 0 0x100000>; /* CS7 */
#address-cells = <1>;
#size-cells = <0>;
cell-index = <1>;
--
2.8.1
prev parent reply other threads:[~2016-04-07 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 12:02 [PATCH 1/2] ARM: dts: mvebu: A37x/XP/38x/39x: Move SPI controller nodes into 'soc' node Stefan Roese
2016-04-07 12:02 ` Stefan Roese [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=1460030537-10054-2-git-send-email-sr@denx.de \
--to=sr@denx.de \
--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;
as well as URLs for NNTP newsgroup(s).