public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pradeep P V K <pradeep.pragallapati@oss.qualcomm.com>
Cc: vkoul@kernel.org, neil.armstrong@linaro.org, robh@kernel.org,
	 krzk+dt@kernel.org, conor+dt@kernel.org,
	martin.petersen@oracle.com,  andersson@kernel.org,
	konradybcio@kernel.org, taniya.das@oss.qualcomm.com,
	 dmitry.baryshkov@oss.qualcomm.com,
	manivannan.sadhasivam@oss.qualcomm.com,
	 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 1/4] dt-bindings: phy: qcom,sc8280xp-qmp-ufs-phy: Add QMP UFS PHY compatible
Date: Tue, 6 Jan 2026 08:32:52 +0100	[thread overview]
Message-ID: <20260106-huge-radical-bear-aeb732@quoll> (raw)
In-Reply-To: <20260105144643.669344-2-pradeep.pragallapati@oss.qualcomm.com>

On Mon, Jan 05, 2026 at 08:16:40PM +0530, Pradeep P V K wrote:
> Document QMP UFS PHY compatible for x1e80100 SoC. Use SM8550 as a
> fallback since x1e80100 is fully compatible with it.
> 
> Signed-off-by: Pradeep P V K <pradeep.pragallapati@oss.qualcomm.com>
> ---
>  .../devicetree/bindings/phy/qcom,sc8280xp-qmp-ufs-phy.yaml    | 4 ++++
>  1 file changed, 4 insertions(+)

Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>

Best regards,
Krzysztof


  reply	other threads:[~2026-01-06  7:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-05 14:46 [PATCH V3 0/4] Add UFS support for x1e80100 SoC Pradeep P V K
2026-01-05 14:46 ` [PATCH V3 1/4] dt-bindings: phy: qcom,sc8280xp-qmp-ufs-phy: Add QMP UFS PHY compatible Pradeep P V K
2026-01-06  7:32   ` Krzysztof Kozlowski [this message]
2026-01-05 14:46 ` [PATCH V3 2/4] dt-bindings: ufs: qcom,sc7180-ufshc: Add UFSHC compatible for x1e80100 Pradeep P V K
2026-01-06  7:34   ` Krzysztof Kozlowski
2026-01-06  8:03   ` Manivannan Sadhasivam
2026-01-05 14:46 ` [PATCH V3 3/4] arm64: dts: qcom: hamoa: Add UFS nodes for x1e80100 SoC Pradeep P V K
2026-01-06  8:06   ` Manivannan Sadhasivam
2026-01-06 13:00     ` Pradeep Pragallapati
2026-01-06 13:40       ` Krzysztof Kozlowski
2026-01-06 13:51         ` Pradeep Pragallapati
2026-01-06 13:52       ` Manivannan Sadhasivam
2026-01-06 14:11         ` Pradeep Pragallapati
2026-01-05 14:46 ` [PATCH V3 4/4] arm64: dts: qcom: hamoa-iot-evk: Enable UFS Pradeep P V K
2026-01-05 22:20 ` [PATCH V3 0/4] Add UFS support for x1e80100 SoC Dmitry Baryshkov
2026-01-06 13:03   ` Pradeep Pragallapati
2026-01-06 16:41     ` Bjorn Andersson
2026-01-07  5:51       ` Pradeep Pragallapati

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=20260106-huge-radical-bear-aeb732@quoll \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --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=manivannan.sadhasivam@oss.qualcomm.com \
    --cc=martin.petersen@oracle.com \
    --cc=neil.armstrong@linaro.org \
    --cc=nitin.rawat@oss.qualcomm.com \
    --cc=pradeep.pragallapati@oss.qualcomm.com \
    --cc=robh@kernel.org \
    --cc=taniya.das@oss.qualcomm.com \
    --cc=vkoul@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