From: Yusuke Goda <yusuke.goda.sx@renesas.com>
To: Arnd Hannemann <arnd@arndnet.de>
Cc: ian@mnementh.co.uk, sameo@linux.intel.com,
linux-mmc@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH 4/4] ARM: mach-shmobile: ap4evb: Fix hotplug for SDHI1
Date: Thu, 26 Aug 2010 05:00:13 +0000 [thread overview]
Message-ID: <4C75F4DD.5020804@renesas.com> (raw)
In-Reply-To: <1282663622-20564-5-git-send-email-arnd@arndnet.de>
Arnd Hannemann wrote:
> On AP4EVB the card detect pin of the top SD/MMC slot is not directly connected
> to the tmio/mmcif controller but to a GPIO pin, so polling needs to be done for
> SDHI1 and MMCIF in order to support hotplug for that slot. SHDI1 and MMCIF
> share that slot, and the used controller is selected by a DIP switch.
> This patch adds a helper function to check if a card is present in that
> particular slot, registers this function with SDHI1 and MMCIF and enables
> polling for SDHI1.
>
> Signed-off-by: Arnd Hannemann <arnd@arndnet.de>
I confirmed normal operation in the following environment.
- AP4EVB board
- CN7 (MMCIF)
Tested-by: Yusuke Goda <yusuke.goda.sx@renesas.com>
prev parent reply other threads:[~2010-08-26 5:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 15:26 [PATCH 0/4] Fix/improve hotplug for sh_mobile_sdhi/tmio_mmc/sh_mmcif Arnd Hannemann
2010-08-24 15:26 ` [PATCH 1/4] tmio_mmc: Allow the mfd driver to specify get_cd handler Arnd Hannemann
2010-09-10 16:10 ` [PATCH 1/4] tmio_mmc: Allow the mfd driver to specify get_cd Samuel Ortiz
2010-09-12 12:51 ` Arnd Hannemann
2010-08-24 15:27 ` [PATCH 2/4] sh_mobile_sdhi: Allow the platform " Arnd Hannemann
2010-08-24 15:27 ` [PATCH 3/4] sh_mmcif: Allow the platform to specify own get_cd handler Arnd Hannemann
2010-08-26 4:59 ` [PATCH 3/4] sh_mmcif: Allow the platform to specify own get_cd Yusuke Goda
2010-08-24 15:27 ` [PATCH 4/4] ARM: mach-shmobile: ap4evb: Fix hotplug for SDHI1 Arnd Hannemann
2010-08-26 5:00 ` Yusuke Goda [this message]
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=4C75F4DD.5020804@renesas.com \
--to=yusuke.goda.sx@renesas.com \
--cc=arnd@arndnet.de \
--cc=ian@mnementh.co.uk \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=sameo@linux.intel.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).