[lkml]   [2007]   [Sep]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] Clarify pci_iomap() usage for MMIO-only devices
    On 9/18/07, Linus Torvalds <> wrote:
    > On Tue, 18 Sep 2007, Luis R. Rodriguez wrote:
    > >
    > > ACK -- driver developers use this just to save themselves a few lines
    > > from calling pci_resource_start() and friends. How about having an
    > > inline which does what pci_iomap() does except it doesn't call
    > > ioport_map() ? I am just not sure where this would go..
    > I'm not understanding what the problem is?
    > Why don't these people just use "ioread*()/iowrite*()"?
    > In other words, the whole point of *not* using "read*/write*()" is that
    > you get a whole slew of much nicer interfaces.
    > So can people explain this fundamental issue? Why do people insist on
    > using the old interfaces (and matching them with the new setup)?

    An extra branch is created on MMIO-only devices on read/writes on the
    IO_COND macro using this interface -- or is this optimized out?

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-09-18 22:15    [W:0.020 / U:4.728 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site