From: Mark Brown <broonie@kernel.org>
To: Ben Whitten <ben.whitten@gmail.com>
Cc: linux-spi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] spi: add spi multiplexing functions for dt
Date: Wed, 24 Jan 2018 14:54:30 +0000 [thread overview]
Message-ID: <20180124145430.GD9366@sirena.org.uk> (raw)
In-Reply-To: <CAF3==it=5_YQVJ9xg8CLzSPw7LQZbCHQHfsufYwwCb=n7x3L0g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
On Wed, Jan 24, 2018 at 02:01:55PM +0000, Ben Whitten wrote:
> On 23 January 2018 at 11:11, Mark Brown <broonie@kernel.org> wrote:
> > level. Things that have their own transfer function would be better off
> > just being first order SPI controllers I think so that they get access
> > to everything the framework offers and can correctly advertise
> > capabilities and so on.
> This runs as a very simple fake SPI controller per bus that the mux is
> controlling. Having this custom transfer message allowed me to pop
> in the way my device exposes the downstream devices, through its
> regmap.
Which like I say is a problem - if your device (which just sounds like a
SPI controller) has different capabilities and constraints to the parent
then client drivers won't see that.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-01-24 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 22:51 [RFC] Add ability to multiplex SPI bus Ben Whitten
2018-01-22 22:51 ` [RFC] spi: add spi multiplexing functions for dt Ben Whitten
2018-01-23 11:11 ` Mark Brown
2018-01-24 14:01 ` Ben Whitten
2018-01-24 14:54 ` Mark Brown [this message]
2018-01-25 15:54 ` Ben Whitten
2018-01-23 10:46 ` [RFC] Add ability to multiplex SPI bus 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=20180124145430.GD9366@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ben.whitten@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.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®