From: Vinod Koul <vkoul@kernel.org>
To: neil.armstrong@linaro.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, mani@kernel.org, alim.akhtar@samsung.com,
bvanassche@acm.org, andersson@kernel.org,
dmitry.baryshkov@oss.qualcomm.com, abel.vesa@oss.qualcomm.com,
luca.weiss@fairphone.com, palash.kambar@oss.qualcomm.com
Cc: linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, nitin.rawat@oss.qualcomm.com
Subject: Re: [PATCH v3 0/3] Add Hawi UFS PHY and Controller support
Date: Fri, 07 Aug 2026 18:03:32 +0530 [thread overview]
Message-ID: <178610601225.740291.16313821217075665373.b4-ty@kernel.org> (raw)
In-Reply-To: <20260526090956.2340262-1-palash.kambar@oss.qualcomm.com>
On Tue, 26 May 2026 14:39:53 +0530, palash.kambar@oss.qualcomm.com wrote:
> This series introduces devicetree binding documentation and PHY
> initialization support required to enable UFS on this platform.
>
> 1. Devicetree binding documentation for the QMP UFS PHY
> used on Qualcomm Hawi.
> 2. Devicetree binding documentation for the UFS controller
> instance present on the Hawi platform.
> 3. Initialization sequence tables and configuration required
> for the QMP UFS PHY on Hawi SoC.
>
> [...]
Applied, thanks!
[1/3] dt-bindings: phy: qcom,sc8280xp-qmp-ufs-phy: Add Hawi UFS PHY compatible
commit: 24d886d9344c7973e202a7f275ff8280b742446c
[2/3] scsi: ufs: qcom: dt-bindings: Document the Hawi UFS controller
(no commit info)
[3/3] phy: qcom-qmp-ufs: Add UFS PHY support on Hawi
commit: 2f7b4bc47b1e22c3e510ff6e25985edbe9cd9f97
Best regards,
--
~Vinod
prev parent reply other threads:[~2026-08-07 12:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 9:09 [PATCH v3 0/3] Add Hawi UFS PHY and Controller support palash.kambar
2026-05-26 9:09 ` [PATCH v3 1/3] dt-bindings: phy: qcom,sc8280xp-qmp-ufs-phy: Add Hawi UFS PHY compatible palash.kambar
2026-05-31 12:33 ` Krzysztof Kozlowski
2026-06-04 16:21 ` Palash Kambar
2026-06-04 16:54 ` Krzysztof Kozlowski
2026-05-26 9:09 ` [PATCH v3 2/3] scsi: ufs: qcom: dt-bindings: Document the Hawi UFS controller palash.kambar
2026-05-26 9:37 ` sashiko-bot
2026-05-31 12:34 ` Krzysztof Kozlowski
2026-05-26 9:09 ` [PATCH v3 3/3] phy: qcom-qmp-ufs: Add UFS PHY support on Hawi palash.kambar
2026-05-26 10:02 ` sashiko-bot
2026-06-08 15:15 ` Palash Kambar
2026-06-08 18:37 ` Dmitry Baryshkov
2026-06-11 15:29 ` Vinod Koul
2026-06-15 5:51 ` Palash Kambar
2026-06-16 2:26 ` (subset) [PATCH v3 0/3] Add Hawi UFS PHY and Controller support Martin K. Petersen
2026-08-07 12:33 ` Vinod Koul [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=178610601225.740291.16313821217075665373.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=abel.vesa@oss.qualcomm.com \
--cc=alim.akhtar@samsung.com \
--cc=andersson@kernel.org \
--cc=bvanassche@acm.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=mani@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=nitin.rawat@oss.qualcomm.com \
--cc=palash.kambar@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