public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Jeremy Linton" <jeremy.linton@arm.com>
To: Ard Biesheuvel <ard.biesheuvel@arm.com>,
	Pete Batard <pete@akeo.ie>,
	devel@edk2.groups.io
Cc: Leif Lindholm <leif@nuviainc.com>,
	Andrei Warkentin <awarkentin@vmware.com>,
	Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
Subject: Re: [PATCH v3 1/5] Platform/RaspberryPi4: Add a basic thermal zone
Date: Mon, 31 Aug 2020 10:49:08 -0500	[thread overview]
Message-ID: <a5e79d7a-b1ae-cb40-489d-728cd9fc9014@arm.com> (raw)
In-Reply-To: <f1daa9c5-b39a-f2d4-c2bc-69b00b9aff1b@arm.com>

On 8/31/20 10:33 AM, Ard Biesheuvel wrote:
> On 8/31/20 5:13 PM, Jeremy Linton wrote:
>> Hi,
>>
>> On 8/31/20 8:15 AM, Pete Batard wrote:
>>> One general, non-blocking comment below:
>>>
>>> On 2020.08.28 23:02, Jeremy Linton wrote:
>>>> Rather than exporting the temp sensor or mailbox
>>>> in ACPI land we can wrap them in AML and use the default
>>>> ACPI drivers provided by the OS. This enables the use of
>>>> "sensors" in linux to report the SOC temp.
>>>>
>>>> As a first pass add a basic passive cooling ACPI thermalzone
>>>> with trip points for passive cooling (throttling) handled
>>>> by the vc firmware, hibernate and critical shutdown. The
>>>> vc apparently kicks in at ~80C, so the hibernate and critical
>>>> set points are set at +5 and +10 of that. In the future
>>>> CPPC should be able to monitor the thermal throttling.
>>>>
>>>> Cc: Leif Lindholm <leif@nuviainc.com>
>>>> Cc: Pete Batard <pete@akeo.ie>
>>>> Cc: Andrei Warkentin <awarkentin@vmware.com>
>>>> Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>
>>>> Cc: Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
>>>> Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
>>>> Reviewed-by: Pete Batard <@pbatard>
>>>> ---
>>>>   Platform/RaspberryPi/AcpiTables/Dsdt.asl           | 31 
>>>> ++++++++++++++++++++++
>>>>   .../Bcm27xx/Include/IndustryStandard/Bcm2711.h     |  2 ++
>>>>   2 files changed, 33 insertions(+)
>>>>
>>>> diff --git a/Platform/RaspberryPi/AcpiTables/Dsdt.asl 
>>>> b/Platform/RaspberryPi/AcpiTables/Dsdt.asl
>>>> index 353af2d876..73067aefd2 100644
>>>> --- a/Platform/RaspberryPi/AcpiTables/Dsdt.asl
>>>> +++ b/Platform/RaspberryPi/AcpiTables/Dsdt.asl
>>>> @@ -252,6 +252,37 @@ DefinitionBlock ("Dsdt.aml", "DSDT", 5, 
>>>> "RPIFDN", "RPI", 2)
>>>>           }
>>>>
>>>>         })
>>>>
>>>>       }
>>>>
>>>> +
>>>>
>>>> +    // Define a simple thermal zone. The idea here is we compute 
>>>> the SOC temp
>>>>
>>>> +    // via a register we can read, and give it to the OS. This 
>>>> enables basic
>>>>
>>>> +    // reports from the "sensors" utility, and the OS can then poll 
>>>> and take
>>>>
>>>> +    // actions if that temp exceeds any of the given thresholds.
>>>>
>>>> +    Device (EC0)
>>>
>>> Just going to point out that all the other ACPI devices we seem to 
>>> define have 4 characters, so I'm not sure if we're breaking a 
>>> convention by introducing a 3 character one here...
>>
>> Well not an ACPI spec convention, because it seems the spec examples 
>> are mostly 3 characters. EDK2 OTOH, seems to be largely 4 but there 
>> are a fair number of 3 character device/etc methods around
>>
>> I'm not sure it matters, unless there is a edk2 convention I'm unaware 
>> of.
>>
> 
> I don't think such a convention exists, although I never tried the MS 
> iasl compiler, and the RPi asl code (which was contributed by MS) 
> suspiciously uses 4 letter identifiers everywhere.
> 
> Samer, any clue?
> 

I have another patch to allow the user to set the temp trip point which 
IIRC Andrei had asked about months ago when I originally mentioned that 
I had hacked up a thermal zone.

I might as well roll a v4 with that, the whitespace, and "0"'s appended 
to EC0 and TZ0 just in case... I'm sanity checking right now that it 
still works.





  reply	other threads:[~2020-08-31 15:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28 22:02 [PATCH v3 0/5] Platform/RasberryPi: Thermal zone Jeremy Linton
2020-08-28 22:02 ` [PATCH v3 1/5] Platform/RaspberryPi4: Add a basic thermal zone Jeremy Linton
2020-08-31 13:15   ` Pete Batard
2020-08-31 15:13     ` Jeremy Linton
2020-08-31 15:33       ` Ard Biesheuvel
2020-08-31 15:49         ` Jeremy Linton [this message]
2020-08-28 22:02 ` [PATCH v3 2/5] Platform/RaspberryPi: Monitor ACPI Table installs Jeremy Linton
2020-08-31 13:17   ` Pete Batard
2020-08-28 22:02 ` [PATCH v3 3/5] Platform/RaspberryPi: Add entry for user fan control Jeremy Linton
2020-08-31 13:17   ` Pete Batard
2020-08-28 22:02 ` [PATCH v3 4/5] Platform/RaspberryPi4: Create ACPI fan object Jeremy Linton
2020-08-31 13:17   ` Pete Batard
2020-08-28 22:02 ` [PATCH v3 5/5] Platform/RaspberryPi: Trivial whitespace cleanup Jeremy Linton
2020-08-31 13:17   ` Pete Batard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a5e79d7a-b1ae-cb40-489d-728cd9fc9014@arm.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox