linux-toradex.git/include/linux/ioport.h, branch v2.6.36-rc5

resource: shared I/O region support

2010-05-11T19:01:10+00:00

SuperIO devices share regions and use lock/unlock operations to chip
select.  We therefore need to be able to request a resource and wait for
it to be freed by whichever other SuperIO device currently hogs it.
Right now you have to poll which is horrible.

Add a MUXED field to IO port resources. If the MUXED field is set on the
resource and on the request (via request_muxed_region) then we block
until the previous owner of the muxed resource releases their region.

This allows us to implement proper resource sharing and locking for
superio chips using code of the form

enable_my_superio_dev() {
	request_muxed_region(0x44, 0x02, "superio:watchdog");
	outb() ..sequence to enable chip
}

disable_my_superio_dev() {
	outb() .. sequence of disable chip
	release_region(0x44, 0x02);
}

Signed-off-by: Giel van Schijndel 
Signed-off-by: Alan Cox 
Signed-off-by: Jesse Barnes

resources: add interfaces that return conflict information

2010-03-23T20:33:50+00:00

request_resource() and insert_resource() only return success or failure,
which no information about what existing resource conflicted with the
proposed new reservation.  This patch adds request_resource_conflict()
and insert_resource_conflict(), which return the conflicting resource.

Callers may use this for better error messages or to adjust the new
resource and retry the request.

Signed-off-by: Bjorn Helgaas 
Signed-off-by: Jesse Barnes

resource: add window support

2010-03-15T00:08:36+00:00

Add support for resource windows.  This is for bridge resources, i.e.,
regions where a bridge forwards transactions from the primary to the
secondary side.

Signed-off-by: Bjorn Helgaas 
Signed-off-by: Len Brown

resource: add bus number support

2010-03-15T00:08:35+00:00

Add support for bus number resources.  This is for bridges with a range of
bus numbers behind them.

Signed-off-by: Bjorn Helgaas 
Signed-off-by: Len Brown

resource: expand IORESOURCE_TYPE_BITS to make room for bus resource type

2010-03-15T00:08:34+00:00

No functional change; this just makes room for another resource type.

Signed-off-by: Bjorn Helgaas 
Signed-off-by: Len Brown

resource: add release_child_resources

2010-02-23T00:17:00+00:00

Useful for freeing a portion of the resource tree, e.g. when trying to
reallocate resources more efficiently.

Signed-off-by: Yinghai Lu 
Acked-by: Linus Torvalds 
Signed-off-by: Jesse Barnes

resource/PCI: mark struct resource as const

2010-02-23T00:16:57+00:00

Now that we return the new resource start position, there is no
need to update "struct resource" inside the align function.
Therefore, mark the struct resource as const.

Cc: Bjorn Helgaas 
Cc: Yinghai Lu 
Signed-off-by: Dominik Brodowski 
Signed-off-by: Jesse Barnes

resource/PCI: align functions now return start of resource

2010-02-23T00:16:56+00:00

As suggested by Linus, align functions should return the start
of a resource, not void. An update of "res->start" is no longer
necessary.

Cc: Bjorn Helgaas 
Cc: Yinghai Lu 
Signed-off-by: Dominik Brodowski 
Signed-off-by: Jesse Barnes

resource: constify arg to resource_size() and resource_type()

2009-12-16T15:20:17+00:00

resource_size() doesn't change the resource it operates on, so the res
parameter can be marked const.  Same for resource_type().

Signed-off-by: Jean Delvare 
Reviewed-by: WANG Cong 
Cc: Greg KH 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

walk system ram range

2009-09-23T14:39:41+00:00

Originally, walk_memory_resource() was introduced to traverse all memory
of "System RAM" for detecting memory hotplug/unplug range.  For doing so,
flags of IORESOUCE_MEM|IORESOURCE_BUSY was used and this was enough for
memory hotplug.

But for using other purpose, /proc/kcore, this may includes some firmware
area marked as IORESOURCE_BUSY | IORESOUCE_MEM.  This patch makes the
check strict to find out busy "System RAM".

Note: PPC64 keeps their own walk_memory_resouce(), which walk through
ppc64's lmb informaton.  Because old kclist_add() is called per lmb, this
patch makes no difference in behavior, finally.

And this patch removes CONFIG_MEMORY_HOTPLUG check from this function.
Because pfn_valid() just show "there is memmap or not* and cannot be used
for "there is physical memory or not", this function is useful in generic
to scan physical memory range.

Signed-off-by: KAMEZAWA Hiroyuki 
Cc: Ralf Baechle 
Cc: Benjamin Herrenschmidt 
Cc: WANG Cong 
Cc: Américo Wang 
Cc: David Rientjes 
Cc: Roland Dreier 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds