Messages in this thread | | | Date | Tue, 18 Oct 2011 14:07:30 +0530 | Subject | Re: [PATCHv4] DMAEngine: Define interleaved transfer request api | From | Jassi Brar <> |
| |
On 18 October 2011 13:56, Vinod Koul <vinod.koul@intel.com> wrote: > On Tue, 2011-10-18 at 14:00 +0530, Jassi Brar wrote: >> On 18 October 2011 13:12, Russell King <rmk@arm.linux.org.uk> wrote: >> > On Tue, Oct 18, 2011 at 11:15:29AM +0530, Jassi Brar wrote: >> >> On 18 October 2011 02:37, Bounine, Alexandre <Alexandre.Bounine@idt.com> wrote: >> >> > With item #1 above being a separate topic, I may have a problem with #2 >> >> > as well: dma_addr_t is sized for the local platform and not guaranteed >> >> > to be a 64-bit value (which may be required by a target). >> >> > Agree with #3 (if #1 and #2 work). >> >> > >> >> Perhaps simply change dma_addr_t to u64 in dmaengine.h alone ? >> > >> > That's just an idiotic suggestion - there's no other way to put that. >> > Let's have some sanity here. >> > >> Yeah, I am not proud of the workaround, so I only probed the option. >> I think I need to explain myself. >> >> The case here is that even a 32-bit RapidIO host could ask transfer against >> 64-bit address space on a remote device. And vice versa 64->32. > I thought RIO address were always 64 + 2 bits, irrespective of what the > host system is... > No, not always. RIO address could be 32, 48 or 64... with the role extra 2 bits not very clear.
| |