From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>
Cc: Thomas Petazzoni
<thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>,
Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>,
stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Ezequiel Garcia
<ezequiel.garcia-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Gregory CLEMENT
<gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Sebastian Hesselbarth
<sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH v5 2/4] ARM: mvebu: Add quirk for i2c for the OpenBlocks AX3-4 board
Date: Fri, 10 Jan 2014 14:06:34 -0700 [thread overview]
Message-ID: <20140110210634.GL18269@obsidianresearch.com> (raw)
In-Reply-To: <20140110194550.GT19878-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
On Fri, Jan 10, 2014 at 02:45:50PM -0500, Jason Cooper wrote:
> > 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.
Right, absent guidance from the originators of the IP block that is
sort of all we are left with. But something like 'marvell,orion-sata'
is just a label to describe the ABI implemented by the HW on that
particular chip.
> 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?
I would stop thinking of this in terms of 'is newer' / 'is older'.
marvell,orion-sata means any HW that implements the same ABI as the
orion chip.
When we get a different chip that has a compatible, but extended ABI
we introduce a new label:
compatible = "marvell,foobar-sata", "marvell,orion-sata";
And if we get one that has a very similar, but incompatible ABI, we
still introduce a new label:
compatible = "marvell,foobar2-sata";
And everything works properly.
> > 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?
'mv78230-i2c' is the name that was picked to describe the ABI that
works as-documented in the manual
'mv78230-a0-i2c' is the name that was picked to describe the ABI that
works as-implemented in the A0 chip :)
There is no newer/older, they are just two different ABIs.
I guess it turns out that 'mv78230-a0-i2c' is a strict compatible
subset of 'mv78230-i2c' - but that doesn't really make a difference.
The 'mv78230-i2c' driver is guarenteed avaialble in all places where
the 'mv78230-a0-i2c' driver would be available.
Jason
WARNING: multiple messages have this Message-ID (diff)
From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
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 14:06:34 -0700 [thread overview]
Message-ID: <20140110210634.GL18269@obsidianresearch.com> (raw)
In-Reply-To: <20140110194550.GT19878@titan.lakedaemon.net>
On Fri, Jan 10, 2014 at 02:45:50PM -0500, Jason Cooper wrote:
> > 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.
Right, absent guidance from the originators of the IP block that is
sort of all we are left with. But something like 'marvell,orion-sata'
is just a label to describe the ABI implemented by the HW on that
particular chip.
> 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?
I would stop thinking of this in terms of 'is newer' / 'is older'.
marvell,orion-sata means any HW that implements the same ABI as the
orion chip.
When we get a different chip that has a compatible, but extended ABI
we introduce a new label:
compatible = "marvell,foobar-sata", "marvell,orion-sata";
And if we get one that has a very similar, but incompatible ABI, we
still introduce a new label:
compatible = "marvell,foobar2-sata";
And everything works properly.
> > 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?
'mv78230-i2c' is the name that was picked to describe the ABI that
works as-documented in the manual
'mv78230-a0-i2c' is the name that was picked to describe the ABI that
works as-implemented in the A0 chip :)
There is no newer/older, they are just two different ABIs.
I guess it turns out that 'mv78230-a0-i2c' is a strict compatible
subset of 'mv78230-i2c' - but that doesn't really make a difference.
The 'mv78230-i2c' driver is guarenteed avaialble in all places where
the 'mv78230-a0-i2c' driver would be available.
Jason
next prev parent reply other threads:[~2014-01-10 21:06 UTC|newest]
Thread overview: 66+ 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 ` Gregory CLEMENT
[not found] ` <1389193589-18485-1-git-send-email-gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
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 ` 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:06 ` Gregory CLEMENT
[not found] ` <1389193589-18485-3-git-send-email-gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-01-08 15:22 ` Wolfram Sang
2014-01-08 15:22 ` Wolfram Sang
2014-01-08 15:28 ` Gregory CLEMENT
2014-01-08 15:28 ` Gregory CLEMENT
2014-01-10 18:22 ` Jason Cooper
2014-01-10 18:22 ` Jason Cooper
2014-01-10 19:05 ` Jason Gunthorpe
2014-01-10 19:05 ` Jason Gunthorpe
2014-01-10 19:45 ` Jason Cooper
2014-01-10 19:45 ` Jason Cooper
2014-01-10 20:08 ` Jason Cooper
2014-01-10 20:08 ` Jason Cooper
2014-01-10 20:12 ` Gregory CLEMENT
2014-01-10 20:12 ` Gregory CLEMENT
[not found] ` <52D05439.7040905-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-01-10 21:14 ` Jason Cooper
2014-01-10 21:14 ` Jason Cooper
2014-01-10 21:21 ` Gregory CLEMENT
2014-01-10 21:21 ` Gregory CLEMENT
2014-01-10 21:37 ` Jason Cooper
2014-01-10 21:37 ` Jason Cooper
[not found] ` <20140110213752.GA19878-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2014-01-10 21:52 ` Gregory CLEMENT
2014-01-10 21:52 ` Gregory CLEMENT
2014-01-13 15:02 ` Gregory CLEMENT
2014-01-13 15:02 ` Gregory CLEMENT
[not found] ` <20140110194550.GT19878-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2014-01-10 20:09 ` Gregory CLEMENT
2014-01-10 20:09 ` Gregory CLEMENT
2014-01-10 21:11 ` Jason Cooper
2014-01-10 21:11 ` Jason Cooper
2014-01-10 21:06 ` Jason Gunthorpe [this message]
2014-01-10 21:06 ` Jason Gunthorpe
2014-01-10 21:19 ` Jason Cooper
2014-01-10 21:19 ` Jason Cooper
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 15:13 ` Arnd Bergmann
2014-01-08 15:06 ` [PATCH v5 3/4] i2c: mv64xxx: Fix " Gregory CLEMENT
2014-01-08 15:06 ` Gregory CLEMENT
2014-01-08 15:21 ` Wolfram Sang
2014-01-08 15:21 ` Wolfram Sang
2014-01-08 15:26 ` Gregory CLEMENT
2014-01-08 15:26 ` Gregory CLEMENT
2014-01-08 15:28 ` Arnd Bergmann
2014-01-08 15:28 ` Arnd Bergmann
2014-01-08 15:28 ` Wolfram Sang
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-08 15:06 ` Gregory CLEMENT
[not found] ` <1389193589-18485-5-git-send-email-gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-01-10 21:55 ` Jason Cooper
2014-01-10 21:55 ` Jason Cooper
[not found] ` <20140110215526.GB19878-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2014-01-10 23:04 ` Gregory CLEMENT
2014-01-10 23:04 ` Gregory CLEMENT
2014-01-08 16:46 ` [PATCH v5 0/4] Fix i2c bus hang on A0 version of the Armada XP SoCs Gregory CLEMENT
2014-01-08 16:46 ` Gregory CLEMENT
2014-01-14 2:14 ` Jason Cooper
2014-01-14 2:14 ` Jason Cooper
2014-01-14 8:46 ` Gregory CLEMENT
2014-01-14 8:46 ` Gregory CLEMENT
[not found] ` <52D4F966.6060200-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-01-20 11:20 ` Gregory CLEMENT
2014-01-20 11:20 ` Gregory CLEMENT
2014-01-20 14:44 ` Jason Cooper
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=20140110210634.GL18269@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=andrew-g2DYL2Zd6BY@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=ezequiel.garcia-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.