From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Johan Hovold <johan@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Jonathan Marek <jonathan@marek.ca>,
Ard Biesheuvel <ardb@kernel.org>,
Maximilian Luz <luzmaximilian@gmail.com>,
Jens Glathe <jens.glathe@oldschoolsolutions.biz>,
Joel Stanley <joel@jms.id.au>, Sebastian Reichel <sre@kernel.org>,
Steev Klimaszewski <steev@kali.org>,
linux-arm-msm@vger.kernel.org, linux-rtc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/6] arm64: dts: qcom: x1e80100: enable rtc
Date: Mon, 17 Mar 2025 12:06:56 +0100 [thread overview]
Message-ID: <2025031711065662ac4072@mail.local> (raw)
In-Reply-To: <Z87avd83XTYQYIP8@hovoldconsulting.com>
On 10/03/2025 13:27:41+0100, Johan Hovold wrote:
> Hi Alexandre,
>
> On Wed, Feb 19, 2025 at 02:41:12PM +0100, Johan Hovold wrote:
> > This series adds support for utilising the UEFI firmware RTC offset to
> > the Qualcomm PMIC RTC driver and uses that to enable the RTC on all X
> > Elite machines.
>
> Do you think you could pick up the driver and binding changes here so
> that Bjorn can take the DT patches for 6.15?
This is taken now but I had to rebase on top of patches I already took,
please verify.
>
> > Johan Hovold (4):
> > rtc: pm8xxx: add support for uefi offset
> > rtc: pm8xxx: mitigate flash wear
> > arm64: dts: qcom: sc8280xp-x13s: switch to uefi rtc offset
> > arm64: dts: qcom: x1e80100: enable rtc
> >
> > Jonathan Marek (2):
> > dt-bindings: rtc: qcom-pm8xxx: document qcom,no-alarm flag
> > rtc: pm8xxx: implement qcom,no-alarm flag for non-HLOS owned alarm
>
> Johan
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-03-17 11:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 13:41 [PATCH v2 0/6] arm64: dts: qcom: x1e80100: enable rtc Johan Hovold
2025-02-19 13:41 ` [PATCH v2 1/6] dt-bindings: rtc: qcom-pm8xxx: document qcom,no-alarm flag Johan Hovold
2025-02-19 13:41 ` [PATCH v2 2/6] rtc: pm8xxx: add support for uefi offset Johan Hovold
2025-02-19 13:41 ` [PATCH v2 3/6] rtc: pm8xxx: mitigate flash wear Johan Hovold
2025-02-19 13:41 ` [PATCH v2 4/6] rtc: pm8xxx: implement qcom,no-alarm flag for non-HLOS owned alarm Johan Hovold
2025-02-19 13:41 ` [PATCH v2 5/6] arm64: dts: qcom: sc8280xp-x13s: switch to uefi rtc offset Johan Hovold
2025-02-19 13:41 ` [PATCH v2 6/6] arm64: dts: qcom: x1e80100: enable rtc Johan Hovold
2025-03-10 12:27 ` [PATCH v2 0/6] " Johan Hovold
2025-03-17 11:06 ` Alexandre Belloni [this message]
2025-03-17 11:52 ` Johan Hovold
2025-03-17 11:05 ` (subset) " Alexandre Belloni
2025-03-17 14:51 ` Bjorn Andersson
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=2025031711065662ac4072@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=andersson@kernel.org \
--cc=ardb@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=joel@jms.id.au \
--cc=johan@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=luzmaximilian@gmail.com \
--cc=robh@kernel.org \
--cc=sre@kernel.org \
--cc=steev@kali.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).