From: Avri Altman <Avri.Altman@wdc.com>
To: Eric Biggers <ebiggers@kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Cc: "linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-fscrypt@vger.kernel.org" <linux-fscrypt@vger.kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Andy Gross <agross@kernel.org>,
Barani Muthukumaran <bmuthuku@qti.qualcomm.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Can Guo <cang@codeaurora.org>,
Elliot Berman <eberman@codeaurora.org>,
John Stultz <john.stultz@linaro.org>,
Satya Tangirala <satyat@google.com>,
Steev Klimaszewski <steev@kali.org>,
Thara Gopinath <thara.gopinath@linaro.org>
Subject: RE: [PATCH v6 2/5] scsi: ufs-qcom: name the dev_ref_clk_ctrl registers
Date: Sun, 12 Jul 2020 08:42:55 +0000 [thread overview]
Message-ID: <SN6PR04MB46408276B769C494EDB742DDFC630@SN6PR04MB4640.namprd04.prod.outlook.com> (raw)
In-Reply-To: <20200710072013.177481-3-ebiggers@kernel.org>
>
>
> From: Eric Biggers <ebiggers@google.com>
>
> In preparation for adding another optional register range to the
> ufs-qcom driver, name the existing optional register range
> "dev_ref_clk_ctrl_mem". This allows the driver to refer to the optional
> register ranges by name rather than index.
>
> No device-tree files actually have to be updated due to this change,
> since none of them actually declares these registers.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
Reviewed-by: Avri Altman <avri.altman@wdc.com>
> ---
> drivers/scsi/ufs/ufs-qcom.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/ufs/ufs-qcom.c b/drivers/scsi/ufs/ufs-qcom.c
> index 2e6ddb5cdfc2..bd0b4ed7b37a 100644
> --- a/drivers/scsi/ufs/ufs-qcom.c
> +++ b/drivers/scsi/ufs/ufs-qcom.c
> @@ -1275,7 +1275,8 @@ static int ufs_qcom_init(struct ufs_hba *hba)
> host->dev_ref_clk_en_mask = BIT(26);
> } else {
> /* "dev_ref_clk_ctrl_mem" is optional resource */
> - res = platform_get_resource(pdev, IORESOURCE_MEM, 1);
> + res = platform_get_resource_byname(pdev, IORESOURCE_MEM,
> + "dev_ref_clk_ctrl_mem");
> if (res) {
> host->dev_ref_clk_ctrl_mmio =
> devm_ioremap_resource(dev, res);
> --
> 2.27.0
next prev parent reply other threads:[~2020-07-12 8:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 7:20 [PATCH v6 0/5] Inline crypto support on DragonBoard 845c Eric Biggers
2020-07-10 7:20 ` [PATCH v6 1/5] firmware: qcom_scm: Add support for programming inline crypto keys Eric Biggers
2020-07-10 7:20 ` [PATCH v6 2/5] scsi: ufs-qcom: name the dev_ref_clk_ctrl registers Eric Biggers
2020-07-12 8:42 ` Avri Altman [this message]
2020-07-22 5:07 ` Bjorn Andersson
2020-07-10 7:20 ` [PATCH v6 3/5] arm64: dts: sdm845: add Inline Crypto Engine registers and clock Eric Biggers
2020-07-14 14:16 ` Martin K. Petersen
2020-07-14 16:15 ` Eric Biggers
2020-07-14 16:35 ` Rob Herring
2020-07-14 16:43 ` Eric Biggers
2020-07-14 16:46 ` Martin K. Petersen
2020-07-14 16:59 ` Rob Herring
2020-07-14 17:12 ` Eric Biggers
2020-07-14 17:31 ` Bjorn Andersson
2020-07-14 17:43 ` Bjorn Andersson
2020-07-14 17:57 ` Eric Biggers
2020-07-14 20:00 ` Bjorn Andersson
2020-07-15 3:00 ` Eric Biggers
2020-07-20 17:07 ` Eric Biggers
2020-07-21 18:20 ` Eric Biggers
2020-07-22 5:11 ` Bjorn Andersson
2020-07-14 17:36 ` Rob Herring
2020-07-10 7:20 ` [PATCH v6 4/5] scsi: ufs: add program_key() variant op Eric Biggers
2020-07-12 9:41 ` Avri Altman
2020-07-10 7:20 ` [PATCH v6 5/5] scsi: ufs-qcom: add Inline Crypto Engine support Eric Biggers
2020-07-12 9:43 ` Avri Altman
2020-07-22 5:09 ` Bjorn Andersson
2020-07-22 4:28 ` [PATCH v6 0/5] Inline crypto support on DragonBoard 845c Martin K. Petersen
2020-07-22 5:25 ` Eric Biggers
2020-07-22 12:21 ` Martin K. Petersen
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=SN6PR04MB46408276B769C494EDB742DDFC630@SN6PR04MB4640.namprd04.prod.outlook.com \
--to=avri.altman@wdc.com \
--cc=agross@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=bjorn.andersson@linaro.org \
--cc=bmuthuku@qti.qualcomm.com \
--cc=cang@codeaurora.org \
--cc=eberman@codeaurora.org \
--cc=ebiggers@kernel.org \
--cc=john.stultz@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=satyat@google.com \
--cc=steev@kali.org \
--cc=thara.gopinath@linaro.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;
as well as URLs for NNTP newsgroup(s).