Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Mikko Perttunen <mperttunen@nvidia.com>
To: Thierry Reding <thierry.reding@kernel.org>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	webgeek1234@gmail.com
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	Aaron Kling <webgeek1234@gmail.com>
Subject: Re: [PATCH 2/2] soc/tegra: fuse: speedo-tegra210: Support revision B01
Date: Tue, 21 Jul 2026 16:43:23 +0900	[thread overview]
Message-ID: <gVqt6-6mTtaAeVdWZqsmEQ@nvidia.com> (raw)
In-Reply-To: <20260717-t210b01-speedo-v1-2-f04a8bd4d997@gmail.com>

On Saturday, July 18, 2026 8:19 AM Aaron Kling via B4 Relay wrote:
> From: Aaron Kling <webgeek1234@gmail.com>
> 
> Tegra210B01 has a separate set of skus and speedo tables
> 
> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> ---
>  drivers/soc/tegra/fuse/speedo-tegra210.c | 22 ++++++++++++++++++++--
>  1 file changed, 20 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/soc/tegra/fuse/speedo-tegra210.c b/drivers/soc/tegra/fuse/speedo-tegra210.c
> index 06c2bcbee5734..699751f4bd0c0 100644
> --- a/drivers/soc/tegra/fuse/speedo-tegra210.c
> +++ b/drivers/soc/tegra/fuse/speedo-tegra210.c
> @@ -65,7 +65,25 @@ static void __init rev_sku_to_speedo_ids(struct tegra_sku_info *sku_info,
>  	sku_info->gpu_speedo_id = 0;
>  	*threshold = THRESHOLD_INDEX_0;
>  
> -	if (sku_info->revision >= TEGRA_REVISION_A02) {
> +	if (sku_info->revision >= TEGRA_REVISION_B01) {
> +		sku_info->gpu_speedo_id = 1;
> +
> +		switch (sku) {
> +		case 0x00: /* Engineering SKU */
> +		case 0x01: /* Engineering SKU */
> +		case 0x83:
> +			break;
> +
> +		case 0x87:
> +			sku_info->cpu_speedo_id = 3;
> +			break;
> +
> +		default:
> +			pr_err("Tegra210B01: unknown SKU %#04x\n", sku);
> +			/* Using the default for the error case */
> +			break;
> +		}
> +	} else if (sku_info->revision >= TEGRA_REVISION_A02) {
>  		switch (sku) {
>  		case 0x00: /* Engineering SKU */
>  		case 0x01: /* Engineering SKU */
> @@ -154,7 +172,7 @@ void __init tegra210_init_speedo_data(struct tegra_sku_info *sku_info)
>  	speedo_revision = get_speedo_revision();
>  	pr_info("Speedo Revision %u\n", speedo_revision);
>  
> -	if (speedo_revision >= 3) {
> +	if (sku_info->revision == TEGRA_REVISION_B01 || speedo_revision >= 3) {
>  		sku_info->cpu_speedo_value = cpu_speedo[0];
>  		sku_info->gpu_speedo_value = cpu_speedo[2];
>  		sku_info->soc_speedo_value = soc_speedo[0];
> 
> -- 
> 2.54.0
> 
> 
> 

Thanks!

Reviewed-by: Mikko Perttunen <mperttunen@nvidia.com>




  reply	other threads:[~2026-07-21  7:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-17 23:19 [PATCH 0/2] soc/tegra: fuse: Support Tegra210B01 Speedos Aaron Kling via B4 Relay
2026-07-17 23:19 ` [PATCH 1/2] soc/tegra: fuse: Support revision B01 Aaron Kling via B4 Relay
2026-07-21  7:37   ` Mikko Perttunen
2026-07-17 23:19 ` [PATCH 2/2] soc/tegra: fuse: speedo-tegra210: " Aaron Kling via B4 Relay
2026-07-21  7:43   ` Mikko Perttunen [this message]
2026-07-21  9:46   ` Jon Hunter
2026-07-21 17:31     ` Aaron Kling
2026-07-22 12:44       ` Jon Hunter
2026-07-23  3:11         ` Aaron Kling

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=gVqt6-6mTtaAeVdWZqsmEQ@nvidia.com \
    --to=mperttunen@nvidia.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=thierry.reding@kernel.org \
    --cc=webgeek1234@gmail.com \
    /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