devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Robert Marko <robimarko@gmail.com>,
	Das Srinagesh <quic_gurus@quicinc.com>
Cc: Bhupesh Sharma <bhupesh.sharma@linaro.org>,
	Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
	Marijn Suijten <marijn.suijten@somainline.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 8/9] arm64: dts: qcom: qcm2290: Add WCN3990 Wi-Fi node
Date: Tue, 4 Apr 2023 11:55:50 +0200	[thread overview]
Message-ID: <a295af57-f8d1-35c2-77e8-7d29d043e47e@linaro.org> (raw)
In-Reply-To: <4816461e-38b7-ba79-dd64-859fa0ee808e@linaro.org>



On 4.04.2023 08:08, Krzysztof Kozlowski wrote:
> On 03/04/2023 19:36, Konrad Dybcio wrote:
>> Add a node for the ATH10K SNoC-managed WCN3990 Wi-Fi.
>>
>> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
>> ---
> 
> We had these talks a lot... All these 3-8 patches should be two patches:
> 1. SoC DTSI
> 2. Board DTS.
> 
> Splitting superficially patchset on initial submission does not make
> sense. If you sent it in separate patchsets during development - release
> early, release often - then of course it would be fine. But hoarding
> patches till everything is ready is not the approach we want (and we
> made it clear that SM8550 should be the last such platform)
That wasn't my intention.

This patchset is "feature-rich", as it piggybacks off of Shawn and Loic
having submitted the driver parts long long ago and SM6115 being quite
well-supported (and almost identical to the QCM). Patches 4-8 were not
"held hostage" waiting for full fat platform enablement, but were
essentially "copy-paste, adjust, verify" and that does not require a
lot of manpower or time.. I split them to ease the review (~850 LoC @
PATCH 3, ~1900 LoC @ PATCH 8).

In any case, the fact that there's so many features submitted with
the initial posting is not related to me holding onto them on
purpose, they were created together, probably within 20 minutes of
each other.. This should have been posted a long time ago with even
more things (like regulators), but there's been some communication
issues with Qualcomm..

LMK how you want me to proceed with this.

Konrad

and does not
> justify later fake-splitting.
> 
> Best regards,
> Krzysztof
> 

  reply	other threads:[~2023-04-04  9:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 17:35 [PATCH 0/9] RB1 + QCM2290 support Konrad Dybcio
2023-04-03 17:35 ` [PATCH 1/9] dt-bindings: firmware: document Qualcomm QCM2290 SCM Konrad Dybcio
2023-04-04  6:02   ` Krzysztof Kozlowski
2023-04-03 17:36 ` [PATCH 2/9] dt-bindings: arm: qcom: Add QRB2210/QCM2290 and RB1 board Konrad Dybcio
2023-04-04  6:03   ` Krzysztof Kozlowski
2023-04-03 17:36 ` [PATCH 3/9] arm64: dts: qcom: Add initial QCM2290, PM2250 & RB1 device trees Konrad Dybcio
2023-04-04  6:06   ` Krzysztof Kozlowski
2023-04-04  9:47     ` Konrad Dybcio
2023-04-04 10:02       ` Krzysztof Kozlowski
2023-04-03 17:36 ` [PATCH 4/9] arm64: dts: qcom: qcm2290: Add most QUPs Konrad Dybcio
2023-04-03 17:36 ` [PATCH 5/9] arm64: dts: qcom: qcm2290: Add thermal zones Konrad Dybcio
2023-04-03 17:36 ` [PATCH 6/9] arm64: dts: qcom: qcm2290: Add SMP2P Konrad Dybcio
2023-04-03 17:36 ` [PATCH 7/9] arm64: dts: qcom: qcm2290: Add ADSP & modem Konrad Dybcio
2023-04-03 17:36 ` [PATCH 8/9] arm64: dts: qcom: qcm2290: Add WCN3990 Wi-Fi node Konrad Dybcio
2023-04-04  6:08   ` Krzysztof Kozlowski
2023-04-04  9:55     ` Konrad Dybcio [this message]
2023-04-04 10:04       ` Krzysztof Kozlowski
2023-04-04 10:05         ` Krzysztof Kozlowski
2023-04-03 17:36 ` [PATCH 9/9] arm64: dts: qcom: qrb2210-rb1: Enable RESIN Volume Down Konrad Dybcio

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=a295af57-f8d1-35c2-77e8-7d29d043e47e@linaro.org \
    --to=konrad.dybcio@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bhupesh.sharma@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=quic_gurus@quicinc.com \
    --cc=robh+dt@kernel.org \
    --cc=robimarko@gmail.com \
    --cc=vladimir.zapolskiy@linaro.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;
as well as URLs for NNTP newsgroup(s).