devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
	Tengfei Fan <quic_tengfan@quicinc.com>,
	agross@kernel.org, andersson@kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Abel Vesa <abel.vesa@linaro.org>,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel@quicinc.com,
	Qiang Yu <quic_qianyu@quicinc.com>,
	Ziyue Zhang <quic_ziyuzhan@quicinc.com>
Subject: Re: [PATCH v2 7/7] arm64: dts: qcom: aim300: add AIM300 AIoT
Date: Wed, 13 Dec 2023 20:38:59 +0100	[thread overview]
Message-ID: <ad65341e-2d84-4fe1-bd04-c788d4c6eecc@linaro.org> (raw)
In-Reply-To: <e2c5d7ba-15c0-45ea-ae45-2a6deffde04e@linaro.org>

On 13/12/2023 20:01, Konrad Dybcio wrote:
> 
> 
> On 12/13/23 15:04, Krzysztof Kozlowski wrote:
>> On 11/12/2023 11:33, Krzysztof Kozlowski wrote:
>>>> @@ -0,0 +1,579 @@
>>>> +// SPDX-License-Identifier: BSD-3-Clause
>>>> +/*
>>>> + * Copyright (c) 2023, Qualcomm Innovation Center, Inc. All rights reserved.
>>>> + */
>>>> +
>>>> +/dts-v1/;
>>>> +
>>>> +#include <dt-bindings/leds/common.h>
>>>> +#include "qcs8550-aim300.dtsi"
>>>
>>> Which includes sm8550.dtsi thus I think this is compatible with sm8550.
>>> You even use sm8550 compatibles here, which is one more hint for that
>>> compatibility.
>>>
>>> We followed this convention for RB5, although not for QRU/QDU1000 boards.
>>>
>>> Anyway, if you add here new SoC compatible, I would expect to see new
>>> SoC DTSI.
>>>
>>> I don't have in my notes any previous consensus or decision in these
>>> matters, so let's discuss now.
>>> +CC few Linaro folks
>>
>> After some talks, the idea is to create qcs8550.dtsi, which will include
>> sm8550.dtsi, and add top level compatible for qcs8550 using sm8550 fallback.
> To the board device tree? Otherwise it'll get overwritten.

Could be both, to serve as a guideline for future DTS, but in general
yes, to the board DTS.

Best regards,
Krzysztof


      reply	other threads:[~2023-12-13 19:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-07  9:27 [PATCH v2 0/7] arm64: qcom: add AIM300 AIoT board support Tengfei Fan
2023-12-07  9:27 ` [PATCH v2 1/7] dt-bindings: arm: qcom: Document qcs8550 SoC and board Tengfei Fan
2023-12-11 10:24   ` Krzysztof Kozlowski
2023-12-07  9:27 ` [PATCH v2 2/7] arm64: dts: qcom: sm8550: remove address/size-cells from pwm Tengfei Fan
2023-12-07  9:27 ` [PATCH v2 3/7] arm64: dts: qcom: sm8550: remove address/size-cells from mdss_dsi1 Tengfei Fan
2023-12-11 10:25   ` Krzysztof Kozlowski
2023-12-18  9:59     ` Tengfei Fan
2023-12-18 10:13       ` Krzysztof Kozlowski
2023-12-19  0:40         ` Tengfei Fan
2023-12-07  9:27 ` [PATCH v2 4/7] dt-bindings: arm: qcom,ids: add SoC ID for QCS8550 Tengfei Fan
2023-12-11 10:26   ` Krzysztof Kozlowski
2023-12-07  9:27 ` [PATCH v2 5/7] soc: qcom: socinfo: add SoC Info support for the QCS8550 platform Tengfei Fan
2023-12-11 10:26   ` Krzysztof Kozlowski
2023-12-07  9:28 ` [PATCH v2 6/7] arm64: dts: qcom: add base AIM300 dtsi Tengfei Fan
2023-12-07  9:28 ` [PATCH v2 7/7] arm64: dts: qcom: aim300: add AIM300 AIoT Tengfei Fan
2023-12-11 10:33   ` Krzysztof Kozlowski
2023-12-13 14:04     ` Krzysztof Kozlowski
2023-12-13 19:01       ` Konrad Dybcio
2023-12-13 19:38         ` Krzysztof Kozlowski [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=ad65341e-2d84-4fe1-bd04-c788d4c6eecc@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=abel.vesa@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=kernel@quicinc.com \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=quic_qianyu@quicinc.com \
    --cc=quic_tengfan@quicinc.com \
    --cc=quic_ziyuzhan@quicinc.com \
    --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).