Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Xin Liu <quic_liuxin@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <kernel@quicinc.com>,
	<quic_jiegan@quicinc.com>, <quic_aiquny@quicinc.com>,
	<quic_tingweiz@quicinc.com>
Subject: Re: [PATCH v3 3/3] arm64: dts: qcom: qcs8300-ride: Add watchdog node
Date: Tue, 26 Nov 2024 11:14:25 +0800	[thread overview]
Message-ID: <c77d69d3-d809-4996-b203-e9496e169a8f@quicinc.com> (raw)
In-Reply-To: <wty3opxcapeesat2bnai6ntbk4utwxk2hf56w4hymwjxj57ora@6f7f2lwtdcpo>



在 2024/11/26 0:45, Dmitry Baryshkov 写道:
> I'd really prefer to have this in the SoC dtsi. It's not a part that can
> change between boards.

I think you're right, this clock won't change because of the board The 
reason for placing it on the board is that sleep_clk is defined on the 
board. The following link is the suggestion you once provided:
https://lore.kernel.org/all/4kopdkvbkrpcpzwteezm427ml5putqvzsnfkpmg76spsple7l5@mg7v3ihwxnit/


      reply	other threads:[~2024-11-26  3:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25  9:35 [PATCH v3 0/3] Enable Watchdog on QCS8300 Xin Liu
2024-11-25  9:35 ` [PATCH v3 1/3] dt-bindings: watchdog: Document Qualcomm QCS8300 watchdog Xin Liu
2024-11-25  9:35 ` [PATCH v3 2/3] arm64: dts: qcom: qcs8300: Add watchdog node Xin Liu
2024-11-25 12:47   ` Konrad Dybcio
2024-11-25  9:35 ` [PATCH v3 3/3] arm64: dts: qcom: qcs8300-ride: " Xin Liu
2024-11-25 16:45   ` Dmitry Baryshkov
2024-11-26  3:14     ` Xin Liu [this message]

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=c77d69d3-d809-4996-b203-e9496e169a8f@quicinc.com \
    --to=quic_liuxin@quicinc.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.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_aiquny@quicinc.com \
    --cc=quic_jiegan@quicinc.com \
    --cc=quic_tingweiz@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