From: Adrian Hunter <adrian.hunter@intel.com>
To: Alex Lemberg <Alex.Lemberg@sandisk.com>,
Uri Yanai <Uri.Yanai@sandisk.com>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH 3/3] mmc: Checking BKOPS status prior to Suspend
Date: Wed, 25 Jan 2017 14:45:07 +0200 [thread overview]
Message-ID: <3dac8e2c-8a24-788b-bc29-8917c465b3e7@intel.com> (raw)
In-Reply-To: <2A84C54D-D96B-4728-BE25-BF082BF0C464@sandisk.com>
On 25/01/17 14:40, Alex Lemberg wrote:
>
>
> On 1/25/17, 12:30 PM, "Adrian Hunter" <adrian.hunter@intel.com> wrote:
>
> On 25/01/17 11:48, Alex Lemberg wrote:
> >
> >
> > On 1/24/17, 4:36 PM, "Adrian Hunter" <adrian.hunter@intel.com> wrote:
> >
> > On 23/01/17 19:07, Alex Lemberg wrote:
> > > Hi Adrian,
> > >
> > > I would like to add several notes on top of Uri’s answer...
> > > I agree with you, by the spec, PON Sleep_Notification should be
> > > set before calling Sleep command.
> > > As you probably remember, we have tried to implement it
> > > in the past and even submitted a patch – “[PATCH] mmc: sleep notification”
> > > https://www.mail-archive.com/linux-mmc@vger.kernel.org/msg30906.html
> > > As you can see from the thread, one of the main issues in Sleep_Notification
> > > is a SLEEP_NOTIFICATION_TIME (defined in EXT_CSD [216]), which need to be
> > > considered in implementation…
> >
> > Does it? I would tend to assume SLEEP_NOTIFICATION_TIME will be acceptable
> > during _suspend until proven otherwise.
> >
> > Potentially, by the spec, the Max value of SLEEP_NOTIFICATION_TIME can be 83.88 seconds.
> > Can we assume that this time is acceptable during _suspend?
>
> Do you know of any cards that take that long?
>
> Yes - for some cards it can take several seconds in some corner cases.
Wouldn't that mean POWER_OFF_SHORT has the same problem since that is
preparing for *both* Vcc and Vccq to go off?
>
> As I wrote, I would assume it is acceptable until we know otherwise.
>
> I think Sleep_Notification requires more detailed review.
> Since PON Sleep_Notification is a blocking command (BUSY asserted),
> in case of getting new request, driver need to send HPI command in order
> to interrupt the Sleep_Notification process.
> We tried to handle this case in our Sleep_Notification patchset…
> Anyway, I think we need to discuss it separately, not related to
> the AUTO_BKOPS support…
>
> >
> > > Thus, I think postponing Sleep during suspend requires a different from current
> > > AUTO_BKOPS implementation, and I suggest to handle it in separate
> > > patchset, if possible.
> >
> > Not at all sure what you mean by "postponing Sleep"?
> >
> > I mean letting Sleep_Notification to be completed before Sleep.
>
> ook.
>
>
>
next prev parent reply other threads:[~2017-01-25 12:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 12:15 [PATCH 0/3] Auto BKOPS PM suspend Uri Yanai
2017-01-17 12:15 ` [PATCH 1/3] mmc: replacing hardcoded value for runtime " Uri Yanai
2017-01-17 12:15 ` [PATCH 2/3] mmc: Adding AUTO_BKOPS_EN bit set for Auto BKOPS support Uri Yanai
2017-01-17 12:15 ` [PATCH 3/3] mmc: Checking BKOPS status prior to Suspend Uri Yanai
2017-01-18 1:59 ` Shawn Lin
2017-01-18 15:01 ` Uri Yanai
2017-01-20 11:56 ` Adrian Hunter
2017-01-22 15:55 ` Uri Yanai
2017-01-23 17:07 ` Alex Lemberg
2017-01-24 14:36 ` Adrian Hunter
2017-01-25 9:48 ` Alex Lemberg
2017-01-25 10:30 ` Adrian Hunter
2017-01-25 12:40 ` Alex Lemberg
2017-01-25 12:45 ` Adrian Hunter [this message]
2017-01-25 13:42 ` Alex Lemberg
2017-01-18 1:53 ` [PATCH 0/3] Auto BKOPS PM suspend Shawn Lin
2017-01-18 14:12 ` Uri Yanai
-- strict thread matches above, loose matches on Subject: below --
2016-09-01 14:24 [PATCH 0/3] mmc: Check BKOPS Level On Runtime Suspend alex lemberg
2016-09-01 14:24 ` [PATCH 3/3] mmc: Checking BKOPS status prior to Suspend alex lemberg
2016-10-13 7:36 ` Ulf Hansson
2016-10-31 9:53 ` Alex Lemberg
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=3dac8e2c-8a24-788b-bc29-8917c465b3e7@intel.com \
--to=adrian.hunter@intel.com \
--cc=Alex.Lemberg@sandisk.com \
--cc=Uri.Yanai@sandisk.com \
--cc=linux-mmc@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox