Messages in this thread |  | | | From | David Woodhouse <> | | Subject | Re: [RFC] I/O Access Abstractions | | Date | Mon, 02 Jul 2001 15:22:56 +0100 |
| |
jes@sunsite.dk said: > But it's going to cost for the ones who do not support this.
You don't need to make it out-of-line for all cases - or indeed in any case where it isn't out-of-line already. Some architectures may have only IO calls out-of-line (many already do). Some may have MMIO calls out-of-line too - some already do that too.
It would just be nice to have a standard way of doing it, and in particular it would be nice to pass the struct resource into the out-of-line functions in the case where they _are_ out of line, so that the Iyou/O functions don't have to play evil tricks with the numbers they're given to work out which bus the caller wanted to talk to.
#ifdef OUT_OF_LINE_MMIO #define res_readb(res, adr) (res->access_ops->readb(res, adr) #else #define res_readb(res, adr) readb(adr) #endif
etc.
-- dwmw2
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |