Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Yijie Yang <yijie.yang@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@oss.qualcomm.com
Subject: Re: [PATCH v2 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board
Date: Mon, 12 Jan 2026 11:54:37 +0100	[thread overview]
Message-ID: <36d3ead4-69c3-4bb5-b29f-25e9b7182618@oss.qualcomm.com> (raw)
In-Reply-To: <CAO9ioeUTPopTg+S-6uASXa=L4DQaVVEJ_CYRGzKbJR3MkcZMFQ@mail.gmail.com>

On 1/12/26 7:01 AM, Dmitry Baryshkov wrote:
> On Mon, 12 Jan 2026 at 07:51, Yijie Yang <yijie.yang@oss.qualcomm.com> wrote:
>>
>>
>>
>> On 1/12/2026 1:00 PM, Dmitry Baryshkov wrote:
>>> On Mon, Jan 12, 2026 at 11:12:09AM +0800, Yijie Yang wrote:
>>>>
>>>>
>>>> On 1/9/2026 7:29 PM, Konrad Dybcio wrote:
>>>>> On 1/9/26 8:59 AM, YijieYang wrote:
>>>>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>>>>
>>>>>> The PURWA-IOT-EVK is an evaluation platform for IoT products, composed of
>>>>>> the Purwa IoT SoM and a carrier board. Together, they form a complete
>>>>>> embedded system capable of booting to UART.
>>>>>
>>>>> [...]
>>>>>
>>>>>> -  backlight: backlight {
>>>>>> -          compatible = "pwm-backlight";
>>>>>> -          pwms = <&pmk8550_pwm 0 5000000>;
>>>>>> -          enable-gpios = <&pmc8380_3_gpios 4 GPIO_ACTIVE_HIGH>;
>>>>>> -          power-supply = <&vreg_edp_bl>;
>>>>>> -
>>>>>> -          pinctrl-0 = <&edp_bl_en>, <&edp_bl_pwm>;
>>>>>> -          pinctrl-names = "default";
>>>>>> -  };
>>>>>
>>>>> Is the backlight infra different on the Purwa IoT EVK?
>>>>
>>>> As you can see, this Purwa file was copied from the latest
>>>> hamoa-iot-evk.dts. However, not all nodes have been verified on Purwa.
>>>> Therefore, I need to retain only the functions that work correctly and keep
>>>> them aligned with the nodes from my initial version. The deleted nodes will
>>>> be updated later by the respective authors from different technical areas.
>>>
>>> Please, only delete nodes which are not present on the Purwa IoT EVK.
>>
>> This isn’t a deletion—it’s just not ready yet. Why do we need to include
>> all the nodes like a mature Hamoa platform in the initial push?
> 
> Purwa seems to be mature enough. What exactly can't be enabled at this moment?

Right, I'm in the same camp. Since you already have the board at your
disposal (because I trust you tested this patchset on hardware), why
not spend the extra 5-10 minutes verifying that e.g. the display lights
up and you can control its brightness?

Konrad

  reply	other threads:[~2026-01-12 10:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09  7:59 [PATCH v2 0/4] Initial patch set for PURWA-IOT-EVK YijieYang
2026-01-09  7:59 ` [PATCH v2 1/4] dt-bindings: arm: qcom: Document PURWA-IOT-EVK board YijieYang
2026-01-09  7:59 ` [PATCH v2 2/4] firmware: qcom: scm: Allow QSEECOM on PURWA-IOT-EVK YijieYang
2026-01-09 12:48   ` Dmitry Baryshkov
2026-01-09  7:59 ` [PATCH v2 3/4] arm64: dts: qcom: Add PURWA-IOT-SOM platform YijieYang
2026-01-09 12:10   ` Dmitry Baryshkov
2026-01-12  3:02     ` Yijie Yang
2026-01-09  7:59 ` [PATCH v2 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board YijieYang
2026-01-09 11:29   ` Konrad Dybcio
2026-01-12  3:12     ` Yijie Yang
2026-01-12  5:00       ` Dmitry Baryshkov
2026-01-12  5:51         ` Yijie Yang
2026-01-12  6:01           ` Dmitry Baryshkov
2026-01-12 10:54             ` Konrad Dybcio [this message]
2026-01-13  1:45             ` Yijie Yang
2026-01-12  7:14           ` Krzysztof Kozlowski
2026-01-09  8:06 ` [PATCH v2 0/4] Initial patch set for PURWA-IOT-EVK Krzysztof Kozlowski
2026-01-09  8:26   ` Yijie Yang
2026-01-09  9:04     ` Krzysztof Kozlowski
2026-01-09  9:28     ` Konrad Dybcio
2026-01-12  3:13       ` Yijie Yang

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=36d3ead4-69c3-4bb5-b29f-25e9b7182618@oss.qualcomm.com \
    --to=konrad.dybcio@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 \
    --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