From: iivanov@mm-sol•com (Ivan T. Ivanov)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC V2 00/12] i2c: describe adapter quirks in a generic way
Date: Thu, 05 Mar 2015 15:27:05 +0200 [thread overview]
Message-ID: <1425562025.5705.24.camel@mm-sol.com> (raw)
In-Reply-To: <1424880126-15047-1-git-send-email-wsa@the-dreams.de>
On Wed, 2015-02-25 at 17:01 +0100, Wolfram Sang wrote:
> From: Wolfram Sang <wsa+renesas@sang-engineering•com>
>
> Here is the second version of the patch series to describe i2c adapter quirks
> in a generic way. For the motivation, please read description of patch 1. This
> is still RFC because I would like to do some more tests on my own, but I need
> to write a tool for that. However, I'd really like to have the driver authors
> to have a look already. Actual testing is very much appreciated. Thanks to the
> Mediatek guys for rebasing their new driver to this framework. That helps, too!
>
> The branch is also here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/quirks
>
> Thanks,
>
> Wolfram
>
> Major changes since V1:
>
> * more fine-grained options to describe modes with combined messages.
> This should also cover the Mediatek HW now as well as all other
> permutations I can think of.
>
> * the core code and at91 driver had to be refactored to reflect the
> above change
>
> * added the bcm-iproc driver which came to mainline recently
>
> Wolfram Sang (12):
> i2c: add quirk structure to describe adapter flaws
> i2c: add quirk checks to core
> i2c: at91: make use of the new infrastructure for quirks
> i2c: opal: make use of the new infrastructure for quirks
> i2c: qup: make use of the new infrastructure for quirks
>
For QUP driver.
Reviewed-by: Ivan T. Ivanov <iivanov@mm-sol•com>
Tested-by: Ivan T. Ivanov <iivanov@mm-sol•com>
Thanks,
Ivan
next prev parent reply other threads:[~2015-03-05 13:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 16:01 [RFC V2 00/12] i2c: describe adapter quirks in a generic way Wolfram Sang
2015-02-25 16:01 ` [RFC V2 01/12] i2c: add quirk structure to describe adapter flaws Wolfram Sang
2015-02-25 16:01 ` [RFC V2 02/12] i2c: add quirk checks to core Wolfram Sang
2015-02-25 16:01 ` [RFC V2 03/12] i2c: at91: make use of the new infrastructure for quirks Wolfram Sang
2015-03-08 8:28 ` Wolfram Sang
2015-03-09 16:11 ` Ludovic Desroches
2015-03-10 13:55 ` Ludovic Desroches
2015-03-12 14:50 ` Wolfram Sang
2015-02-25 16:01 ` [RFC V2 04/12] i2c: opal: " Wolfram Sang
2015-03-10 17:13 ` Neelesh Gupta
2015-03-10 23:12 ` Benjamin Herrenschmidt
2015-03-11 4:26 ` Neelesh Gupta
2015-03-12 14:55 ` Wolfram Sang
2015-02-25 16:01 ` [RFC V2 05/12] i2c: qup: " Wolfram Sang
2015-02-25 16:01 ` [RFC V2 06/12] i2c: cpm: " Wolfram Sang
2015-02-25 16:01 ` [RFC V2 07/12] i2c: axxia: " Wolfram Sang
2015-02-25 16:01 ` [RFC V2 08/12] i2c: dln2: " Wolfram Sang
2015-02-25 16:02 ` [RFC V2 09/12] i2c: powermac: " Wolfram Sang
2015-02-25 16:02 ` [RFC V2 10/12] i2c: viperboard: " Wolfram Sang
2015-02-25 16:02 ` [RFC V2 11/12] i2c: pmcmsp: " Wolfram Sang
2015-02-25 16:02 ` [RFC V2 12/12] i2c: bcm-iproc: " Wolfram Sang
2015-02-26 23:32 ` Ray Jui
2015-03-12 14:56 ` Wolfram Sang
2015-03-05 13:27 ` Ivan T. Ivanov [this message]
2015-03-12 14:56 ` [RFC V2 00/12] i2c: describe adapter quirks in a generic way Wolfram Sang
2015-03-14 11:14 ` Wolfram Sang
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=1425562025.5705.24.camel@mm-sol.com \
--to=iivanov@mm-sol$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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