From: Viken Dadhaniya <quic_vdadhani@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, <andersson@kernel.org>,
<konrad.dybcio@linaro.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <linux-arm-msm@vger.kernel.org>,
<conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <quic_msavaliy@quicinc.com>, <quic_anupkulk@quicinc.com>
Subject: Re: [V1 RESEND] arm64: dts: qcom: sa8775p: Add UART node
Date: Wed, 11 Sep 2024 20:43:01 +0530 [thread overview]
Message-ID: <e95b3c9c-12f1-4dc0-8bc1-db92f4b2338f@quicinc.com> (raw)
In-Reply-To: <98e7dc28-4413-4247-bad1-98b529f6d62d@kernel.org>
Hi Krzysztof, Thanks for review.
On 9/6/2024 5:55 PM, Krzysztof Kozlowski wrote:
> On 27/08/2024 10:32, Viken Dadhaniya wrote:
>> Add missing UART configuration for sa8775.
>>
>> Signed-off-by: Viken Dadhaniya <quic_vdadhani@quicinc.com>
>> ---
>> arch/arm64/boot/dts/qcom/sa8775p.dtsi | 231 ++++++++++++++++++++++++++
>> 1 file changed, 231 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/sa8775p.dtsi b/arch/arm64/boot/dts/qcom/sa8775p.dtsi
>> index e8dbc8d820a6..0c95a23aecec 100644
>> --- a/arch/arm64/boot/dts/qcom/sa8775p.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/sa8775p.dtsi
>> @@ -1,6 +1,7 @@
>
>
> Please don't grow the file. At least not with above explanation. There
> is no sa8775p according to what I have been just told.
>
> We achieved consensus allowing sa8775p to stay, but now Qualcomm changes
> point of view and insists on new approach of dropping sa8775p. Therefore
> this change does not make much sense in the new approach.
>
Qualcomm has decided to keep current SA8775p and don’t have plan to drop
SA8775p support. Hope you are in consensus and help with further review.
Updated commit log and Posted v2.
> Best regards,
> Krzysztof
>
prev parent reply other threads:[~2024-09-11 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 8:32 Viken Dadhaniya
2024-09-06 12:25 ` Krzysztof Kozlowski
2024-09-11 15:13 ` Viken Dadhaniya [this message]
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=e95b3c9c-12f1-4dc0-8bc1-db92f4b2338f@quicinc.com \
--to=quic_vdadhani@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_anupkulk@quicinc.com \
--cc=quic_msavaliy@quicinc.com \
--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®