public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Hector Palacios <hector.palacios@digi.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"maxime.ripard@free-electrons.com"
	<maxime.ripard@free-electrons.com>,
	"fabio.estevam@freescale.com" <fabio.estevam@freescale.com>
Subject: Re: [PATCH RFC] ARM: dts: mxs: leave card detect out of common mmc pins config
Date: Mon, 8 Apr 2013 18:28:26 +0200	[thread overview]
Message-ID: <201304081828.27127.marex@denx.de> (raw)
In-Reply-To: <20130408145019.GD5044@S2101-09.ap.freescale.net>

Dear Shawn Guo,

> On Mon, Apr 08, 2013 at 03:58:05PM +0200, Hector Palacios wrote:
> > On 04/08/2013 02:48 PM, Shawn Guo wrote:
> > >On Mon, Apr 08, 2013 at 12:12:20PM +0200, Hector Palacios wrote:
> > >>MicroSD card sockets don't usually have card detect line. This pin
> > >>is actually not needed for the MMC to work and it is more of a
> > >>platform design decission to have it.
> > >>The card detect pin already has a configuration entry of its own:
> > >>'mmc0_cd_cfg' so we complete the iomux configuration here and let
> > >>platforms to include it or not depending on whether the card detect
> > >>line is routed to the SD socket.
> > >
> > >Sounds sensible.
> > >
> > >>Signed-off-by: Hector Palacios <hector.palacios@digi.com>
> > >>---
> > >>
> > >>Hello,
> > >>
> > >>All imx28 based platforms except 'bluegiga,apx4devkit' and
> > >>'schulercontrol,imx28-sps1', use 'mmc0_cd_cfg' in their mmc
> > >>configuration so please check whether this patch would break these
> > >>platforms.
> > >
> > >I just tested the patch on imx28-evk and card-detection still works.  So
> > >patches applied, thanks.
> > 
> > The EVK and most platforms will work because they are using
> > 'mmc0_cd_cfg' so actually this patch does not change anything on
> > them.
> > Platforms 'bluegiga,apx4devkit' and 'schulercontrol,imx28-sps1'
> > however are not referencing 'mmc0_cd_cfg' so after applying this
> > patch they will have unconfigured CD line and they may break.
> 
> Ah, yes.  I thought that any board that has CD support has to reference
> 'mmc0_cd_cfg'.  That's not necessarily true.
> 
> > The driver will call get_cd() upon probing, which returns the status of
> > the CD line. Please check these two platforms before applying.
> 
> Ok, let's wait for people owning the boards to confirm.

Maybe you want to use MMC_CAP_NEEDS_POLL as was noted by someone before on the 
olinuxino -- the slot is there, it's just the CD line that's missing.

Best regards,
Marek Vasut

  reply	other threads:[~2013-04-08 16:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 10:12 [PATCH RFC] ARM: dts: mxs: leave card detect out of common mmc pins config Hector Palacios
2013-04-08 12:48 ` Shawn Guo
2013-04-08 13:58   ` Hector Palacios
2013-04-08 14:50     ` Shawn Guo
2013-04-08 16:28       ` Marek Vasut [this message]
2013-04-09  7:18         ` Hector Palacios
2013-04-09  8:15           ` Marek Vasut
2013-04-09  9:00             ` Hector Palacios
2013-04-09 10:51               ` Marek Vasut
2013-04-10  8:56                 ` Hector Palacios

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=201304081828.27127.marex@denx.de \
    --to=marex@denx.de \
    --cc=fabio.estevam@freescale.com \
    --cc=hector.palacios@digi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=shawn.guo@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