[PATCH v2 2/2] dt-bindings: i2c: Update documentation for "mv78230-a0-i2c"

Wolfram Sang wsa at the-dreams.de
Sun Nov 5 04:54:19 PST 2017


On Thu, Oct 05, 2017 at 06:29:53PM -0500, Rob Herring wrote:
> On Thu, Oct 05, 2017 at 01:08:20PM +0200, Wolfram Sang wrote:
> > On Mon, Oct 02, 2017 at 04:23:43PM +0200, Gregory CLEMENT wrote:
> > > Hi Wolfram,
> > >  
> > >  On ven., sept. 29 2017, Kalyan Kinthada <kalyan.kinthada at alliedtelesis.co.nz> wrote:
> > > 
> > > > This commit modifies the documentation for
> > > > "marvell,mv78230-a0-i2c" compatible string.
> > > >
> > > > The "marvell,mv78230-a0-i2c" compatible string enables the workaround
> > > > for an i2c repeated start timing violation, but unlike
> > > > "marvell,mv78230-i2c" it disables the i2c offload support. This is
> > > > applicable to a number of SoCs such as early revisions of the Armada XP
> > > > and the Armada 38x.
> > > >
> > > > Signed-off-by: Kalyan Kinthada <kalyan.kinthada at alliedtelesis.co.nz>
> > > 
> > > 
> > > I applied the dt fix on my mvebu/fixes branch. Do you want to apply this
> > > one on your branch, or do you prefer I take it. In this case an acked-by
> > > would be nice.
> > 
> > I'd prefer to take it. What I'd really like to see here is an ack from
> > Rob because of the previous discussion of an earlier revision of this
> > patch.
> 
> I'm confused how mv78230 relates to Armada XP or 38x... I don't really 
> want to know either. If normal compatible string conventions were 
> followed then I wouldn't have to.

Is this a NAK or "annoyed, but don't really care"? ;)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20171105/e334224e/attachment.sig>


More information about the linux-arm-kernel mailing list