The leg-kernel release has been made and tagged as leg-20140318.0
This is based on mainline kernel v3.14-rc7
Repository : http://git.linaro.org/leg/acpi/leg-kernel.git
Direct Link: https://git.linaro.org/leg/acpi/leg-kernel.git/commit/9ce67dfb053ccec04f580…
Notes :-
1) starting from this release, a FDT is not used to describe the platform. The
kernel uses ACPI tables only. This release contains prototype code to boot
the CPUs from information held in the MADT. It is hard coded to PSCI control
method for the FVP base model
The leg-kernel release has been made and tagged as leg-20140313.0
This is based on mainline kernel v3.14-rc6
Repository : http://git.linaro.org/leg/acpi/leg-kernel.git
Direct Link: https://git.linaro.org/leg/acpi/leg-kernel.git/commit/d8bfabcad828ad3dbf3b6…
Notes :-
1) starting from this release, a FDT is not used to describe the platform. The
kernel uses ACPI tables only. This release contains prototype code to boot
the CPUs from information held in the MADT. It is hard coded to PSCI control
method for the FVP base model
The leg-kernel release has been made and tagged as leg-20140306.0
This is based on mainline kernel v3.14-rc5
Repository : http://git.linaro.org/leg/acpi/leg-kernel.git
Direct Link: https://git.linaro.org/leg/acpi/leg-kernel.git/commit/8506af0325655fef22731…
Notes :-
1) starting from this release, a FDT is not used to describe the platform. The
kernel uses ACPI tables only. This release contains prototype code to boot
the CPUs from information held in the MADT. It is hard coded to PSCI control
method for the FVP base model
Hi,
The ACPI and leg-kernel repos will be moving from their current location
which to under the leg/ location instead.
So they will become
leg/acpi/acpi.git - The kernel development tree of the ACPI team
leg/acpi/acpi-asl.git - The ASL tree
leg/acpi/leg-kernel.git - the leg-kernel releases tree.
This is due to the arm/ location being meant for arm landing team.
ACPI Team if you could check wiki pages for references to old address
and update as needed that would be great.
Fathi if you could change the leg-kernel CI loop to the new address? We
will owe you a beer!
Thanks
Graeme
Hi,
Here are the minutes I took, its always difficult to capture everything
so I apologise if I missed something or misrepresented.
ACPI Power Management
---------------------
Not sure if it is ACPI core or driver that calls _PS? methods, Graeme
thinks
it is ACPI core. Must check.
PSCI transitions do not go through AML
Where people say "UEFI" when talking about hardware initialisation this
actually means
that by the time we enter kernel it will have been done. This does not
actually
mean UEFI needs to do this.
Fine grained means devices, so if two children shut off its upto
firmware to work
out and shut down the parent.
ASWG ASAP items, new GIC tables, flags for PSCI, GTDT memory mapped
timers.
Is there a way to repeat runtime PM ability to not shutdown due to
latency cost. Will
need to be investigated.
If using an embedded power controller, what is the path for events.
There is a general lack of latency type control in ACPI. Also missing
dependencies
between devices and also devices states and C states.
At least one CPU is always in control of D-State transitions.
Improved CPU state change latency is in discussion in ASWG.
Discussion on extending the spec to allow for P-States on devices, this
would give
devfreq support for ACPI machines.
Dong Wei - Please participate in ASWG to improve the spec.