mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tengfei Fan <quic_tengfan@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: <andersson@kernel.org>, <konrad.dybcio@linaro.org>,
	<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<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>,
	<quic_chenlei@quicinc.com>
Subject: Re: [PATCH v9 4/4] arm64: dts: qcom: aim300: add AIM300 AIoT
Date: Mon, 3 Jun 2024 15:38:44 +0800	[thread overview]
Message-ID: <89c5c663-df8a-43d4-91b3-0a84b0c9a324@quicinc.com> (raw)
In-Reply-To: <CAA8EJpqFq=6YFcUpjdkKikN54iQ76i8Rk_z+mLH1Tt0zFFmciQ@mail.gmail.com>



On 5/31/2024 4:38 PM, Dmitry Baryshkov wrote:
> On Fri, 31 May 2024 at 11:35, Tengfei Fan <quic_tengfan@quicinc.com> wrote:
>>
>>
>>
>> On 5/29/2024 11:18 PM, Dmitry Baryshkov wrote:
>>> On Wed, May 29, 2024 at 06:09:26PM +0800, Tengfei Fan wrote:
>>>> Add AIM300 AIoT Carrier board DTS support, including usb, UART, PCIe,
>>>> I2C functions support.
>>>> Here is a diagram of AIM300 AIoT Carrie Board and SoM
>>>>    +--------------------------------------------------+
>>>>    |             AIM300 AIOT Carrier Board            |
>>>>    |                                                  |
>>>>    |           +-----------------+                    |
>>>>    |power----->| Fixed regulator |---------+          |
>>>>    |           +-----------------+         |          |
>>>>    |                                       |          |
>>>>    |                                       v VPH_PWR  |
>>>>    | +----------------------------------------------+ |
>>>>    | |                          AIM300 SOM |        | |
>>>>    | |                                     |VPH_PWR | |
>>>>    | |                                     v        | |
>>>>    | |   +-------+       +--------+     +------+    | |
>>>>    | |   | UFS   |       | QCS8550|     |PMIC  |    | |
>>>>    | |   +-------+       +--------+     +------+    | |
>>>>    | |                                              | |
>>>>    | +----------------------------------------------+ |
>>>>    |                                                  |
>>>>    |                    +----+          +------+      |
>>>>    |                    |USB |          | UART |      |
>>>>    |                    +----+          +------+      |
>>>>    +--------------------------------------------------+
>>>>
>>>> Co-developed-by: Qiang Yu <quic_qianyu@quicinc.com>
>>>> Signed-off-by: Qiang Yu <quic_qianyu@quicinc.com>
>>>> Co-developed-by: Ziyue Zhang <quic_ziyuzhan@quicinc.com>
>>>> Signed-off-by: Ziyue Zhang <quic_ziyuzhan@quicinc.com>
>>>> Signed-off-by: Tengfei Fan <quic_tengfan@quicinc.com>
>>>> ---
>>>>    arch/arm64/boot/dts/qcom/Makefile             |   1 +
>>>>    .../boot/dts/qcom/qcs8550-aim300-aiot.dts     | 322 ++++++++++++++++++
>>>>    2 files changed, 323 insertions(+)
>>>>    create mode 100644 arch/arm64/boot/dts/qcom/qcs8550-aim300-aiot.dts
>>>
>>> [trimmed]
>>>
>>>> +&remoteproc_adsp {
>>>> +    firmware-name = "qcom/qcs8550/adsp.mbn",
>>>> +                    "qcom/qcs8550/adsp_dtbs.elf";
>>>
>>> Please excuse me, I think I missed those on the previous run.
>>>
>>> adsp_dtb.mbn
>>
>> Currently, waht we have released is adsp_dtbs.elf. If we modify it to
>> adsp_dtb.mbn, it may cause the ADSP functionality can not boot normally.
> 
> Released where? linux-firmware doesn't have such a file. And the modem
> partition most likely has a different path for it anyway.

Firmware releases can be obtained from 
https://qpm-git.qualcomm.com/home2/git/qualcomm/qualcomm-linux-spf-1-0_test_device_public.git 
after users sign up for free accounts on both 
https://qpm-git.qualcomm.com and https://chipmaster2.qti.qualcomm.com.

> 
>>
>>>
>>>> +    status = "okay";
>>>> +};
>>>> +
>>>> +&remoteproc_cdsp {
>>>> +    firmware-name = "qcom/qcs8550/cdsp.mbn",
>>>> +                    "qcom/qcs8550/cdsp_dtbs.elf";
>>>
>>> cdsp_dtb.mbn
>>
>> CDSP also as above ADSP.
>>
>>>
> 
>>>> +
>>>> +    te_active: te-active-state {
>>>> +            pins = "gpio86";
>>>> +            function = "mdp_vsync";
>>>> +            drive-strength = <2>;
>>>> +            bias-pull-down;
>>>> +    };
>>>> +
>>>> +    te_suspend: te-suspend-state {
>>>> +            pins = "gpio86"
>>>> +            function = "mdp_vsync";
>>>> +            drive-strength = <2>;
>>>> +            bias-pull-down;
>>>> +    };
>>>
>>> What is the difference between these two?
>>
>> TE pin needs to be pulled down for both active and suspend states. There
>> is no difference.
> 
> So why do you need two different states for it?

Dividing into two different states can provide a clearer expression of 
whether the corresponging functionality is avtive or suspend.

We can also find similar settings in the other SM8550 and SM8650 
platform dts files, such as sm8550-qrd.dts and sm8650-qrd.dts.

[1] sm8550-qrd.dts: 
https://elixir.bootlin.com/linux/v6.9.3/source/arch/arm64/boot/dts/qcom/sm8550-qrd.dts#L1052

[2] sm8650-qrd.dts: 
https://elixir.bootlin.com/linux/v6.9.3/source/arch/arm64/boot/dts/qcom/sm8650-qrd.dts#L1098

> 
> 
> 
> 
> 

-- 
Thx and BRs,
Tengfei Fan

  reply	other threads:[~2024-06-03  7:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-29 10:09 [PATCH v9 0/4] arm64: qcom: add AIM300 AIoT board support Tengfei Fan
2024-05-29 10:09 ` [PATCH v9 1/4] dt-bindings: arm: qcom: Document QCS8550 SoC and the AIM300 AIoT board Tengfei Fan
2024-05-29 10:09 ` [PATCH v9 2/4] arm64: dts: qcom: qcs8550: introduce qcs8550 dtsi Tengfei Fan
2024-06-03  9:20   ` Caleb Connolly
2024-06-04 10:51     ` Aiqun Yu (Maria)
2024-06-04 11:20       ` Caleb Connolly
2024-06-05  4:51         ` Aiqun Yu (Maria)
2024-06-05 12:00           ` Caleb Connolly
2024-06-12  7:06             ` Aiqun Yu (Maria)
2024-05-29 10:09 ` [PATCH v9 3/4] arm64: dts: qcom: add base AIM300 dtsi Tengfei Fan
2024-05-29 10:09 ` [PATCH v9 4/4] arm64: dts: qcom: aim300: add AIM300 AIoT Tengfei Fan
2024-05-29 15:18   ` Dmitry Baryshkov
2024-05-31  8:35     ` Tengfei Fan
2024-05-31  8:38       ` Dmitry Baryshkov
2024-06-03  7:38         ` Tengfei Fan [this message]
2024-06-03  7:52           ` Dmitry Baryshkov
2024-06-04  5:35             ` Tengfei Fan
2024-06-06  9:27             ` Tingwei Zhang
2024-06-06 10:54               ` Dmitry Baryshkov
2024-06-13  1:18                 ` Tengfei Fan

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=89c5c663-df8a-43d4-91b3-0a84b0c9a324@quicinc.com \
    --to=quic_tengfan@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=konrad.dybcio@linaro.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_chenlei@quicinc.com \
    --cc=quic_qianyu@quicinc.com \
    --cc=quic_ziyuzhan@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

all inboxes | Powered by JetHome®