From: Christer Weinigel <christer@weinigel.se>
To: linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org
Cc: Christer Weinigel <christer@weinigel.se>,
Mark Brown <broonie@kernel.org>
Subject: [PATCH] devicetree - document using aliases to set spi bus number.
Date: Tue, 24 May 2016 18:39:20 +0200 [thread overview]
Message-ID: <1464107960-10775-1-git-send-email-christer@weinigel.se> (raw)
Document how to use devicetree aliases to assign a stable
bus number to a spi bus.
Signed-off-by: Christer Weinigel <christer@weinigel.se>
---
Trivial documentation change.
Not having used devicetree that much it was surprisingly hard to
figure out how to assign a stable bus number to a spi bus. Add a
simple example that shows how to do that.
Mark Cced as the SPI maintainer. Or should trivial documentation
fixes like this be addressed to someone else?
/Christer
Documentation/devicetree/bindings/spi/spi-bus.txt | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/Documentation/devicetree/bindings/spi/spi-bus.txt b/Documentation/devicetree/bindings/spi/spi-bus.txt
index 42d5954..c35c4c2 100644
--- a/Documentation/devicetree/bindings/spi/spi-bus.txt
+++ b/Documentation/devicetree/bindings/spi/spi-bus.txt
@@ -94,3 +94,13 @@ SPI example for an MPC5200 SPI bus:
reg = <1>;
};
};
+
+Normally SPI buses are assigned dynamic bus numbers starting at 32766
+and counting downwards. It is possible to assign the bus number
+statically using devicetee aliases. For example, on the MPC5200 the
+"spi@f00" device above is connected to the "soc" bus. To set its
+bus_num to 1 add an aliases entry like this:
+
+ aliases {
+ spi1 = "/soc/spi@f00";
+ };
--
1.9.1
next reply other threads:[~2016-05-24 16:47 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 16:39 Christer Weinigel [this message]
2016-05-24 17:20 ` Mark Brown
2016-05-24 18:03 ` Christer Weinigel
2016-05-24 18:32 ` Mark Brown
2016-05-24 18:57 ` Christer Weinigel
2016-05-25 12:19 ` Mark Rutland
2016-05-25 12:50 ` Mark Brown
2016-05-25 12:33 ` Mark Brown
2016-05-24 23:34 ` Frank Rowand
2016-05-25 0:18 ` Frank Rowand
2016-05-25 17:49 ` Rob Herring
2016-05-25 18:03 ` Mark Brown
2016-05-25 18:06 ` Frank Rowand
2016-05-25 18:44 ` Mark Brown
2016-05-26 1:10 ` Christer Weinigel
2016-05-26 1:44 ` Rob Herring
2016-05-26 1:56 ` Christer Weinigel
2016-05-26 10:07 ` Mark Brown
2016-05-26 10:58 ` Christer Weinigel
2016-05-26 18:47 ` Mark Brown
2016-05-26 21:04 ` Christer Weinigel
2016-05-27 16:43 ` Mark Brown
2016-05-24 17:41 ` Mark Rutland
2016-05-24 20:41 ` Frank Rowand
2016-05-25 9:20 ` Mark Rutland
2016-05-25 10:38 ` Mark Brown
2016-05-25 11:20 ` Christer Weinigel
2016-05-25 12:34 ` Mark Rutland
2016-05-25 13:08 ` Mark Brown
2016-05-25 15:32 ` Frank Rowand
2016-05-25 15:59 ` Mark Rutland
2016-05-25 16:21 ` Frank Rowand
2016-05-25 18:02 ` Mark Brown
2016-05-25 17:48 ` Mark Brown
2016-05-25 18:46 ` Frank Rowand
2016-05-27 18:36 ` Mark Brown
2016-05-28 20:57 ` Christer Weinigel
2016-05-30 16:13 ` Mark Brown
2016-05-25 15:25 ` Frank Rowand
2016-05-25 16:06 ` Mark Rutland
2016-05-25 16:31 ` Frank Rowand
2016-05-25 18:44 ` Rob Herring
2016-05-25 18:48 ` Mark Brown
2016-05-26 8:21 ` Geert Uytterhoeven
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=1464107960-10775-1-git-send-email-christer@weinigel.se \
--to=christer@weinigel.se \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.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
all inboxes | Powered by JetHome®