[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1fd4b0db-f9c1-44db-9aec-45f3aa269e19@quicinc.com>
Date: Mon, 7 Oct 2024 11:36:52 +0530
From: Viken Dadhaniya <quic_vdadhani@...cinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
CC: <andersson@...nel.org>, <konradybcio@...nel.org>, <robh@...nel.org>,
<krzk+dt@...nel.org>, <conor+dt@...nel.org>,
<linux-arm-msm@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <quic_msavaliy@...cinc.com>,
<quic_anupkulk@...cinc.com>
Subject: Re: [RESEND PATCH v2] arm64: dts: qcom: sa8775p: Populate additional
UART DT nodes
On 10/7/2024 2:26 AM, Dmitry Baryshkov wrote:
> On Mon, Sep 30, 2024 at 02:25:33PM GMT, Viken Dadhaniya wrote:
>> Currently, UART configuration is populated for few
>> SEs(Serial engine) only in sa8775p DTSI file.
>>
>> Populate UART configurations of remaining SEs for sa8775p soc.
>
> I think this is a long standing tradition of adding UART configuration
> only to those nodes that actually will be used for UART on one or
> another device. Is this the case for all these UART nodes?
Recently, we have begun adding all possible UART configurations, similar
to what we’ve done with I2C and SPI.
We will continue this approach for future targets.
>
>>
>> Co-developed-by: Mukesh Kumar Savaliya <quic_msavaliy@...cinc.com>
>> Signed-off-by: Mukesh Kumar Savaliya <quic_msavaliy@...cinc.com>
>> Signed-off-by: Viken Dadhaniya <quic_vdadhani@...cinc.com>
>> ---
>> v1 -> v2:
>>
>> - Modifed commit log as requested by Krzysztof.
>> - Added co-developed-by tag.
>>
>> v1 Link: https://lore.kernel.org/linux-arm-msm/98e7dc28-4413-4247-bad1-98b529f6d62d@kernel.org/T/
>> ---
>> ---
>> arch/arm64/boot/dts/qcom/sa8775p.dtsi | 231 ++++++++++++++++++++++++++
>> 1 file changed, 231 insertions(+)
>>
>
Powered by blists - more mailing lists