From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: mvebu: Add the i2c-bridge capability to the mv64xxx-i2c
Date: Fri, 7 Jun 2013 20:50:15 +0200 [thread overview]
Message-ID: <20130607205015.0a6d6bfd@skate> (raw)
In-Reply-To: <20130607180941.GW23859@titan.lakedaemon.net>
Dear Jason Cooper,
On Fri, 7 Jun 2013 14:09:41 -0400, Jason Cooper wrote:
> > +- i2c,i2c-bridge : This flag indicate that the i2c controller have the
> > + Transaction Generator support and we want to use it. Not all the
> > + mv64xxx controller have this feature.
>
> Do you have a list of which controllers definitely do, or definitely
> don't? That would be helpful for folks adding new boards.
As mentioned in the first commit log:
""
This feature is currently only available on Armada XP, so usage of
this mechanism is activated through device tree.
""
So Armada XP is the only to have that, for now. We can probably assume
future Marvell SoC may also have this feature, but we don't know for
sure.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-06-07 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 15:42 [PATCH 0/2] i2c-mv64xxx: Add I2C Transaction Generator support Gregory CLEMENT
2013-06-07 15:42 ` [PATCH 1/2] " Gregory CLEMENT
2013-06-07 16:21 ` Thomas Petazzoni
2013-06-07 19:57 ` Russell King - ARM Linux
2013-06-07 15:42 ` [PATCH 2/2] ARM: dts: mvebu: Add the i2c-bridge capability to the mv64xxx-i2c Gregory CLEMENT
2013-06-07 17:03 ` Maxime Ripard
2013-06-07 18:09 ` Jason Cooper
2013-06-07 18:50 ` Thomas Petazzoni [this message]
2013-06-07 19:52 ` Russell King - ARM Linux
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=20130607205015.0a6d6bfd@skate \
--to=thomas.petazzoni@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).