From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Raj Aryan <raryan@qti.qualcomm.com>
Subject: Re: [PATCH 1/2] dt-bindings: soc: qcom: qcom,pmic-glink: Document RTC client properties
Date: Wed, 26 Aug 2026 08:11:36 +0200 [thread overview]
Message-ID: <6079c72b-cb98-4a38-b887-962a78be2877@kernel.org> (raw)
In-Reply-To: <2yndadk6urzktzbb4mg7rhnywb3lxi6liuw2afdee6tswhnl6h@tqvt3n2r4qkj>
On 20/08/2026 21:23, Kamal Wadhwa wrote:
> On Thu, Aug 06, 2026 at 07:02:44PM -0500, Bjorn Andersson wrote:
>>
>>>
>>> Assisted-by: Claude:claude-sonnet-5
>>> Signed-off-by: Raj Aryan <raryan@qti.qualcomm.com>
>>> Signed-off-by: Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>
>>
>> As with the driver, the author/s-o-b chain is wrong.
>>
>
> Ack. will have it this way
>
> Assisted-by: Claude:claude-sonnet-5
> Signed-off-by: Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>
> Signed-off-by: Raj Aryan <raryan@qti.qualcomm.com>
> Signed-off-by: Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>
The original SoB chain was right in such case. You sign only once, so
first one is dropped. And this is what b4 produces.
>
>>> ---
>>> Documentation/devicetree/bindings/soc/qcom/qcom,pmic-glink.yaml | 5 +++++
>>> 1 file changed, 5 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,pmic-glink.yaml b/Documentation/devicetree/bindings/soc/qcom/qcom,pmic-glink.yaml
>>> index 16ad4f5698fc..38db1ff473c0 100644
>>> --- a/Documentation/devicetree/bindings/soc/qcom/qcom,pmic-glink.yaml
>>> +++ b/Documentation/devicetree/bindings/soc/qcom/qcom,pmic-glink.yaml
>>> @@ -79,6 +79,11 @@ properties:
>>> - const: charge_limit_end
>>> - const: charge_limit_delta
>>>
>>> + allow-set-time:
>>> + $ref: /schemas/types.yaml#/definitions/flag
>>> + description:
>>> + Indicates that the setting of RTC time is allowed by the host CPU.
>>
>> What property of the hardware/firmware that this describes would cause
>> you to set or not set this?
>>
>> Also, what would the expected outcome be if I declare that my Hamoa
>> hardware has pmic-glink with allow-set-time?
>
> Actually Hamoa firmware does not support it yet, so it may get ignored.
> but if the support was present, the writes will cause the system time
> to go bad, which relies on the RTC time elapsed during off state to
> calculate current system time, incase network is not available.
>
> this was used on rtc-pm8xxx.c driver as well
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/rtc/rtc-pm8xxx.c?h=v7.2#n622
It's a generic property, so where is it defined?
Why isn't it implied by the compatible?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-08-26 6:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 20:56 [PATCH 0/2] rtc: Add Qualcomm PMIC RTC-GLINK support for Glymur Kamal Wadhwa
2026-08-06 20:56 ` [PATCH 1/2] dt-bindings: soc: qcom: qcom,pmic-glink: Document RTC client properties Kamal Wadhwa
2026-08-07 0:02 ` Bjorn Andersson
2026-08-20 19:23 ` Kamal Wadhwa
2026-08-26 6:11 ` Krzysztof Kozlowski [this message]
2026-08-06 20:56 ` [PATCH 2/2] rtc: qcom: rtc-glink: Add PMIC GLINK RTC driver and extend pmic_glink Kamal Wadhwa
2026-08-06 23:53 ` Bjorn Andersson
2026-08-20 17:59 ` Kamal Wadhwa
2026-08-07 20:58 ` Alexandre Belloni
2026-08-20 16:49 ` Kamal Wadhwa
2026-08-11 12:10 ` [PATCH 0/2] rtc: Add Qualcomm PMIC RTC-GLINK support for Glymur Troels Vognbjerg
2026-08-20 16:38 ` Kamal Wadhwa
2026-08-25 19:38 ` Troels Vognbjerg
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=6079c72b-cb98-4a38-b887-962a78be2877@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kamal.wadhwa@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=raryan@qti.qualcomm.com \
--cc=robh@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