From: Chris Packham <chris.packham@alliedtelesis.co.nz>
To: wsa@the-dreams.de, linux-i2c@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: [PATCH 0/4] i2c: pca-platform: updates
Date: Tue, 13 Jun 2017 13:56:37 +1200 [thread overview]
Message-ID: <20170613015641.29373-1-chris.packham@alliedtelesis.co.nz> (raw)
We're using a PCA9564 on an embedded platform to provide an i2c
controller. This adds devicetree support and I've included some
cleanups for the driver while I was at it.
Chris Packham (4):
i2c: pca-platform: add devicetree awareness
i2c: pca-platform: use gpio_is_valid
i2c: pca-platform: use device managed allocations
i2c: pca-platform: use dev_warn/dev_info instead of printk
.../devicetree/bindings/i2c/i2c-pca-platform.txt | 18 ++++
drivers/i2c/busses/i2c-pca-platform.c | 96 +++++++++-------------
2 files changed, 56 insertions(+), 58 deletions(-)
create mode 100644 Documentation/devicetree/bindings/i2c/i2c-pca-platform.txt
--
2.13.0
next reply other threads:[~2017-06-13 1:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 1:56 Chris Packham [this message]
[not found] ` <20170613015641.29373-1-chris.packham-6g8wRflRTwXFdCa3tKVlE6U/zSkkHjvu@public.gmane.org>
2017-06-13 1:56 ` [PATCH 1/4] i2c: pca-platform: add devicetree awareness Chris Packham
2017-06-13 4:38 ` Chris Packham
2017-06-18 14:04 ` Rob Herring
2017-06-13 1:56 ` [PATCH 2/4] i2c: pca-platform: use gpio_is_valid Chris Packham
2017-06-13 1:56 ` [PATCH 3/4] i2c: pca-platform: use device managed allocations Chris Packham
2017-06-13 1:56 ` [PATCH 4/4] i2c: pca-platform: use dev_warn/dev_info instead of printk Chris Packham
2017-06-19 15:01 ` [PATCH 0/4] i2c: pca-platform: updates Wolfram Sang
2017-06-19 20:50 ` Chris Packham
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=20170613015641.29373-1-chris.packham@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).