From: Lee Jones <lee.jones@linaro.org>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] mfd: tc6393xb fail ohci suspend if full state restore is required
Date: Mon, 3 Nov 2014 12:30:35 +0000 [thread overview]
Message-ID: <20141103123035.GD4538@x1> (raw)
In-Reply-To: <CALT56yPLnitsAqKJ=ryFE1uXwQqpbqwP3BmOf8L+fYG88kPnhw@mail.gmail.com>
On Wed, 29 Oct 2014, Dmitry Eremin-Solenikov wrote:
> 2014-10-24 20:19 GMT+03:00 Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>:
> > Some boards with TC6393XB chip require full state restore during system
> > resume thanks to chip's VCC being cut off during suspend (Sharp SL-6000
> > tosa is one of them). Failing to do so would result in ohci Oops on
> > resume due to internal memory contentes being changed. Fail ohci suspend
> > on tc6393xb is full state restore is required.
> >
> > Recommended workaround is to unbind tmio-ohci driver before suspend and
> > rebind it after resume.
>
> ping
Don't do that. If you think the patch has slipped through the net
please sent it again with a [RESEND] tag in the email's subject line.
As it happens it hasn't been forgotten about, I was on vacation last
week and will get round to reviewing this shortly.
> > Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
> > Cc: stable@vger.kernel.org
> > ---
> > drivers/mfd/tc6393xb.c | 13 ++++++++++++-
> > 1 file changed, 12 insertions(+), 1 deletion(-)
>
>
>
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-11-03 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 17:19 [PATCH] mfd: tc6393xb fail ohci suspend if full state restore is required Dmitry Eremin-Solenikov
2014-10-29 18:38 ` Dmitry Eremin-Solenikov
2014-11-03 12:30 ` Lee Jones [this message]
2014-11-03 14:56 ` Lee Jones
2014-11-04 8:33 ` Dmitry Eremin-Solenikov
2014-11-04 9:20 ` Lee Jones
2014-11-04 9:20 ` Lee Jones
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=20141103123035.GD4538@x1 \
--to=lee.jones@linaro.org \
--cc=dbaryshkov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=stable@vger.kernel.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).