[CPUFREQ] Fix _OSC UUID in pcc-cpufreq
UUID needs to be written out the way it is described in Sec 18.5.124 of ACPI 4.0a Specification. Platform firmware's use of this UUID/_OSC is optional, which is why we didn't notice this bug earlier. Signed-off-by: Naga Chumbalkar <nagananda.chumbalkar@hp.com> Signed-off-by: Dave Jones <davej@redhat.com> Cc: stable@kernel.orghifive-unleashed-5.1
parent
5dd12af05c
commit
904cc1e637
|
@ -39,7 +39,7 @@
|
||||||
|
|
||||||
#include <acpi/processor.h>
|
#include <acpi/processor.h>
|
||||||
|
|
||||||
#define PCC_VERSION "1.00.00"
|
#define PCC_VERSION "1.10.00"
|
||||||
#define POLL_LOOPS 300
|
#define POLL_LOOPS 300
|
||||||
|
|
||||||
#define CMD_COMPLETE 0x1
|
#define CMD_COMPLETE 0x1
|
||||||
|
@ -102,7 +102,7 @@ static struct acpi_generic_address doorbell;
|
||||||
static u64 doorbell_preserve;
|
static u64 doorbell_preserve;
|
||||||
static u64 doorbell_write;
|
static u64 doorbell_write;
|
||||||
|
|
||||||
static u8 OSC_UUID[16] = {0x63, 0x9B, 0x2C, 0x9F, 0x70, 0x91, 0x49, 0x1f,
|
static u8 OSC_UUID[16] = {0x9F, 0x2C, 0x9B, 0x63, 0x91, 0x70, 0x1f, 0x49,
|
||||||
0xBB, 0x4F, 0xA5, 0x98, 0x2F, 0xA1, 0xB5, 0x46};
|
0xBB, 0x4F, 0xA5, 0x98, 0x2F, 0xA1, 0xB5, 0x46};
|
||||||
|
|
||||||
struct pcc_cpu {
|
struct pcc_cpu {
|
||||||
|
|
Loading…
Reference in New Issue