From: Thomas Renninger <trenn@suse.de>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
fseidel@suse.de, linux-acpi@vger.kernel.org, "Brown,
Len" <len.brown@intel.com>,
shaohua.li@intel.com
Subject: Re: [patch 0/2] acpi: driverregistration again can report ENODEV
Date: Wed, 25 Oct 2006 13:31:55 +0200 [thread overview]
Message-ID: <1161775915.32262.235.camel@queen.suse.de> (raw)
In-Reply-To: <1161772831.14917.36.camel@localhost.localdomain>
On Wed, 2006-10-25 at 18:40 +0800, Zhang Rui wrote:
> We won't have such issues if we make ACPI use driver model.
> I've sent out a patch series which throw the legacy ACPI driver model
> away. The patches will be added to -mm tree.
>
> On Sat, 2006-10-21 at 00:55 +0800, Bjorn Helgaas wrote:
> > > acpi_bus_register_driver must return -ENODEV when no device with
> > > matching HID was found. E.g. battery also should currently get
> > always
> > > loaded even a system never has one.
> >
> > If the driver wants to unload if it doesn't find any devices,
> > it can easily do so by counting calls to its add() method, as
> > asus_acpi.c currently does. I don't think that's a good long-
> > term solution, though. I think it would be better to have a
> > hotplug scheme that loads the driver when the hardware is
> > found, like we do for PCI.
> >
> that's true. With this patch series, .uevent method of ACPI bus will be
> called when an ACPI device is found. Then udev script loads the right
> driver by checking hid/cid offered by .uevent method.
That are great news.
Maybe you can CC linux-acpi list on further patches, I didn't know about
this.
I am looking forward to give these a try as soon as I get some time...
Thanks,
Thomas
prev parent reply other threads:[~2006-10-25 11:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 9:25 [patch 0/2] acpi: driverregistration again can report ENODEV fseidel
2006-10-20 9:25 ` [patch 1/2] " fseidel
2006-10-20 9:25 ` [patch 2/2] " fseidel
2006-10-20 9:59 ` [patch 0/2] " Thomas Renninger
2006-10-20 16:55 ` Bjorn Helgaas
2006-10-22 15:09 ` Thomas Renninger
2006-10-23 15:34 ` Bjorn Helgaas
2006-10-23 16:33 ` Frank Seidel
2006-10-24 9:05 ` Frank Seidel
2006-10-25 19:58 ` [patch] ACPI: asus_acpi: return -ENODEV when no device found Bjorn Helgaas
2006-10-26 9:22 ` Frank Seidel
2006-10-25 10:40 ` [patch 0/2] acpi: driverregistration again can report ENODEV Zhang Rui
2006-10-25 11:31 ` Thomas Renninger [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=1161775915.32262.235.camel@queen.suse.de \
--to=trenn@suse.de \
--cc=bjorn.helgaas@hp.com \
--cc=fseidel@suse.de \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=shaohua.li@intel.com \
/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).