From: Mark Brown <broonie@kernel.org>
To: Harini Katakam <harinikatakamlinux@gmail.com>
Cc: Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
linux-spi@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] devicetree: Add devicetree bindings documentation for Cadence SPI
Date: Fri, 4 Apr 2014 15:42:44 +0100 [thread overview]
Message-ID: <20140404144244.GV14763@sirena.org.uk> (raw)
In-Reply-To: <CAFcVEC+FAAxxxxA8PgcTzLU5UFu=pkDEM4Li06dRmEwA95sz_g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
On Fri, Apr 04, 2014 at 07:38:14PM +0530, Harini Katakam wrote:
> OK. I understand.
> Can you comment on the case where a decoder is used?
> There is support for adding a decoder where extended slaves can be selected
> through the IP's control register.
> (This is not currently implemented in the driver but will be in the future.)
> How should the driver know whether it is 4 or 16 select lines for example?
> This has to be written to master->num_chipselect.
That's the sort of case where it's useful yes - depending on how the
implementation is done it may be sensible to just have a property
specifying if a decoder is there (if it just changes the encoding in the
register for example).
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-04-04 14:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 11:10 [PATCH v2 1/2] SPI: Add driver for Cadence SPI controller Harini Katakam
2014-04-03 11:10 ` [PATCH v2 2/2] devicetree: Add devicetree bindings documentation for Cadence SPI Harini Katakam
2014-04-03 21:34 ` Mark Brown
2014-04-04 3:00 ` Harini Katakam
2014-04-04 8:09 ` Geert Uytterhoeven
2014-04-04 11:16 ` Michal Simek
2014-04-04 10:09 ` Mark Brown
2014-04-04 12:14 ` Harini Katakam
2014-04-04 12:24 ` Peter Crosthwaite
2014-04-04 12:39 ` Harini Katakam
2014-04-04 12:46 ` Mark Brown
2014-04-04 14:08 ` Harini Katakam
2014-04-04 14:30 ` Harini Katakam
2014-04-04 23:14 ` Peter Crosthwaite
2014-04-05 6:05 ` Harini Katakam
2014-04-05 23:43 ` Peter Crosthwaite
2014-04-07 7:46 ` Harini Katakam
2014-04-04 14:42 ` Mark Brown [this message]
2014-04-04 14:49 ` Harini Katakam
2014-04-03 21:43 ` [PATCH v2 1/2] SPI: Add driver for Cadence SPI controller Mark Brown
2014-04-04 3:49 ` Harini Katakam
2014-04-04 9:04 ` sourav
2014-04-04 9:24 ` sourav
2014-04-04 10:02 ` Michal Simek
2014-04-04 22:58 ` Peter Crosthwaite
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=20140404144244.GV14763@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=harinikatakamlinux@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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®