diff options
author | Myron Stowe <myron.stowe@hp.com> | 2008-11-04 14:53:00 -0700 |
---|---|---|
committer | Len Brown <len.brown@intel.com> | 2008-11-06 20:14:41 -0500 |
commit | b26e9286fb438eb78bcdb68b67a3dbb8bc539125 (patch) | |
tree | b3990cdebfa7a11f3a49b9b01de81629e01d36c8 /drivers/acpi/executer/exresop.c | |
parent | ad93a765c1834db031b5bf1c2baf2a50d0462ca4 (diff) | |
download | kernel_samsung_smdk4412-b26e9286fb438eb78bcdb68b67a3dbb8bc539125.zip kernel_samsung_smdk4412-b26e9286fb438eb78bcdb68b67a3dbb8bc539125.tar.gz kernel_samsung_smdk4412-b26e9286fb438eb78bcdb68b67a3dbb8bc539125.tar.bz2 |
ACPI: Behave uniquely based on processor declaration definition type
Associating a Local SAPIC with a processor object is dependent upon the
processor object's definition type. CPUs declared as "Processor" should
use the Local SAPIC's 'processor_id', and CPUs declared as "Device"
should use the 'uid'. Note that for "Processor" declarations, even if a
'_UID' child object exists, it has no bearing with respect to mapping
Local SAPICs (see section 5.2.11.13 - Local SAPIC Structure; "Advanced
Configuration and Power Interface Specification", Revision 3.0b).
This patch changes the lsapic mapping logic to rely on the distinction of
how the processor object was declared - the mapping can't just try both
types of matches regardless of declaration type and rely on one failing
as is currently being done.
Signed-off-by: Myron Stowe <myron.stowe@hp.com>
Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'drivers/acpi/executer/exresop.c')
0 files changed, 0 insertions, 0 deletions