linux-toradex.git/include/linux/pnp.h, branch v2.6.25-rc2

isapnp driver semaphore to mutex

2008-02-06T18:41:20+00:00

Changed the isapnp semaphore to a mutex.

[akpm@linux-foundation.org: no externs-in-c]
[akpm@linux-foundation.org: build fix]
Signed-off-by: Daniel Walker 
Cc: Bjorn Helgaas 
Cc: Ingo Molnar 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

include/linux/: Spelling fixes

2008-02-03T15:45:46+00:00

Signed-off-by: Joe Perches 
Signed-off-by: Adrian Bunk

increase PNP_MAX_PORT to 40 from 24

2007-12-28T04:55:13+00:00

a7839e960675b549f06209d18283d5cee2ce9261
(PNP: increase the maximum number of resources)
increased PNP_MAX_PORT to 24 from 8.
It also added a test and a complaint when a
machine exceeded the limit, causing:

pnpacpi: exceeded the max number of IO resources: 24

http://bugzilla.kernel.org/show_bug.cgi?id=9535

We should have been squawking about this all along,
as this is a potentially serious issue.

For now, simply burn some dynamic bytes and
increase the limit by another 16 to 40.
There is no guarantee that this will satisfy
every system on Earth.  It probably will not,
but it should be an improvement.

In the future, PNPACPI should allocate resource
structures as needed, rather than max-sized arrays.

Signed-off-by: Len Brown

PNP: increase the maximum number of resources

2007-11-29T17:24:52+00:00

On some systems the number of resources(IO,MEM) returnedy by PNP device is
greater than the PNP constant, for example motherboard devices.  It brings
that some resources can't be reserved and resource confilicts.  This will
cause PCI resources are assigned wrongly in some systems, and cause hang.
This is a regression since we deleted ACPI motherboard driver and use PNP
system driver.

[akpm@linux-foundation.org: fix text and coding-style a bit]
Signed-off-by: Li Shaohua 
Signed-off-by: Zhao Yakui 
Cc: Bjorn Helgaas 
Cc: Thomas Renninger 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

PNP: remove null pointer checks

2007-10-17T15:43:04+00:00

Remove some null pointer checks.  Null pointers in these areas indicate
programming errors, and I think it's better to oops immediately rather than
return an error that is easily ignored.

Signed-off-by: Bjorn Helgaas 
Cc: Adam Belay 
Cc: Len Brown 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

PNP: fix up after Lindent

2007-07-26T18:35:21+00:00

These are manual fixups after running Lindent.  No functional change.

Signed-off-by: Bjorn Helgaas 
Cc: Len Brown 
Cc: Adam Belay 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

PNP: Lindent all source files

2007-07-26T18:35:20+00:00

Run Lindent on all PNP source files.

Produced by:

    $ quilt new pnp-lindent
    $ find drivers/pnp -name \*.[ch] | xargs quilt add
    $ quilt add include/linux/{pnp.h,pnpbios.h}
    $ scripts/Lindent drivers/pnp/*.c drivers/pnp/*/*.c include/linux/pnp*.h
    $ quilt refresh --sort

Signed-off-by: Bjorn Helgaas 
Cc: Len Brown 
Cc: Adam Belay 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

ACPI, PNP: hook ACPI D-state to PNP suspend/resume

2007-07-22T08:18:20+00:00

applied after Rafel's 'PM: Update global suspend and hibernation operations framework' patch set

Signed-off-by: Shaohua Li 
Signed-off-by: Len Brown

PNP: notice whether we have PNP devices (PNPBIOS or PNPACPI)

2007-05-08T18:15:23+00:00

This series converts i386 and x86_64 legacy serial ports to be platform
devices and prevents probing for them if we have PNP.

This prevents double discovery, where a device was found both by the legacy
probe and by 8250_pnp.

This also prevents the serial driver from claiming IRDA devices (unless they
have a UART PNP ID).  The serial legacy probe sometimes assumed the wrong IRQ,
so the user had to use "setserial" to fix it.

Removing the need for setserial to make IRDA devices work seems good, but it
does break some things.  In particular, you may need to keep setserial from
poking legacy UART stuff back in by doing something like "dpkg-reconfigure
setserial" with the "kernel" option.  Otherwise, the setserial-discovered
"UART" will claim resources and prevent the IRDA driver from loading.

This patch:

If we can discover devices using PNP, we can skip some legacy probes.  This
flag ("pnp_platform_devices") indicates that PNPBIOS or PNPACPI is enabled and
should tell us about builtin devices.

Signed-off-by: Bjorn Helgaas 
Cc: Keith Owens 
Cc: Len Brown 
Cc: Adam Belay 
Cc: Matthieu CASTET 
Cc: Jean Tourrilhes 
Cc: Matthew Garrett 
Cc: Ville Syrjala 
Cc: Russell King 
Cc: Samuel Ortiz 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

init dma masks in pnp_dev

2007-05-08T18:15:00+00:00

PNP now initializes device dma masks, which prevents oopses when generic
dma calls are made using pnp device nodes.

This assumes PNP only uses ISA DMA, with 24 bit addresses; and that it's
safe to init those masks for all devices (rather than finding out which
devices have been assigned DMA channels, and handling only those).

Signed-off-by: David Brownell 
Cc: Adam Belay 
Cc: Jaroslav Kysela 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds