public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Besar Wicaksono <bwicaksono@nvidia.com>,
	"will@kernel.org" <will@kernel.org>,
	"suzuki.poulose@arm.com" <suzuki.poulose@arm.com>,
	"robin.murphy@arm.com" <robin.murphy@arm.com>,
	"ilkka@os.amperecomputing.com" <ilkka@os.amperecomputing.com>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	Thierry Reding <treding@nvidia.com>,
	Vikram Sethi <vsethi@nvidia.com>, Rich Wiley <rwiley@nvidia.com>,
	Shanker Donthineni <sdonthineni@nvidia.com>,
	Sean Kelley <skelley@nvidia.com>, Yifei Wan <YWan@nvidia.com>,
	Matt Ochs <mochs@nvidia.com>, Nirmoy Das <nirmoyd@nvidia.com>
Subject: Re: [PATCH 8/8] arm64: defconfig: Enable NVIDIA TEGRA410 PMU
Date: Wed, 11 Feb 2026 10:36:18 +0000	[thread overview]
Message-ID: <085ad06e-61fa-4f18-a7d4-d88554344553@nvidia.com> (raw)
In-Reply-To: <a04e5648-86c0-4930-ac2f-a824acb35941@kernel.org>


On 11/02/2026 06:19, Krzysztof Kozlowski wrote:

...

>>>>>> Enable driver for NVIDIA TEGRA410 CMEM Latency and C2C PMU device.
>>>>>
>>>>> Why? Why do we want it? Which *upstream board* uses it?
>>>>>
>>>>
>>>> These are for NVIDIA Vera platform (Tegra410 SoC).
>>>
>>> There is no such board (git grep), but anyway, don't explain it to me.
>>> Your commit should explain such stuff.
>>>
>>
>> This is a server platform. There is no upstream board using this device currently.
> 
> I don't understand why server or not server matters.

We should probably say this is an ACPI based platform.

> If there is no upstream user of this, it is wrong to add it to
> defconfig. This is upstream defconfig, not your distro.

This device does not support device-tree (so far) and hence, you will 
not see any device-tree for this. However, enabling this is still valid 
from an ACPI perspective.

Jon

-- 
nvpublic



  reply	other threads:[~2026-02-11 10:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-26 18:11 [PATCH 0/8] perf: add NVIDIA Tegra410 Uncore PMU support Besar Wicaksono
2026-01-26 18:11 ` [PATCH 1/8] perf/arm_cspmu: nvidia: Rename doc to Tegra241 Besar Wicaksono
2026-01-26 18:11 ` [PATCH 2/8] perf/arm_cspmu: nvidia: Add Tegra410 UCF PMU Besar Wicaksono
2026-01-29 22:20   ` Ilkka Koskinen
2026-01-26 18:11 ` [PATCH 3/8] perf/arm_cspmu: Add arm_cspmu_acpi_dev_get Besar Wicaksono
2026-01-29 22:23   ` Ilkka Koskinen
2026-01-26 18:11 ` [PATCH 4/8] perf/arm_cspmu: nvidia: Add Tegra410 PCIE PMU Besar Wicaksono
2026-01-28 15:56   ` kernel test robot
2026-01-29 22:34   ` Ilkka Koskinen
2026-01-26 18:11 ` [PATCH 5/8] perf/arm_cspmu: nvidia: Add Tegra410 PCIE-TGT PMU Besar Wicaksono
2026-01-29 22:40   ` Ilkka Koskinen
2026-02-10 16:01     ` Besar Wicaksono
2026-01-26 18:11 ` [PATCH 6/8] perf: add NVIDIA Tegra410 CPU Memory Latency PMU Besar Wicaksono
2026-01-28  0:40   ` kernel test robot
2026-01-30  2:09   ` Ilkka Koskinen
2026-01-26 18:11 ` [PATCH 7/8] perf: add NVIDIA Tegra410 C2C PMU Besar Wicaksono
2026-01-30  2:54   ` Ilkka Koskinen
2026-01-26 18:11 ` [PATCH 8/8] arm64: defconfig: Enable NVIDIA TEGRA410 PMU Besar Wicaksono
2026-02-08 11:18   ` Krzysztof Kozlowski
2026-02-10 16:05     ` Besar Wicaksono
2026-02-10 16:15       ` Krzysztof Kozlowski
2026-02-10 17:42         ` Besar Wicaksono
2026-02-11  6:19           ` Krzysztof Kozlowski
2026-02-11 10:36             ` Jon Hunter [this message]
2026-02-11 10:41               ` Krzysztof Kozlowski
2026-02-11 10:47                 ` Jon Hunter

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=085ad06e-61fa-4f18-a7d4-d88554344553@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=YWan@nvidia.com \
    --cc=bwicaksono@nvidia.com \
    --cc=ilkka@os.amperecomputing.com \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mochs@nvidia.com \
    --cc=nirmoyd@nvidia.com \
    --cc=robin.murphy@arm.com \
    --cc=rwiley@nvidia.com \
    --cc=sdonthineni@nvidia.com \
    --cc=skelley@nvidia.com \
    --cc=suzuki.poulose@arm.com \
    --cc=treding@nvidia.com \
    --cc=vsethi@nvidia.com \
    --cc=will@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