On Thu, Jan 15, 2015 at 11:07:12AM +1000, Ken Wilson wrote:
> I agree that we could support any sane chip select for a slave, since the
> slave addresses do need
> to be explicitly defined. I'm happy with whatever your preference is.
Just accepting anything seems easier both for users and in
impl
On 15/01/15 06:06, Mark Brown wrote:
On Mon, Jan 12, 2015 at 01:14:00PM +1000, Ken Wilson wrote:
+- num-cs : The total number of chip selects used by this platform.
+ If unset, this defaults to 1.
So, this is intended to be the number of hardware chip selects that can
be con
On Mon, Jan 12, 2015 at 01:14:00PM +1000, Ken Wilson wrote:
> +- num-cs : The total number of chip selects used by this platform.
> + If unset, this defaults to 1.
So, this is intended to be the number of hardware chip selects that can
be configured but the first commit mentioned
This commit adds support for multiple hardware chip selects to spi-orion.
The number of supported chip selects varies based on the SoC and pin
configuration, so it is set using the num-cs device tree binding.
Signed-off-by: Ken Wilson
---
Documentation/devicetree/bindings/spi/spi-orion.txt | 3
4 matches
Mail list logo
