[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAO9ioeUTPopTg+S-6uASXa=L4DQaVVEJ_CYRGzKbJR3MkcZMFQ@mail.gmail.com>
Date: Mon, 12 Jan 2026 08:01:24 +0200
From: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
To: Yijie Yang <yijie.yang@....qualcomm.com>
Cc: Konrad Dybcio <konrad.dybcio@....qualcomm.com>, andersson@...nel.org,
konradybcio@...nel.org, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
krzysztof.kozlowski@....qualcomm.com
Subject: Re: [PATCH v2 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board
On Mon, 12 Jan 2026 at 07:51, Yijie Yang <yijie.yang@....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@....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?
--
With best wishes
Dmitry
Powered by blists - more mailing lists