From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759884AbaLLCka (ORCPT ); Thu, 11 Dec 2014 21:40:30 -0500 Received: from mailgw02.mediatek.com ([210.61.82.184]:37037 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1756958AbaLLCk1 (ORCPT ); Thu, 11 Dec 2014 21:40:27 -0500 X-Listener-Flag: 11101 Subject: Re: [PATCH v3 0/2] ARM: mediatek: Add driver for Mediatek I2C controller From: Yingjoe Chen To: Wolfram Sang CC: Liguo Zhang , Xudong Chen , Mark Rutland , Russell King , Pawel Moll , , Ian Campbell , Linus Walleij , YH Chen , , Grant Likely , , Rob Herring , Arnd Bergmann , , Sascha Hauer , Kumar Gala , Matthias Brugger , Nathan Chung , Eddie Huang , Jean Delvare , In-Reply-To: <20141127164536.GC5667@katana> References: <1416821928-11453-1-git-send-email-xudong.chen@mediatek.com> <20141124121555.GG3733@katana> <1417096856.12707.59.camel@mtksdaap41> <20141127164536.GC5667@katana> Content-Type: text/plain; charset="UTF-8" Date: Fri, 12 Dec 2014 10:40:22 +0800 Message-ID: <1418352022.4994.44.camel@mtksdaap41> MIME-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit X-MTK: N Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2014-11-27 at 17:45 +0100, Wolfram Sang wrote: > > > I think there are now 3 drivers in my queue which are not fully I2C > > > compatible but more supporting the very minimum to, say, read an eeprom. > > > I am not feeling well to allow them to use I2C_FUNC_I2C. So, I want to > > > think about ways how to communicate deficiencies like "only 255 byte" or > > > "only WRRD messages" to users of that I2C controller. This is most > > > likely not happening before 3.19. But assistance is very welcome. Hi Wolfram, We've started upstream work for MT8173[1]. We've fixed these issues for new SoC, and we believe it is fully I2C compatible now. We'll add mt8173 support to this driver, so this driver will support both fully I2C compatible SoC and the current one. Joe.C [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-December/309847.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yingjoe Chen Subject: Re: [PATCH v3 0/2] ARM: mediatek: Add driver for Mediatek I2C controller Date: Fri, 12 Dec 2014 10:40:22 +0800 Message-ID: <1418352022.4994.44.camel@mtksdaap41> References: <1416821928-11453-1-git-send-email-xudong.chen@mediatek.com> <20141124121555.GG3733@katana> <1417096856.12707.59.camel@mtksdaap41> <20141127164536.GC5667@katana> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20141127164536.GC5667@katana> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Wolfram Sang Cc: Mark Rutland , Linus Walleij , linux-i2c@vger.kernel.org, Jean Delvare , Xudong Chen , Russell King , Arnd Bergmann , YH Chen , Liguo Zhang , Nathan Chung , Grant Likely , devicetree@vger.kernel.org, Pawel Moll , Ian Campbell , Rob Herring , Matthias Brugger , Eddie Huang , linux-arm-kernel@lists.infradead.org, srv_heupstream@mediatek.com, linux-kernel@vger.kernel.org, Sascha Hauer , Kumar Gala List-Id: devicetree@vger.kernel.org On Thu, 2014-11-27 at 17:45 +0100, Wolfram Sang wrote: > > > I think there are now 3 drivers in my queue which are not fully I2C > > > compatible but more supporting the very minimum to, say, read an eeprom. > > > I am not feeling well to allow them to use I2C_FUNC_I2C. So, I want to > > > think about ways how to communicate deficiencies like "only 255 byte" or > > > "only WRRD messages" to users of that I2C controller. This is most > > > likely not happening before 3.19. But assistance is very welcome. Hi Wolfram, We've started upstream work for MT8173[1]. We've fixed these issues for new SoC, and we believe it is fully I2C compatible now. We'll add mt8173 support to this driver, so this driver will support both fully I2C compatible SoC and the current one. Joe.C [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-December/309847.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: yingjoe.chen@mediatek.com (Yingjoe Chen) Date: Fri, 12 Dec 2014 10:40:22 +0800 Subject: [PATCH v3 0/2] ARM: mediatek: Add driver for Mediatek I2C controller In-Reply-To: <20141127164536.GC5667@katana> References: <1416821928-11453-1-git-send-email-xudong.chen@mediatek.com> <20141124121555.GG3733@katana> <1417096856.12707.59.camel@mtksdaap41> <20141127164536.GC5667@katana> Message-ID: <1418352022.4994.44.camel@mtksdaap41> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, 2014-11-27 at 17:45 +0100, Wolfram Sang wrote: > > > I think there are now 3 drivers in my queue which are not fully I2C > > > compatible but more supporting the very minimum to, say, read an eeprom. > > > I am not feeling well to allow them to use I2C_FUNC_I2C. So, I want to > > > think about ways how to communicate deficiencies like "only 255 byte" or > > > "only WRRD messages" to users of that I2C controller. This is most > > > likely not happening before 3.19. But assistance is very welcome. Hi Wolfram, We've started upstream work for MT8173[1]. We've fixed these issues for new SoC, and we believe it is fully I2C compatible now. We'll add mt8173 support to this driver, so this driver will support both fully I2C compatible SoC and the current one. Joe.C [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-December/309847.html