[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=VS6YBjUQsix=nHteKG6jt=+LGWpDSqrP4VRu5LxOVc3A@mail.gmail.com>
Date: Tue, 28 Feb 2017 14:54:33 -0800
From: Doug Anderson <dianders@...omium.org>
To: Heiko Stuebner <heiko@...ech.de>
Cc: Brian Norris <briannorris@...omium.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Caesar Wang <wxt@...k-chips.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
Stephen Barber <smbarber@...omium.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Chris Zhong <zyw@...k-chips.com>
Subject: Re: [PATCH v2 4/6] arm64: dts: rockchip: add Gru/Kevin DTS
Hi,
On Tue, Feb 28, 2017 at 2:00 PM, Heiko Stuebner <heiko@...ech.de> wrote:
>> + pp3300_wifi_bt: pp3300-wifi-bt {
>> + compatible = "regulator-fixed";
>> + regulator-name = "pp3300_wifi_bt";
>> + /* NOTE: wlan_module_pd_l pinctrl in pp1800_pcie */
>> +
>> + enable-active-high;
>> +
>> + /* NOTE: this GPIO also used in pp1800_pcie */
>
> does the gpio subsystem like this double usage?
Yes, see commit f19b00da8ed3 ("regulator: core: support shared enable
GPIO concept"). ...but there's no great place to put the pinctrl node
though, unfortunately. It's either randomly pick one of the two or
add it as a system-level hog.
-Doug
Powered by blists - more mailing lists