From: "Sugaya, Taichi" <sugaya.taichi@socionext.com>
To: Rob Herring <robh@kernel.org>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Russell King <linux@armlinux.org.uk>,
Jiri Slaby <jslaby@suse.com>,
Masami Hiramatsu <masami.hiramatsu@linaro.org>,
Jassi Brar <jaswinder.singh@linaro.org>
Subject: Re: [PATCH 10/14] dt-bindings: pinctrl: milbeaut: Add Milbeaut M10V pinctrl description
Date: Thu, 6 Dec 2018 17:29:43 +0900 [thread overview]
Message-ID: <c71e44af-3a17-884c-78b4-686be8b293b1@socionext.com> (raw)
In-Reply-To: <20181204231131.GA7366@bogus>
Hi,
Thank you for your comments.
On 2018/12/05 8:11, Rob Herring wrote:
> On Mon, Nov 19, 2018 at 10:02:12AM +0900, Sugaya Taichi wrote:
>> Add DT bindings document for Milbeaut M10V pinctrl.
>>
>> Signed-off-by: Sugaya Taichi <sugaya.taichi@socionext.com>
>> ---
>> .../pinctrl/socionext,milbeaut-pinctrl.txt | 33 ++++++++++++++++++++++
>> 1 file changed, 33 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/pinctrl/socionext,milbeaut-pinctrl.txt
>>
>> diff --git a/Documentation/devicetree/bindings/pinctrl/socionext,milbeaut-pinctrl.txt b/Documentation/devicetree/bindings/pinctrl/socionext,milbeaut-pinctrl.txt
>> new file mode 100644
>> index 0000000..7469189
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/pinctrl/socionext,milbeaut-pinctrl.txt
>> @@ -0,0 +1,33 @@
>> +Milbeaut SoCs pin controller
>> +
>> +Required properties:
>> +- compatible: should be one of the following:
>> + "socionext,milbeaut-m10v-pinctrl" - for m10v SoC
>> +- reg: offset and length of the register set.
>> +- reg-names: should be "pinctrl", "exiu".
>> +- gpio-cells; should be 2.
>
> #gpio-cells
>
> gpio-controller?
Ah yes. I forgot to add it.
Add it.
>
>> +- interrupt-cells: should be 2.
>
> #interrupt-cells
>
> interrupt-controller?
Add it also.
Thanks,
Sugaya Taichi
>
>> +- clocks: phandle to the input clock.
>> +- interrupts: three interrupts specifer.
>> +- interrupt-names: corresponds "interrupts" factor.
>> +
>> +Example:
>> + pinctrl: pinctrl@1d022000 {
>> + compatible = "socionext,milbeaut-m10v-pinctrl";
>> + reg = <0x1d022000 0x1000>,
>> + <0x1c26f000 0x1000>;
>> + reg-names = "pinctrl", "exiu";
>> + gpio-controller;
>> + #gpio-cells = <2>;
>> + interrupt-controller;
>> + #interrupt-cells = <2>;
>> + clocks = <&dummy_clk>;
>> + interrupts = <0 54 4>, <0 55 4>, <0 56 4>, <0 57 4>,
>> + <0 58 4>, <0 59 4>, <0 60 4>, <0 61 4>,
>> + <0 62 4>, <0 63 4>, <0 64 4>, <0 65 4>,
>> + <0 66 4>, <0 67 4>, <0 68 4>, <0 69 4>;
>> + interrupt-names = "pin-48", "pin-49", "pin-50", "pin-51",
>> + "pin-52", "pin-53", "pin-54", "pin-55",
>> + "pin-56", "pin-57", "pin-58", "pin-59",
>> + "pin-60", "pin-61", "pin-62", "pin-63";
>> + }
>> --
>> 1.9.1
>>
prev parent reply other threads:[~2018-12-06 8:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 1:02 Sugaya Taichi
2018-11-19 1:02 ` [PATCH 11/14] pinctrl: milbeaut: Add Milbeaut M10V pinctrl Sugaya Taichi
2018-12-04 11:23 ` Masahiro Yamada
2018-12-05 5:03 ` Sugaya, Taichi
2018-11-19 1:02 ` [PATCH 12/14] ARM: dts: milbeaut: Add device tree set for the Milbeaut M10V board Sugaya Taichi
2018-11-19 15:46 ` Rob Herring
2018-11-21 2:36 ` sugaya.taichi
2018-11-19 1:02 ` [PATCH 13/14] ARM: configs: Add Milbeaut M10V defconfig Sugaya Taichi
2018-11-19 1:02 ` [PATCH 14/14] MAINTAINERS: Add entry to MAINTAINERS for Milbeaut Sugaya Taichi
2018-12-04 23:11 ` [PATCH 10/14] dt-bindings: pinctrl: milbeaut: Add Milbeaut M10V pinctrl description Rob Herring
2018-12-06 8:29 ` Sugaya, Taichi [this message]
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=c71e44af-3a17-884c-78b4-686be8b293b1@socionext.com \
--to=sugaya.taichi@socionext.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jaswinder.singh@linaro.org \
--cc=jslaby@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=masami.hiramatsu@linaro.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®