On Sun, Jul 26, 2020 at 12:00:37PM +0300, Andy Shevchenko wrote:
> On Sun, Jul 26, 2020 at 6:14 AM Stafford Horne <shorne@xxxxxxxxx> wrote:
> >
> > The return type of functions _inb, _inw and _inl are all u16 which looks
> > wrong. This patch makes them u8, u16 and u32 respectively.
> >
> > The original commit text for these does not indicate that these should
> > be all forced to u16.
>
> Is it in alight with all architectures? that support this interface natively?
>
> (Return value is arch-dependent AFAIU, so it might actually return
> 16-bit for byte read, but I agree that this is weird for 32-bit value.
> I think you have elaborate more in the commit message)
Well, this is the generic io code, at least these api's appear to not be different
for each architecture. The output read by the architecture dependant code i.e.
__raw_readb() below is getting is placed into a u8. So I think the output of
the function will be u8.
static inline u8 _inb(unsigned long addr)
{
u8 val;
__io_pbr();
val = __raw_readb(PCI_IOBASE + addr);
__io_par(val);
return val;
}
I can expand the commit text, but I would like to get some comments from the
original author to confirm if this is an issue.
-Stafford
