Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262713AbVAFEB5 (ORCPT ); Wed, 5 Jan 2005 23:01:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262714AbVAFEB4 (ORCPT ); Wed, 5 Jan 2005 23:01:56 -0500 Received: from fmr14.intel.com ([192.55.52.68]:35477 "EHLO fmsfmr002.fm.intel.com") by vger.kernel.org with ESMTP id S262713AbVAFEBy (ORCPT ); Wed, 5 Jan 2005 23:01:54 -0500 Subject: Re: [PATCH 0/4]Bind physical devices with ACPI devices - take 2 From: Len Brown To: Shaohua Li Cc: ACPI Developers , lkml , Greg , Patrick Mochel , Pavel Machek , Adam Belay In-Reply-To: <1104893444.5550.127.camel@sli10-desk.sh.intel.com> References: <1104893444.5550.127.camel@sli10-desk.sh.intel.com> Content-Type: text/plain Organization: Message-Id: <1104984055.18173.239.camel@d845pe> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.3 Date: 05 Jan 2005 23:00:55 -0500 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1540 Lines: 40 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/