linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ulf Hansson <ulf.hansson@linaro.org>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Jaehoon Chung <jh80.chung@samsung.com>
Subject: Re: [PATCH] mmc: dw_mmc: Add support for multiple SD cards on one host interface
Date: Mon, 2 Oct 2017 09:12:30 +0200	[thread overview]
Message-ID: <CAPDyKFr3==eZQOojPac4fse8baHa+UXweOezdb9vFiSB9jae_Q@mail.gmail.com> (raw)
In-Reply-To: <AM5PR0701MB2657094CA5D94164E6D63A8DE47F0@AM5PR0701MB2657.eurprd07.prod.outlook.com>

On 30 September 2017 at 17:39, Bernd Edlinger <bernd.edlinger@hotmail.de> wrote:
>
> Needs external logic to multiplex the clock signal,
> which is controlled by a GPIO output pin.
>
> Only the selected SD card receives the clock,
> while the other SD card's clock is forced to LOW.
> DATA and CMD lines can be connected to both SD cards.
>
> On warm-start UBOOT should use a sequence of
> CMD12 and CMD7 with RCA=0 to force any active SD card
> to stop transmission and release the DATA bus.

I doubt that is sufficient to support multiple slots.

Sometimes the mmc core needs to perform a sequence of operations
towards *one* host/card and that must be done in guaranteed manner, to
that no other operations are performed for another card/host
in-between.

Perhaps if you are lucky you may get something that is very fragile to
work, but in the end I think the core needs to play along. Moreover,
dw_mmc has recently removed its multiple slot support - simply because
the complexity wasn't worth it.

Unless Jaehoon have changed his mind, I am not going to pick this up.

[...]

Kind regards
Uffe

  reply	other threads:[~2017-10-02  7:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-30 15:39 [PATCH] mmc: dw_mmc: Add support for multiple SD cards on one host interface Bernd Edlinger
2017-10-02  7:12 ` Ulf Hansson [this message]
2017-10-02 14:31   ` Bernd Edlinger
2017-10-10  7:59     ` 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='CAPDyKFr3==eZQOojPac4fse8baHa+UXweOezdb9vFiSB9jae_Q@mail.gmail.com' \
    --to=ulf.hansson@linaro.org \
    --cc=bernd.edlinger@hotmail.de \
    --cc=jh80.chung@samsung.com \
    --cc=linux-mmc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).