From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 2/4] ARM: mvebu: Add quirk for i2c for the OpenBlocks AX3-4 board
Date: Fri, 10 Jan 2014 22:21:29 +0100 [thread overview]
Message-ID: <52D06459.5000403@free-electrons.com> (raw)
In-Reply-To: <20140110211417.GX19878@titan.lakedaemon.net>
On 10/01/2014 22:14, Jason Cooper wrote:
> On Fri, Jan 10, 2014 at 09:12:41PM +0100, Gregory CLEMENT wrote:
>> Jason,
>> On 10/01/2014 21:08, Jason Cooper wrote:
>>> On Fri, Jan 10, 2014 at 02:45:50PM -0500, Jason Cooper wrote:
>>>> On Fri, Jan 10, 2014 at 12:05:21PM -0700, Jason Gunthorpe wrote:
>>>>> On Fri, Jan 10, 2014 at 01:22:40PM -0500, Jason Cooper wrote:
>>>>>
>>>>>> Do we create new compatible strings to indicate errata, or to indicate
>>>>>> 'from this version forward there are new features'? The former would
>>>>>> indicate as Gregory has written '...-a0-i2c', the latter would warrant
>>>>>> '...-b0-i2c' and disabling offloading if we don't see '...-b0-i2c'.
>>>>
>>>> s/-b0-i2c'./-b0-i2c' or newer./
>>>>
>>>>> IMHO the compatible string should represent a specific HW/SW ABI. So
>>>>> you need a unique compatible string for every variation of that ABI.
>>>>
>>>> My concern is that we tend to do things like "marvell,orion-sata" for
>>>> the first version of the IP block we can work with. orion5x, kirkwood,
>>>> dove, and armada 370/xp all use that compatible string to refer to that
>>>> IP block.
>>>>
>>>> Given that we look at it as 'and newer', '...-a0-i2c' would mean no
>>>> offloading until we introduce '-b0-i2c'. Or am I mis-understanding what
>>>> you're saying?
>>>>
>>>>> We already have a compatible string defined for the ABI that B0
>>>>> presents.
>>>>
>>>> So 'mv78230-i2c' is newer than 'mv78230-a0-i2c', or are you referring to
>>>> something else?
>>>
>>> I think the crux of it is: Is mv78230-i2c the first, or the default?
>>
>> Here it's clearly the default
>
> So we should default to no offloading when we see it? Since it has been
> deployed referring to -a0 revision i2c IP blocks?
>
But this assumption is wrong as I already wrote few days ago, mv78230-i2c
has been deployed referring to -b0 revision i2c IP blocks since the begining.
It was developed on and for B0 version, and this compatible was created for
this specific version. It was latter that we realized that it was not fully
compatible with A0. But for sure:
mv78230-i2c == I2C IP running on Armada XP B0 (or latter)
> thx,
>
> Jason.
>
--
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-10 21:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 15:06 [PATCH v5 0/4] Fix i2c bus hang on A0 version of the Armada XP SoCs Gregory CLEMENT
2014-01-08 15:06 ` [PATCH v5 1/4] ARM: mvebu: Add support to get the ID and the revision of a SoC Gregory CLEMENT
2014-01-08 15:06 ` [PATCH v5 2/4] ARM: mvebu: Add quirk for i2c for the OpenBlocks AX3-4 board Gregory CLEMENT
2014-01-08 15:22 ` Wolfram Sang
2014-01-08 15:28 ` Gregory CLEMENT
2014-01-10 18:22 ` Jason Cooper
2014-01-10 19:05 ` Jason Gunthorpe
2014-01-10 19:45 ` Jason Cooper
2014-01-10 20:08 ` Jason Cooper
2014-01-10 20:12 ` Gregory CLEMENT
2014-01-10 21:14 ` Jason Cooper
2014-01-10 21:21 ` Gregory CLEMENT [this message]
2014-01-10 21:37 ` Jason Cooper
2014-01-10 21:52 ` Gregory CLEMENT
2014-01-13 15:02 ` Gregory CLEMENT
2014-01-10 20:09 ` Gregory CLEMENT
2014-01-10 21:11 ` Jason Cooper
2014-01-10 21:06 ` Jason Gunthorpe
2014-01-10 21:19 ` Jason Cooper
2014-01-08 15:06 ` [PATCH v5 3/4] i2c: mv64xxx: Fix bus hang on A0 version of the Armada XP SoCs Gregory CLEMENT
2014-01-08 15:21 ` Wolfram Sang
2014-01-08 15:26 ` Gregory CLEMENT
2014-01-08 15:28 ` Arnd Bergmann
2014-01-08 15:28 ` Wolfram Sang
2014-01-08 15:06 ` [PATCH v5 4/4] i2c: mv64xxx: Document the newly introduced Armada XP A0 compatible Gregory CLEMENT
2014-01-10 21:55 ` Jason Cooper
2014-01-10 23:04 ` Gregory CLEMENT
2014-01-08 15:13 ` [PATCH v5 0/4] Fix i2c bus hang on A0 version of the Armada XP SoCs Arnd Bergmann
2014-01-08 16:46 ` Gregory CLEMENT
2014-01-14 2:14 ` Jason Cooper
2014-01-14 8:46 ` Gregory CLEMENT
2014-01-20 11:20 ` Gregory CLEMENT
2014-01-20 14:44 ` Jason Cooper
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=52D06459.5000403@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).