From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v3 4/4] gpio: aspeed: Add interfaces for co-processor to grab GPIOs
Date: Thu, 28 Jun 2018 16:33:18 +1000 [thread overview]
Message-ID: <c8a71b3f23b2039fa1a7b28d5f1f91cb6c6870f8.camel@kernel.crashing.org> (raw)
In-Reply-To: <20180622020448.6102-5-benh@kernel.crashing.org>
On Fri, 2018-06-22 at 12:04 +1000, Benjamin Herrenschmidt wrote:
> On the Aspeed chip, the GPIOs can be under control of the ARM
> chip or of the ColdFire coprocessor. (There's a third command
> source, the LPC bus, which we don't use or support yet).
At the risk of offending people even more, I'm going to respin
this with another extra Aspeed specific interface to retrieve
a given GPIO registers and bit number.
So far, I've made the corprocessor code system specific, effectively
hard wiring in the binary the above. But I found a way to make it
more flexible without losing too much performance, thus drastically
simplifying deployment for us since every machine out there seems
to be wiring these things differently.
However, for that to work, after "grabbing" the GPIOs, the coprocessor
driver will need to give the data and write data latch registers and
bit numbers to the microcode.
I'll respin a v4 with that added interface in the form of a separate
patch at the end of the series.
Cheers,
Ben.
prev parent reply other threads:[~2018-06-28 6:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 2:04 [PATCH v3 0/4] gpio: aspeed: Fixes and support for sharing with co-processor Benjamin Herrenschmidt
2018-06-22 2:04 ` [PATCH v3 1/4] gpio: aspeed: Rework register type accessors Benjamin Herrenschmidt
2018-06-22 2:04 ` [PATCH v3 2/4] gpio: aspeed: Add "Read Data" register to read the write latch Benjamin Herrenschmidt
2018-06-22 2:04 ` [PATCH v3 3/4] gpio: aspeed: Add command source registers Benjamin Herrenschmidt
2018-06-22 2:04 ` [PATCH v3 4/4] gpio: aspeed: Add interfaces for co-processor to grab GPIOs Benjamin Herrenschmidt
2018-06-28 6:33 ` 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=c8a71b3f23b2039fa1a7b28d5f1f91cb6c6870f8.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=linux-aspeed@lists.ozlabs.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).