From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jon Hunter <jonathanh@nvidia.com>, Shubhi Garg <shgarg@nvidia.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rtc@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v5 1/4] dt-bindings: rtc: Document NVIDIA VRS RTC
Date: Thu, 24 Jul 2025 12:06:03 +0200 [thread overview]
Message-ID: <f69a76c5-157d-4cb4-bf46-1acdb6a87319@kernel.org> (raw)
In-Reply-To: <2c59e665-6415-460b-8ff8-c06f8d94f9eb@nvidia.com>
On 24/07/2025 11:41, Jon Hunter wrote:
>
> On 24/07/2025 08:59, Krzysztof Kozlowski wrote:
>> On Wed, Jul 23, 2025 at 01:03:40PM +0000, Shubhi Garg wrote:
>>> +description:
>>> + NVIDIA VRS (Voltage Regulator Specification) RTC provides 32kHz RTC clock
>>> + support with backup battery for system timing. It provides alarm functionality
>>> + to wake system from suspend and shutdown state. The device also acts as an
>>> + interrupt controller for managing interrupts from the VRS.
>>> +
>>> +properties:
>>> + compatible:
>>> + const: nvidia,vrs10-rtc
>>
>> Nothing improved. You never replied to comments and then replaced one
>> redundant word into other redundant word.
>>
>> Respond to review or implement it fully, not partially.
>>
>> Or add COMPLETE bindings, not partial ones. See writing bindings doc.
>
> OK, right so the DT binding should describe the overall PMIC device,
> even though the driver needs to support the RTC.
This is not a driver patch. This is patch for hardware. Sending
incomplete pieces of a device, without complete picture is really not
the right way. Knowing this is part of PMIC this should be rejected, but
how can we decide on that if contributor never tells us this is a part
of PMIC?
>
> Shubhi, is vrs10 the version of the VRS spec for the PMIC device or just
> the RTC portion? If it is, the maybe 'nvidia,vrs10' is sufficient here.
>
> Jon
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-24 10:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 13:03 [PATCH v5 0/4] Add NVIDIA VRS RTC support Shubhi Garg
2025-07-23 13:03 ` [PATCH v5 1/4] dt-bindings: rtc: Document NVIDIA VRS RTC Shubhi Garg
2025-07-24 7:59 ` Krzysztof Kozlowski
2025-07-24 9:41 ` Jon Hunter
2025-07-24 10:06 ` Krzysztof Kozlowski [this message]
2025-07-24 10:50 ` Jon Hunter
2025-07-25 15:58 ` Shubhi Garg
[not found] ` <424cd602-412f-4981-9b7f-9d04d769b3c7@nvidia.com>
2025-08-05 6:18 ` Shubhi Garg
2025-09-05 6:40 ` Shubhi Garg
2025-07-23 13:03 ` [PATCH v5 2/4] arm64: tegra: Add device-tree node for NVVRS RTC Shubhi Garg
2025-07-23 13:03 ` [PATCH v5 3/4] rtc: nvvrs: add NVIDIA VRS device driver Shubhi Garg
2025-07-23 13:03 ` [PATCH v5 4/4] arm64: defconfig: enable NVIDIA VRS RTC Shubhi Garg
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=f69a76c5-157d-4cb4-bf46-1acdb6a87319@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=shgarg@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;
as well as URLs for NNTP newsgroup(s).