mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bean Huo <beanhuo@iokpp.de>
To: ulf.hansson@linaro.org, adrian.hunter@intel.com,
	beanhuo@micron.com, jakub.kwapisz@toradex.com,
	rafael.beims@toradex.com
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH v4] mmc: Add quirk MMC_QUIRK_BROKEN_CACHE_FLUSH for Micron eMMC Q2J54A
Date: Tue, 10 Oct 2023 16:14:35 +0200	[thread overview]
Message-ID: <0f66769bb82bdba201ddfc7a826aacf3dc6b2296.camel@iokpp.de> (raw)
In-Reply-To: <f9beb373-a6c8-ba07-f3d1-c72ecc058806@gmail.com>


Hi Ulf,

ping you again, have you recieved this mail?

Kind regards,
Bean


On Wed, 2023-10-04 at 21:07 +0200, Bean Huo wrote:
> Hi Ulf,
> 
> Any comments on this version?
> 
> Kind regards,
> 
> Beam
> 
> On 01.10.23 9:49 PM, Bean Huo wrote:
> > From: Bean Huo <beanhuo@micron.com>
> > 
> > Micron MTFC4GACAJCN eMMC supports cache but requires that flush
> > cache
> > operation be allowed only after a write has occurred. Otherwise,
> > the
> > cache flush command or subsequent commands will time out.
> > 
> > Signed-off-by: Bean Huo <beanhuo@micron.com>
> > Signed-off-by: Rafael Beims <rafael.beims@toradex.com>
> > Cc: stable@vger.kernel.org
> > 
> > ---
> > Changelog:
> > 
> > v3--v4:
> >       1. Add helper function for this quirk in
> > drivers/mmc/core/card.h.
> >       2. Set card->written_flag only for REQ_OP_WRITE.
> > v2--v3:
> >       1. Set card->written_flag in mmc_blk_mq_issue_rq().
> > v1--v2:
> >       1. Add Rafael's test-tag, and Co-developed-by.
> >       2. Check host->card whether NULL or not in
> > __mmc_start_request() before asserting host->card->->quirks


  reply	other threads:[~2023-10-10 14:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-01 19:49 Bean Huo
2023-10-04 19:07 ` Bean Huo
2023-10-10 14:14   ` Bean Huo [this message]
2023-10-10 14:20 ` Ulf Hansson
2023-10-10 15:33   ` Bean Huo
2023-10-10 21:04     ` Ulf Hansson
2023-10-18 16:05       ` Rafael Beims
2023-10-18 22:49         ` 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=0f66769bb82bdba201ddfc7a826aacf3dc6b2296.camel@iokpp.de \
    --to=beanhuo@iokpp.de \
    --cc=adrian.hunter@intel.com \
    --cc=beanhuo@micron.com \
    --cc=jakub.kwapisz@toradex.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=rafael.beims@toradex.com \
    --cc=stable@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

all inboxes | Powered by JetHome®