From: Peng Fan <van.freenix@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] fsl: esdhc: consolidate fsl_esdhc_cfg structure
Date: Tue, 29 Mar 2016 09:22:13 +0800 [thread overview]
Message-ID: <20160329012211.GA11150@linux-7smt.suse> (raw)
In-Reply-To: <AM4PR0401MB1732A6E08189E058B4A6B49C9A870@AM4PR0401MB1732.eurprd04.prod.outlook.com>
Hi York,
On Tue, Mar 29, 2016 at 12:33:42AM +0000, york sun wrote:
>On 03/15/2016 03:14 AM, Peng Fan wrote:
>> We can use phys_addr_to for esdhc_base to discard
>> the #ifdef.
>>
>> Signed-off-by: Peng Fan <van.freenix@gmail.com>
>> Cc: York Sun <york.sun@nxp.com>
>> Cc: Yangbo Lu <yangbo.lu@nxp.com>
>> Cc: Eric Nelson <eric@nelint.com>
>> Cc: Fabio Estevam <fabio.estevam@nxp.com>
>> Cc: Pantelis Antoniou <panto@antoniou-consulting.com>
>> Cc: Tom Rini <trini@konsulko.com>
>> ---
>>
>> V2:
>> Split this patch from the V1 patch set.
>>
>> include/fsl_esdhc.h | 6 +-----
>> 1 file changed, 1 insertion(+), 5 deletions(-)
>>
>> diff --git a/include/fsl_esdhc.h b/include/fsl_esdhc.h
>> index 073048f..fa760a5 100644
>> --- a/include/fsl_esdhc.h
>> +++ b/include/fsl_esdhc.h
>> @@ -168,11 +168,7 @@
>> #define ESDHC_VENDORSPEC_VSELECT 0x00000002 /* Use 1.8V */
>>
>> struct fsl_esdhc_cfg {
>> -#ifdef CONFIG_FSL_LAYERSCAPE
>> - u64 esdhc_base;
>> -#else
>> - u32 esdhc_base;
>> -#endif
>> + phys_addr_t esdhc_base;
>> u32 sdhc_clk;
>> u8 max_bus_width;
>> struct mmc_config cfg;
>>
>
>Peng,
>
>I thought this change is trivial and should be OK. But it turns out this change
>brings comping warning to many PPC boards
>
>drivers/mmc/fsl_esdhc.c:184:27: warning: cast to pointer from integer of
>different size [-Wint-to-pointer-cast]
You can apply https://patchwork.ozlabs.org/patch/601919/ and retest.
I think the reason is that to PPC 64bit, "typedef unsigned long long phys_addr_t"
I think "esdhc_regs = (struct fsl_esdhc *)(unsigned long)(cfg->esdhc_base);"
can fix it.
Do I need to send a single V3 patch to fix the warning, or you apply the
driver model V3 patch, if the driver model V3 can fix it?
Regards,
Peng.
>
>For assignment like this
>
>struct fsl_esdhc *regs = (struct fsl_esdhc *)cfg->esdhc_base;
>
>The phys_addr is not u32 for many targets.
>
>York
>
next prev parent reply other threads:[~2016-03-29 1:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 9:57 [U-Boot] [PATCH V2] fsl: esdhc: consolidate fsl_esdhc_cfg structure Peng Fan
2016-03-15 13:58 ` Tom Rini
2016-03-29 0:33 ` york sun
2016-03-29 1:22 ` Peng Fan [this message]
2016-03-29 1:35 ` york sun
2016-03-29 4:37 ` Peng Fan
2016-03-29 4:49 ` York Sun
2016-04-05 3:01 ` Peng Fan
2016-04-05 3:20 ` york sun
2016-04-06 17:22 ` York Sun
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=20160329012211.GA11150@linux-7smt.suse \
--to=van.freenix@gmail.com \
--cc=u-boot@lists.denx.de \
/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