public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/4] usb: gadget: dwc2: Fix warning over 32bit vs 64bit targets
Date: Sun, 28 Jan 2018 10:57:33 +0100	[thread overview]
Message-ID: <20180128105733.2daeed72@jawa> (raw)
In-Reply-To: <35e383b9-62db-f392-16dd-d88f493fa06b@denx.de>

Hi Marek, Tom, Philipp,

> On 01/27/2018 09:17 PM, Dr. Philipp Tomsich wrote:
> >   
> >> On 27 Jan 2018, at 20:56, Tom Rini <trini@konsulko.com> wrote:
> >>
> >> On Sat, Jan 27, 2018 at 08:52:43PM +0100, Marek Vasut wrote:  
> >>> On 01/27/2018 08:48 PM, Tom Rini wrote:  
> >>>> When we have a driver that is used on both 32bit and 64bit
> >>>> targets and we are talking about address space we cannot use u64
> >>>> nor u32 and instead need to use phys_addr_t.  
> >>>
> >>> Can someoneone pass in a pointer above 32bit address range ? That
> >>> might cause some mess ...  
> >>
> >> On rockchip, where this gets used as well, it comes down to writel
> >> and a warning about "cast from pointer to integer of different
> >> size”.  

I'm not sure if DWC2 is prepared to work with 64B pointers. As fair as
I remember it works with 32B.

> > 
> > I had submitted a patch to resolve this middle of last year
> > 	https://patchwork.ozlabs.org/patch/783541/

Unfortunately, I did not received this patch.

> > and used the rationale that this change would make the truncation
> > explicit.
> > 
> > I don’t recall why did this didn’t move anywhere, but darkly
> > remember the discussion veering towards bounce buffers…  
> 
> I'll just bounce this to Lukasz, since he maintains the gadget, but
> the DWC2 UDC driver looks really dark ... ew ...
> 




Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180128/91848388/attachment.sig>

  reply	other threads:[~2018-01-28  9:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-27 19:48 [U-Boot] [PATCH 1/4] mvpp2: Fix warning over 32bit vs 64bit targets Tom Rini
2018-01-27 19:48 ` [U-Boot] [PATCH 2/4] usb: gadget: dwc2: " Tom Rini
2018-01-27 19:52   ` Marek Vasut
2018-01-27 19:56     ` Tom Rini
2018-01-27 20:09       ` Marek Vasut
2018-01-27 20:17       ` Dr. Philipp Tomsich
2018-01-27 20:31         ` Marek Vasut
2018-01-28  9:57           ` Lukasz Majewski [this message]
2018-01-27 19:48 ` [U-Boot] [PATCH 3/4] fs: btrfs: Fix printf format character warning Tom Rini
2018-01-27 22:17   ` Marek Behun
2018-01-27 22:23   ` [U-Boot] [PATCH v2 " Tom Rini
2018-01-27 22:36     ` Marek Behun
2018-01-29 20:21     ` [U-Boot] [U-Boot, v2, " Tom Rini
2018-01-27 19:48 ` [U-Boot] [PATCH 4/4] usb: ehci-mxs: Fix argument order for ehci_writel() Tom Rini
2018-01-27 19:53   ` Marek Vasut
2018-01-27 19:53     ` Tom Rini
2018-01-29  7:15 ` [U-Boot] [PATCH 1/4] mvpp2: Fix warning over 32bit vs 64bit targets Stefan Roese
2018-01-29 17:46 ` Joe Hershberger
2018-01-29 20:20 ` [U-Boot] [U-Boot, " Tom Rini

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=20180128105733.2daeed72@jawa \
    --to=lukma@denx.de \
    --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