devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: "Manjunathappa, Prakash" <prakash.pm@ti.com>
Cc: linux-mmc@vger.kernel.org, grant.likely@secretlab.ca,
	rob.herring@calxeda.com, rob@landley.net, linux@arm.linux.org.uk,
	hs@denx.de, devicetree-discuss@lists.ozlabs.org,
	linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	cjb@laptop.org, davinci-linux-open-source@linux.davincidsp.com
Subject: Re: [PATCH v5 1/4] ARM: davinci: mmc: derive version information from device name
Date: Thu, 14 Mar 2013 16:38:09 +0530	[thread overview]
Message-ID: <5141AF99.5090608@ti.com> (raw)
In-Reply-To: <1363097637-11371-2-git-send-email-prakash.pm@ti.com>

Prakash,

The series looks good to me. I tested it again on DA850 EVM (with and
without DT).

On 3/12/2013 7:43 PM, Manjunathappa, Prakash wrote:
> Remove specifying mmc controller IP version information via platform
> data, instead specify device name so that driver derives it from
> platform_device_id table. Also change the clock node name to match
> the changed dev_id.
> Tested on da850-evm to make sure driver loads without clk_get failures.
> 
> Signed-off-by: Manjunathappa, Prakash <prakash.pm@ti.com>
> Reviewed-by: Sekhar Nori <nsekhar@ti.com>
> ---

> diff --git a/drivers/mmc/host/davinci_mmc.c b/drivers/mmc/host/davinci_mmc.c
> index 27123f8..50e9782 100644
> --- a/drivers/mmc/host/davinci_mmc.c
> +++ b/drivers/mmc/host/davinci_mmc.c
> @@ -1157,6 +1157,18 @@ static void __init init_mmcsd_host(struct mmc_davinci_host *host)
>  	mmc_davinci_reset_ctrl(host, 0);
>  }
>  
> +static struct platform_device_id davinci_mmc_devtype[] = {
> +	{
> +		.name	= "davinci-mmc-dm355",
> +		.driver_data = MMC_CTLR_VERSION_1,
> +	}, {
> +		.name	= "davinci-mmc-da830",
> +		.driver_data = MMC_CTLR_VERSION_2,
> +	},
> +	{},
> +};
> +MODULE_DEVICE_TABLE(platform, davinci_mmc_devtype);

I should have mentioned this previously, but your choice of name here is
too long. You can simply use dm355-mmc (rather dm6441-mmc?) and
da830-mmc instead like you did for SPI. This would have saved some long
lines. Sorry about not asking for this earlier. I know it would have
saved you a bunch of effort.

Thanks,
Sekhar

  reply	other threads:[~2013-03-14 11:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 14:13 [PATCH v5 0/4] Add DT support for davinci_mmc driver Manjunathappa, Prakash
2013-03-12 14:13 ` [PATCH v5 1/4] ARM: davinci: mmc: derive version information from device name Manjunathappa, Prakash
2013-03-14 11:08   ` Sekhar Nori [this message]
2013-03-14 13:51     ` Manjunathappa, Prakash
2013-03-12 14:13 ` [PATCH v5 2/4] mmc: davinci_mmc: add DT support Manjunathappa, Prakash
2013-03-12 14:13 ` [PATCH v5 3/4] ARM: davinci: da850: add mmc DT entries Manjunathappa, Prakash
2013-03-12 14:13 ` [PATCH v5 4/4] ARM: davinci: da850: override mmc DT node device name Manjunathappa, Prakash
2013-03-14 11:55 ` [PATCH v5 0/4] Add DT support for davinci_mmc driver Sekhar Nori
2013-03-14 13:52   ` Manjunathappa, Prakash

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=5141AF99.5090608@ti.com \
    --to=nsekhar@ti.com \
    --cc=cjb@laptop.org \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=hs@denx.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=prakash.pm@ti.com \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    /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).