[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqJ=ocVCQig4cQKrF3nrYWg+ou9yu+USs201vHUS-O8GFQ@mail.gmail.com>
Date: Thu, 30 Nov 2017 14:24:15 -0600
From: Rob Herring <robh@...nel.org>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
Mark Rutland <mark.rutland@....com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linus Walleij <linus.walleij@...aro.org>,
Randy Dunlap <rdunlap@...radead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] dt-bindings: pinctrl: uniphier: add UniPhier pinctrl binding
On Tue, Nov 28, 2017 at 9:44 PM, Masahiro Yamada
<yamada.masahiro@...ionext.com> wrote:
> Hi Rob,
>
>
> 2017-11-29 0:27 GMT+09:00 Rob Herring <robh@...nel.org>:
>> On Tue, Nov 28, 2017 at 04:49:45PM +0900, Masahiro Yamada wrote:
>>> The driver has been in the tree for a while, but its binding document
>>> is missing. Hence, here it is.
>>>
>>> Signed-off-by: Masahiro Yamada <yamada.masahiro@...ionext.com>
>>> ---
>>>
>>> .../pinctrl/socionext,uniphier-pinctrl.txt | 27 ++++++++++++++++++++++
>>> MAINTAINERS | 1 +
>>> 2 files changed, 28 insertions(+)
>>> create mode 100644 Documentation/devicetree/bindings/pinctrl/socionext,uniphier-pinctrl.txt
>>>
>>> diff --git a/Documentation/devicetree/bindings/pinctrl/socionext,uniphier-pinctrl.txt b/Documentation/devicetree/bindings/pinctrl/socionext,uniphier-pinctrl.txt
>>> new file mode 100644
>>> index 0000000..8173b12
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/pinctrl/socionext,uniphier-pinctrl.txt
>>> @@ -0,0 +1,27 @@
>>> +UniPhier SoCs pin controller
>>> +
>>> +Required properties:
>>> +- compatible: should be one of the following:
>>> + "socionext,uniphier-ld4-pinctrl" - for LD4 SoC
>>> + "socionext,uniphier-pro4-pinctrl" - for Pro4 SoC
>>> + "socionext,uniphier-sld8-pinctrl" - for sLD8 SoC
>>> + "socionext,uniphier-pro5-pinctrl" - for Pro5 SoC
>>> + "socionext,uniphier-pxs2-pinctrl" - for PXs2 SoC
>>> + "socionext,uniphier-ld6b-pinctrl" - for LD6b SoC
>>> + "socionext,uniphier-ld11-pinctrl" - for LD11 SoC
>>> + "socionext,uniphier-ld20-pinctrl" - for LD20 SoC
>>> + "socionext,uniphier-pxs3-pinctrl" - for PXs3 SoC
>>> +
>>> +Note:
>>> +The UniPhier pinctrl should be a subnode of a "syscon" compatible node.
>>> +
>>> +Example:
>>> + soc-glue@...00000 {
>>> + compatible = "socionext,uniphier-pro4-soc-glue",
>>> + "simple-mfd", "syscon";
>>> + reg = <0x5f800000 0x2000>;
>>> +
>>> + pinctrl: pinctrl {
>>> + compatible = "socionext,uniphier-pro4-pinctrl";
>>
>> There's not a contiguous register range that can be put here?
>
>
> Right.
>
> I saw SATA PHY registers are inserted among the pinctrl registers.
Okay,
Acked-by: Rob Herring <robh@...nel.org>
> Hardware engineers often make crazy design.
If there's 2 ways to do things, they will find a 3rd way.
Rob
Powered by blists - more mailing lists