Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp3663997imj; Tue, 19 Feb 2019 07:23:23 -0800 (PST) X-Google-Smtp-Source: AHgI3IaYZMDkNWs06i0sjwndiXuvs8WQjyL9FzcCtybiMF3hyaw1cvNuhrAP2Ncc7yvw/+Xd0QSl X-Received: by 2002:a62:e082:: with SMTP id d2mr30840481pfm.240.1550589803844; Tue, 19 Feb 2019 07:23:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550589803; cv=none; d=google.com; s=arc-20160816; b=HpqW38aKX+fHP81rPT+NE89iPShdXPqqBva4RGbm3z/vjAwXGkW/96RKP4eS4ZEBWn 7/3RdTL5KiVrqW+5yhw8s9dxXtDUPCVTcDyDF8KP65aqhZRPSdJ3NoU81+XtKD7FooIM z3XvT29ebgv8xaCvILIyNlPwsYrIMEATVWIsdXDpeD7zki9Nhe+kZi//uSBVM8l42LHF 7QLTcln+kuVgdGwl5XP24sPb6ygKzCexYIqg0F5l8SINnnQKSfo7s3rxRq6UDiAu1bY+ M+hfNTFToa1dMXNcg5qD8rmyuP/j88dO2pPU//472gzEY1PocG6nIdquPRDfi8WAhCY6 bSTQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=RYUphA6WRgsVd1L1lT8RgSH/in3Q66Qiqbr8D8bfH8Y=; b=cCbJGpm5hT4an9xjgpudGmokwGbE+U+Wnp8CRYRpH9Kn056eMfRnT4XhQe3v4IvtQJ Aa7DCNtxdipl0lMWYJ7sPhGZz3ygcVITCIXu+ILbsLN2DqwRC2CeKMDkRga1dNcwdrxf LUXQTQSK1aecw1+Cb8gI4geUr8xigV+G0ZHvA0qr1tvlFCf3GRGKSzU1HYkuSnINbcVq TX5WoGt1lxcWQ22pWXGIUJiYxkR0xcdj2wUspiYYfV6OocV5pTtGsvQHXfUVFOPbLhEe 5l9S4zFBcR9e6/SNQ1jy2UHBurP/u14G+jVyhWl6LKbTKyvEj4sZxmOgeMWqn7s182f6 Uvjg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=fH2222xk; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e6si15309424pgk.201.2019.02.19.07.23.08; Tue, 19 Feb 2019 07:23:23 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=fH2222xk; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728246AbfBSPWL (ORCPT + 99 others); Tue, 19 Feb 2019 10:22:11 -0500 Received: from mail.kernel.org ([198.145.29.99]:36160 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726110AbfBSPWL (ORCPT ); Tue, 19 Feb 2019 10:22:11 -0500 Received: from mail-qt1-f177.google.com (mail-qt1-f177.google.com [209.85.160.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 8951821773; Tue, 19 Feb 2019 15:22:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1550589729; bh=nWrp3hRt+m/nWI1jpFziRhc1dk8W/7e+eu+0/lLsSuk=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=fH2222xkFAwQphhNO87XJwKnDMy6hs/hiOYFc7un/JyK0Dng3BcSyJWLXskIl/1j/ Y/RRpjwvzhecmFG/3r+jJvbxHYegf8MR8ev73KRu6AQLwinJ94EFXkr/9nshp4E9va u3t1+1esuPBWmd+wxQla7hyAkaNoKxz+h3yA/fyk= Received: by mail-qt1-f177.google.com with SMTP id d18so13455437qtg.12; Tue, 19 Feb 2019 07:22:09 -0800 (PST) X-Gm-Message-State: AHQUAub+Dj/pZ2q/uMGABxsCX28kO/H/Qlsv7tDVpp33EEpIgW8RVnEE bnoYLtmz5nZvJYPqSdYIJWVAAEmnddJcoo7Tdg== X-Received: by 2002:ac8:2f4e:: with SMTP id k14mr22638752qta.76.1550589728749; Tue, 19 Feb 2019 07:22:08 -0800 (PST) MIME-Version: 1.0 References: <1550210558-30516-1-git-send-email-erin.lo@mediatek.com> <1550210558-30516-4-git-send-email-erin.lo@mediatek.com> <20190218163211.GB2714@bogus> <1550544357.4739.32.camel@mhfsdcap03> In-Reply-To: <1550544357.4739.32.camel@mhfsdcap03> From: Rob Herring Date: Tue, 19 Feb 2019 09:21:57 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v7 3/6] dt-bindings: pinctrl: mt8183: add binding document To: Zhiyong Tao Cc: Erin Lo , Linus Walleij , Matthias Brugger , Mark Rutland , Thomas Gleixner , Jason Cooper , Marc Zyngier , Greg Kroah-Hartman , Stephen Boyd , devicetree@vger.kernel.org, srv_heupstream , "linux-kernel@vger.kernel.org" , "open list:SERIAL DRIVERS" , "moderated list:ARM/Mediatek SoC support" , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , Yingjoe Chen , Mars Cheng , Eddie Huang , linux-clk Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 18, 2019 at 8:46 PM Zhiyong Tao wrote: > > On Mon, 2019-02-18 at 10:32 -0600, Rob Herring wrote: > > On Fri, Feb 15, 2019 at 02:02:35PM +0800, Erin Lo wrote: > > > From: Zhiyong Tao > > > > > > The commit adds mt8183 compatible node in binding document. > > > > > > Signed-off-by: Zhiyong Tao > > > Signed-off-by: Erin Lo > > > --- > > > .../devicetree/bindings/pinctrl/pinctrl-mt8183.txt | 115 +++++++++++++++++++++ > > > 1 file changed, 115 insertions(+) > > > create mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-mt8183.txt > > > > > > diff --git a/Documentation/devicetree/bindings/pinctrl/pinctrl-mt8183.txt b/Documentation/devicetree/bindings/pinctrl/pinctrl-mt8183.txt > > > new file mode 100644 > > > index 0000000..364e673 > > > --- /dev/null > > > +++ b/Documentation/devicetree/bindings/pinctrl/pinctrl-mt8183.txt > > > @@ -0,0 +1,115 @@ > > > +* Mediatek MT8183 Pin Controller > > > + > > > +The Mediatek's Pin controller is used to control SoC pins. > > > + > > > +Required properties: > > > +- compatible: value should be one of the following. > > > + "mediatek,mt8183-pinctrl", compatible with mt8183 pinctrl. > > > +- gpio-controller : Marks the device node as a gpio controller. > > > +- #gpio-cells: number of cells in GPIO specifier. Since the generic GPIO > > > + binding is used, the amount of cells must be specified as 2. See the below > > > + mentioned gpio binding representation for description of particular cells. > > > +- gpio-ranges : gpio valid number range. > > > +- reg: physicall address base for gpio base registers. There are nine > > > + physicall address base in mt8183. They are 0x10005000, 0x11F20000, > > > + 0x11E80000, 0x11E70000, 0x11E90000, 0x11D30000, 0x11D20000, 0x11C50000, > > > + 0x11F30000. > > > > You don't need to list out each address, just what each address is. (Or > > just '9 GPIO base addresses'.) > > ==>ok, we will change it. > > > > > + > > > + Eg: <&pio 6 0> > > > > How is this an example of reg? Seems something is missing. > > > > > + <[phandle of the gpio controller node] > > > + [line number within the gpio controller] > > > + [flags]> > > > + > > > + Values for gpio specifier: > > > + - Line number: is a value between 0 to 202. > > > + - Flags: bit field of flags, as defined in . > > > + Only the following flags are supported: > > > + 0 - GPIO_ACTIVE_HIGH > > > + 1 - GPIO_ACTIVE_LOW > > > + > > > +Optional properties: > > > +- reg-names: gpio base register names. There are nine gpio base register > > > + names in mt8183. They are "iocfg0", "iocfg1", "iocfg2", "iocfg3", "iocfg4", > > > + "iocfg5", "iocfg6", "iocfg7", "iocfg8". > > > +- interrupt-controller: Marks the device node as an interrupt controller > > > +- #interrupt-cells: Should be two. > > > +- interrupts : The interrupt outputs from the controller. > > > > outputs? More than 1? If so, need to say what they are and the order. > > > ==> there is only use one interrupt in mt8183. we will change > "interrupts" to "interrupt" in v8. No, 'interrupts' is always plural. The problem is 'outputs'. Rob