[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=XTBgKnnswhfoQH3qWjpbp831e1L1+j+QCjxx2h=aQoog@mail.gmail.com>
Date: Thu, 2 May 2019 11:36:01 -0700
From: Doug Anderson <dianders@...omium.org>
To: Felipe Balbi <felipe.balbi@...ux.intel.com>
Cc: Minas Harutyunyan <hminas@...opsys.com>,
Heiko Stübner <heiko@...ech.de>,
Alan Stern <stern@...land.harvard.edu>,
Artur Petrosyan <Arthur.Petrosyan@...opsys.com>,
Alexandru M Stan <amstan@...omium.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
William Wu <william.wu@...k-chips.com>,
linux-usb@...r.kernel.org, Stefan Wahren <stefan.wahren@...e.com>,
Randy Li <ayaka@...lik.info>, Chris <zyw@...k-chips.com>,
Matthias Kaehlcke <mka@...omium.org>,
Ryan Case <ryandcase@...omium.org>,
Amelie Delaunay <amelie.delaunay@...com>,
Julius Werner <jwerner@...omium.org>,
Dinh Nguyen <dinguyen@...nsource.altera.com>,
Elaine Zhang <zhangqing@...k-chips.com>,
devicetree@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Mark Rutland <mark.rutland@....com>
Subject: Re: [PATCH v2 3/5] Documentation: dt-bindings: Add
snps,need-phy-for-wake for dwc2 USB
Hi,
On Thu, Apr 25, 2019 at 5:40 AM Felipe Balbi
<felipe.balbi@...ux.intel.com> wrote:
>
> Douglas Anderson <dianders@...omium.org> writes:
>
> > Some SoCs with a dwc2 USB controller may need to keep the PHY on to
> > support remote wakeup. Allow specifying this as a device tree
> > property.
> >
> > Signed-off-by: Douglas Anderson <dianders@...omium.org>
> > ---
> > For relevant prior discussion on this patch, see:
> >
> > https://lkml.kernel.org/r/1435017144-2971-3-git-send-email-dianders@chromium.org
> >
> > I didn't make any changes from the prior version since I never found
> > out what Rob thought of my previous arguments. If folks want a
> > change, perhaps they could choose from these options:
> >
> > 1. Assume that all dwc2 hosts would like to keep their PHY on for
> > suspend if there's a USB wakeup enabled, thus we totally drop this
> > binding. This doesn't seem super great to me since I'd bet that
> > many devices that use dwc2 weren't designed for USB wakeup (they
> > may not keep enough clocks or rails on) so we might be wasting
> > power for nothing.
> > 2. Rename this property to "snps,wakeup-from-suspend-with-phy" to make
> > it more obvious that this property is intended both to document
> > that wakeup from suspend is possible and that we need the PHY for
> > said wakeup.
> > 3. Rename this property to "snps,can-wakeup-from-suspend" and assume
> > it's implicit that if we can wakeup from suspend that we need to
> > keep the PHY on. If/when someone shows that a device exists using
> > dwc2 where we can wakeup from suspend without the PHY they can add
> > a new property.
> >
> > Changes in v2: None
> >
> > Documentation/devicetree/bindings/usb/dwc2.txt | 3 +++
> > 1 file changed, 3 insertions(+)
>
> checking file Documentation/devicetree/bindings/usb/dwc2.txt
> Hunk #1 FAILED at 37.
> Hunk #2 succeeded at 52 (offset -1 lines).
> 1 out of 2 hunks FAILED
Can you try applying this and the next two patches again? ...or let
me know that you'd like me to repost?
Thanks!
-Doug
Powered by blists - more mailing lists