From: Greg Ungerer <gerg@linux-m68k.org>
To: Angelo Dureghello <angelo.dureghello@timesys.com>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH] m68knommu: include SDHC support only when hardware has it
Date: Mon, 21 Sep 2020 22:22:46 +1000 [thread overview]
Message-ID: <694273da-be1c-56ab-d06d-2365451a661b@linux-m68k.org> (raw)
In-Reply-To: <CALJHbkD=eujoo5Cx+5YwGkFRmmZ4i=Vpvznm=5+=5n3fKOBR_Q@mail.gmail.com>
Hi Angelo,
On 21/9/20 5:38 pm, Angelo Dureghello wrote:
> Hi Greg,
>
> thanks a lot for the fix.
>
> On Mon, Sep 21, 2020 at 5:09 AM Greg Ungerer <gerg@linux-m68k.org> wrote:
>>
>> The mere fact that the kernel has the MMC subsystem enabled (CONFIG_MMC
>> enabled) does not mean that the underlying hardware platform has the
>> SDHC hardware present. Within the ColdFire hardware defines that is
>> signified by MCFSDHC_BASE being defined with an address.
>>
>> The platform data for the ColdFire parts is including the SDHC hardware
>> if CONFIG_MMC is enabled, instead of MCFSDHC_BASE. This means that if
>> you are compiling for a ColdFire target that does not support SDHC but
>> enable CONFIG_MMC you will fail to compile with errors like this:
>>
>> arch/m68k/coldfire/device.c:565:12: error: ‘MCFSDHC_BASE’ undeclared here (not in a function)
>> .start = MCFSDHC_BASE,
>> ^
>> arch/m68k/coldfire/device.c:566:25: error: ‘MCFSDHC_SIZE’ undeclared here (not in a function)
>> .end = MCFSDHC_BASE + MCFSDHC_SIZE - 1,
>> ^
>> arch/m68k/coldfire/device.c:569:12: error: ‘MCF_IRQ_SDHC’ undeclared here (not in a function)
>> .start = MCF_IRQ_SDHC,
>> ^
>>
>> Make the SDHC platform support depend on MCFSDHC_BASE, that is only
>> include it if the specific ColdFire SoC has that hardware module.
>>
>> Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
>> ---
>> arch/m68k/coldfire/device.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/arch/m68k/coldfire/device.c b/arch/m68k/coldfire/device.c
>> index 9ef4ec0aea00..59f7dfe50a4d 100644
>> --- a/arch/m68k/coldfire/device.c
>> +++ b/arch/m68k/coldfire/device.c
>> @@ -554,7 +554,7 @@ static struct platform_device mcf_edma = {
>> };
>> #endif /* IS_ENABLED(CONFIG_MCF_EDMA) */
>>
>> -#if IS_ENABLED(CONFIG_MMC)
>> +#ifdef MCFSDHC_BASE
>> static struct mcf_esdhc_platform_data mcf_esdhc_data = {
>> .max_bus_width = 4,
>> .cd_type = ESDHC_CD_NONE,
>> @@ -579,7 +579,7 @@ static struct platform_device mcf_esdhc = {
>> .resource = mcf_esdhc_resources,
>> .dev.platform_data = &mcf_esdhc_data,
>> };
>> -#endif /* IS_ENABLED(CONFIG_MMC) */
>> +#endif /* MCFSDHC_BASE */
>>
>> static struct platform_device *mcf_devices[] __initdata = {
>> &mcf_uart,
>> @@ -613,7 +613,7 @@ static struct platform_device *mcf_devices[] __initdata = {
>> #if IS_ENABLED(CONFIG_MCF_EDMA)
>> &mcf_edma,
>> #endif
>> -#if IS_ENABLED(CONFIG_MMC)
>> +#ifdef MCFSDHC_BASE
>> &mcf_esdhc,
>> #endif
>> };
>> --
>> 2.25.1
>>
>
> Tested on mcf54418 stmark2.
>
> Reviewed-by: Angelo Dureghello <angelo.dureghello@timesys.com>
> Tested-by: Angelo Dureghello <angelo.dureghello@timesys.com>
Thanks, will add those.
Regards
Greg
prev parent reply other threads:[~2020-09-21 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 3:08 [PATCH] m68knommu: include SDHC support only when hardware has it Greg Ungerer
2020-09-21 7:23 ` Geert Uytterhoeven
2020-09-21 12:22 ` Greg Ungerer
2020-09-21 7:38 ` Angelo Dureghello
2020-09-21 12:22 ` Greg Ungerer [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=694273da-be1c-56ab-d06d-2365451a661b@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=angelo.dureghello@timesys.com \
--cc=linux-m68k@vger.kernel.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