Re: problems about ACPI sysfs convert work

Len Brown
2006-11-22T22:09:57Z

On Tuesday 21 November 2006 11:34, Matthew Garrett wrote:

> > > I’m doing the ACPI sysfs convert work now. And I have some problems when duplicating some procfs interfaces to sysfs.
> > > Under driver model (this will be available soon), files under /proc/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 /prco/acpi, including “alarm”, “sleep”, “wakeup”, “debug_layer”, “debug_level”, “dsdt”, “fadt”, “event” and “info”.
> > > Following is a proposal as well as some problem and I’m not quite sure about the places all these attributes should be located at. I wish to get some advice from you, and any comment is welcome☺.
> > >
> > > 1. Where should “alarm” be located? Another problem is whether we should put a duration into this file instead of a future time.
> > Don't know, never used...
>
> This should presumably just be handled by the clock driver rather than
> the ACPI subsystem. There's only a tiny amount of acpi-related code in
> the driver, and that's information that we could just export to the
> clock instead.

Matthew, exactly what code in "the clock driver" to you refer to that
should be involved here?

Re: duration vs. absolute time.
Currently use use absolute time, and that capability needs to stay.

I requested also a sleep duration capability.
I'd like to use it to make the suspend/resume stress test suite a little better,
but others might like it for "real" use as well.
Either a different sysfs file, or a special syntax like preceeding the time
with a '+' to make it a duration?

thanks,
-Len