From: Mark Brown <broonie@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Sebastian Reichel <sebastian.reichel@collabora.co.uk>,
Rob Herring <robh@kernel.org>,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org, kernel@collabora.com
Subject: Re: [DISCUSSION] spi multi chipselect support
Date: Thu, 19 Jul 2018 14:25:12 +0100 [thread overview]
Message-ID: <20180719132512.GA27938@sirena.org.uk> (raw)
In-Reply-To: <c497b0e2-c663-fa29-dabc-6dd5ca26e0a4@metafoo.de>
[-- Attachment #1: Type: text/plain, Size: 477 bytes --]
On Wed, Jul 18, 2018 at 07:19:19PM +0200, Lars-Peter Clausen wrote:
> My preferred solution would to have something like
> i2c_new_secondary_device(), but for SPI. This way the driver that binds to
> the compatible string can allocate devices for additional chip selects as
> necessary. Also make use of the reg-names property the same way as in I2C.
Yes, that's at least the most consistent way forwards if nothing else.
I don't really have any more appealing ideas anyway.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-07-19 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 16:35 [DISCUSSION] spi multi chipselect support Sebastian Reichel
2018-07-18 17:19 ` Lars-Peter Clausen
2018-07-19 13:25 ` Mark Brown [this message]
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=20180719132512.GA27938@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.co.uk \
/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).