From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Witold Szczeponik <Witold.Szczeponik@gmx.net>
Cc: bhelgaas@google.com, lenb@kernel.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH V3 0/3] PNP: Allow PNP resources to be disabled (interface)
Date: Sun, 29 Jul 2012 21:22:28 +0200 [thread overview]
Message-ID: <201207292122.28249.rjw@sisk.pl> (raw)
In-Reply-To: <50158321.4030007@gmx.net>
Hi,
On Sunday, July 29, 2012, Witold Szczeponik wrote:
> 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 devices need
> to have their IRQs disabled in order to support all the devices the 600E has.
>
> To better understand the motivation, let's look at an excerpt from the 600E's
> DSDT:
>
> Name (PLPT, ResourceTemplate ()
> {
> StartDependentFnNoPri ()
> {
> IO (Decode16, 0x03BC, 0x03BC, 0x01, 0x04)
> IRQNoFlags () {7}
> }
> /* Some entries deleted */
> StartDependentFnNoPri ()
> {
> IO (Decode16, 0x03BC, 0x03BC, 0x01, 0x04)
> IRQNoFlags () {}
> }
> EndDependentFn ()
> })
>
> As one can see, the IRQ line for the last option is empty/disabled. Also, both
> options share the same priority, meaning they are equal alternatives. In order
> to be able to use the IRQ 7 for some other device, it is necessary to select
> the second option, which can be done with the patch series applied.
Do I understand correctly that you want to disable those things through
sysfs?
Rafael
next prev parent reply other threads:[~2012-07-29 19:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-29 18:38 [PATCH V3 0/3] PNP: Allow PNP resources to be disabled (interface) Witold Szczeponik
2012-07-29 18:44 ` [PATCH V3 1/3] PNP: Simplify setting of resources Witold Szczeponik
2012-07-29 18:48 ` [PATCH V3 2/3] PNP: Allow resources to be set as disabled Witold Szczeponik
2012-07-29 18:49 ` [PATCH V3 3/3] PNP: Handle IORESOURCE_BITS in resource allocation Witold Szczeponik
2012-07-29 19:22 ` Rafael J. Wysocki [this message]
2012-07-29 19:31 ` [PATCH V3 0/3] PNP: Allow PNP resources to be disabled (interface) Witold Szczeponik
2012-07-30 8:28 ` Borislav Petkov
2012-07-30 10:58 ` Witold Szczeponik
2012-08-02 20:09 ` Rafael J. Wysocki
2012-08-02 20:20 ` Witold Szczeponik
2012-08-02 21:40 ` Rafael J. Wysocki
2012-08-02 21:57 ` Witold Szczeponik
2012-09-16 14:18 ` Witold Szczeponik
2012-09-18 21:42 ` Rafael J. Wysocki
2012-10-03 15:57 ` Witold Szczeponik
2012-10-14 15:57 ` Witold Szczeponik
2012-10-19 19:02 ` Witold Szczeponik
2012-10-19 22:19 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2012-08-02 16:32 Witold Szczeponik
2012-08-02 16:38 ` 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=201207292122.28249.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=Witold.Szczeponik@gmx.net \
--cc=bhelgaas@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).