linux-kernel - Re: [PATCH] spi: xilinx: Use standard num-cs binding

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 27 Mar 2015 10:53:18 -0700
From:	Mark Brown <broonie@...nel.org>
To:	Michal Simek <michal.simek@...inx.com>
Cc:	linux-kernel@...r.kernel.org, monstr@...str.eu,
	Sören Brinkmann <soren.brinkmann@...inx.com>,
	linux-spi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] spi: xilinx: Use standard num-cs binding

On Fri, Mar 27, 2015 at 11:55:49AM +0100, Michal Simek wrote:

Please fix your mail client to word wrap within paragraphs at less than
80 columns - this makes your mails easier to read and reply to.

> On 03/08/2015 08:00 PM, Mark Brown wrote:
> > On Fri, Jan 16, 2015 at 01:55:14PM +0100, Michal Simek wrote:
> >> Use standard num-cs binding property and setup
> >> "xlnx,num-ss-bits" as deprecated.

> > Why?  These properties mean different things - num-cs is a bit confused
> > and is the total number of available chip selects for the system (which
> > could include GPIOs) while num-ss-bits is the size of the bitfield
> > (which could include things not actually mapped out properly/successfully 
> > or something if the hardware designers were feeling particularly inspired).

> I was checking meaning of num-ss-bits and meaning is Number of slaves (taking
> explanation from Vivado 2014.4) Range 1-32.
> http://www.xilinx.com/support/documentation/ip_documentation/axi_spi/v1_02_a/axi_spi_ds742.pdf
> Table 1 - page 4

> Checking through the hw design every pin is connected to device to do chip select.
> That's why I think that num-cs (based on spi-bus.txt) is the right property.

Remember that we can at least in theory have additional chip selects
that aren't controlled by the IP block but are instead GPIOs.  There's
also some potential confusion for users between the number of chip
selects in use in a given system and the size of the bitfield that the
driver needs to take care of.

> > I'm not convinced num-cs ever made any sense.

> Does it mean that num-cs property used by 11 SPI drivers is just incorrect?

> Based on Documentation/devicetree/bindings/spi/spi-bus.txt it is the part of binding
> - num-cs : total number of chipselects

> Please let me know what you think.

I don't think it has any value.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)