linux-aspeed.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v4 0/4] gpio: aspeed: Fixes and support for sharing with co-processor
Date: Fri, 29 Jun 2018 14:11:15 +1000	[thread overview]
Message-ID: <20180629041119.5132-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
v3: - Adds Reviewed-by tags
v4: - Document the reason for including gpiolob.h
    - Expose GPIO offsets & bit number so coprocessor firmware doesn't
      have to hard-code them (allows multi-system generic firwmare
      that gets "configure" by the copro driver)

Please consider putting this in a topic branch so I can pull it
back into dependent series and point the reviewers to dependencies



             reply	other threads:[~2018-06-29  4:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-29  4:11 Benjamin Herrenschmidt [this message]
2018-06-29  4:11 ` [PATCH v4 1/4] gpio: aspeed: Rework register type accessors Benjamin Herrenschmidt
2018-06-29  4:11 ` [PATCH v4 2/4] gpio: aspeed: Add "Read Data" register to read the write latch Benjamin Herrenschmidt
2018-06-29  4:11 ` [PATCH v4 3/4] gpio: aspeed: Add command source registers Benjamin Herrenschmidt
2018-06-29  4:11 ` [PATCH v4 4/4] gpio: aspeed: Add interfaces for co-processor to grab GPIOs Benjamin Herrenschmidt
2018-07-02 14:13 ` [PATCH v4 0/4] gpio: aspeed: Fixes and support for sharing with co-processor Linus Walleij
2018-07-03  0:59   ` Benjamin Herrenschmidt

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=20180629041119.5132-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).