linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Amelie Delaunay <amelie.delaunay@st.com>
Cc: Lee Jones <lee.jones@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexandre Torgue <alexandre.torgue@st.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v2 1/7] dt-bindings: mfd: Add ST Multi-Function eXpander (STMFX) core bindings
Date: Wed, 26 Sep 2018 17:57:54 -0500	[thread overview]
Message-ID: <20180926225754.GA20472@bogus> (raw)
In-Reply-To: <1537363669-25991-2-git-send-email-amelie.delaunay@st.com>

On Wed, Sep 19, 2018 at 03:27:43PM +0200, Amelie Delaunay wrote:
> This patch adds documentation of device tree bindings for the
> STMicroelectronics Multi-Function eXpander (STMFX) MFD core.
> 
> Signed-off-by: Amelie Delaunay <amelie.delaunay@st.com>
> ---
>  Documentation/devicetree/bindings/mfd/stmfx.txt | 28 +++++++++++++++++++++++++
>  1 file changed, 28 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/mfd/stmfx.txt
> 
> diff --git a/Documentation/devicetree/bindings/mfd/stmfx.txt b/Documentation/devicetree/bindings/mfd/stmfx.txt
> new file mode 100644
> index 0000000..21cf798
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mfd/stmfx.txt
> @@ -0,0 +1,28 @@
> +STMicroelectonics Multi-Function eXpander (STMFX) Core bindings
> +
> +ST Multi-Function eXpander (STMFX) is a slave controller using I2C for
> +communication with the main MCU. Its main features are GPIO expansion, main
> +MCU IDD measurement (IDD is the amount of current that flows through VDD) and
> +resistive touchscreen controller.
> +
> +Required properties:
> +- compatible: should be "st,stmfx-0300".
> +- reg: I2C slave address of the device.
> +- interrupt-parent: phandle of the STMFX parent interrupt controller.

Drop this. It is implied and could be in the parent.

> +- interrutps: interrupt specifier triggered by MFX_IRQ_OUT signal.

typo

> +
> +Optional properties:
> +- drive-open-drain: configure MFX_IRQ_OUT as open drain.
> +- vdd-supply: phandle of the regulator supplying STMFX.
> +
> +Example:
> +
> +	stmfx: stmfx@42 {
> +		compatible = "st,stmfx-0300";
> +		reg = <0x42>;
> +		interrupts = <8 IRQ_TYPE_EDGE_RISING>;
> +		interrupt-parent = <&gpioi>;
> +		vdd-supply = <&v3v3>;
> +	};
> +
> +Please refer to ../pinctrl/pinctrl-stmfx.txt for STMFX GPIO expander function bindings.
> -- 
> 2.7.4
> 

  parent reply	other threads:[~2018-09-26 22:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19 13:27 [PATCH v2 0/7] Introduce STMFX I2C Multi-Function eXpander Amelie Delaunay
2018-09-19 13:27 ` [PATCH v2 1/7] dt-bindings: mfd: Add ST Multi-Function eXpander (STMFX) core bindings Amelie Delaunay
2018-09-19 19:37   ` Linus Walleij
2018-09-26 22:57   ` Rob Herring [this message]
2018-09-19 13:27 ` [PATCH v2 2/7] mfd: Add ST Multi-Function eXpander (STMFX) core driver Amelie Delaunay
2018-09-19 19:40   ` Linus Walleij
2018-09-21  6:29   ` kbuild test robot
2018-09-19 13:27 ` [PATCH v2 3/7] dt-bindings: pinctrl: document the STMFX pinctrl bindings Amelie Delaunay
2018-09-19 19:42   ` Linus Walleij
2018-09-26 22:59   ` Rob Herring
2018-09-19 13:27 ` [PATCH v2 4/7] pinctrl: Add STMFX GPIO expander Pinctrl/GPIO driver Amelie Delaunay
2018-09-19 19:46   ` Linus Walleij
2018-09-19 13:27 ` [PATCH v2 5/7] ARM: dts: stm32: add STMFX support on stm32746g-eval Amelie Delaunay
2018-09-19 19:47   ` Linus Walleij
2018-09-19 13:27 ` [PATCH v2 6/7] ARM: dts: stm32: add joystick " Amelie Delaunay
2018-09-19 19:47   ` Linus Walleij
2018-09-19 13:27 ` [PATCH v2 7/7] ARM: dts: stm32: add orange and blue leds " Amelie Delaunay
2018-09-19 19:48   ` Linus Walleij
2018-09-19 16:20 ` [PATCH v2 0/7] Introduce STMFX I2C Multi-Function eXpander Alexandre Torgue
2018-09-19 19:50 ` 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=20180926225754.GA20472@bogus \
    --to=robh@kernel.org \
    --cc=alexandre.torgue@st.com \
    --cc=amelie.delaunay@st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mark.rutland@arm.com \
    --cc=mcoquelin.stm32@gmail.com \
    /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).