[lkml]   [2006]   [Mar]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 0/4] PCI legacy I/O port free driver (take4)
On Thu, Mar 02, 2006 at 10:24:36AM -0700, Grant Grundler wrote:
> On Thu, Mar 02, 2006 at 03:50:57PM +0000, Russell King wrote:
> > I've been wondering whether this "no_ioport" flag is the correct approach,
> > or whether it's adding to complexity when it isn't really required.
> I think it's the simplest solution to allowing a driver
> to indicate which resources it wants to use. It solves
> the problem of I/O Port resource allocation sufficiently
> well.

It's not really "I/O port resource allocation" though - the resources
have already been allocated and potentially programmed into the BARs
well before the driver gets anywhere near the device.

> > In the non-Intel world, the kernel itself sets up the PCI bus mappings,
> mappings, yes. But many of the architectures depend on (or assume)
> firmware will assign appropriate resources. The problem is firmware
> runs out of I/O Port resources.

Are you implying that somehow resources are allocated at pci_enable_device
time? If so, shouldn't we be thinking of moving completely to that model
rather than having yet-another-pci-setup-model.

Let's see - we have the i386 method, the drivers/pci/setup-* method, and
it sounds like some pci_enable_device() method now.

The problem is that the "no_ioport" method is completely useless for the
drivers/pci/setup-* method since that information from the drivers comes
well after the PCI setup code has been run.

> Several people have already agreed the driver needs to indicate which
> resource it wants to work with. I don't see how the arch PCI support
> can provide that "knowledge".

What I'm saying is that we need to unify this stuff, rather than keep
bluring and overloading the interfaces. Otherwise we'll end up with
drivers developed on one platform which have one expectation from the
PCI API, which could potentially be different from drivers developed
on some other platform.

Let's have some uniformity - and a solution which can fit everyone -
that's all I'm asking.

Russell King
Linux kernel 2.6 ARM Linux -
maintainer of: 2.6 Serial core
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: 2006-03-02 19:03    [W:0.068 / U:4.112 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site