[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52B4BA0A.1030902@zytor.com>
Date: Fri, 20 Dec 2013 13:43:38 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
CC: joeyli <jlee@...e.com>, Alessandro Zummo <a.zummo@...ertech.it>,
Matt Fleming <matt@...sole-pimps.org>,
Matthew Garrett <matthew.garrett@...ula.com>, Elliott@...com,
samer.el-haj-mahmoud@...com, Oliver Neukum <oneukum@...e.de>,
werner@...e.com, trenn@...e.de, JBeulich@...e.com,
linux-kernel@...r.kernel.org, rtc-linux@...glegroups.com,
x86@...nel.org,
"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
linux-acpi@...r.kernel.org, Borislav Petkov <bp@...e.de>
Subject: Re: [RFC PATCH 00/14] Support timezone of ACPI TAD and EFI TIME
On 12/20/2013 01:45 PM, Rafael J. Wysocki wrote:
>
> My understanding, however, is that to use the TAD, we don't actually need to
> create a struct acpi_device for it. We just need a handle to the ACPICA
> object which can be found using acpi_get_devices() as soon as the namespace
> has been extracted from the DSDT and friends. That in turn happens in
> acpi_early_init(), which is called from start_kernel() right before
> efi_late_init().
>
> Is that early enough?
>
Possibly... will have to investigate. I would also ask if the same
applies to the PNP0B0x devices -- all we really need there is the
presence/absence indication and the I/O port base.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists