Linux MultiMedia Card development
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Subject: Re: [PATCH RFC] HACK: mmc: core: also abort tuning with CMD12 for SD
Date: Thu, 9 Sep 2021 15:03:25 +0200	[thread overview]
Message-ID: <YToGHbgakZdrY/4R@shikoro> (raw)
In-Reply-To: <CAPDyKFptgZgDsKyHt-sO6yyRBm+LqeWkwOSoB9ED+b3QTPqD-w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]

Hi Ulf,

> > 1) despite not being mentioned in the spec, do we want to allow CMD12 to
> >    abort tuning for SD as well?
> 
> It sounds like we should give it a try with the CMD12 command for SD
> cards as well.

I think so.

> > 2) If so, how to make sure not apply it to SDIO but SD only?
> 
> For now, I am fine with adding a new bus_ops callback
> (->abort_tuning()) and then let mmc_send_abort_tuning() to call it.

Cool, I like that approach.

> I have some additional plans to improve life cycle issues for the
> bus_ops, but let's ignore that for now. I can deal with that later.

Ok, good.

> That said, mmc_send_abort_tuning() should no longer need to take the
> opcode as an in-parameter, thus some additional cleanup should be
> needed in a few host drivers because of that.
> 
> Would that work?

I think that would work nicely. I will have a go with the above approach
and come back then. Or do you want to implement it?

Thanks and happy hacking,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-09-09 13:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31 13:33 [PATCH RFC] HACK: mmc: core: also abort tuning with CMD12 for SD Wolfram Sang
2021-09-09  8:54 ` Ulf Hansson
2021-09-09 13:03   ` Wolfram Sang [this message]
2021-09-09 14:35     ` 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=YToGHbgakZdrY/4R@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=adrian.hunter@intel.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=yoshihiro.shimoda.uh@renesas.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