linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] spi: xilinx: Use standard num-cs binding
Date: Fri, 27 Mar 2015 10:53:18 -0700	[thread overview]
Message-ID: <20150327175318.GG1743@sirena.org.uk> (raw)
In-Reply-To: <2a81c738-f7e2-4387-b04c-05c9892ba8e4@BN1AFFO11FD026.protection.gbl>

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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150327/fcc8a0f3/attachment-0001.sig>

  reply	other threads:[~2015-03-27 17:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16 12:55 [PATCH] spi: xilinx: Use standard num-cs binding Michal Simek
2015-02-12  9:45 ` Michal Simek
     [not found] ` <CAHTX3dJRGhwo7FW+VJxfEJmx-9FdjFN5EnxG0RRDfMOm3=VU4A@mail.gmail.com>
     [not found]   ` <20150214053543.GL9110@finisterre.sirena.org.uk>
2015-02-23 10:22     ` Michal Simek
2015-02-24 14:52       ` Mark Brown
2015-03-08 19:00 ` Mark Brown
2015-03-27 10:55   ` Michal Simek
2015-03-27 17:53     ` Mark Brown [this message]
2015-03-30  6:46       ` Michal Simek
2015-03-31  5:47         ` Mark Brown
2015-03-31  8:16           ` Michal Simek
2015-03-31 11:16             ` Mark Brown
2015-03-31 11:25               ` Michal Simek
2015-03-31 12:24                 ` Mark Brown

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=20150327175318.GG1743@sirena.org.uk \
    --to=broonie@kernel.org \
    --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).