[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170115155931.l5tjcdhbz6sj3wke@localhost>
Date: Sun, 15 Jan 2017 16:59:32 +0100
From: Rask Ingemann Lambertsen <rask@...melder.dk>
To: Chen-Yu Tsai <wens@...e.org>
Cc: Andre Przywara <andre.przywara@....com>,
Mark Rutland <mark.rutland@....com>,
devicetree <devicetree@...r.kernel.org>,
Ulf Hansson <ulf.hansson@...aro.org>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
linux-sunxi <linux-sunxi@...glegroups.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Hans De Goede <hdegoede@...hat.com>,
Rob Herring <robh+dt@...nel.org>,
Icenowy Zheng <icenowy@...c.xyz>,
Maxime Ripard <maxime.ripard@...e-electrons.com>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Dropping device tree pinmux nodes for GPIO usage (Was: [PATCH 3/5]
arm64: dts: sun50i: add MMC nodes)
On Tue, Jan 03, 2017 at 10:52:12AM +0800, Chen-Yu Tsai wrote:
> On Tue, Jan 3, 2017 at 7:03 AM, Andre Przywara <andre.przywara@....com> wrote:
> > +
> > + mmc0_default_cd_pin: mmc0_cd_pin@0 {
> > + pins = "PF6";
> > + function = "gpio_in";
> > + bias-pull-up;
> > + };
>
> We are starting to drop pinmux nodes for gpio usage.
How do we get the equivalent of bias-pull-up/down and drive-strength if we
run across a pin that needs it?
--
Rask Ingemann Lambertsen
Powered by blists - more mailing lists