From: Doug Anderson <dianders@chromium.org>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: linux-mmc@vger.kernel.org, Olof Johansson <olof@lixom.net>,
Alim Akhtar <alim.akhtar@samsung.com>,
Thomas P Abraham <thomas.ab@samsung.com>,
Chris Ball <cjb@laptop.org>, Will Newton <will.newton@imgtec.com>,
Seungwon Jeon <tgih.jun@samsung.com>,
James Hogan <james.hogan@imgtec.com>,
linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [PATCH 1/2] mmc: core: Add a capability for disabling mmc cards
Date: Wed, 22 Aug 2012 08:44:03 -0700 [thread overview]
Message-ID: <CAD=FV=UZM9b6++DkgemZA7qpAZgFN+NyyLjRecgSdjcEsu0YYA@mail.gmail.com> (raw)
In-Reply-To: <50346181.3010406@samsung.com>
Jaehoon,
On Tue, Aug 21, 2012 at 9:35 PM, Jaehoon Chung <jh80.chung@samsung.com> wrote:
>
> Hi Doug,
>
> I didn't know what purpose is.
> Why need to add the MMC_CAP2_NO_MMC?
> If card is SD or SDIO, mmc_attach_mmc(host) should not be entered.
> Could you explain to me in more detail?
Thanks for your feedback. In this case I have a card that is an MMC
card so mmc_attach_sdio() and mmc_attach_sd() will fail. If I let
mmc_attach_mmc() run it will actually find the MMC card. However, on
this platform it is not valid to recognize MMC cards.
-Doug
next prev parent reply other threads:[~2012-08-22 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 4:05 [PATCH 1/2] mmc: core: Add a capability for disabling mmc cards Doug Anderson
2012-08-22 4:05 ` [PATCH 2/2] mmc: dw_mmc: Add a DISABLE_MMC quirk that sets the core mmc cap Doug Anderson
2012-08-22 4:35 ` [PATCH 1/2] mmc: core: Add a capability for disabling mmc cards Jaehoon Chung
2012-08-22 15:44 ` Doug Anderson [this message]
2012-08-22 16:00 ` Philip Rakity
2012-08-22 16:50 ` Olof Johansson
2012-08-22 18:25 ` Nicolas Pitre
2012-08-22 18:27 ` Olof Johansson
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='CAD=FV=UZM9b6++DkgemZA7qpAZgFN+NyyLjRecgSdjcEsu0YYA@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=cjb@laptop.org \
--cc=james.hogan@imgtec.com \
--cc=jh80.chung@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=tgih.jun@samsung.com \
--cc=thomas.ab@samsung.com \
--cc=ulf.hansson@linaro.org \
--cc=will.newton@imgtec.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;
as well as URLs for NNTP newsgroup(s).