[PATCH v7 1/2] iopoll: Introduce memory-mapped IO polling macros
From: arnd@arndb.de (Arnd Bergmann)
Date: 2014-10-30 12:00:23
Also in:
linux-iommu
On Thursday 30 October 2014 11:41:00 Will Deacon wrote:
quoted
+ +#define readl_poll_timeout(addr, val, cond, delay_us, timeout_us) \ + readx_poll_timeout(readl, addr, val, cond, delay_us, timeout_us) + +#define readl_poll_timeout_atomic(addr, val, cond, delay_us, timeout_us) \ + readx_poll_timeout_atomic(readl, addr, val, cond, delay_us, timeout_us) + +#define readb_poll_timeout(addr, val, cond, delay_us, timeout_us) \ + readx_poll_timeout(readb, addr, val, cond, delay_us, timeout_us) + +#define readb_poll_timeout_atomic(addr, val, cond, delay_us, timeout_us) \ + readx_poll_timeout_atomic(readb, addr, val, cond, delay_us, timeout_us) + +#define readw_poll_timeout(addr, val, cond, delay_us, timeout_us) \ + readx_poll_timeout(readw, addr, val, cond, delay_us, timeout_us) + +#define readw_poll_timeout_atomic(addr, val, cond, delay_us, timeout_us) \ + readx_poll_timeout_atomic(readw, addr, val, cond, delay_us, timeout_us) + +#define readq_poll_timeout(addr, val, cond, delay_us, timeout_us) \ + readx_poll_timeout(readq, addr, val, cond, delay_us, timeout_us) + +#define readq_poll_timeout_atomic(addr, val, cond, delay_us, timeout_us) \ + readx_poll_timeout_atomic(readq, addr, val, cond, delay_us, timeout_us)
Sort these by size (b, w, l, q) maybe?
quoted
+#define ioread32_poll_timeout(addr, val, cond, delay_us, timeout_us) \ + readx_poll_timeout(ioread32, addr, val, cond, delay_us, timeout_us) + +#define ioread32_poll_timeout_atomic(addr, val, cond, delay_us, timeout_us) \ + readx_poll_timeout_atomic(ioread32, addr, val, cond, delay_us, timeout_us) + +#define ioread32b3_poll_timeout(addr, val, cond, delay_us, timeout_us) \ + readx_poll_timeout(ioread32b3, addr, val, cond, delay_us, timeout_us) + +#define ioread32b3_poll_timeout_atomic(addr, val, cond, delay_us, timeout_us) \ + readx_poll_timeout_atomic(ioread32b3, addr, val, cond, delay_us, timeout_us)
What is ioread32b3?
quoted
+#define inb_poll_timeout(addr, val, cond, delay_us, timeout_us) \ + readx_poll_timeout(inb, addr, val, cond, delay_us, timeout_us) + +#define inb_poll_timeout_atomic(addr, val, cond, delay_us, timeout_us) \ + readx_poll_timeout_atomic(inb, addr, val, cond, delay_us, timeout_us) + +#define inb_p_poll_timeout(addr, val, cond, delay_us, timeout_us) \ + readx_poll_timeout(inb_p, addr, val, cond, delay_us, timeout_us) + +#define inb_p_poll_timeout_atomic(addr, val, cond, delay_us, timeout_us) \ + readx_poll_timeout_atomic(inb_p, addr, val, cond, delay_us, timeout_us)
I would leave out the _p variants, they are very rarely used anyway.
Looking at the long list, I wonder if we should really define each variant,
or just expect drivers to call readx_poll_timeout{,_atomic} directly and
pass whichever accessor they want.
Arnd