public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: ACPI Developers <acpi-devel@lists.sourceforge.net>,
	lkml <linux-kernel@vger.kernel.org>, Greg <greg@kroah.com>,
	Patrick Mochel <mochel@digitalimplant.org>,
	Pavel Machek <pavel@suse.cz>, Adam Belay <ambx1@neo.rr.com>
Subject: Re: [PATCH 0/4]Bind physical devices with ACPI devices - take 2
Date: 05 Jan 2005 23:00:55 -0500	[thread overview]
Message-ID: <1104984055.18173.239.camel@d845pe> (raw)
In-Reply-To: <1104893444.5550.127.camel@sli10-desk.sh.intel.com>

On Tue, 2005-01-04 at 21:50, Li Shaohua wrote:
> Hi,
> The series of patches implement binding physical devices with ACPI
> devices. With it, device drivers can utilize methods provided by
> firmware (ACPI). These patches are against 2.6.10, please give your
> comments.

I think we'll save some significant power when ACPI D-states
are invoked for the devices that supply them.  While many
PCI devices support PCI power management and thus don't need/use
ACPI D-states, I think it will be even more important to add
this functionality to the legacy devices which never have
PCI power management and thus always depend on ACPI for D-states.

It looks like some device drivers scribble on dev->platform_data;
and we need to fix those drivers before deploying this patch.
Alternatively, we could add a new field to struct device,
but then we'd probably never get rid of it...

I'm a little unformforable with platform_notify
and platform_notify_remove available as globals.
We should probably BUG_ON if we
find them set before ACPI writes on them.

We'll need to update this patch to handle erroneous
but real platforms that don't have _BBN
by using _CRS to get PCI bus number.

Unclear to me if/how this association of ACPI capability
should be reflected in the sysfs device tree.

thanks,
-Len

  reply	other threads:[~2005-01-06  4:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05  2:50 [PATCH 0/4]Bind physical devices with ACPI devices - take 2 Li Shaohua
2005-01-06  4:00 ` Len Brown [this message]
2005-01-06  7:50   ` Li Shaohua
2005-01-06  9:57     ` Pavel Machek
     [not found] ` <1104893444.5550.127.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-01-17  7:57   ` Li Shaohua
2005-01-17 11:28     ` Pavel Machek
     [not found]       ` <20050117112822.GA1354-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-01-18  1:20         ` Li Shaohua

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=1104984055.18173.239.camel@d845pe \
    --to=len.brown@intel.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=ambx1@neo.rr.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@digitalimplant.org \
    --cc=pavel@suse.cz \
    --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