devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas KANDAGATLA <srinivas.kandagatla@st.com>
To: Girish K S <girish.shivananjappa@linaro.org>
Cc: grant.likely@secretlab.ca, rob.herring@calxeda.com,
	viresh.linux@gmail.com, g.liakhovetski@gmx.de,
	ian@mnementh.co.uk, thomas.ab@samsung.com,
	spear-devel@list.st.com, linux-mmc@vger.kernel.org,
	devicetree-discuss@lists.ozlabs.org
Subject: Re: [RFC PATCH 3.7.0-rc4 2/4] mm:exynos: use of_simple_module_id_table macro.
Date: Fri, 16 Nov 2012 13:37:33 +0000	[thread overview]
Message-ID: <50A6419D.7000609@st.com> (raw)
In-Reply-To: <CAGxe1ZEGn7Oq+6NbWFKwEx53RPS-Xh3MvRdHKNj1sb2kT3vEVg@mail.gmail.com>

On 16/11/12 13:30, Girish K S wrote:
> On 16 November 2012 18:51, Srinivas KANDAGATLA
> <srinivas.kandagatla@st.com> wrote:
>> From: Srinivas Kandagatla <srinivas.kandagatla@st.com>
>>
>> This patch uses of_simple_module_id_table macro to replace code like:
>>
>> #ifdef CONFIG_OF
>>     static struct of_device_id xxx_of_match[] = {
>>         { .compatible = "yyy,xxx" },
>>         { },
>>     };
>>     MODULE_DEVICE_TABLE(of, xxx_of_match);
>> #endif
>>
>> with
>>         of_simple_module_id_table(xxx_of_match, "yyy,zzz");
>>
>> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@st.com>
>> ---
>>  drivers/mmc/host/dw_mmc-exynos.c |    7 +------
>>  1 files changed, 1 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/mmc/host/dw_mmc-exynos.c b/drivers/mmc/host/dw_mmc-exynos.c
>> index 660bbc5..1e9596a 100644
>> --- a/drivers/mmc/host/dw_mmc-exynos.c
>> +++ b/drivers/mmc/host/dw_mmc-exynos.c
>> @@ -218,12 +218,7 @@ static struct dw_mci_drv_data exynos5250_drv_data = {
>>         .setup_bus              = dw_mci_exynos_setup_bus,
>>  };
>>
>> -static const struct of_device_id dw_mci_exynos_match[] = {
>> -       { .compatible = "samsung,exynos5250-dw-mshc",
>> -                       .data = (void *)&exynos5250_drv_data, },
>> -       {},
>> -};
> Here's the problem. You are missing the driver data for the exynos
> SoC. this is very much required.
> where's the  .data = (void *)&exynos5250_drv_data,?
Thanks for looking,
Yep, You are correct.


>> -MODULE_DEVICE_TABLE(of, dw_mci_pltfm_match);
>> +of_simple_module_id_table(dw_mci_pltfm_match, "samsung,exynos5250-dw-mshc");
>>
>>  int dw_mci_exynos_probe(struct platform_device *pdev)
>>  {
>> --
>> 1.7.0.4
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html


      reply	other threads:[~2012-11-16 13:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16 13:21 [RFC PATCH 3.7.0-rc4 2/4] mm:exynos: use of_simple_module_id_table macro Srinivas KANDAGATLA
2012-11-16 13:30 ` Girish K S
2012-11-16 13:37   ` Srinivas KANDAGATLA [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=50A6419D.7000609@st.com \
    --to=srinivas.kandagatla@st.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=girish.shivananjappa@linaro.org \
    --cc=grant.likely@secretlab.ca \
    --cc=ian@mnementh.co.uk \
    --cc=linux-mmc@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=spear-devel@list.st.com \
    --cc=thomas.ab@samsung.com \
    --cc=viresh.linux@gmail.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).