From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 4/4] ARM: dts: mvebu: Introduce a new compatible string for mv64xxx-i2c
Date: Fri, 21 Jun 2013 16:15:29 +0200 [thread overview]
Message-ID: <51C46001.30500@gmail.com> (raw)
In-Reply-To: <20130621140707.GO31667@titan.lakedaemon.net>
On 06/21/13 16:07, Jason Cooper wrote:
> On Fri, Jun 21, 2013 at 03:32:09PM +0200, Gregory CLEMENT wrote:
>> The mv64xxx-i2c embedded in the Armada XP have a new feature to
>> offload i2c transaction. This new version of the IP come also with
>> some errata. This lead to the introduction to a another compatible
>> string.
>>
>> This commit split the i2c information into armada-370.dtsi and
>> armada-xp.dtsi. Most of the data remains the same and stay in the
>> common file Armada-370-xp.dtsi. With this new feature the size of the
>> registers are bigger for Armada XP and the new compatible string is
>> used.
>>
>> The Device Tree binding documentation is updated accordingly.
>>
>> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
>> ---
>> Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt | 13 ++++++++++++-
>> arch/arm/boot/dts/armada-370-xp.dtsi | 2 --
>> arch/arm/boot/dts/armada-370.dtsi | 8 ++++++++
>> arch/arm/boot/dts/armada-xp.dtsi | 10 ++++++++++
>> 4 files changed, 30 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt b/Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt
>> index a1ee681..ce7af6a 100644
>> --- a/Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt
>> +++ b/Documentation/devicetree/bindings/i2c/i2c-mv64xxx.txt
>> @@ -4,7 +4,8 @@
>> Required properties :
>>
>> - reg : Offset and length of the register set for the device
>> - - compatible : Should be "marvell,mv64xxx-i2c"
>> + - compatible : Should be "marvell,mv64xxx-i2c" and "marvell,mv7230-i2c"
>> +for controller which support the I2C Transaction Generator
Jason, Gregory,
Also, s/mv7230/mv78230/
from a quick check of the patch set (which you forgot to send to LKML)
I am wondering why you didn't update the of matches struct with the new
compatible for "marvell,mv78230-i2c"? This will save you from still
having "marvell,mv64xxx-i2c" as additional compatible to match device
and driver. With that the above should also be s/and/or/.
>> - interrupts : The interrupt number
>>
>> Optional properties :
>> @@ -20,3 +21,13 @@ Examples:
>> interrupts = <29>;
>> clock-frequency = <100000>;
>> };
>> +
>> +For a controller which support the I2C Transaction Generator:
>> +
>> + i2c at 11000 {
>> + compatible = "marvell,mv64xxx-i2c", "marvell,mv78230-i2c";
>> + reg = <0x11000 0x100>;
>> + compatible = "marvell,mv64xxx-i2c";
>
> extra compatible line. If there's nothing else, I'll fix this up when I
> pull it in.
next prev parent reply other threads:[~2013-06-21 14:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 13:32 [PATCH v3 0/4] i2c-mv64xxx: Fixes and new feature for controlers embedded in Aramda XP Gregory CLEMENT
2013-06-21 13:32 ` [PATCH v3 1/4] i2c-mv64xxx: Set bus frequency to 100kHz if clock-frequency is not provided Gregory CLEMENT
2013-06-25 21:44 ` Wolfram Sang
2013-06-26 7:55 ` Gregory CLEMENT
2013-06-26 13:41 ` Wolfram Sang
2013-06-21 13:32 ` [PATCH v3 2/4] i2c-mv64xxx: Add I2C Transaction Generator support Gregory CLEMENT
2013-06-21 13:32 ` [PATCH v3 3/4] i2c-mv64xxx: Fix timing issue on Armada XP (errata FE-8471889) Gregory CLEMENT
2013-06-21 13:32 ` [PATCH v3 4/4] ARM: dts: mvebu: Introduce a new compatible string for mv64xxx-i2c Gregory CLEMENT
2013-06-21 14:07 ` Jason Cooper
2013-06-21 14:15 ` Sebastian Hesselbarth [this message]
2013-06-21 14:23 ` Gregory CLEMENT
2013-06-21 14:56 ` Jason Cooper
2013-06-21 15:03 ` Wolfram Sang
2013-06-21 15:06 ` Jason Cooper
2013-06-21 17:18 ` Jason Gunthorpe
2013-06-22 16:14 ` Sebastian Hesselbarth
2013-06-24 9:54 ` 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=51C46001.30500@gmail.com \
--to=sebastian.hesselbarth@gmail.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).