mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
To: Bjorn Andersson <andersson@kernel.org>
Cc: Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Abel Vesa <abel.vesa@oss.qualcomm.com>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>,
	Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>,
	Rakesh Kota <rakesh.kota@oss.qualcomm.com>
Subject: Re: [PATCH v9 0/3] Add DT Support for USB on Shikra
Date: Mon, 5 Oct 2026 15:39:38 +0530	[thread overview]
Message-ID: <c42c8f3e-fb8b-48fb-bbc6-5b6532ea9d72@oss.qualcomm.com> (raw)
In-Reply-To: <ar50erRON6cMF9Oz@zenbook>

On 10/1/2026 8:32 PM, Bjorn Andersson wrote:
> On Sat, Sep 12, 2026 at 08:17:00PM +0530, Komal Bajaj wrote:
>> Shikra has two USB controllers. Adding both USB controllers support
>> in device mode in this series. Also squashing Type-C enablement on
>> CQS/CQM platforms [1] into base USB enablement changes on these
>> platforms [2] based on feedback to squash related subsystem changes.
>>
>> While at it, also sorting subnodes under soc@0 for consistency.
>>
> When you repackage scattered patches like this into new series patchwork
> is often unable to determine that these patches supersed the previous
> version.
>
> The result is that for each patch I now have (at least) 2 similar and
> conflicting patches in my queue. As the patches was altered to the point
> that patchwork doesn't detect it and nobody told me that the previous
> versions are no longer to be considered, we now manually have to spend
> time to detangle this.

I understand your concern, and thank you for pointing this out.
By repackaging patches into a new series, I should have made it explicit 
that the previous submissions were superseded. I will keep this in mid 
for future submissions.

>
> In other words, this series doesn't apply - please determine if there
> are any remaining parts of these changes that isn't accounted for in
> linux-next and resubmit those.

I see that one of the patches has already been merged into linux-next. I 
will review the remaining changes and resubmit only those that are not 
yet applied.

Thanks
Komal

>
> Regards,
> Bjorn
>
>> [1]: https://lore.kernel.org/all/20260818-pm4125_typec_changes-v1-1-6e6ede93db19@oss.qualcomm.com/
>> [2]: https://lore.kernel.org/all/20260811-usb-shikra-v7-v7-2-753e928f37ae@oss.qualcomm.com/
>>
>> Changes in v9:
>> - Move usb_2_hsphy above usb_qmpphy to maintain alphabetical ordering
>>
>> Link to v8:
>> https://lore.kernel.org/r/20260911-usb-shikra-v7-v8-0-851ee4bc0eec@oss.qualcomm.com
>>
>> Changes in v8:
>>   - Rebase on top of latest linux-next branch
>>   - Sort /soc@0 subnodes in ascending order of unit address
>>   - Squashed with Type-C support change
>>   - Individual patches were previously reviewed by Abel, Dmitry, Konrad and
>>     Mani; however, those reviews do not apply to the squashed commit and
>>     are therefore being dropped
>>
>>   Link to v7:
>>   https://lore.kernel.org/all/20260811-usb-shikra-v7-v7-0-753e928f37ae@oss.qualcomm.com/
>>
>> Changes in v7:
>> - Rebased on top of latest for-next branch
>> - Added Mani's tag from cover letter to both the induvidual patches.
>>
>> Link to v6:
>> https://lore.kernel.org/all/20260729-shikra-usb-v6-dt-v6-0-72ffb4796a08@oss.qualcomm.com/
>>
>> Changes in v6:
>> - Moved dr_mode property to shikra-evk.dtsi
>> - Merged platform specific changes into one patch
>>
>> Link to v5:
>> https://lore.kernel.org/all/20260723-usb-shikra-dt-v4-v5-0-5b69d9eb0888@oss.qualcomm.com/
>>
>> Changes in v5:
>> - Added interconnects and sorted nodes alphanumerically - Dmitry
>> - Updated commit text mentioning that device mode is being enabled
>>    since role switching changes are not yet present.
>>
>> Link to v4:
>> https://patch.msgid.link/20260721-usb-shikra-dt-v4-v4-0-2e7a092d7f27@oss.qualcomm.com
>>
>> Changes in v4:
>> - Enable both controllers in CQS/CQM platform
>> - Fixed iface clock in usb_2 node
>> - Skipped adding RB tags obtained from Konrad since on CQM/CQS, second
>>    controller also is enabled in v4. Also specified dr_mode as peripheral
>>    for first controller.
>>
>> Link to v3:
>> https://lore.kernel.org/all/20260716-shikra-usb-dt-v3-v3-0-13f73a0571bb@oss.qualcomm.com/
>>
>> Changes in v3:
>> - USB changes were sent as part of consolidated submission in v2, but
>>    they were later dropped since bindings had to be updated.
>> - Remove double vote on USB3_PRIM_CLKREF and also removed xo clock.
>> - Uses &mpm as interrupt reference (sashiko bot)
>>
>> Link to v2:
>> https://lore.kernel.org/all/20260519-shikra-dt-v2-0-c01b90fb4395@oss.qualcomm.com/
>>
>> Changes in v2:
>> - Moved to using mpm interrupt handler for ss phy irq (sashiko bot)
>>
>> Link to v1:
>> https://lore.kernel.org/all/20260512-shikra-dt-v1-0-716438330dd0@oss.qualcomm.com/
>>
>> Signed-off-by: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
>> Signed-off-by: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
>> ---
>> Komal Bajaj (1):
>>        arm64: dts: qcom: shikra: sort /soc@0 nodes by unit address
>>
>> Krishna Kurapati (2):
>>        arm64: dts: qcom: Add support for usb nodes on Shikra
>>        arm64: dts: qcom: shikra: Enable USB controllers and primary Type-C support
>>
>>   arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts  |  43 +++
>>   arch/arm64/boot/dts/qcom/shikra-cqm-som.dtsi |  41 +++
>>   arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts  |  43 +++
>>   arch/arm64/boot/dts/qcom/shikra-evk.dtsi     |  12 +
>>   arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts  |  23 ++
>>   arch/arm64/boot/dts/qcom/shikra.dtsi         | 515 +++++++++++++++++++--------
>>   6 files changed, 536 insertions(+), 141 deletions(-)
>> ---
>> base-commit: f2bfbc3554ca6919484030729424b9dee2942d24
>> change-id: 20260811-usb-shikra-v7-2dc0d3afc3d4
>>
>> Best regards,
>> -- 
>> Komal Bajaj <komal.bajaj@oss.qualcomm.com>
>>


      reply	other threads:[~2026-10-05 10:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-12 14:47 Komal Bajaj
2026-09-12 14:47 ` [PATCH v9 1/3] arm64: dts: qcom: shikra: sort /soc@0 nodes by unit address Komal Bajaj
2026-09-14 10:57   ` Konrad Dybcio
2026-09-12 14:47 ` [PATCH v9 2/3] arm64: dts: qcom: Add support for usb nodes on Shikra Komal Bajaj
2026-09-12 14:47 ` [PATCH v9 3/3] arm64: dts: qcom: shikra: Enable USB controllers and primary Type-C support Komal Bajaj
2026-10-01 15:02 ` [PATCH v9 0/3] Add DT Support for USB on Shikra Bjorn Andersson
2026-10-05 10:09   ` Komal Bajaj [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=c42c8f3e-fb8b-48fb-bbc6-5b6532ea9d72@oss.qualcomm.com \
    --to=komal.bajaj@oss.qualcomm.com \
    --cc=abel.vesa@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krishna.kurapati@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@oss.qualcomm.com \
    --cc=rakesh.kota@oss.qualcomm.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®