From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Subject: Re: [PATCH v2 2/2] dt-bindings: i2c: Update documentation for "mv78230-a0-i2c" Date: Thu, 5 Oct 2017 18:29:53 -0500 Message-ID: <20171005232953.gsxs6ecp6kopolf2@rob-hp-laptop> References: <20170928213605.22874-1-kalyan.kinthada@alliedtelesis.co.nz> <20170928213605.22874-3-kalyan.kinthada@alliedtelesis.co.nz> <87k20dmxw0.fsf@free-electrons.com> <20171005110820.phcjh7dmygi43dhq@ninjato> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20171005110820.phcjh7dmygi43dhq@ninjato> Sender: linux-i2c-owner@vger.kernel.org To: Wolfram Sang Cc: Gregory CLEMENT , Kalyan Kinthada , jason@lakedaemon.net, andrew@lunn.ch, sebastian.hesselbarth@gmail.com, mark.rutland@arm.com, linux@armlinux.org.uk, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org, Chris Packham List-Id: devicetree@vger.kernel.org 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 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 > > > > > > 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. Rob