[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1035ed36-8659-4fc9-9a4b-aa6bd2c3a286@oss.qualcomm.com>
Date: Wed, 4 Feb 2026 10:52:27 +0800
From: Yijie Yang <yijie.yang@....qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
Cc: Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@....qualcomm.com>,
andersson@...nel.org, krzk+dt@...nel.org, konradybcio@...nel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, conor+dt@...nel.org,
Konrad Dybcio <konrad.dybcio@....qualcomm.com>
Subject: Re: [PATCH v5 0/4] Initial patch set for PURWA-IOT-EVK
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@....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@....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@....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@....qualcomm.com:
>>>
>>> arch/arm64/boot/dts/qcom/purwa-iot-evk.dtb: phy@...4000 (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.
>
>>
>>
>>>
>>>
>>>
>>
>> --
>> Best Regards,
>> Yijie
>>
>
--
Best Regards,
Yijie
Powered by blists - more mailing lists