Re: RFC: extending struct pci_ops to include HW specific read and write functions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>
> What you can do is abuse the iomap/io{read,write}{8,16,32} interfaces to
> sort this out.  Because iomap has to cope with port addresses as well
> as memory addresses, the ioread8 (et al) functions are allowed to be a
> bit more complex.
>

I just located another example (at
~/arch/arm/mach-ixp4xx/include/mach/io.h) along the same lines of
'tagging' the most significant bits of an address to indicate if it
should be handled differently by 'io{read,write}{8,16,32}'.

Thanks,

Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux