From: Linus Walleij <linus.walleij@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: Amelie Delaunay <amelie.delaunay@st.com>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Alexandre Torgue <alexandre.torgue@st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH 1/5] dt-bindings: pinctrl: document the STMFX pinctrl bindings
Date: Thu, 26 Apr 2018 14:49:44 +0200 [thread overview]
Message-ID: <CACRpkdYOMjjYyWQz7PK34jqUK7z5-CmH1HY6un4k8nBn7Cq8ag@mail.gmail.com> (raw)
In-Reply-To: <20180416181940.4b5z4svbde3ompij@rob-hp-laptop>
On Mon, Apr 16, 2018 at 8:19 PM, Rob Herring <robh@kernel.org> wrote:
> On Wed, Apr 11, 2018 at 11:47:01AM +0200, Amelie Delaunay wrote:
>> This patch adds documentation of device tree bindings for the
>> STMicroelectronics Multi-Function eXpander (STMFX) GPIO expander.
>>
>> Signed-off-by: Amelie Delaunay <amelie.delaunay@st.com>
>> + stmfxpinctrl: stmfx@42 {
>> + compatible = "st,stmfx-0300";
>> + reg = <0x42>;
>> + interrupt-parent = <&gpioi>;
>> + interrupts = <8 IRQ_TYPE_EDGE_RISING>;
>> + vdd-supply = <&v3v3>;
>> + status = "okay";
>
> Don't show status in examples.
>
>> +
>> + stmfxgpio: gpio {
>
> Why does this need to be a sub node? Are there functions beyond GPIO?
Amelie can answer to whether there are, I suspect there
are and in the review of patch 2 I suggest a MFD parent
and parent/child spawning of a MFD child for the GPIO
and pin control device.
Yours,
Linus Walleij
next prev parent reply other threads:[~2018-04-26 12:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 9:47 [PATCH 0/5] Introduce STMFX I2C GPIO expander Amelie Delaunay
2018-04-11 9:47 ` [PATCH 1/5] dt-bindings: pinctrl: document the STMFX pinctrl bindings Amelie Delaunay
2018-04-16 18:19 ` Rob Herring
2018-04-26 12:49 ` Linus Walleij [this message]
2018-05-09 7:56 ` Amelie DELAUNAY
2018-05-16 14:20 ` Linus Walleij
2018-05-16 15:01 ` Amelie DELAUNAY
2018-05-17 6:36 ` Lee Jones
2018-05-18 7:29 ` Amelie DELAUNAY
2018-05-18 13:52 ` Lee Jones
2018-05-18 15:13 ` Amelie DELAUNAY
2018-05-24 7:13 ` Linus Walleij
2018-05-28 11:39 ` Amelie DELAUNAY
2018-05-29 7:36 ` Lee Jones
2018-05-09 7:31 ` Amelie DELAUNAY
2018-04-11 9:47 ` [PATCH 2/5] pinctrl: Add STMFX GPIO expander Pinctrl/GPIO driver Amelie Delaunay
2018-04-12 3:11 ` kbuild test robot
2018-04-26 12:48 ` Linus Walleij
2018-05-09 9:13 ` Amelie DELAUNAY
2018-04-11 9:47 ` [PATCH 3/5] ARM: dts: stm32: add STMFX pinctrl/gpio expander support on stm32746g-eval Amelie Delaunay
2018-04-11 9:47 ` [PATCH 4/5] ARM: dts: stm32: add orange and blue leds " Amelie Delaunay
2018-04-11 9:47 ` [PATCH 5/5] ARM: dts: stm32: add joystick support " Amelie Delaunay
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=CACRpkdYOMjjYyWQz7PK34jqUK7z5-CmH1HY6un4k8nBn7Cq8ag@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=alexandre.torgue@st.com \
--cc=amelie.delaunay@st.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@kernel.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).