From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>
Cc: "jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 6/7] arm64: dts: renesas: r8a779f0: Add UFS node
Date: Wed, 13 Apr 2022 08:27:05 +0200 [thread overview]
Message-ID: <1fccb130-2807-4376-a1d4-db1d44e6a7ef@linaro.org> (raw)
In-Reply-To: <TYBPR01MB534192EDF0C76F77A797187AD8EC9@TYBPR01MB5341.jpnprd01.prod.outlook.com>
On 13/04/2022 02:09, Yoshihiro Shimoda wrote:
>>> + ufs: scsi@e6860000 {
>>
>> Node name: ufs (it is not a SCSI device, AFAIK).
>
> I got it. I'll fix it.
> (I had assumed that we should choose a node name from "2.2.2 Generic Names
> Recommendation" of the ePAPR v1.1 [1]. But, that's wrong. )
>
> [1]
> https://elinux.org/images/c/cf/Power_ePAPR_APPROVED_v1.1.pdf
These are examples and at the time written, I am not sure if UFS was
considered. :) "ufs" is name of a standard, so it is a generic name.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-04-13 6:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 7:36 [PATCH 0/7] treewide: scsi: ufs: Add support for Renesas R-Car UFS controller Yoshihiro Shimoda
2022-04-12 7:36 ` [PATCH 1/7] dt-bindings: ufs: Document Renesas R-Car UFS host controller Yoshihiro Shimoda
2022-04-12 12:23 ` Krzysztof Kozlowski
2022-04-13 0:59 ` Yoshihiro Shimoda
2022-04-12 15:18 ` Rob Herring
2022-04-12 7:36 ` [PATCH 2/7] ufs: add UFSHCD_QUIRK_BROKEN_64BIT_ADDRESS Yoshihiro Shimoda
2022-04-15 6:45 ` Christoph Hellwig
2022-04-15 7:45 ` Yoshihiro Shimoda
2022-04-12 7:36 ` [PATCH 3/7] ufs: add UFSHCD_QUIRK_HIBERN_FASTAUTO Yoshihiro Shimoda
2022-04-12 7:36 ` [PATCH 4/7] scsi: ufs-renesas: Add support for Renesas R-Car UFS controller Yoshihiro Shimoda
2022-04-12 12:24 ` Krzysztof Kozlowski
2022-04-13 1:24 ` Yoshihiro Shimoda
2022-04-12 7:36 ` [PATCH 5/7] scsi: MAINTAINERS: Add maintainer for Renesas UFS driver Yoshihiro Shimoda
2022-04-12 7:36 ` [PATCH 6/7] arm64: dts: renesas: r8a779f0: Add UFS node Yoshihiro Shimoda
2022-04-12 9:04 ` Krzysztof Kozlowski
2022-04-13 0:09 ` Yoshihiro Shimoda
2022-04-13 6:27 ` Krzysztof Kozlowski [this message]
2022-04-14 2:25 ` Yoshihiro Shimoda
2022-04-12 7:36 ` [PATCH 7/7] arm64: dts: renesas: r8a779f0: spider-cpu: Enable UFS device Yoshihiro Shimoda
2022-04-12 9:19 ` [PATCH 0/7] treewide: scsi: ufs: Add support for Renesas R-Car UFS controller Krzysztof Kozlowski
2022-04-12 15:52 ` Randy Dunlap
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=1fccb130-2807-4376-a1d4-db1d44e6a7ef@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=devicetree@vger.kernel.org \
--cc=jejb@linux.ibm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=robh+dt@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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).