From: Wolfram Sang <wsa@the-dreams.de>
To: linux-i2c@vger.kernel.org
Cc: linux-sh@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
Simon Horman <horms@verge.net.au>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Andrey Danin <danindrey@mail.ru>,
Stephen Warren <swarren@wwwdotorg.org>
Subject: Re: [PATCH 00/10] i2c: improve i2c client address spaces and their DT support
Date: Fri, 14 Aug 2015 20:22:12 +0200 [thread overview]
Message-ID: <20150814182210.GA1822@katana> (raw)
In-Reply-To: <1439066007-13951-1-git-send-email-wsa@the-dreams.de>
On Sat, Aug 08, 2015 at 10:33:17PM +0200, Wolfram Sang wrote:
> Here is the updated RFC series ready for submission. This gives the i2c core
> seperate address spaces for standard clients, 10 bit clients, and our own slave
> clients. So, you can now have a 7 bit slave at 0x50 and a 10 bit slave at
> 0x050. Or, you can have a slave driver listening at some address and at the
> same time have a client driver talking to this address. Note that this is only
> the core support for that separation, I am still not sure if there is hardware
> being able talking to its own slave address, but we will see. The RFC had DT
> support, this series also has support for that when instantiating via sysfs at
> runtime.
>
> Changes since RFC:
>
> * dropped the patches for Tegra slave support. I couldn't get them to work
> and we found out that they need further changes. Tests have now been
> performed with a Renesas Lager board
> * the hardcoded arbitrary offsets have now been #defined. Other than that,
> patches 1-7 which also have been in the RFC stayed the same.
> * patch 8 adds support for the new flags in sysfs
> * patch 9 gives some extra warning for users in case of a misconfiguration
> * patch 10 finally introduces a binding documentation for generic i2c
> bindings. Finally, at last, hooray!
> * tags from Andrey and Stephen have been added, thanks a lot!
>
> Please comment, review...
>
> Thanks,
>
> Wolfram
>
>
> Wolfram Sang (10):
> dt-bindings: add header for generic I2C flags in bindings
> i2c: add a flag to mark clients as slaves
> i2c: apply address offset for slaves, too
> i2c: rename address check functions
> i2c: make address check indpendent from client struct
> i2c: apply DT flags when probing
> i2c: take address space into account when checking for used addresses
> i2c: support 10 bit and slave addresses in sysfs 'new_device'
> i2c: slave: print warning if slave flag not set
> i2c: dt: describe generic bindings
>
> Documentation/devicetree/bindings/i2c/i2c.txt | 33 ++++++++++
> Documentation/i2c/slave-interface | 9 ++-
> Documentation/i2c/ten-bit-addresses | 4 ++
Applied to for-next, thanks!
prev parent reply other threads:[~2015-08-14 18:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 20:33 [PATCH 00/10] i2c: improve i2c client address spaces and their DT support Wolfram Sang
2015-08-08 20:33 ` [PATCH 01/10] dt-bindings: add header for generic I2C flags in bindings Wolfram Sang
2015-08-08 20:33 ` [PATCH 02/10] i2c: add a flag to mark clients as slaves Wolfram Sang
[not found] ` <1439066007-13951-1-git-send-email-wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
2015-08-08 20:33 ` [PATCH 03/10] i2c: apply address offset for slaves, too Wolfram Sang
2015-08-08 20:33 ` [PATCH 09/10] i2c: slave: print warning if slave flag not set Wolfram Sang
2015-08-08 20:33 ` [PATCH 04/10] i2c: rename address check functions Wolfram Sang
2015-08-08 20:33 ` [PATCH 05/10] i2c: make address check indpendent from client struct Wolfram Sang
2015-08-08 20:33 ` [PATCH 06/10] i2c: apply DT flags when probing Wolfram Sang
2015-08-08 20:33 ` [PATCH 07/10] i2c: take address space into account when checking for used addresses Wolfram Sang
2015-08-08 20:33 ` [PATCH 08/10] i2c: support 10 bit and slave addresses in sysfs 'new_device' Wolfram Sang
2015-08-10 13:17 ` Geert Uytterhoeven
2015-08-10 14:00 ` Wolfram Sang
2015-08-08 20:33 ` [PATCH 10/10] i2c: dt: describe generic bindings Wolfram Sang
2015-08-09 9:51 ` Vaibhav Hiremath
2015-08-09 12:15 ` Wolfram Sang
2015-08-09 12:17 ` Vaibhav Hiremath
2015-08-14 18:22 ` Wolfram Sang [this message]
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=20150814182210.GA1822@katana \
--to=wsa@the-dreams.de \
--cc=danindrey@mail.ru \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=swarren@wwwdotorg.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).