From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zhang Rui Subject: Re: problems about ACPI sysfs convert work Date: Wed, 22 Nov 2006 15:53:47 +0800 Message-ID: <1164182027.5461.22.camel@localhost.localdomain> References: <58A36151585E4047913F40517D307BAE01719E@pdsmsx404.ccr.corp.intel.com> <1164021493.3721.229.camel@queen.suse.de> <1164158892.3551.3.camel@sli10-conroe.sh.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mga01.intel.com ([192.55.52.88]:32830 "EHLO mga01.intel.com") by vger.kernel.org with ESMTP id S1756959AbWKVHuZ (ORCPT ); Wed, 22 Nov 2006 02:50:25 -0500 In-Reply-To: <1164158892.3551.3.camel@sli10-conroe.sh.intel.com> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Shaohua Li , trenn@suse.de Cc: linux-acpi@vger.kernel.org, "Brown, Len" , "Yu, Luming" , Kay Sievers On Wed, 2006-11-22 at 09:28 +0800, Shaohua Li wrote: > On Mon, 2006-11-20 at 12:18 +0100, Thomas Renninger wrote: > > On Mon, 2006-11-20 at 18:10 +0800, Zhang, Rui wrote: > > > Hello, lists > > > I=E2=80=99m doing the ACPI sysfs convert work now. And I have som= e problems when duplicating some procfs interfaces to sysfs. > > > Under driver model (this will be available soon), files under /pr= oc/acpi/xxx(driver)/yyy(device)/ will be duplicated under /sys/device/ = as they are properties of individual devices. > > > But I still have some trouble on dealing with the files under /pr= co/acpi, including =E2=80=9Calarm=E2=80=9D, =E2=80=9Csleep=E2=80=9D, =E2= =80=9Cwakeup=E2=80=9D, =E2=80=9Cdebug_layer=E2=80=9D, =E2=80=9Cdebug_le= vel=E2=80=9D, =E2=80=9Cdsdt=E2=80=9D, =E2=80=9Cfadt=E2=80=9D, =E2=80=9C= event=E2=80=9D and =E2=80=9Cinfo=E2=80=9D. > > > Following is a proposal as well as some problem and I=E2=80=99m n= ot quite sure about the places all these attributes should be located a= t. I wish to get some advice from you, and any comment is welcome=E2=98= =BA. > > >=20 > > > 1. Where should =E2=80=9Calarm=E2=80=9D be located? Another probl= em is whether we should put a duration into this file instead of a futu= re time. > > Don't know, never used... > > > 2. =E2=80=9Csleep=E2=80=9D is already marked as deprecated becaus= e /sys/power/state has the same function. I won=E2=80=99t do the repeat= ed work again. > > Yep. > > > 3. =E2=80=9Cwakeup=E2=80=9D should not exist, but be an attribute= of individual devices kobjects. > > Maybe the devices can be linked > > like /sys/.../wakeup/${links_to_wakeup_devices} > > So that userspace does not need to search over the whole device tre= e to > > find them? Sounds great. I'll have a try. > Sounds like a good idea. But this should be done in driver core. Othe= r > devices like pci might support wakeup too. device declaims to support > wakeup, and driver core create a link to /sys/.../wakeup/xxx. I'd > suggest don't do this in acpi part. >=20 Yes. That makes sense. But I don't want too many files to be involved, especially at the beginning. :). This should be done in another patch i= n the future if everything goes well. Thanks, Ray - To unsubscribe from this list: send the line "unsubscribe linux-acpi" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html