From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Brian Masney <bmasney@redhat.com>, andersson@kernel.org
Cc: agross@kernel.org, konrad.dybcio@linaro.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, jejb@linux.ibm.com,
martin.petersen@oracle.com, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/2] scsi: ufs: ufs-qcom: add basic interconnect support
Date: Fri, 23 Dec 2022 00:17:23 +0200 [thread overview]
Message-ID: <71bf6521-71d7-ec45-912f-e3dc6038d3a4@linaro.org> (raw)
In-Reply-To: <20221117104957.254648-2-bmasney@redhat.com>
On 17/11/2022 12:49, Brian Masney wrote:
> The firmware on the Qualcomm platforms expects the interconnect votes to
> be present. Let's add very basic support where the maximum throughput is
> requested to match what's done in a few other drivers.
>
> This will not break boot on systems where the interconnects and
> interconnect-names properties are not specified in device tree for UFS
> since the interconnect framework will silently return.
>
> Signed-off-by: Brian Masney <bmasney@redhat.com>
> ---
> drivers/ufs/host/ufs-qcom.c | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/drivers/ufs/host/ufs-qcom.c b/drivers/ufs/host/ufs-qcom.c
> index 8ad1415e10b6..55bf8dd88985 100644
> --- a/drivers/ufs/host/ufs-qcom.c
> +++ b/drivers/ufs/host/ufs-qcom.c
> @@ -7,6 +7,7 @@
> #include <linux/time.h>
> #include <linux/clk.h>
> #include <linux/delay.h>
> +#include <linux/interconnect.h>
> #include <linux/module.h>
> #include <linux/of.h>
> #include <linux/platform_device.h>
> @@ -936,6 +937,22 @@ static const struct reset_control_ops ufs_qcom_reset_ops = {
> .deassert = ufs_qcom_reset_deassert,
> };
>
> +static int ufs_qcom_icc_init(struct device *dev, char *pathname)
> +{
> + struct icc_path *path;
> + int ret;
> +
> + path = devm_of_icc_get(dev, pathname);
> + if (IS_ERR(path))
> + return dev_err_probe(dev, PTR_ERR(path), "failed to acquire interconnect path\n");
> +
> + ret = icc_set_bw(path, 0, UINT_MAX);
I noticed that this patch bumps peak_bw (and leaves average_bw as 0),
while vendor kernels bump average_bw, but ib (peak_bw) is set to 0.
> + if (ret < 0)
> + return dev_err_probe(dev, ret, "failed to set bandwidth request\n");
> +
> + return 0;
> +}
> +
> /**
> * ufs_qcom_init - bind phy with controller
> * @hba: host controller instance
> @@ -991,6 +1008,14 @@ static int ufs_qcom_init(struct ufs_hba *hba)
> err = dev_err_probe(dev, PTR_ERR(host->generic_phy), "Failed to get PHY\n");
> goto out_variant_clear;
> }
> +
> + err = ufs_qcom_icc_init(dev, "ufs-ddr");
> + if (err)
> + goto out_variant_clear;
> +
> + err = ufs_qcom_icc_init(dev, "cpu-ufs");
> + if (err)
> + goto out_variant_clear;
> }
>
> host->device_reset = devm_gpiod_get_optional(dev, "reset",
--
With best wishes
Dmitry
next prev parent reply other threads:[~2022-12-22 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 10:49 [PATCH 0/2] qcom: add basic interconnect support to UFS Brian Masney
2022-11-17 10:49 ` [PATCH 1/2] scsi: ufs: ufs-qcom: add basic interconnect support Brian Masney
2022-11-17 11:33 ` Manivannan Sadhasivam
2022-12-22 22:17 ` Dmitry Baryshkov [this message]
2023-05-19 17:20 ` Konrad Dybcio
2022-11-17 10:49 ` [PATCH 2/2] arm64: dts: qcom: sc8280xp: add interconnect properties to ufs nodes Brian Masney
2022-11-17 11:12 ` [PATCH 0/2] qcom: add basic interconnect support to UFS Krzysztof Kozlowski
2023-01-19 14:40 ` Dmitry Baryshkov
-- strict thread matches above, loose matches on Subject: below --
2023-01-19 14:43 [PATCH 0/2] arm64/msm8996: enable UFS interconnect Dmitry Baryshkov
2023-01-19 14:43 ` [PATCH 1/2] scsi: ufs: ufs-qcom: add basic interconnect support Dmitry Baryshkov
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=71bf6521-71d7-ec45-912f-e3dc6038d3a4@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bmasney@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=jejb@linux.ibm.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.