From: Balaji T K <balajitk@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Tony Lindgren <tony@atomide.com>,
Amarinder Bindra <a-bindra@ti.com>, Chris Ball <cjb@laptop.org>,
"uclinux-dist-devel@blackfin.uclinux.org"
<uclinux-dist-devel@blackfin.uclinux.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: Multiple CCR definitions
Date: Fri, 17 Jan 2014 20:05:54 +0530 [thread overview]
Message-ID: <52D93FCA.1090202@ti.com> (raw)
In-Reply-To: <CAGo_u6or57HEqRQjSjUXFpRNiFNbJyRYrsPX19Gf97J-sg4iHQ@mail.gmail.com>
On Friday 17 January 2014 12:09 AM, Nishanth Menon wrote:
> +linux-omap as well.
>
> On Thu, Jan 16, 2014 at 7:07 AM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
>> On Tue, Sep 10, 2013 at 11:05 PM, Linux Kernel Mailing List
>> <linux-kernel@vger.kernel.org> wrote:
>>> mmc: omap_hsmmc: use the generic config for omap2plus devices
>>>
>>> OMAP's hs_mmc driver is used for MMC controller operation on many
>>> omap2plus SoCs (OMAP2430, OMAP3, 4, 5 and AM335x).
>>>
>>> Considering that the device tree entries are already present for these,
>>> allow the driver to be built using the config ARCH_OMAP2PLUS rather
>>> than individually adding a config for each SoC to enable the
>>> support.
>>>
>>> Use COMPILE_TEST to enable the build for other platforms.
>>>
>>> Signed-off-by: Amarinder Bindra <a-bindra@ti.com>
>>> Cc: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
>>> Cc: Nishanth Menon <nm@ti.com>
>>> Acked-by: Felipe Balbi <balbi@ti.com>
>>> Acked-by: Balaji T K <balajitk@ti.com>
>>> Signed-off-by: Chris Ball <cjb@laptop.org>
>>> ---
>>> drivers/mmc/host/Kconfig | 6 +++---
>>> 1 files changed, 3 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/mmc/host/Kconfig b/drivers/mmc/host/Kconfig
>>> index 84102bc..b8ce939 100644
>>> --- a/drivers/mmc/host/Kconfig
>>> +++ b/drivers/mmc/host/Kconfig
>>> @@ -284,11 +284,11 @@ config MMC_OMAP
>>>
>>> config MMC_OMAP_HS
>>> tristate "TI OMAP High Speed Multimedia Card Interface support"
>>> - depends on SOC_OMAP2430 || ARCH_OMAP3 || ARCH_OMAP4
>>> + depends on ARCH_OMAP2PLUS || COMPILE_TEST
>>
>> sh-allmodconfig (http://kisskb.ellerman.id.au/kisskb/buildresult/10477672/):
>> include/linux/omap-dma.h:171:8: error: expected identifier before
>> numeric constant
>> make[4]: *** [drivers/mmc/host/omap_hsmmc.o] Error 1
>>
>> It fails because sh #defines "CCR", which is one of the enum values in
>> include/linux/omap-dma.h.
>>
>> I expect a similar failure on blackfin, which also has #define CCR.
>>
>> Possible solutions:
>> 1. Rename CCR in sh/bfin to e.g. SH_CCR resp. BF_CCR.
>> 2. Use "depends on ARCH_OMAP2PLUS || (COMPILE_TEST && ARM)
omap-dma.h will be needed until all OMAPs are converted to DT only boot.
So depends on ARCH_OMAP2PLUS || (COMPILE_TEST && ARM) looks good to me
>> 3. Stop using include/linux/omap-dma.h, as it says:
>>
>> * Legacy OMAP DMA handling defines and functions
>> *
>> * NOTE: Do not use these any longer.
>> *
>> * Use the generic dmaengine functions as defined in
>> * include/linux/dmaengine.h.
>>
>> Gr{oetje,eeting}s,
>>
>> Geert
>>
>> --
>> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>>
>> In personal conversations with technical people, I call myself a hacker. But
>> when I'm talking to journalists I just say "programmer" or something like that.
>> -- Linus Torvalds
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2014-01-17 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMuHMdVLat9-EMnCX=usthZLrP2YhCCT7-a3nhSQmgLvn_ftBg@mail.gmail.com>
2014-01-16 18:39 ` Multiple CCR definitions (was: Re: mmc: omap_hsmmc: use the generic config for omap2plus devices) Nishanth Menon
2014-01-17 14:35 ` Balaji T K [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=52D93FCA.1090202@ti.com \
--to=balajitk@ti.com \
--cc=a-bindra@ti.com \
--cc=cjb@laptop.org \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=nm@ti.com \
--cc=tony@atomide.com \
--cc=uclinux-dist-devel@blackfin.uclinux.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).