From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Jonathan Marek <jonathan@marek.ca>
Cc: linux-arm-msm@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:REAL TIME CLOCK (RTC) SUBSYSTEM"
<linux-rtc@vger.kernel.org>, Rob Herring <robh@kernel.org>,
Satya Priya <quic_c_skakit@quicinc.com>
Subject: Re: [PATCH v3 0/5] x1e80100 RTC support
Date: Mon, 13 Jan 2025 00:35:38 +0100 [thread overview]
Message-ID: <202501122335384a545895@mail.local> (raw)
In-Reply-To: <20241015004945.3676-1-jonathan@marek.ca>
Hello,
Did I miss v4 of this series?
On 14/10/2024 20:47:25-0400, Jonathan Marek wrote:
> x1e80100 needs a workaround because the RTC alarm is not owned by HLOS.
> It also needs the same offset workaround as sc8280xp/etc.
>
> v2: remove duplicated ops and use RTC_FEATURE_ALARM instead
> v3:
> - renamed flag to qcom,no-alarm
> - don't remove alarm registers/interrupt from dts
>
> Jonathan Marek (5):
> rtc: pm8xxx: implement qcom,no-alarm flag for non-HLOS owned alarm
> dt-bindings: rtc: qcom-pm8xxx: document qcom,no-alarm flag
> arm64: dts: qcom: x1e80100-pmics: enable RTC
> arm64: dts: qcom: x1e80100-crd: add rtc offset to set rtc time
> arm64: dts: qcom: x1e78100-t14s: add rtc offset to set rtc time
>
> .../bindings/rtc/qcom-pm8xxx-rtc.yaml | 5 +++
> .../qcom/x1e78100-lenovo-thinkpad-t14s.dts | 11 +++++
> arch/arm64/boot/dts/qcom/x1e80100-crd.dts | 11 +++++
> arch/arm64/boot/dts/qcom/x1e80100-pmics.dtsi | 3 +-
> drivers/rtc/rtc-pm8xxx.c | 44 +++++++++++++------
> 5 files changed, 58 insertions(+), 16 deletions(-)
>
> --
> 2.45.1
>
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-01-12 23:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 0:47 [PATCH v3 0/5] x1e80100 RTC support Jonathan Marek
2024-10-15 0:47 ` [PATCH v3 2/5] dt-bindings: rtc: qcom-pm8xxx: document qcom,no-alarm flag Jonathan Marek
2024-10-15 5:33 ` Krzysztof Kozlowski
2024-10-16 6:46 ` Johan Hovold
2024-10-15 0:47 ` [PATCH v3 3/5] arm64: dts: qcom: x1e80100-pmics: enable RTC Jonathan Marek
2024-10-15 0:47 ` [PATCH v3 4/5] arm64: dts: qcom: x1e80100-crd: add rtc offset to set rtc time Jonathan Marek
2024-10-16 6:51 ` Johan Hovold
2024-10-16 13:31 ` Jonathan Marek
2024-10-18 9:44 ` Johan Hovold
2024-10-31 20:09 ` Konrad Dybcio
2024-10-15 0:47 ` [PATCH v3 5/5] arm64: dts: qcom: x1e78100-t14s: " Jonathan Marek
2025-01-12 23:35 ` Alexandre Belloni [this message]
2025-01-20 14:51 ` [PATCH v3 0/5] x1e80100 RTC support Johan Hovold
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=202501122335384a545895@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathan@marek.ca \
--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=quic_c_skakit@quicinc.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;
as well as URLs for NNTP newsgroup(s).