From: Michal Simek <monstr@monstr.eu>
To: Jingoo Han <jg1.han@samsung.com>
Cc: "'Michal Simek'" <michal.simek@xilinx.com>,
"'Jean-Christophe Plagniol-Villard'" <plagnioj@jcrosoft.com>,
"'Tomi Valkeinen'" <tomi.valkeinen@ti.com>,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"'Stepan Moskovchenko'" <stepanm@codeaurora.org>
Subject: Re: [PATCH] video: xilinxfb: Fix compilation warning
Date: Wed, 24 Jul 2013 09:18:21 +0200 [thread overview]
Message-ID: <51EF7FBD.8070103@monstr.eu> (raw)
In-Reply-To: <007401ce8833$22ce0600$686a1200$@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]
On 07/24/2013 08:00 AM, Jingoo Han wrote:
> On Wednesday, July 24, 2013 2:32 PM, Michal Simek wrote:
>>
>> regs_phys is phys_addr_t (u32 or u64).
>> Lets retype it to u64.
>>
>> Fixes compilation warning introduced by:
>> video: xilinxfb: Use drvdata->regs_phys instead of physaddr
>> (sha1: c88fafef0135e1e1c3e23c3e32ccbeeabc587f81)
>
> CC'ed Stepan Moskovchenko
>
>
> phys_addr_t is defined as below:
>
> #ifdef CONFIG_PHYS_ADDR_T_64BIT
> typedef u64 phys_addr_t;
> #else
> typedef u32 phys_addr_t;
> #endif
>
> According to 'Documentation/printk-formats.txt',
> Physical addresses:
> %pa 0x01234567 or 0x0123456789abcdef
> For printing a phys_addr_t type (and its derivatives, such as
> resource_size_t) which can vary based on build options, regardless of
> the width of the CPU data path. Passed by reference.
>
> Thus, '%pa' option looks proper, instead of casting (unsigned long long).
>
> dev_dbg(dev, "regs: phys=%pa, virt=%p\n", drvdata->regs_phys,
> drvdata->regs);
>
Ah. Wasn't aware about that.
Will retest.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-07-24 7:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 5:31 [PATCH] video: xilinxfb: Fix compilation warning Michal Simek
2013-07-24 6:00 ` Jingoo Han
2013-07-24 7:18 ` Michal Simek [this message]
2013-07-24 7:41 ` Michal Simek
2013-07-24 8:08 ` Jingoo Han
2013-07-24 8:24 ` Michal Simek
2013-07-25 10:09 ` Geert Uytterhoeven
[not found] ` <CAAY4GiVG-c63oJO1Kqv0Jf2Wa2Ba+hgLtHQYFqyuRW-f6hJ14Q@mail.gmail.com>
2013-07-24 7:17 ` Michal Simek
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=51EF7FBD.8070103@monstr.eu \
--to=monstr@monstr.eu \
--cc=jg1.han@samsung.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=plagnioj@jcrosoft.com \
--cc=stepanm@codeaurora.org \
--cc=tomi.valkeinen@ti.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