From: Joe Perches <joe@perches.com>
To: Emil Goode <emilgoode@gmail.com>,
Stepan Moskovchenko <stepanm@codeaurora.org>
Cc: balbi@ti.com, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] usb: musb: use the new %pa format specifier for dma_addr_t
Date: Sat, 01 Jun 2013 20:31:25 +0000 [thread overview]
Message-ID: <1370118685.2098.7.camel@joe-AO722> (raw)
In-Reply-To: <20130601190926.GA5541@debian>
On Sat, 2013-06-01 at 21:09 +0200, Emil Goode wrote:
> I see, will send a second version.
Hey Emil.
I believe you can not use %pa with a dma_addr_t
because that could be a different size than a
phy_addr_t.
(the vsprintf cast and deref is to a phy_addr_t)
The definitions are: (types.h)
#ifdef CONFIG_ARCH_DMA_ADDR_T_64BIT
typedef u64 dma_addr_t;
#else
typedef u32 dma_addr_t;
#endif /* dma_addr_t */
[]
#ifdef CONFIG_PHYS_ADDR_T_64BIT
typedef u64 phys_addr_t;
#else
typedef u32 phys_addr_t;
#endif
On Sat, Jun 01, 2013 at 11:29:10AM -0700, Joe Perches wrote:
> On Sat, 2013-06-01 at 20:02 +0200, Emil Goode wrote:
> > This patch makes use of the new format specifier %pa that was introduced
> > by the following commit.
> >
> > 7d7992108d02aa92ad4c77e5d9ce14088c942e75
> > ("lib/vsprintf.c: add %pa format specifier for phys_addr_t types")
> []
> > diff --git a/drivers/usb/musb/musb_host.c b/drivers/usb/musb/musb_host.c
> []
> > @@ -1756,12 +1756,11 @@ void musb_host_rx(struct musb *musb, u8 epnum)
> []
> > - dev_dbg(musb->controller, "RX%d count %d, buffer 0x%llx len %d/%d\n",
> > + dev_dbg(musb->controller, "RX%d count %d, buffer 0x%pa len %d/%d\n",
>
> This would emit 0x0x<addr>
next prev parent reply other threads:[~2013-06-01 20:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 18:02 [PATCH] usb: musb: use the new %pa format specifier for dma_addr_t Emil Goode
2013-06-01 18:29 ` Joe Perches
2013-06-01 19:09 ` Emil Goode
2013-06-01 20:31 ` Joe Perches [this message]
2013-06-01 21:56 ` Randy Dunlap
2013-06-01 22:16 ` Joe Perches
2013-06-01 23:06 ` Emil Goode
2013-06-01 23:22 ` Joe Perches
2013-06-02 13:32 ` Emil Goode
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=1370118685.2098.7.camel@joe-AO722 \
--to=joe@perches.com \
--cc=balbi@ti.com \
--cc=emilgoode@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stepanm@codeaurora.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