public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: linux-rockchip@lists.infradead.org, heiko@sntech.de,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	stable@vger.kernel.org, Alexey Charkov <alchark@gmail.com>
Subject: Re: [PATCH] arm64: dts: rockchip: Remove overdrive-mode OPPs from RK3588J SoC dtsi
Date: Mon, 24 Mar 2025 10:36:54 +0100	[thread overview]
Message-ID: <460503eb831485ede9a49dcf226aef1b@manjaro.org> (raw)
In-Reply-To: <960c038ad9f7b83fe14d0ded388b42f7@manjaro.org>

Hello Quentin,

On 2025-03-23 11:19, Dragan Simic wrote:
> On 2025-03-21 10:53, Quentin Schulz wrote:
>> On 3/21/25 4:28 AM, Dragan Simic wrote:
>>> The differences in the vendor-approved CPU and GPU OPPs for the 
>>> standard
>>> Rockchip RK3588 variant [1] and the industrial Rockchip RK3588J 
>>> variant [2]
>>> come from the latter, presumably, supporting an extended temperature 
>>> range
>>> that's usually associated with industrial applications, despite the 
>>> two SoC
>>> variant datasheets specifying the same upper limit for the allowed 
>>> ambient
>>> temperature for both variants.  However, the lower temperature limit 
>>> is
>> 
>> RK3588 is rated for 0-80°C, RK3588J for -40-85°C, c.f. Recommended
>> Operating Conditions, Table 3-2, Ambient Operating Temperature.
> 
> Indeed, which is why I specifically wrote "specifying the same upper
> limit", because having a lower negative temperature limit could hardly
> put the RK3588J in danger of overheating or running hotter. :)

Oh, now I see what you actually wrote above, which I misread a bit
initially...  In fact, the upper ambient temperature limit is the
same for both RK3588J and RK3588, according to the datasheets;  it's
just that the lower temperature limit is much lower for the RK3588J,
which the patch description says.

I'm not sure where did you find the 80 vs. 85 oC difference;  please,
see a couple of screenshots from the datasheets, linked below:

- RK3588 datasheet v1.6 (v1.7 is the same): https://0x0.st/8j1a.png
- RK3588J datasheet v1.1: https://0x0.st/8j1m.png

The v2 of the patch is coming soon, with the patch description improved
according to your suggestions.

      parent reply	other threads:[~2025-03-24  9:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-21  3:28 [PATCH] arm64: dts: rockchip: Remove overdrive-mode OPPs from RK3588J SoC dtsi Dragan Simic
2025-03-21  9:53 ` Quentin Schulz
2025-03-23 10:19   ` Dragan Simic
2025-03-24  9:23     ` Quentin Schulz
2025-03-24  9:53       ` Dragan Simic
2025-03-24 10:20         ` Quentin Schulz
2025-03-24 10:33           ` Dragan Simic
2025-03-24  9:36     ` Dragan Simic [this message]

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-all 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=460503eb831485ede9a49dcf226aef1b@manjaro.org \
    --to=dsimic@manjaro.org \
    --cc=alchark@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=quentin.schulz@cherry.de \
    --cc=robh@kernel.org \
    --cc=stable@vger.kernel.org \
    /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