From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org
Subject: Re: spi-oc-tiny.c and microwatt chip select
Date: Sat, 06 Jun 2020 23:02:46 +1000 [thread overview]
Message-ID: <06ac360bfb039a71bd4048954af3c3300a54a3c6.camel@kernel.crashing.org> (raw)
In-Reply-To: <20200606113716.GA2055@sirena.org.uk>
On Sat, 2020-06-06 at 12:37 +0100, Mark Brown wrote:
> On Sat, Jun 06, 2020 at 06:50:37PM +1000, Benjamin Herrenschmidt
> wrote:
>
> > Now as for chip-selects... I could also add some concept of GPIOs,
> > write a simple MMIO GPIO controller etc... or I could for now make
> > my
> > life easier and send a patch adding an extra register to control
> > chip
> > select to spi-oc-tiny.c keyd off a device-tree property (or the
> > compatible property) :-)
> > Any objection to the "easy/fast" way :-) ?
>
> That sounds fine (I'd go with a different compatible).
Great ! Thanks.
Cheers,
Ben.
prev parent reply other threads:[~2020-06-06 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 8:50 spi-oc-tiny.c and microwatt chip select Benjamin Herrenschmidt
2020-06-06 11:37 ` Mark Brown
2020-06-06 13:02 ` Benjamin Herrenschmidt [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=06ac360bfb039a71bd4048954af3c3300a54a3c6.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=broonie@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;
as well as URLs for NNTP newsgroup(s).