linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Jassi Brar <jassisinghbrar@gmail.com>,
	Johan Hovold <johan+linaro@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] arm64: dts: qcom: add SC8280XP platform
Date: Wed, 22 Jun 2022 16:44:26 +0200	[thread overview]
Message-ID: <6f5606be-5b6a-23f5-1fb3-b4964f8166b4@linaro.org> (raw)
In-Reply-To: <YrKNNQ2h6I8aseiW@ripper>

On 22/06/2022 05:32, Bjorn Andersson wrote:
>>>>
>>>
>>> It's an interesting question, but I don't think it's possible to change
>>> the rate of this clock from one board to another.
>>>
>>> So I think it's best to keep this in the .dtsi, to avoid unnecessary
>>> duplication.
>>
>> It does not matter whether the frequency can be changed or not. This is
>> the same on almost every SoC and the same comments appear every time -
>> the clock is a property of the board, not of the SoC, so it should be in
>> the board DTSI. To avoid the duplication you can indeed keep here most
>> of the clock properties, but the frequency must be in board DTS.
>>
> 
> I find this to be a rather strict interpretation of "board specific",
> but I'm okay with it.

Yes, it is quite strict, but in the long term helps - people explicitly
need to enable/fill properties in new board DTSes, which hopefully will
trigger some thinking - "do I really have 385 MHz XO clock"?

Although here it might not really important, but that approach is useful
for all other cases, including aliases and buses. And one day, such
clear design will help new guys doing new hardware bring-up and they
will say: "I will start my new DTS board on some examples from mainline". :)

Best regards,
Krzysztof

  reply	other threads:[~2022-06-22 14:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 21:41 [PATCH 0/4] arm64: dts: qcom: Introduce SC8280XP Bjorn Andersson
2022-06-07 21:41 ` [PATCH 1/4] dt-bindings: mailbox: qcom-ipcc: Add NSP1 client Bjorn Andersson
2022-06-08  7:59   ` Krzysztof Kozlowski
2022-08-02  3:28   ` Jassi Brar
2022-06-07 21:41 ` [PATCH 2/4] arm64: dts: qcom: add SC8280XP platform Bjorn Andersson
2022-06-08  8:18   ` Krzysztof Kozlowski
2022-06-21  3:37     ` Bjorn Andersson
2022-06-21  6:53       ` Krzysztof Kozlowski
2022-06-22  3:32         ` Bjorn Andersson
2022-06-22 14:44           ` Krzysztof Kozlowski [this message]
2022-06-08 16:00   ` Johan Hovold
2022-06-23  5:22   ` Vinod Koul
2022-06-23  6:42     ` Johan Hovold
2022-06-07 21:41 ` [PATCH 3/4] arm64: dts: qcom: sc8280x: Add reference device Bjorn Andersson
2022-06-08  8:24   ` Krzysztof Kozlowski
2022-06-08 16:17   ` Johan Hovold
2022-06-21  3:39     ` Bjorn Andersson
2022-06-07 21:41 ` [PATCH 4/4] arm64: dts: qcom: add SA8540P and ADP Bjorn Andersson
2022-06-08  8:26   ` 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=6f5606be-5b6a-23f5-1fb3-b4964f8166b4@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=johan+linaro@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=robh+dt@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).