From: Rob Herring <robh@kernel.org>
Cc: Minas Harutyunyan <hminas@synopsys.com>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
heiko@sntech.de, Alan Stern <stern@rowland.harvard.edu>,
Artur Petrosyan <Arthur.Petrosyan@synopsys.com>,
amstan@chromium.org, linux-rockchip@lists.infradead.org,
William Wu <william.wu@rock-chips.com>,
linux-usb@vger.kernel.org, Stefan Wahren <stefan.wahren@i2se.com>,
Randy Li <ayaka@soulik.info>,
zyw@rock-chips.com, mka@chromium.org, ryandcase@chromium.org,
Amelie Delaunay <amelie.delaunay@st.com>,
jwerner@chromium.org, Elaine Zhang <zhangqing@rock-chips.com>,
Douglas Anderson <dianders@chromium.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v3 1/3] Documentation: dt-bindings: Add snps,need-phy-for-wake for dwc2 USB
Date: Thu, 13 Jun 2019 17:06:07 -0600 [thread overview]
Message-ID: <20190613230607.GA10347@bogus> (raw)
In-Reply-To: <20190520175605.2405-2-dianders@chromium.org>
On Mon, 20 May 2019 10:56:03 -0700, Douglas Anderson wrote:
> 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@chromium.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.
>
> NOTE FOR REPOST:
> - In v2 Rob said [1] he'd prefer something based on the SoC
> compatibility string, but that doesn't work because not all boards
> will have the regulator setup / board design / suspend logic
> necessary to make this work.
>
> [1] https://lkml.kernel.org/r/20190430012328.GA25660@bogus
>
>
> Changes in v3: None
> Changes in v2: None
>
> Documentation/devicetree/bindings/usb/dwc2.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Douglas Anderson <dianders@chromium.org>
Cc: Minas Harutyunyan <hminas@synopsys.com>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
heiko@sntech.de, Alan Stern <stern@rowland.harvard.edu>,
Artur Petrosyan <Arthur.Petrosyan@synopsys.com>,
amstan@chromium.org, linux-rockchip@lists.infradead.org,
William Wu <william.wu@rock-chips.com>,
linux-usb@vger.kernel.org, Stefan Wahren <stefan.wahren@i2se.com>,
Randy Li <ayaka@soulik.info>,
zyw@rock-chips.com, mka@chromium.org, ryandcase@chromium.org,
Amelie Delaunay <amelie.delaunay@st.com>,
jwerner@chromium.org, Elaine Zhang <zhangqing@rock-chips.com>,
Douglas Anderson <dianders@chromium.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v3 1/3] Documentation: dt-bindings: Add snps,need-phy-for-wake for dwc2 USB
Date: Thu, 13 Jun 2019 17:06:07 -0600 [thread overview]
Message-ID: <20190613230607.GA10347@bogus> (raw)
In-Reply-To: <20190520175605.2405-2-dianders@chromium.org>
On Mon, 20 May 2019 10:56:03 -0700, Douglas Anderson wrote:
> 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@chromium.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.
>
> NOTE FOR REPOST:
> - In v2 Rob said [1] he'd prefer something based on the SoC
> compatibility string, but that doesn't work because not all boards
> will have the regulator setup / board design / suspend logic
> necessary to make this work.
>
> [1] https://lkml.kernel.org/r/20190430012328.GA25660@bogus
>
>
> Changes in v3: None
> Changes in v2: None
>
> Documentation/devicetree/bindings/usb/dwc2.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-06-13 23:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 17:56 [PATCH v3 0/3] USB: dwc2: Allow wakeup from suspend; enable for rk3288-veyron Douglas Anderson
2019-05-20 17:56 ` Douglas Anderson
2019-05-20 17:56 ` [PATCH v3 1/3] Documentation: dt-bindings: Add snps,need-phy-for-wake for dwc2 USB Douglas Anderson
2019-06-13 23:06 ` Rob Herring [this message]
2019-06-13 23:06 ` Rob Herring
2019-05-20 17:56 ` [PATCH v3 2/3] USB: dwc2: Don't turn off the usbphy in suspend if wakeup is enabled Douglas Anderson
2019-05-20 17:56 ` [PATCH v3 3/3] ARM: dts: rockchip: Allow wakeup from rk3288-veyron's dwc2 USB ports Douglas Anderson
2019-05-20 17:56 ` Douglas Anderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190613230607.GA10347@bogus \
--to=robh@kernel.org \
--cc=Arthur.Petrosyan@synopsys.com \
--cc=amelie.delaunay@st.com \
--cc=amstan@chromium.org \
--cc=ayaka@soulik.info \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=hminas@synopsys.com \
--cc=jwerner@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--cc=ryandcase@chromium.org \
--cc=stefan.wahren@i2se.com \
--cc=stern@rowland.harvard.edu \
--cc=william.wu@rock-chips.com \
--cc=zhangqing@rock-chips.com \
--cc=zyw@rock-chips.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.