[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACna6ryrABjF3ie8uE6_q-pfNjhQaGbRhNR9jWMEPKwaUt88hQ@mail.gmail.com>
Date: Tue, 21 Jun 2016 17:23:18 +0200
From: Rafał Miłecki <zajec5@...il.com>
To: Imre Kaloz <kaloz@...nwrt.org>
Cc: Mark Rutland <mark.rutland@....com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
Florian Fainelli <f.fainelli@...il.com>,
Pawel Moll <pawel.moll@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Hauke Mehrtens <hauke@...ke-m.de>,
Russell King <linux@...linux.org.uk>,
open list <linux-kernel@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
"open list:BROADCOM BCM5301X ARM ARCHITECTURE"
<bcm-kernel-feedback-list@...adcom.com>,
Kumar Gala <galak@...eaurora.org>,
"open list:BROADCOM BCM5301X ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] ARM: BCM5301X: Set GPIO enabling USB power on Netgear R7000
On 21 June 2016 at 16:29, Imre Kaloz <kaloz@...nwrt.org> wrote:
> On Tue, 21 Jun 2016 14:26:11 +0200, Rafał Miłecki <zajec5@...il.com> wrote:
>
>> On 21 June 2016 at 14:22, Imre Kaloz <kaloz@...nwrt.org> wrote:
>>>
>>> Is there any reason you are not handling this properly as a regulator
>>> with
>>> usb-nop-xceiv?
>>
>>
>> We can't use USB NOP PHY as we need a specific PHY driver for Broadcom's
>> USB.
>
>
> I see. That shouldn't stop you from addressing the regulator part, tho ;)
How? Be more specific please.
--
Rafał
Powered by blists - more mailing lists