LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: merez@codeaurora.org
To: "Nikita Yushchenko" <nikita.yoush@yandex.ru>
Cc: "Maya Erez" <merez@codeaurora.org>,
	linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: mmc idle time bkops?
Date: Mon, 16 Mar 2015 19:37:45 -0000	[thread overview]
Message-ID: <bdb5de1e1c2c1cfacdf02ba8f44025a3.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <550098CE.1010407@yandex.ru>

Hi Nikita,

The patch got stuck for a while as there was a request to use the runtime
PM framework for implementing the idle time BKOPs and I didn't have the
ability to test it back then.
We plan to re-implement and test in the upcoming few months (aim to July).
Do you have a need for this feature in an earlier date or it can wait for
july?

Thanks,
Maya

> Hi
>
> Some months ago, you've been working on "idle time bkops" feature. The
> latest (v6) sign of this work I could found is [1]
>
> [1] https://lkml.org/lkml/2013/4/14/29
>
> However this did not land in mainline, also no replies, and no sign of
> any follow-up...  Complete mystery what has happened to this effort :(
>
> What is the latest status of "idle time bkops" functionality?
> Is any working implementation available?
>
> TIA,
> Nikita Yushchenko
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


-- 
Maya Erez
Qualcomm Israel, on behalf of Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
Collaborative Project


  reply	other threads:[~2015-03-16 19:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 19:34 Nikita Yushchenko
2015-03-16 19:37 ` merez [this message]
2015-03-16 19:46   ` Nikita Yushchenko

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=bdb5de1e1c2c1cfacdf02ba8f44025a3.squirrel@www.codeaurora.org \
    --to=merez@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=nikita.yoush@yandex.ru \
    --subject='Re: mmc idle time bkops?' \
    /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

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).