From: Arnd Bergmann <arnd@arndb.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Girish K S <girish.shivananjappa@linaro.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc@vger.kernel.org, Chris Ball <cjb@laptop.org>,
Per Forlin <per.forlin@stericsson.com>,
Johan Rudholm <johan.rudholm@stericsson.com>,
Lee Jones <lee.jones@linaro.org>,
Saugata Das <saugata.das@linaro.org>,
Asutosh Das <asutoshd@codeaurora.org>
Subject: Re: [PATCH] mmc: Fixup broken suspend and eMMC4.5 power off notify
Date: Fri, 14 Sep 2012 15:04:14 +0000 [thread overview]
Message-ID: <201209141504.14658.arnd@arndb.de> (raw)
In-Reply-To: <CACRpkdaV_PDaYH+RgM2pa9f9Gp97-D9xbxfDkPUBfXSR+-csAg@mail.gmail.com>
On Friday 14 September 2012, Linus Walleij wrote:
> On Fri, Sep 14, 2012 at 10:25 AM, Girish K S
> <girish.shivananjappa@linaro.org> wrote:
> > On 14 September 2012 12:37, Ulf Hansson <ulf.hansson@linaro.org> wrote:
> >> Hi Girish,
> >>
> >> I should also have stated that this patch has not been tested with an
> >> eMMC 4.5 device, thus the power off notification is not fully tested.
> >> Unfortunate I don't have such a device available right now. What I did
> >> test was that patch must not break anything and tested that the
> >> suspend/resume sequence is fixed for eMMC with sleep support. I also
> >> tested this with MMC_CAP2_POWEROFF_NOTIFY enabled.
> >>
> >> Are you able to help out in testing with a eMMC 4.5 device with
> >> POWER_OFF_NOTIFY support?
> >
> > I am also facing the same problem. The board that i used earlier to
> > upstream 4.5 patches is not functioning. Thats the reason for the
> > delay in upstreaming or sending the patch. Once i get it repaired i ll
> > definitely do it.
> > It would be helpful if somebody in the list can do this in the mean time.
>
> Let's page Arnd, I was under the impression that he has a eMMC 4.5
> board so maybe he can test it?
I have a few eMMC samples but am only using them with my (slow) thinkpad
SD card reader. I also don't know which eMMC-4.5 features they implement,
as some may be early prototypes.
What exactly do you need tested?
Arnd
next prev parent reply other threads:[~2012-09-14 15:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 9:20 [PATCH] mmc: Fixup broken suspend and eMMC4.5 power off notify Ulf Hansson
2012-09-14 5:08 ` Girish K S
2012-09-14 6:38 ` Girish K S
2012-09-14 7:07 ` Ulf Hansson
2012-09-14 8:25 ` Girish K S
2012-09-14 9:19 ` Ulf Hansson
2012-09-14 9:41 ` Girish K S
2012-09-14 14:03 ` Linus Walleij
2012-09-14 15:04 ` Arnd Bergmann [this message]
2012-09-17 4:50 ` Girish K S
2012-09-19 16:06 ` Ulf Hansson
2012-09-20 1:35 ` Chris Ball
2012-09-25 9:19 ` Ulf Hansson
2012-09-26 11:19 ` Linus Walleij
2012-09-20 7:58 ` Tanya Brokhman
2012-09-20 15:39 ` Ulf Hansson
2012-09-20 17:56 ` Tanya Brokhman
2012-09-27 11:27 ` Tanya Brokhman
2012-09-27 11:45 ` Ulf Hansson
2012-09-30 6:48 ` Tanya Brokhman
2012-09-30 7:07 ` Girish K S
2012-09-30 7:09 ` Girish K S
2012-10-03 21:03 ` Chris Ball
2012-10-04 11:46 ` Ulf Hansson
2012-10-04 13:11 ` Girish K S
2012-10-05 16:50 ` Chris Ball
2012-10-08 7:31 ` Ulf Hansson
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=201209141504.14658.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=asutoshd@codeaurora.org \
--cc=cjb@laptop.org \
--cc=girish.shivananjappa@linaro.org \
--cc=johan.rudholm@stericsson.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-mmc@vger.kernel.org \
--cc=per.forlin@stericsson.com \
--cc=saugata.das@linaro.org \
--cc=ulf.hansson@linaro.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 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.