On Thu, Mar 20, 2014 at 05:19:32PM +0000, Catalin Marinas wrote:
On Thu, Mar 20, 2014 at 01:43:57PM +0000, Mark Brown wrote:
Given ACPI (which really looks like it's going to happen at some point and presumably make OF optional) I'm not sure removing the handling of OF is actually constructive but whatever, it's done now...
CONFIG_OF will always be enabled in the kernel even when we get ACPI. We still use the chosen DT node to tell the kernel about ACPI.
One thing that occurs to me with this - if we've always got a DT even if we are booting with ACPI that might confuse code that implements handling for firmware idioms. The regulator code does this sort of thing, though in that case we make exactly the same assumptions for ACPI and DT so there won't be any confusion. There's a few other examples though and we might acquire more by the time ACPI gets merged. Probably not a big deal but something that needs attention paying.
I was aware that there was a stub DT on ACPI systems but had expected that if we were booting with real ACPI support that'd get masked from the running system. I can see why at least initially we'd want to just pull in the infrastructure to use when identifying that this is an ACPI system.