[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZFrRXEBW6KnqZ=h_7BxYn-RaAzhP4ovwC_DQSbAGZCVw@mail.gmail.com>
Date: Thu, 22 Feb 2018 14:54:31 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Amelie Delaunay <amelie.delaunay@...com>
Cc: Lee Jones <lee.jones@...aro.org>, Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Russell King <linux@...linux.org.uk>,
Alexandre Torgue <alexandre.torgue@...com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
linux-gpio@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 4/6] ARM: dts: stm32: add MFX support on I2C1 on stm32746g-eval
On Thu, Feb 8, 2018 at 3:27 PM, Amelie Delaunay <amelie.delaunay@...com> wrote:
> MFX is used as gpio expander on stm32746g-eval.
>
> Signed-off-by: Amelie Delaunay <amelie.delaunay@...com>
(...)
> + mfx: mfx@42 {
> + compatible = "st,mfx";
> + reg = <0x42>;
> + interrupts = <8 1>;
> + interrupt-parent = <&gpioi>;
> + interrupt-controller;
> + #interrupt-cells = <1>;
> +
> + mfxgpio: mfx_gpio {
> + compatible = "st,mfx-gpio";
> + interrupts = <0>;
> + interrupt-parent = <&mfx>;
> + gpio-controller;
> + #gpio-cells = <2>;
So I think this node should contain some pin config states
that can be referenced by the drivers to set up push/pull
etc. Probably it can use just standard pin config properties
like sx150x.
Yours,
Linus Walleij
Powered by blists - more mailing lists