linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] dt-bindings: mediatek: Modify pinctrl bindings for mt2701
Date: Fri, 27 Nov 2015 14:38:00 -0600	[thread overview]
Message-ID: <20151127203800.GA9092@rob-hp-laptop> (raw)
In-Reply-To: <1448527472-20651-3-git-send-email-biao.huang@mediatek.com>

On Thu, Nov 26, 2015 at 04:44:29PM +0800, Biao Huang wrote:
> Signed-off-by: Biao Huang <biao.huang@mediatek.com>
> ---
>  .../devicetree/bindings/pinctrl/pinctrl-mt65xx.txt |    9 +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/pinctrl/pinctrl-mt65xx.txt b/Documentation/devicetree/bindings/pinctrl/pinctrl-mt65xx.txt
> index 0480bc3..ca6a27a 100644
> --- a/Documentation/devicetree/bindings/pinctrl/pinctrl-mt65xx.txt
> +++ b/Documentation/devicetree/bindings/pinctrl/pinctrl-mt65xx.txt
> @@ -4,10 +4,11 @@ The Mediatek's Pin controller is used to control SoC pins.
>  
>  Required properties:
>  - compatible: value should be one of the following.
> -    (a) "mediatek,mt8135-pinctrl", compatible with mt8135 pinctrl.
> -    (b) "mediatek,mt8173-pinctrl", compatible with mt8173 pinctrl.
> -    (c) "mediatek,mt6397-pinctrl", compatible with mt6397 pinctrl.
> -    (d) "mediatek,mt8127-pinctrl", compatible with mt8127 pinctrl.
> +    (a) "mediatek,mt2701-pinctrl", compatible with mt2701 pinctrl.
> +    (b) "mediatek,mt6397-pinctrl", compatible with mt6397 pinctrl.
> +    (c) "mediatek,mt8135-pinctrl", compatible with mt8135 pinctrl.
> +    (d) "mediatek,mt8173-pinctrl", compatible with mt8173 pinctrl.
> +    (e) "mediatek,mt8127-pinctrl", compatible with mt8127 pinctrl.

If you were trying to sort these, they still aren't quite sorted. There 
is no point in sorting if you number (or letter) them because you will 
have to update many lines on any change. So drop the (a), (b), (c), etc.

Rob

>  - pins-are-numbered: Specify the subnodes are using numbered pinmux to
>    specify pins.
>  - gpio-controller : Marks the device node as a gpio controller.
> -- 
> 1.7.9.5
> 

  reply	other threads:[~2015-11-27 20:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-26  8:44 [PATCH 0/5] pinctrl: mediatek: add pinctrl/GPIO/EINT driver for mt2701 Biao Huang
2015-11-26  8:44 ` [PATCH 1/5] ARM: mediatek: Add MT2701 config options for mediatek SoCs Biao Huang
2015-12-09 22:44   ` Linus Walleij
2015-11-26  8:44 ` [PATCH 2/5] dt-bindings: mediatek: Modify pinctrl bindings for mt2701 Biao Huang
2015-11-27 20:38   ` Rob Herring [this message]
2015-12-08 10:56     ` biao huang
2015-11-26  8:44 ` [PATCH 3/5] pinctrl: dt bindings: Add pinfunc header file " Biao Huang
2015-12-09 22:47   ` Linus Walleij
2015-11-26  8:44 ` [PATCH 4/5] pinctrl: mediatek: Add Pinctrl/GPIO/EINT driver " Biao Huang
2015-12-09 22:52   ` Linus Walleij
2015-12-10  2:34     ` biao huang
2015-11-26  8:44 ` [PATCH 5/5] arm: dts: Add pinctrl/GPIO/EINT node " Biao Huang
2015-12-09 22:48   ` Linus Walleij

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151127203800.GA9092@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).