From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarkko Nikula Subject: Re: [PATCH v3 0/6] Add support for MSCC Ocelot i2c Date: Tue, 7 Aug 2018 17:10:11 +0300 Message-ID: References: <20180806185412.7210-1-alexandre.belloni@bootlin.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20180806185412.7210-1-alexandre.belloni@bootlin.com> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Alexandre Belloni , Wolfram Sang , James Hogan Cc: Paul Burton , Andy Shevchenko , Mika Westerberg , linux-i2c@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mips@linux-mips.org, Thomas Petazzoni , Allan Nielsen List-Id: devicetree@vger.kernel.org On 08/06/2018 09:54 PM, Alexandre Belloni wrote: > Hello, > > Because the designware IP was not able to handle the SDA hold time before > version 1.11a, MSCC has its own implementation. Add support for it and then add > i2c on ocelot boards. > > I would expect patches 1 to 4 to go through the i2c tree and 5-6 through > the mips tree once patch 4 has been reviewed by the DT maintainers. > For the patches 1-4/6 that touch i2c-designware: Tested-by: Jarkko Nikula Acked-by: Jarkko Nikula I tested acpi_match_device() conversion to device_get_match_data() didn't affect MODEL_CHERRYTRAIL case and quick test that i2c communication continue working.