From: "Subhash Jadavani" <subhashj@codeaurora.org>
To: 'Ulf Hansson' <ulf.hansson@stericsson.com>
Cc: 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>
Subject: RE: [PATCH] mmc: core: Add option to prevent eMMC sleep command
Date: Wed, 14 Dec 2011 21:08:43 +0530 [thread overview]
Message-ID: <000c01ccba76$787f7cf0$697e76d0$@org> (raw)
In-Reply-To: <4EE8C1FB.5080205@stericsson.com>
> -----Original Message-----
> From: Ulf Hansson [mailto:ulf.hansson@stericsson.com]
> Sent: Wednesday, December 14, 2011 9:04 PM
> To: Subhash Jadavani
> Cc: linux-mmc@vger.kernel.org; 'Chris Ball'; Per FORLIN; Johan RUDHOLM;
> 'Lee Jones'
> Subject: Re: [PATCH] mmc: core: Add option to prevent eMMC sleep
> command
>
> Subhash Jadavani wrote:
> > Why is this patch needed? Do you see any issue with eMMC sleep on
> particular
> > cards?
> >
> > Regards,
> > Subhash
>
> Suppose the eMMC is put in sleep state when doing suspend, at that
> point
> the kernel crashes. The kernel crash is supposed to be dumped to the
> same eMMC by some other software than the kernel itself. But this
> software do not have support for waking up the eMMC from sleep and is
> thus not able to store the dump.
Ok. This means that SW still has some support to read/write eMMC. As part of
suspend, we also deselect the card. So does that SW is capable of
re-selecting the card and the do read/write transfer? I know this discussion
might not be required. But still it's good to know.
As far as patch is concerned, it looks good. You might want to mention the
motivation for this patch in commit text.
>
> Br
> Ulf Hansson
next prev parent reply other threads:[~2011-12-14 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 15:20 [PATCH] mmc: core: Add option to prevent eMMC sleep command Ulf Hansson
2011-12-14 15:25 ` Subhash Jadavani
2011-12-14 15:34 ` Ulf Hansson
2011-12-14 15:38 ` Subhash Jadavani [this message]
2011-12-14 16:48 ` 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='000c01ccba76$787f7cf0$697e76d0$@org' \
--to=subhashj@codeaurora.org \
--cc=cjb@laptop.org \
--cc=johan.rudholm@stericsson.com \
--cc=lee.jones@linaro.org \
--cc=linux-mmc@vger.kernel.org \
--cc=per.forlin@stericsson.com \
--cc=ulf.hansson@stericsson.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;
as well as URLs for NNTP newsgroup(s).