From: Jie Gan <jie.gan@oss.qualcomm.com>
To: Yijie Yang <yijie.yang@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
andersson@kernel.org, krzk+dt@kernel.org, konradybcio@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, conor+dt@kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v5 0/4] Initial patch set for PURWA-IOT-EVK
Date: Tue, 3 Mar 2026 11:09:17 +0800 [thread overview]
Message-ID: <9e933431-44da-40b6-85eb-9fa667a7c1fa@oss.qualcomm.com> (raw)
In-Reply-To: <1035ed36-8659-4fc9-9a4b-aa6bd2c3a286@oss.qualcomm.com>
On 2/4/2026 10:52 AM, Yijie Yang wrote:
>
>
> On 2/4/2026 10:38 AM, Dmitry Baryshkov wrote:
>> On Wed, Feb 04, 2026 at 09:42:04AM +0800, Yijie Yang wrote:
>>>
>>>
>>> On 2/4/2026 1:37 AM, Rob Herring wrote:
>>>>
>>>> On Mon, 02 Feb 2026 15:35:44 +0800, YijieYang wrote:
>>>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>>>
>>>>> Introduce the device tree, DT bindings, and driver updates required
>>>>> to enable
>>>>> the bring-up of the PURWA-IOT-EVK evaluation board. Focus is on two
>>>>> key
>>>>> hardware components:
>>>>>
>>>>> PURWA-IOT-SOM — A compact System-on-Module integrating the SoC,
>>>>> GPIOs, and
>>>>> PMICs. Designed for modularity, it can pair with various carrier
>>>>> boards to
>>>>> support diverse use cases.
>>>>>
>>>>> PURWA-IOT-EVK — A carrier board tailored for IoT scenarios, providing
>>>>> essential peripherals such as UART, on-board PMICs, and USB
>>>>> components.
>>>>>
>>>>> Together, these components form a flexible and scalable platform.
>>>>> Initial
>>>>> functionality is achieved through proper device tree configuration
>>>>> and driver
>>>>> support.
>>>>>
>>>>> The PURWA-IOT-EVK/SOM shares most of its hardware design with
>>>>> HAMOA-IOT-EVK/SOM, differing primarily in the BOM. Consequently,
>>>>> the DTS files
>>>>> are largely similar. Both platforms belong to Qualcomm’s IQ-X
>>>>> family. For more
>>>>> details on the IQ-X series, see:
>>>>> https://www.qualcomm.com/internet-of-things/products/iq-x-series
>>>>>
>>>>> Hardware differences between HAMOA-IOT and PURWA-IOT:
>>>>> - Display — PURWA uses a different number of clocks and frequency
>>>>> compared to
>>>>> HAMOA.
>>>>> - GPU — PURWA integrates a different GPU.
>>>>> - USB0 — PURWA uses a PS8833 retimer, while HAMOA employs an
>>>>> FSUSB42 as the
>>>>> SBU switch.
>>>>>
>>>>> Features added and enabled:
>>>>> - UART
>>>>> - On-board regulators
>>>>> - Regulators on the SOM
>>>>> - PMIC GLINK
>>>>> - USB0 through USB6 and their PHYs
>>>>> - Embedded USB (eUSB) repeaters
>>>>> - USB Type-C mux
>>>>> - PCIe3, PCIe4, PCIe5, PCIe6a
>>>>> - Reserved memory regions
>>>>> - Pinctrl
>>>>> - NVMe
>>>>> - ADSP, CDSP
>>>>> - WLAN, Bluetooth (M.2 interface)
>>>>> - USB DisplayPort and eDP
>>>>> - Graphics
>>>>> - Audio
>>>>> - TPM
>>>>>
>>>>> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>>> ---
>>>>> Changes in v2:
>>>>> - Update the GPU firmware path.
>>>>> - Update the description in the cover letter.
>>>>> - Reorder the patches.
>>>>> - Use separate DTS files for Purwa and Hamoa.
>>>>> - Update base commit.
>>>>> - Link to v1: https://lore.kernel.org/all/20251222-purwa-
>>>>> v1-0-14ab9316e5ff@oss.qualcomm.com/
>>>>>
>>>>> Changes in v3:
>>>>> - Delete unused PMIC and thermal nodes.
>>>>> - Add WiFi node.
>>>>> - Add display backlight node.
>>>>> - Add connectors and VBUS regulators for USB3 and USB6.
>>>>> - Enable PCIe3 and PCIe5; add PCIe ports along with reset and wake-
>>>>> up GPIOs.
>>>>> - Link to v2: https://lore.kernel.org/r/20260109-purwa-v2-0-
>>>>> f39ee10684cb@oss.qualcomm.com
>>>>>
>>>>> Changes in v4:
>>>>> - Enable TPM.
>>>>> - Update the descriptions for video and the USB OF graph.
>>>>> - Link to v3: https://lore.kernel.org/all/20260113-purwa-
>>>>> v3-0-16eefacbdce9@oss.qualcomm.com/
>>>>>
>>>>> Changes in v5:
>>>>> - Reorder nodes in purwa-iot-evk.dts.
>>>>> - Update base commit.
>>>>> - The DT binding change that fixes the DT warning for pcie3_phy is
>>>>> located at: https://lore.kernel.org/linux-arm-msm/20260119-topic-
>>>>> purwa_phy_shutup_warning-v1-1-997a692b31c6@oss.qualcomm.com/T/#u
>>>>> - Link to v4: https://lore.kernel.org/r/20260116-purwa-
>>>>> v4-0-89b2adae9f09@oss.qualcomm.com
>>>>>
>>>>> ---
>>>>> Yijie Yang (4):
>>>>> dt-bindings: arm: qcom: Document PURWA-IOT-EVK board
>>>>> firmware: qcom: scm: Allow QSEECOM on PURWA-IOT-EVK
>>>>> arm64: dts: qcom: Add PURWA-IOT-SOM platform
>>>>> arm64: dts: qcom: Add base PURWA-IOT-EVK board
>>>>>
>>>>> Documentation/devicetree/bindings/arm/qcom.yaml | 6 +
>>>>> arch/arm64/boot/dts/qcom/Makefile | 1 +
>>>>> arch/arm64/boot/dts/qcom/purwa-iot-evk.dts | 1549 +++++++++
>>>>> ++++++++++++++
>>>>> arch/arm64/boot/dts/qcom/purwa-iot-som.dtsi | 685 ++++++++++
>>>>> drivers/firmware/qcom/qcom_scm.c | 1 +
>>>>> 5 files changed, 2242 insertions(+)
>>>>> ---
>>>>> base-commit: 6267b2da1b2d04847a1a8f441e138bc4a89435ee
>>>>> change-id: 20251113-purwa-907ec75b4959
>>>>>
>>>>> Best regards,
>>>>> --
>>>>> Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> My bot found DTB warnings on the .dts/.dtsi files added or changed in
>>>> this series.
>>>>
>>>> Some warnings may be existing warnings. Consider fixing existing
>>>> warnings before adding new features.
>>>>
>>>> Perhaps the warnings are fixed by another series. If that is the case,
>>>> please set the base commit and any dependencies for the series using
>>>> "b4".
>>>>
>>>> Ultimately, it is up to the platform maintainer whether these warnings
>>>> are acceptable or not.
>>>>
>>>> If you already ran DT checks and didn't see these error(s), then
>>>> make sure dt-schema is up to date:
>>>>
>>>> pip3 install dtschema --upgrade
>>>>
>>>>
>>>> This patch series was applied (using b4) to base:
>>>> Base: 6267b2da1b2d04847a1a8f441e138bc4a89435ee (use --merge-base
>>>> to override)
>>>>
>>>> If this is not the correct base, please add 'base-commit' tag
>>>> (or use b4 which does this automatically)
>>>>
>>>>
>>>> New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/
>>>> qcom/' for 20260202-purwa-v5-0-1f5a93578802@oss.qualcomm.com:
>>>>
>>>> arch/arm64/boot/dts/qcom/purwa-iot-evk.dtb: phy@1bd4000
>>>> (qcom,x1p42100-qmp-gen4x4-pcie-phy): 'qcom,4ln-config-sel' is a
>>>> required property
>>>> from schema $id: http://devicetree.org/schemas/phy/
>>>> qcom,sc8280xp-qmp-pcie-phy.yaml
>>>>
>>>
>>> I have already listed the fix in the cover letter:
>>> https://lore.kernel.org/linux-arm-msm/20260119-topic-
>>> purwa_phy_shutup_warning-v1-1-997a692b31c6@oss.qualcomm.com/T/#u
>>> It is not recommended to list it as a dependency in the latest version.
>>
>> You can use `b4 prep --edit-deps` to mark it as a dependency to be
>> picked up by the bot.
>
> Krzysztof mentioned in v4 that this is not a dependency and only needs
> to be mentioned in the changelog.
>
Gentle reminder. Do we need another version to address the dependency issue?
Thanks,
Jie
>
>>
>>>
>>>
>>>>
>>>>
>>>>
>>>
>>> --
>>> Best Regards,
>>> Yijie
>>>
>>
>
next prev parent reply other threads:[~2026-03-03 3:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 7:35 YijieYang
2026-02-02 7:35 ` [PATCH v5 1/4] dt-bindings: arm: qcom: Document PURWA-IOT-EVK board YijieYang
2026-02-02 7:35 ` [PATCH v5 2/4] firmware: qcom: scm: Allow QSEECOM on PURWA-IOT-EVK YijieYang
2026-02-02 15:25 ` Abel Vesa
2026-02-02 7:35 ` [PATCH v5 3/4] arm64: dts: qcom: Add PURWA-IOT-SOM platform YijieYang
2026-02-02 15:24 ` Abel Vesa
2026-02-02 7:35 ` [PATCH v5 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board YijieYang
2026-02-02 15:02 ` Konrad Dybcio
2026-02-02 15:24 ` Abel Vesa
2026-02-03 17:37 ` [PATCH v5 0/4] Initial patch set for PURWA-IOT-EVK Rob Herring
2026-02-04 1:42 ` Yijie Yang
2026-02-04 2:38 ` Dmitry Baryshkov
2026-02-04 2:52 ` Yijie Yang
2026-03-03 3:09 ` Jie Gan [this message]
2026-03-10 2:45 ` (subset) " Bjorn Andersson
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=9e933431-44da-40b6-85eb-9fa667a7c1fa@oss.qualcomm.com \
--to=jie.gan@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=yijie.yang@oss.qualcomm.com \
/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®