linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Witold Szczeponik" <Witold.Szczeponik@gmx.net>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	lenb@kernel.org, bhelgaas@google.com, rjw@sisk.pl
Subject: Re: [PATCH V3 0/3] PNP: Allow PNP resources to be disabled (interface)
Date: Mon, 30 Jul 2012 12:58:16 +0200	[thread overview]
Message-ID: <20120730105816.59030@gmx.net> (raw)
In-Reply-To: <20120730082820.GA32745@liondog.tnic>

> On Sun, Jul 29, 2012 at 09:31:53PM +0200, Witold Szczeponik wrote:
> > the aim is to select a PNP ACPI option where resources can be disabled
> > (or are not needed).  E.g., the parallel port of the 600E can be used
> > with and without IRQ lines.  The means to allow for this is to use the
> > sysfs interface to select disabled resources (just like any other 
> > resource value).  In https://lkml.org/lkml/2011/7/3/41, I used the 
> > following example:
> > 
> >   echo disable > /sys/bus/pnp/devices/$device/resources
> >   echo clear > /sys/bus/pnp/devices/$device/resources
> >   echo set irq disabled > /sys/bus/pnp/devices/$device/resources
> >   echo fill > /sys/bus/pnp/devices/$device/resources
> >   echo activate > /sys/bus/pnp/devices/$device/resources
> > 
> > The third line is made possible by the patch series.  All other
> > lines are already implemented.
> 
> Shouldn't this be rather "disable_irq" or something which is a single
> word and thus would simplify parsing a lot?
> 
> Also, <Documentation/filesystems/sysfs.txt> says
> 
> "Attributes should be ASCII text files, preferably with only one value
> per file. It is noted that it may not be efficient to contain only one
> value per file, so it is socially acceptable to express an array of
> values of the same type."
> 
> Thanks.
> 
> -- 
> Regards/Gruss,
>     Boris.

Hi Boris, 

the patch series is about adding the term "disabled" (or "<none") to
the list of possible values for resources.  The current state of the
kernel ABI already allows to use the following statement (cf. DSDT
excerpt from https://lkml.org/lkml/2011/7/3/41): 

  echo set irq 7 > /sys/bus/pnp/devices/$device/resources

i.e., the "resources" file can already parse all the values necessary for setting PNP values.  

The patch series is not about adding a new ABI or changing an existing ABI.  It is about extending the existing one to be able to handle the term "disabled" (or "<none>") as a special for a resource value. 

--- Witold

  reply	other threads:[~2012-07-30 10:58 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 ` [PATCH V3 0/3] PNP: Allow PNP resources to be disabled (interface) Rafael J. Wysocki
2012-07-29 19:31   ` Witold Szczeponik
2012-07-30  8:28     ` Borislav Petkov
2012-07-30 10:58       ` Witold Szczeponik [this message]
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=20120730105816.59030@gmx.net \
    --to=witold.szczeponik@gmx.net \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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).