From: Sylvain Rochet <sylvain.rochet@finsecur.com>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Wenyou Yang <wenyou.yang@atmel.com>,
linux@maxim.org.za, linux@arm.linux.org.uk,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, peda@axentia.se
Subject: Re: [PATCH 2/3] pm: at91: pm_slowclock: remove clocks which are already stopped when entering slow clock mode
Date: Tue, 3 Mar 2015 23:50:24 +0100 [thread overview]
Message-ID: <20150303225024.GA28292@gradator.net> (raw)
In-Reply-To: <54F60092.5070902@atmel.com>
Hello Nicolas,
On Tue, Mar 03, 2015 at 07:42:26PM +0100, Nicolas Ferre wrote:
> Le 05/02/2015 07:01, Wenyou Yang a écrit :
> > From: Sylvain Rochet <sylvain.rochet@finsecur.com>
> >
> > Assume USB PLL and PLL B are already stopped before entering sleep mode,
> > print a warning if this isn't the case.
> >
> > Removed PLL B from slow clock code, all drivers are supposed to properly
> > unprepare clocks.
> >
> > Signed-off-by: Sylvain Rochet <sylvain.rochet@finsecur.com>
> > Acked-by: Wenyou.Yang <wenyou.yang@atmel.com>
>
> I keep this one for 4.1 as all the USB drivers are not converted yet.
I agree we should wait to prevent a regression, in case you missed that
I sent a v7 of my USBA PM support a few weeks ago (ping ;-).
Sylvain
next prev parent reply other threads:[~2015-03-03 22:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 5:59 [PATCH 0/3] at91-3.19: pm fixes Wenyou Yang
2015-02-05 6:00 ` [PATCH 1/3] pm: at91: pm_slowclock: fix suspend/resume hang up in timeouts Wenyou Yang
2015-03-03 18:41 ` Nicolas Ferre
2015-02-05 6:01 ` [PATCH 2/3] pm: at91: pm_slowclock: remove clocks which are already stopped when entering slow clock mode Wenyou Yang
2015-03-03 18:42 ` Nicolas Ferre
2015-03-03 22:50 ` Sylvain Rochet [this message]
2015-03-12 15:37 ` Nicolas Ferre
2015-02-05 6:02 ` [PATCH 3/3] pm: at91: Workaround DDRSDRC self-refresh bug with LPDDR1 memories Wenyou Yang
2015-03-03 18:41 ` Nicolas Ferre
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=20150303225024.GA28292@gradator.net \
--to=sylvain.rochet@finsecur.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@maxim.org.za \
--cc=nicolas.ferre@atmel.com \
--cc=peda@axentia.se \
--cc=wenyou.yang@atmel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox