From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 3/3] i2c: mv64xxx: Document the newly introduced Armada XP A0 compatible
Date: Thu, 02 Jan 2014 17:34:52 +0100 [thread overview]
Message-ID: <52C5952C.5050707@free-electrons.com> (raw)
In-Reply-To: <20140101214552.GB19878@titan.lakedaemon.net>
On 01/01/2014 22:45, Jason Cooper wrote:
> [+ DT ml, Grant, Rob]
>
> On Tue, Dec 31, 2013 at 05:44:53PM +0100, Gregory CLEMENT wrote:
>> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
>> ---
>> Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt b/Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt
>> index 82e8f6f17179..9410ed72ec45 100644
>> --- a/Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt
>> +++ b/Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt
>> @@ -5,7 +5,7 @@ Required properties :
>>
>> - reg : Offset and length of the register set for the device
>> - compatible : Should be "marvell,mv64xxx-i2c" or "allwinner,sun4i-i2c"
>> - or "marvell,mv78230-i2c"
>> + or "marvell,mv78230-i2c" or "marvell,mv78230-a0-i2c"
>
> Once we nail down how we want to do this, Please add an explanation of
> the differences between the compatibles. eg 'offloading broken'.
>
Just to keep the DT mailing list, Grant and Rob in touch: I have
submitted an other series in which we don't have to use the device
tree to know the SoC revision. So if everything turns well we won't
have to apply this series.
If at the end we still need it, then I will add the explanation in
the next version.
Gregory
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2014-01-02 16:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 16:44 [RFC PATCH 0/3] Fix i2c bus hang on A0 version of the Armada XP SoCs Gregory CLEMENT
2013-12-31 16:44 ` [RFC PATCH 1/3] arm: mvebu: add new dts file for old variant of Openblocks AX3-4 Gregory CLEMENT
2014-01-01 21:41 ` Jason Cooper
2014-01-01 21:42 ` Jason Cooper
2014-01-02 16:17 ` Gregory CLEMENT
2013-12-31 16:44 ` [RFC PATCH 2/3] i2c: mv64xxx: Fix bus hang on A0 version of the Armada XP SoCs Gregory CLEMENT
2013-12-31 16:44 ` [RFC PATCH 3/3] i2c: mv64xxx: Document the newly introduced Armada XP A0 compatible Gregory CLEMENT
2014-01-01 21:44 ` Jason Cooper
2014-01-01 21:45 ` Jason Cooper
2014-01-02 16:34 ` Gregory CLEMENT [this message]
2014-01-01 19:28 ` [RFC PATCH 0/3] Fix i2c bus hang on A0 version of the Armada XP SoCs Andrew Lunn
2014-01-02 16:22 ` Gregory CLEMENT
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=52C5952C.5050707@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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).