>On May 12, 2009, at 3:35 AM, Li Yang wrote: > >> Add the mapping functions used to support direct IO memory access of >> rapidIO. >> >> Signed-off-by: Zhang Wei <z...@zh-kernel.org> >> Signed-off-by: Li Yang <le...@freescale.com> > >Use inbnd/outbnd instead of inb/outb which make one think of >byte level io accessors. > >As I look at this I don't think this is the correct API. I >think we should be using the DMA mapping API to hide these >details. The concept of mapping like this seems to be more a >function of FSL's Address translation/mapping unit (ATMU) than >anything specific to the RIO bus standard.
This is a separate RIO block level ATMU. Although it looks like the system level ATMU, system ATMU doesn't have the knowledge of rapidIO target device ID. The mapping need to be dynamic, as it's easy to have more RIO devices than the outbound windows. - Leo _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
