From: Witold Szczeponik <Witold.Szczeponik@gmx.net>
To: bhelgaas@google.com, abelay@mit.edu
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] PNP: Allow PNP resources to be disabled (interface)
Date: Tue, 20 Mar 2012 19:49:47 +0100 [thread overview]
Message-ID: <4F68D14B.60409@gmx.net> (raw)
Hello everybody,
this simple patch series continues the work begun in commit
18fd470a48396c8795ba7256c5973e92ffa25cb3 where ACPI PNP resource templates
with empty/disabled resources are handled.
The aim of this patch series is to allow to set resources as "disabled" using
the "/sys/bus/pnp/devices/*/resources" interface. Such "disabled" resources
are needed by some vintage IBM ThinkPads like the 600E where some resources
need to have their IRQs disabled in order to support all the devices the 600E
has.
To this end, some preparatory work is done, simplifying the code and allowing
for more flexibility in the definition of these resources.
Here's a brief description of these patches.
[1/3] - Factor out common some code
[2/3] - Perform the actual setting
[3/3] - Generalize handling of resource flags
The patches are applied against Linux 3.3.x.
Comments are, as always, welcome. :-)
--- Witold
next reply other threads:[~2012-03-20 19:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 18:49 Witold Szczeponik [this message]
2012-03-20 19:57 ` [PATCH 1/3] PNP: Simplify setting of resources Witold Szczeponik
2012-03-27 20:32 ` Bjorn Helgaas
2012-04-01 16:05 ` Witold Szczeponik
2012-03-20 20:00 ` [PATCH 2/3] PNP: Allow resources to be set as disabled Witold Szczeponik
2012-03-27 20:38 ` Bjorn Helgaas
2012-04-01 16:06 ` Witold Szczeponik
2012-03-20 20:05 ` [PATCH 3/3] PNP: Allow resource flags to be set explicitly Witold Szczeponik
2012-03-27 20:52 ` Bjorn Helgaas
2012-04-01 16:07 ` Witold Szczeponik
2012-03-27 20:57 ` [PATCH 0/3] PNP: Allow PNP resources to be disabled (interface) Bjorn Helgaas
2012-04-01 16:04 ` Witold Szczeponik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F68D14B.60409@gmx.net \
--to=witold.szczeponik@gmx.net \
--cc=abelay@mit.edu \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.