linux-toradex.git/include/linux/ioport.h, branch v4.4.93

ACPI/PCI: Enhance ACPI core to support sparse IO space

2015-10-16T20:18:51+00:00

Enhance ACPI resource parsing interfaces to support sparse IO space,
which will be used to share common code between x86 and IA64 later.

Tested-by: Tony Luck 
Signed-off-by: Jiang Liu 
Reviewed-by: Hanjun Guo 
Signed-off-by: Rafael J. Wysocki

kernel/resource.c: remove deprecated __check_region() and friends

2015-04-15T23:35:22+00:00

All users of __check_region(), check_region(), and check_mem_region() are
gone.  We got rid of the last user in v4.0-rc1.  Remove them.

bloat-o-meter on x86_64 shows:

add/remove: 0/3 grow/shrink: 0/0 up/down: 0/-102 (-102)
function                                     old     new   delta
__kstrtab___check_region                      15       -     -15
__ksymtab___check_region                      16       -     -16
__check_region                                71       -     -71

Signed-off-by: Jakub Sitnicki 
Cc: Bjorn Helgaas 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

resources: Add device-managed request/release_resource()

2014-09-04T20:41:43+00:00

Provide device-managed implementations of the request_resource() and
release_resource() functions.  Upon failure to request a resource, the new
devm_request_resource() function will output an error message for
consistent error reporting.

Signed-off-by: Thierry Reding 
Signed-off-by: Bjorn Helgaas 
Acked-by: Tejun Heo

resource: provide new functions to walk through resources

2014-08-08T22:57:32+00:00

I have added two more functions to walk through resources.

Currently walk_system_ram_range() deals with pfn and /proc/iomem can
contain partial pages.  By dealing in pfn, callback function loses the
info that last page of a memory range is a partial page and not the full
page.  So I implemented walk_system_ram_res() which returns u64 values to
callback functions and now it properly return start and end address.

walk_system_ram_range() uses find_next_system_ram() to find the next ram
resource.  This in turn only travels through siblings of top level child
and does not travers through all the nodes of the resoruce tree.  I also
need another function where I can walk through all the resources, for
example figure out where "GART" aperture is.  Figure out where ACPI memory
is.

So I wrote another function walk_iomem_res() which walks through all
/proc/iomem resources and returns matches as asked by caller.  Caller can
specify "name" of resource, start and end and flags.

Got rid of find_next_system_ram_res() and instead implemented more generic
find_next_iomem_res() which can be used to traverse top level children
only based on an argument.

Signed-off-by: Vivek Goyal 
Cc: Yinghai Lu 
Cc: Borislav Petkov 
Cc: Michael Kerrisk 
Cc: Eric Biederman 
Cc: H. Peter Anvin 
Cc: Matthew Garrett 
Cc: Greg Kroah-Hartman 
Cc: Dave Young 
Cc: WANG Chao 
Cc: Baoquan He 
Cc: Andy Lutomirski 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

vsprintf: Add support for IORESOURCE_UNSET in %pR

2014-02-26T21:42:09+00:00

Sometimes we have a struct resource where we know the type (MEM/IO/etc.)
and the size, but we haven't assigned address space for it.  The
IORESOURCE_UNSET flag is a way to indicate this situation.  For these
"unset" resources, the start address is meaningless, so print only the
size, e.g.,

  - pci 0000:0c:00.0: reg 184: [mem 0x00000000-0x00001fff 64bit]
  + pci 0000:0c:00.0: reg 184: [mem size 0x2000 64bit]

For %pr (printing with raw flags), we still print the address range,
because %pr is mostly used for debugging anyway.

Thanks to Fengguang Wu  for suggesting
resource_size().

Signed-off-by: Bjorn Helgaas

resource: Add resource_contains()

2014-02-26T21:42:09+00:00

We have two identical copies of resource_contains() already, and more
places that could use it.  This moves it to ioport.h where it can be
shared.

resource_contains(struct resource *r1, struct resource *r2) returns true
iff r1 and r2 are the same type (most callers already checked this
separately) and the r1 address range completely contains r2.

In addition, the new resource_contains() checks that both r1 and r2 have
addresses assigned to them.  If a resource is IORESOURCE_UNSET, it doesn't
have a valid address and can't contain or be contained by another resource.
Some callers already check this or for res->start.

No functional change.

Signed-off-by: Bjorn Helgaas

resource: add release_mem_region_adjustable()

2013-04-29T22:54:37+00:00

Add release_mem_region_adjustable(), which releases a requested region
from a currently busy memory resource.  This interface adjusts the
matched memory resource accordingly even if the requested region does
not match exactly but still fits into.

This new interface is intended for memory hot-delete.  During bootup,
memory resources are inserted from the boot descriptor table, such as
EFI Memory Table and e820.  Each memory resource entry usually covers
the whole contigous memory range.  Memory hot-delete request, on the
other hand, may target to a particular range of memory resource, and its
size can be much smaller than the whole contiguous memory.  Since the
existing release interfaces like __release_region() require a requested
region to be exactly matched to a resource entry, they do not allow a
partial resource to be released.

This new interface is restrictive (i.e.  release under certain
conditions), which is consistent with other release interfaces,
__release_region() and __release_resource().  Additional release
conditions, such as an overlapping region to a resource entry, can be
supported after they are confirmed as valid cases.

There is no change to the existing interfaces since their restriction is
valid for I/O resources.

[akpm@linux-foundation.org: use GFP_ATOMIC under write_lock()]
[akpm@linux-foundation.org: switch back to GFP_KERNEL, less buggily]
[akpm@linux-foundation.org: remove unneeded and wrong kfree(), per Toshi]
Signed-off-by: Toshi Kani 
Reviewed-by : Yasuaki Ishimatsu 
Cc: David Rientjes 
Reviewed-by: Ram Pai 
Cc: T Makphaibulchoke 
Cc: Wen Congyang 
Cc: Tang Chen 
Cc: Jiang Liu 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

resources: Document IORESOURCE_IO

2012-09-11T08:15:02+00:00

Help clarify that this is specifically for PCI/ISA I/O ports and not for
any other similar thing.

Signed-off-by: Mark Brown 
Acked-by: Arnd Bergmann 
Acked-by: Haojian Zhuang 
Tested-by: Haojian Zhuang 
Signed-off-by: Samuel Ortiz

resources: Add register address resource type

2012-09-11T08:15:02+00:00

Currently a bunch of I2C/SPI MFD drivers are using IORESOURCE_IO for
register address ranges. Since this causes some confusion due to the
primary use of this resource type for PCI/ISA I/O ports create a new
resource type IORESOURCE_REG.

Unfortunately the current resource types are specified as bitmasks and
there are no free bitmasks even though they really shouldn't be used as
such so we define the new type as IORESOURCE_IO | IORESOURCE_MEM.
Benjamin Herrenschmidt and Russell King have both verified that none of
the users in this series will have a problem with this, and no new code
should be affected.

This patch was written by Russell King but he found himself unable to
take the patch further.

Signed-off-by: Mark Brown 
Acked-by: Arnd Bergmann 
Acked-by: Haojian Zhuang 
Tested-by: Haojian Zhuang 
Signed-off-by: Samuel Ortiz

resources: add resource_overlaps()

2012-05-07T16:58:57+00:00

Add resource_overlaps(), which returns true if two resources overlap at all.

Use this to replace the complicated check in coalesce_windows().

Signed-Off-By: Wei Yang 
Signed-off-by: Bjorn Helgaas