Re: [RFC v1 01/16] lib: devres: don't enclose pcim_*() functions inCONFIG_HAS_IOPORT

From: Alan Cox
Date: Tue Dec 11 2012 - 12:11:31 EST


> Correct. If HAS_IOPORT is not selected then we are potentially missing
> the dependent functions (because the platform has no IOPORT support) _or_
> it does have ISA/PCI IO spaces _but_ they're not mappable via the
> ioport_map() mechanism due to some non-linearity involved in the
> translation.
>
> To make that second point clear, that's platforms where:
>
> ioport_map(addr + 4) != ioport_map(addr) + 4.

For inb/inw and friends this shouldn't matter.

You can implement inl for example

as

if (unlikely(addr & 3))
// or in fact BUG on this for almost all h/w
uninlined_hard_slow_inl(addr);
else
return *(u32 *)iospace_map[addr];






--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/