From: Jon Hunter <jonathanh@nvidia.com>
To: Peter Robinson <pbrobinson@gmail.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-rtc@vger.kernel.org
Cc: Shubhi Garg <shgarg@nvidia.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH] rtc: nvvrs: Add ARCH_TEGRA to the NV VRS RTC driver
Date: Fri, 2 Jan 2026 11:01:58 +0000 [thread overview]
Message-ID: <dd1f2ecd-033b-4b10-bc27-f561ec315808@nvidia.com> (raw)
In-Reply-To: <20251222035651.433603-1-pbrobinson@gmail.com>
On 22/12/2025 03:56, Peter Robinson wrote:
> The NV VRS RTC driver currently is only supported on the
> Tegra platform so add a dep for ARCH_TEGRA and compile test
> so it doesn't show up universally across all arches/platforms.
>
> Fixes: 9d6d6b06933c8 ("rtc: nvvrs: add NVIDIA VRS RTC device driver")
> Cc: Shubhi Garg <shgarg@nvidia.com>
> Cc: Jon Hunter <jonathanh@nvidia.com>
> Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
> ---
> drivers/rtc/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
> index 50dc779f7f983..50ba48609d74e 100644
> --- a/drivers/rtc/Kconfig
> +++ b/drivers/rtc/Kconfig
> @@ -418,6 +418,7 @@ config RTC_DRV_SPACEMIT_P1
>
> config RTC_DRV_NVIDIA_VRS10
> tristate "NVIDIA VRS10 RTC device"
> + depends on ARCH_TEGRA || COMPILE_TEST
> help
> If you say yes here you will get support for the battery backed RTC device
> of NVIDIA VRS (Voltage Regulator Specification). The RTC is connected via
Looks good to me.
Acked-by: Jon Hunter <jonathanh@nvidia.com>
Thanks!
Jon
--
nvpublic
next prev parent reply other threads:[~2026-01-02 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 3:56 [PATCH] rtc: nvvrs: Add ARCH_TEGRA to the NV VRS RTC driver Peter Robinson
2026-01-02 11:01 ` Jon Hunter [this message]
2026-01-19 23:17 ` Alexandre Belloni
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=dd1f2ecd-033b-4b10-bc27-f561ec315808@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pbrobinson@gmail.com \
--cc=shgarg@nvidia.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