From: Shawn Guo <shengchao.guo@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
Manivannan Sadhasivam <mani@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Dmitry Baryshkov <lumag@kernel.org>,
Kumar Dwivedi <ram.dwivedi@oss.qualcomm.com>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>,
linux-scsi@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] scsi: ufs: dt-bindings: Add compatible for SA8797P UFS Host Controller
Date: Tue, 21 Apr 2026 22:28:42 +0800 [thread overview]
Message-ID: <aeeJmk3mGn7-SSYS@QCOM-aGQu4IUr3Y> (raw)
In-Reply-To: <20260421-tiger-of-pastoral-potency-d4502e@quoll>
On Tue, Apr 21, 2026 at 12:37:31PM +0200, Krzysztof Kozlowski wrote:
> On Mon, Apr 20, 2026 at 06:04:16PM +0800, Shawn Guo wrote:
> > From: Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>
> >
> > SA8797P is the automotive variant of the Nord SoC. Like SA8255P, its
> > platform firmware implements an SCMI server that manages UFS resources
> > such as the PHY, clocks, regulators and resets via the SCMI power
> > protocol. As a result, the OS-visible DT only describes the controller's
> > MMIO, interrupt, IOMMU and power-domain interfaces, making SA8255P the
> > appropriate fallback compatible.
> >
> > Signed-off-by: Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>
> > Signed-off-by: Shawn Guo <shengchao.guo@oss.qualcomm.com>
> > ---
> > .../devicetree/bindings/ufs/qcom,sa8255p-ufshc.yaml | 7 +++++--
> > 1 file changed, 5 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/ufs/qcom,sa8255p-ufshc.yaml b/Documentation/devicetree/bindings/ufs/qcom,sa8255p-ufshc.yaml
> > index 75fae9f1eba7..f2f3bfc73216 100644
> > --- a/Documentation/devicetree/bindings/ufs/qcom,sa8255p-ufshc.yaml
> > +++ b/Documentation/devicetree/bindings/ufs/qcom,sa8255p-ufshc.yaml
> > @@ -11,8 +11,11 @@ maintainers:
> >
> > properties:
> > compatible:
> > - const: qcom,sa8255p-ufshc
> > -
>
> Do not remove the blank line separating from the next property.
You are right! I dropped the newline accidentally.
Shawn
next prev parent reply other threads:[~2026-04-21 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 10:04 [PATCH 0/2] scsi: ufs: dt-bindings: Add compatibles for Nord UFS controller Shawn Guo
2026-04-20 10:04 ` [PATCH 1/2] scsi: ufs: dt-bindings: Add compatible for Nord UFS Host Controller Shawn Guo
2026-04-21 10:43 ` Krzysztof Kozlowski
2026-04-21 10:57 ` Manivannan Sadhasivam
2026-04-20 10:04 ` [PATCH 2/2] scsi: ufs: dt-bindings: Add compatible for SA8797P " Shawn Guo
2026-04-21 10:37 ` Krzysztof Kozlowski
2026-04-21 14:28 ` Shawn Guo [this message]
2026-04-21 10:56 ` Manivannan Sadhasivam
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=aeeJmk3mGn7-SSYS@QCOM-aGQu4IUr3Y \
--to=shengchao.guo@oss.qualcomm.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=deepti.jaggi@oss.qualcomm.com \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ram.dwivedi@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