linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hzpeterchen@gmail.com (Peter Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/6] power: add power sequence library
Date: Tue, 2 Aug 2016 09:08:13 +0800	[thread overview]
Message-ID: <20160802010812.GA26831@shlinux2> (raw)
In-Reply-To: <579F62CE.1050900@gmail.com>

On Mon, Aug 01, 2016 at 07:55:10AM -0700, Joshua Clayton wrote:
> 
> 
> On 07/28/2016 09:41 AM, Fabio Estevam wrote:
> > Hi Joshua,
> >
> > On Thu, Jul 28, 2016 at 12:56 PM, Joshua Clayton
> > <stillcompiling@gmail.com> wrote:
> >
> >> I assume there is a v4 coming due to rmk's comments on patch 5.
> >> I couldn't figure out where to null the of_node in error paths, but in testing
> >> we did put a line of code to null the of_node on release.
> >>
> >> but...
> >> As an aside,
> >> I was hoping this series would magically fix a problem
> >> with the imx6q-evi which has forced us to disable
> >> runtime power management. But it did not. :(
> > I also see a similar problem on a mx28 board with a hub.
> >
> > Does it help in your case if you pass 'usbcore.autosuspend=-1' in the
> > kernel command line?
> >
> > Regards,
> >
> > Fabio Estevam
> Thanks a million, Fabio!
> 
> 'usbcore.autosuspend=-1' quiets the errors.
> 
> ~joshua
> 

If you are using imx6q, there are some patches which is not upstreamed
to workaround one SoC problem.

http://www.spinics.net/lists/linux-usb/msg98682.html

Try to implement the design for notify_suspend/resume at
drivers/usb/phy/phy-mxs-usb.c and drivers/usb/chipidea/host.c

You can refer to the code at:
http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/tree/?h=imx_4.1.15_1.0.0_ga

-- 

Best Regards,
Peter Chen

  parent reply	other threads:[~2016-08-02  1:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-20  9:40 [PATCH v3 0/6] power: add power sequence library Peter Chen
2016-07-20  9:40 ` [PATCH v3 1/6] binding-doc: power: pwrseq-generic: add binding doc for generic " Peter Chen
2016-07-29  2:09   ` Peter Chen
2016-07-29 21:09   ` Rob Herring
2016-07-20  9:40 ` [PATCH v3 2/6] power: add " Peter Chen
2016-07-29 20:06   ` [v3,2/6] " Matthias Kaehlcke
2016-08-01  1:58     ` Peter Chen
2016-08-02  3:32     ` Peter Chen
2016-07-20  9:40 ` [PATCH v3 3/6] binding-doc: usb: usb-device: add optional properties for power sequence Peter Chen
2016-07-29 21:11   ` Rob Herring
2016-07-20  9:40 ` [PATCH v3 4/6] usb: core: add power sequence handling for USB devices Peter Chen
2016-07-27 16:25   ` Joshua Clayton
2016-07-28  1:45     ` Peter Chen
2016-07-28 16:18       ` Joshua Clayton
2016-07-20  9:40 ` [PATCH v3 5/6] usb: chipidea: let chipidea core device of_node equal's glue layer device of_node Peter Chen
2016-07-21  9:14   ` Russell King - ARM Linux
2016-07-21  9:20     ` Peter Chen
2016-07-21  9:41       ` Russell King - ARM Linux
2016-07-21 10:12         ` Peter Chen
2016-07-20  9:40 ` [PATCH v3 6/6] ARM: dts: imx6qdl-udoo.dtsi: fix onboard USB HUB property Peter Chen
2016-07-28 15:56 ` [PATCH v3 0/6] power: add power sequence library Joshua Clayton
2016-07-28 16:41   ` Fabio Estevam
2016-08-01 14:55     ` Joshua Clayton
2016-08-01 16:29       ` Fabio Estevam
2016-08-02  1:08       ` Peter Chen [this message]
2016-07-29  1:46   ` Peter Chen

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=20160802010812.GA26831@shlinux2 \
    --to=hzpeterchen@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).