From: Jeremy Kerr <jk@ozlabs.org>
To: linux-kernel@vger.kernel.org
Cc: Joel Stanley <joel@jms.id.au>,
Christopher Bostic <cbostic@linux.vnet.ibm.com>,
Jeremy Kerr <jk@ozlabs.org>
Subject: [PATCH 0/3] Add 'external mode' for GPIO-based FSI master
Date: Mon, 19 Jun 2017 17:26:42 +0800 [thread overview]
Message-ID: <1497864405-26990-1-git-send-email-jk@ozlabs.org> (raw)
This series (on top of current char-misc-next) implements "external
mode" (ie, support for FSI debug devices) for the GPIO-based FSI master
driver.
We implement this control in the GPIO master driver, as it has the
mapping of raw GPIO pins to fsi control signals, and provides a
mechanism for the kernel to retain exclusive access to those GPIOs.
Cheers,
Jeremy
---
Jeremy Kerr (3):
fsi: Add fsi_master_rescan()
fsi/master-gpio: Add locking around gpio operations during break &
link enable
fsi/master-gpio: Add external mode
.../ABI/testing/sysfs-driver-fsi-master-gpio | 10 +++
drivers/fsi/fsi-core.c | 9 ++-
drivers/fsi/fsi-master-gpio.c | 85 +++++++++++++++++++++-
drivers/fsi/fsi-master.h | 2 +
4 files changed, 102 insertions(+), 4 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-driver-fsi-master-gpio
--
2.7.4
next reply other threads:[~2017-06-19 9:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 9:26 Jeremy Kerr [this message]
2017-06-19 9:26 ` [PATCH 1/3] fsi: Add fsi_master_rescan() Jeremy Kerr
2017-06-20 2:59 ` [PATCH v2 " Jeremy Kerr
2017-06-19 9:26 ` [PATCH 2/3] fsi/master-gpio: Add locking around gpio operations during break & link enable Jeremy Kerr
2017-06-19 9:26 ` [PATCH 3/3] fsi/master-gpio: Add external mode Jeremy Kerr
2017-06-19 17:17 ` kbuild test robot
2017-06-21 6:01 ` Joel Stanley
2017-06-21 22:07 ` Jeremy Kerr
2017-06-21 22:10 ` [PATCH v2 " Jeremy Kerr
2018-01-30 4:45 ` Joel Stanley
2017-09-04 6:55 ` [PATCH 0/3] Add 'external mode' for GPIO-based FSI master Joel Stanley
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=1497864405-26990-1-git-send-email-jk@ozlabs.org \
--to=jk@ozlabs.org \
--cc=cbostic@linux.vnet.ibm.com \
--cc=joel@jms.id.au \
--cc=linux-kernel@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®