From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v2 0/4] gpio: aspeed: Fixes and support for sharing with co-processor
Date: Mon, 18 Jun 2018 14:53:48 +1000 [thread overview]
Message-ID: <20180618045352.9489-1-benh@kernel.crashing.org> (raw)
This series cleans up the register accessors a bit, adds missing ones,
fixes the access to the write latch and finally adds an interface
that a co-processor driver can use to change the owner of some of
the GPIO lines and arbitrate access to shared GPIO banks.
v2: - Address Joel comments
NOTE: I haven't changed the inclusion of gpio/consumer.h and gpiolib.h
as, according to my replies, I do actually need them. I'm happy
to use an alternative if somebody can suggest a reasonable one.
next reply other threads:[~2018-06-18 4:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 4:53 Benjamin Herrenschmidt [this message]
2018-06-18 4:53 ` [PATCH v2 1/4] gpio: aspeed: Rework register type accessors Benjamin Herrenschmidt
2018-06-18 5:38 ` Joel Stanley
2018-06-18 5:55 ` Andrew Jeffery
2018-06-18 4:53 ` [PATCH v2 2/4] gpio: aspeed: Add "Read Data" register to read the write latch Benjamin Herrenschmidt
2018-06-18 5:38 ` Joel Stanley
2018-06-18 13:38 ` Andrew Jeffery
2018-06-18 13:49 ` Benjamin Herrenschmidt
2018-06-18 4:53 ` [PATCH v2 3/4] gpio: aspeed: Add command source registers Benjamin Herrenschmidt
2018-06-18 5:38 ` Joel Stanley
2018-06-18 6:14 ` Andrew Jeffery
2018-06-18 4:53 ` [PATCH v2 4/4] gpio: aspeed: Add interfaces for co-processor to grab GPIOs Benjamin Herrenschmidt
2018-06-18 5:38 ` Joel Stanley
2018-06-18 14:23 ` Andrew Jeffery
2018-06-18 14:38 ` Benjamin Herrenschmidt
2018-06-19 0:36 ` Benjamin Herrenschmidt
2018-06-19 0:38 ` Andrew Jeffery
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=20180618045352.9489-1-benh@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).