From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: Len Brown <lenb@kernel.org>,
Eric Piel <eric.piel@tremplin-utc.net>,
Pavel Machek <pavel@suse.cz>,
Jonathan Woithe <jwoithe@physics.adelaide.edu.au>,
Mattia Dongili <malattia@linux.it>,
linux-acpi@vger.kernel.org
Subject: Re: why do drivers evaluate _INI?
Date: Tue, 23 Jun 2009 09:01:38 -0600 [thread overview]
Message-ID: <200906230901.38855.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <71cd59b00906230153q38f2d9b5h6c57621c389ecb0f@mail.gmail.com>
On Tuesday 23 June 2009 2:53:07 am Corentin Chary wrote:
> I don't know if it's related, but:
> eeepc-laptop is calling "INIT" for device ASUS010
> asus-laptop is calling "INIT" for device ATK0100
>
> But for eeepc-laptop we provide some flags special to INIT, and in
> asus-laptop it returns the model name.
> So I don't think we can move INIT for these.
Thanks for looking into this. The "INIT" methods are something
completely different -- they are device-specific things, so it's
fine for them to be in the driver. The "_INI" method, like others
named with a leading underscore, is defined by the ACPI spec.
Drivers do even use some of these spec-defined methods, but in
the case of "_INI", I think it makes more sense to take care of
it in the ACPI CA or the Linux/ACPI core.
Bjorn
prev parent reply other threads:[~2009-06-23 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 23:32 why do drivers evaluate _INI? Bjorn Helgaas
2009-06-22 23:59 ` Jonathan Woithe
2009-06-23 15:17 ` nokos
2009-06-24 0:15 ` Jonathan Woithe
2009-06-24 9:19 ` nokos
2009-06-23 0:01 ` Tony Vroon
2009-06-23 0:28 ` Jonathan Woithe
2009-06-23 2:05 ` Mattia Dongili
2009-06-23 8:53 ` Corentin Chary
2009-06-23 15:01 ` Bjorn Helgaas [this message]
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=200906230901.38855.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=corentin.chary@gmail.com \
--cc=eric.piel@tremplin-utc.net \
--cc=jwoithe@physics.adelaide.edu.au \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=malattia@linux.it \
--cc=pavel@suse.cz \
/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