Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1031336AbbD2FSa (ORCPT ); Wed, 29 Apr 2015 01:18:30 -0400 Received: from mail-ie0-f173.google.com ([209.85.223.173]:33225 "EHLO mail-ie0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751706AbbD2FSZ (ORCPT ); Wed, 29 Apr 2015 01:18:25 -0400 MIME-Version: 1.0 In-Reply-To: <1430209869-6631-2-git-send-email-eddie.huang@mediatek.com> References: <1430209869-6631-1-git-send-email-eddie.huang@mediatek.com> <1430209869-6631-2-git-send-email-eddie.huang@mediatek.com> Date: Wed, 29 Apr 2015 10:48:25 +0530 Message-ID: Subject: Re: [PATCH v6 1/3] dt-bindings: Add I2C bindings for mt65xx/mt81xx. From: rajeev kumar To: Eddie Huang Cc: Wolfram Sang , Matthias Brugger , Sascha Hauer , srv_heupstream@mediatek.com, Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Jean Delvare , David Box , Arnd Bergmann , Doug Anderson , Max Schwarz , Boris BREZILLON , Anders Berg , Neelesh Gupta , Lee Jones , Simon Glass , Jim Cromie , Wei Yan , Bjorn Andersson , Beniamino Galvani , Xudong Chen , Liguo Zhang , linux-i2c@vger.kernel.org, devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , linux-mediatek@lists.infradead.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3111 Lines: 74 On Tue, Apr 28, 2015 at 2:01 PM, Eddie Huang wrote: > From: Xudong Chen > > Add devicetree bindings for Mediatek Soc I2C driver. > > Signed-off-by: Xudong Chen > Signed-off-by: Eddie Huang > --- > .../devicetree/bindings/i2c/i2c-mt6577.txt | 41 ++++++++++++++++++++++ > 1 file changed, 41 insertions(+) > create mode 100644 Documentation/devicetree/bindings/i2c/i2c-mt6577.txt > > diff --git a/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt b/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt > new file mode 100644 > index 0000000..0ce6fa3 > --- /dev/null > +++ b/Documentation/devicetree/bindings/i2c/i2c-mt6577.txt > @@ -0,0 +1,41 @@ > +* Mediatek's I2C controller > + > +The Mediatek's I2C controller is used to interface with I2C devices. > + > +Required properties: > + - compatible: value should be either of the following. > + (a) "mediatek,mt6577-i2c", for i2c compatible with mt6577 i2c. > + (b) "mediatek,mt6589-i2c", for i2c compatible with mt6589 i2c. > + (c) "mediatek,mt8127-i2c", for i2c compatible with mt8127 i2c. > + (d) "mediatek,mt8135-i2c", for i2c compatible with mt8135 i2c. > + (e) "mediatek,mt8173-i2c", for i2c compatible with mt8173 i2c. > + - reg: physical base address of the controller and dma base, length of memory > + mapped region. > + - interrupts: interrupt number to the cpu. > + - clock-div: the fixed value for frequency divider of clock source in i2c > + module. Each IC may be different. > + - clocks: clock name from clock manager > + - clock-names: Must include "main" and "dma", if enable have-pmic need include > + "pmic" extra. > + > +Optional properties: > + - clock-frequency: Frequency in Hz of the bus when transfer, the default value > + is 100000. 100000 HZ ... > + - mediatek,have-pmic: platform can control i2c form special pmic side. > + Only mt6589 and mt8135 support this feature. > + - mediatek,use-push-pull: IO config use push-pull mode. > + > +Example: > + > + i2c0: i2c@1100d000 { > + compatible = "mediatek,mt6577-i2c"; > + reg = <0x1100d000 0x70>, > + <0x11000300 0x80>; > + interrupts = ; > + clock-frequency = <400000>; > + mediatek,have-pmic; > + clock-div = <16>; > + clocks = <&i2c0_ck>, <&ap_dma_ck>; > + clock-names = "main", "dma"; > + }; > + > -- > 1.8.1.1.dirty > > -- > To unsubscribe from this list: send the line "unsubscribe linux-i2c" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/