linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: fabio.estevam@freescale.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmc: mmc_mxc: Allow selection only for the correct platforms
Date: Fri, 21 Jan 2011 14:11:46 -0200	[thread overview]
Message-ID: <4D39B042.5050004@freescale.com> (raw)
In-Reply-To: <20110121153351.GR14956@pengutronix.de>

Hi Uwe,

On 1/21/2011 1:33 PM, Uwe Kleine-K?nig wrote:
> Hallo,
> 
> On Thu, Jan 20, 2011 at 03:02:59PM -0200, Fabio Estevam wrote:
>> Currently MMC_MXC driver can be selected by all i.MX devices.
>>
>> Restrict its use only for the appropriate processors.
>>
>> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
>> ---
>>  drivers/mmc/host/Kconfig |    2 +-
>>  1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/mmc/host/Kconfig b/drivers/mmc/host/Kconfig
>> index d618e86..a3a9ec1 100644
>> --- a/drivers/mmc/host/Kconfig
>> +++ b/drivers/mmc/host/Kconfig
>> @@ -288,7 +288,7 @@ config MMC_MSM
>>  
>>  config MMC_MXC
>>  	tristate "Freescale i.MX2/3 Multimedia Card Interface support"
>> -	depends on ARCH_MXC
>> +	depends on MACH_MX21 || MACH_MX27 || ARCH_MX31
> What about
> 
> 	depends IMX_HAVE_PLATFORM_MXC_MMC

I would prefer to let the architectures explicitly in Kconfig.

If someone selects IMX_HAVE_PLATFORM_MXC_MMC by mistake on a MX51 board, it will be possible to select the MXC_MMC driver in the kernel for MX51, which is incorrect.

Using the approach of explicitly marking the architectures that support MXC_MMC would avoid such problems as well.
> 
> ?  Then if i.MX29 has the same IP you don't need to touch this again.

Not likely to happen. 

Thanks,

Fabio Estevam

  reply	other threads:[~2011-01-21 16:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 17:02 [PATCH] mmc: mmc_mxc: Allow selection only for the correct platforms Fabio Estevam
2011-01-21 10:35 ` Sascha Hauer
2011-02-09  0:40   ` Estevam Fabio-R49496
2011-02-09  0:54     ` Chris Ball
2011-01-21 15:33 ` Uwe Kleine-König
2011-01-21 16:11   ` Fabio Estevam [this message]
2011-01-21 19:32     ` Uwe Kleine-König

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=4D39B042.5050004@freescale.com \
    --to=fabio.estevam@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.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).