From: Krzysztof Kozlowski <krzk@kernel.org>
To: Tingguo Cheng <quic_tingguoc@quicinc.com>,
andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@quicinc.com,
quic_kotarake@quicinc.com, quic_kamalw@quicinc.com,
quic_skakitap@quicinc.com, quic_fenglinw@quicinc.com
Subject: Re: [PATCH] arm64: dts: qcom: sa8775p: pmic: enable rtc
Date: Fri, 6 Sep 2024 14:22:42 +0200 [thread overview]
Message-ID: <f5b768b3-37ad-4bdf-9cb6-b39b14c8ee45@kernel.org> (raw)
In-Reply-To: <20240902104302.3959670-1-quic_tingguoc@quicinc.com>
On 02/09/2024 12:43, Tingguo Cheng wrote:
> Add RTC node, the RTC is controlled by PMIC device via spmi bus.
>
> Signed-off-by: Tingguo Cheng <quic_tingguoc@quicinc.com>
> ---
> arch/arm64/boot/dts/qcom/sa8775p-pmics.dtsi | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/sa8775p-pmics.dtsi b/arch/arm64/boot/dts/qcom/sa8775p-pmics.dtsi
> index 1369c3d43f86..47d05b897d5a 100644
> --- a/arch/arm64/boot/dts/qcom/sa8775p-pmics.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sa8775p-pmics.dtsi
We achieved consensus allowing sa8775p to stay, but now Qualcomm changes
point of view and insists on new approach of dropping sa8775p. Therefore
this change does not make much sense in the new approach.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-06 12:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 10:43 [PATCH] arm64: dts: qcom: sa8775p: pmic: enable rtc Tingguo Cheng
2024-09-06 12:22 ` Krzysztof Kozlowski [this message]
2024-09-19 2:23 ` Tingguo Cheng
2024-11-22 10:38 ` Tingguo Cheng
2024-11-22 11:00 ` Dmitry Baryshkov
2025-01-16 7:44 ` Tingguo Cheng
2025-01-16 9:11 ` Krzysztof Kozlowski
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=f5b768b3-37ad-4bdf-9cb6-b39b14c8ee45@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@quicinc.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_fenglinw@quicinc.com \
--cc=quic_kamalw@quicinc.com \
--cc=quic_kotarake@quicinc.com \
--cc=quic_skakitap@quicinc.com \
--cc=quic_tingguoc@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