mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yijie Yang <yijie.yang@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v4 0/4] Initial patch set for PURWA-IOT-EVK
Date: Mon, 19 Jan 2026 14:54:04 +0800	[thread overview]
Message-ID: <e2dfb857-1fd1-4d29-b04b-6dec0b7563d5@oss.qualcomm.com> (raw)
In-Reply-To: <b3p5yhstng6nbrrdavx67vlv62hqqlnms7742txbimpeswqklv@eomkmkkearwp>



On 1/19/2026 2:34 PM, Dmitry Baryshkov wrote:
> On Mon, Jan 19, 2026 at 10:39:04AM +0800, Yijie Yang wrote:
>>
>>
>> On 1/16/2026 7:31 PM, Dmitry Baryshkov wrote:
>>> On Fri, Jan 16, 2026 at 06:41:26PM +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 v4:
>>>> - EDITME: describe what is new in this series revision.
>>>> - EDITME: use bulletpoints and terse descriptions.
>>>
>>> Oh no. B4 probably even warned you about not sending it out.
>>>
>>>   From this changelog I can assume that nothing has changed. Is it
>>> correct?
>>
>> This section was generated automatically by b4 and was not reviewed
>> carefully. The actual list of changes is in the section below.
> 
> But why????? Why do you ignore what was done for you and write it on
> your own, reversing the order, etc? And even if you decided to ignore it
> for any reason, why didn't you delete it?

The confusion was caused by mixing b4 and git format-patch to handle 
fine‑grained patch formatting. The Git configuration Konrad suggested 
did not work for me. I ran b4 prep --manual-reroll <msg-id> to allow b4 
to track the upstream thread, which caused this section to be generated 
automatically. I did not notice this and mistakenly re‑wrote it myself.

> 
>>
>>>
>>>> - Link to v3: https://lore.kernel.org/r/20260113-purwa-v3-0-16eefacbdce9@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/
>>
>> Here.
>>
>>>>
>>>> ---
>>>> 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: 377054868ffa544991cc491ecc4016589fc58565
>>>> change-id: 20251113-purwa-907ec75b4959
>>>>
>>>> Best regards,
>>>> --
>>>> Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>>
>>>
>>
>> -- 
>> Best Regards,
>> Yijie
>>
> 

-- 
Best Regards,
Yijie


  reply	other threads:[~2026-01-19  6:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 10:41 YijieYang
2026-01-16 10:41 ` [PATCH v4 1/4] dt-bindings: arm: qcom: Document PURWA-IOT-EVK board YijieYang
2026-01-16 10:41 ` [PATCH v4 2/4] firmware: qcom: scm: Allow QSEECOM on PURWA-IOT-EVK YijieYang
2026-01-16 10:41 ` [PATCH v4 3/4] arm64: dts: qcom: Add PURWA-IOT-SOM platform YijieYang
2026-01-20 12:44   ` Konrad Dybcio
2026-01-16 10:41 ` [PATCH v4 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board YijieYang
2026-01-16 16:19   ` Krzysztof Kozlowski
2026-01-19  3:13     ` Yijie Yang
2026-01-19  6:33       ` Dmitry Baryshkov
2026-01-19  7:10         ` Yijie Yang
2026-01-19  8:48         ` Yijie Yang
2026-01-19  9:46           ` Dmitry Baryshkov
2026-01-19 10:42             ` Yijie Yang
2026-01-19 13:31             ` Konrad Dybcio
2026-01-20  6:47               ` Yijie Yang
2026-01-19  7:05       ` Krzysztof Kozlowski
2026-01-20  6:49         ` Yijie Yang
2026-01-20  7:17           ` Krzysztof Kozlowski
2026-01-20  7:55             ` Yijie Yang
2026-01-19 13:53   ` Konrad Dybcio
2026-01-20  7:01     ` Yijie Yang
2026-01-16 11:31 ` [PATCH v4 0/4] Initial patch set for PURWA-IOT-EVK Dmitry Baryshkov
2026-01-19  2:39   ` Yijie Yang
2026-01-19  6:34     ` Dmitry Baryshkov
2026-01-19  6:54       ` Yijie Yang [this message]
2026-01-19 13:35         ` Konrad Dybcio
2026-01-19 13:51           ` Krzysztof Kozlowski
2026-01-19 13:52             ` Konrad Dybcio
2026-01-20  7:14               ` Yijie Yang
2026-01-16 15:40 ` Rob Herring

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=e2dfb857-1fd1-4d29-b04b-6dec0b7563d5@oss.qualcomm.com \
    --to=yijie.yang@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@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 \
    /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®