From: Phil Reid <preid@electromag.com.au>
To: jarkko.nikula@linux.intel.com, andriy.shevchenko@linux.intel.com,
mika.westerberg@linux.intel.com, wsa@the-dreams.de,
tim@krieglstein.org, linux-i2c@vger.kernel.org
Cc: Phil Reid <preid@electromag.com.au>
Subject: [PATCH v2 0/2] i2c: designware: add i2c gpio recovery option
Date: Fri, 16 Jun 2017 15:42:55 +0800 [thread overview]
Message-ID: <1497598977-37622-1-git-send-email-preid@electromag.com.au> (raw)
Changes from V1:
- In review Andy suggested change the i2c core to use the gpiod
I've added a patch that allows the gradual switching of drivers
to using gpiod interface. The old interface is preserved so
that changes can be made incrementally.
- I've update Tim's patch for the designware driver to use the new
interface. Tweaked a couple of things to his patch and fixed
up things Andy id in last review.
The core changes in p1 don't require the get/set scl/sda functions.
Hopefully I've done the right thing with preserving authorship and
signoff.
Phil Reid (1):
i2c: Switch to using gpiod interface for gpio bus recovery
Tim Sander (1):
i2c: designware: add i2c gpio recovery option
drivers/i2c/busses/i2c-designware-core.c | 12 ++++--
drivers/i2c/busses/i2c-designware-core.h | 1 +
drivers/i2c/busses/i2c-designware-platdrv.c | 58 +++++++++++++++++++++++++++++
drivers/i2c/i2c-core-base.c | 22 +++++++++--
include/linux/i2c.h | 2 +
5 files changed, 88 insertions(+), 7 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-06-16 7:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 7:42 Phil Reid [this message]
2017-06-16 7:42 ` [PATCH v2 1/2] i2c: Switch to using gpiod interface for gpio bus recovery Phil Reid
2017-06-16 7:42 ` [PATCH v2 2/2] i2c: designware: add i2c gpio recovery option Phil Reid
2017-08-24 9:21 ` [PATCH v2 0/2] " Phil Reid
2017-08-24 11:59 ` Andy Shevchenko
2017-08-29 16:28 ` Andy Shevchenko
2017-08-30 6:18 ` Phil Reid
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=1497598977-37622-1-git-send-email-preid@electromag.com.au \
--to=preid@electromag.com.au \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=tim@krieglstein.org \
--cc=wsa@the-dreams.de \
/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).