From: <tthayer@opensource.altera.com>
To: <broonie@kernel.org>
Cc: <andriy.shevchenko@linux.intel.com>,
<jarkko.nikula@linux.intel.com>, <jszhang@marvell.com>,
<michael@smart-africa.com>, <kernel@mseidel.net>,
<linux-spi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<tthayer@opensource.altera.com>
Subject: [PATCHv2 1/2] Documentation: dt: spi: Add GPIO Slave Select Parameter
Date: Fri, 7 Oct 2016 09:56:33 -0500 [thread overview]
Message-ID: <1475852194-27690-1-git-send-email-tthayer@opensource.altera.com> (raw)
From: Thor Thayer <tthayer@opensource.altera.com>
Some SPI masters require the slave to be selected before a
transaction can occur - even in the case of GPIO chip select.
This patch adds a GPIO slave select parameter to indicate
the slave needs to be selected in the GPIO CS case.
Signed-off-by: Thor Thayer <tthayer@opensource.altera.com>
---
v2 Add to SPI framework - add bindings.
---
Documentation/devicetree/bindings/spi/spi-bus.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/spi/spi-bus.txt b/Documentation/devicetree/bindings/spi/spi-bus.txt
index 4b1d6e7..3a006bc 100644
--- a/Documentation/devicetree/bindings/spi/spi-bus.txt
+++ b/Documentation/devicetree/bindings/spi/spi-bus.txt
@@ -24,6 +24,7 @@ support describing the chip select layout.
Optional properties:
- cs-gpios - gpios chip select.
- num-cs - total number of chipselects.
+- gpio-ss - use internal slave select with gpio chip select.
If cs-gpios is used the number of chip selects will be increased automatically
with max(cs-gpios > hw cs).
--
1.7.9.5
next reply other threads:[~2016-10-07 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 14:56 tthayer [this message]
2016-10-07 14:56 ` [PATCHv2 2/2] spi: Add Flag to Enable Slave Select with GPIO Chip Select tthayer
2016-10-07 14:56 ` tthayer-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx
2016-10-07 19:33 ` [PATCHv2 1/2] Documentation: dt: spi: Add GPIO Slave Select Parameter Geert Uytterhoeven
2016-10-07 20:01 ` Thor Thayer
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=1475852194-27690-1-git-send-email-tthayer@opensource.altera.com \
--to=tthayer@opensource.altera.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=jszhang@marvell.com \
--cc=kernel@mseidel.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=michael@smart-africa.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.