From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: qcom_smd: Keep one rpm handle for all vregs
Date: Wed, 27 Dec 2023 13:48:05 +0200 [thread overview]
Message-ID: <ae1c1cb6-00f9-41ce-afd1-d557fbf3034f@linaro.org> (raw)
In-Reply-To: <20231227-topic-rpm_vreg_cleanup-v1-1-949da0864ac5@linaro.org>
On 27/12/2023 03:29, Konrad Dybcio wrote:
> For no apparent reason (as there's just one RPM per SoC), all vregs
> currently store a copy of a pointer to smd_rpm. Introduce a single,
> global one to save up on space in each definition.
>
> bloat-o-meter reports:
>
> Total: Before=43944, After=43924, chg -0.05%
>
> plus sizeof(ptr) on every dynamically allocated regulator :)
>
> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
> ---
> drivers/regulator/qcom_smd-regulator.c | 18 +++++++-----------
> 1 file changed, 7 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/regulator/qcom_smd-regulator.c b/drivers/regulator/qcom_smd-regulator.c
> index d1be9568025e..905c15df8c85 100644
> --- a/drivers/regulator/qcom_smd-regulator.c
> +++ b/drivers/regulator/qcom_smd-regulator.c
> @@ -11,11 +11,10 @@
> #include <linux/regulator/of_regulator.h>
> #include <linux/soc/qcom/smd-rpm.h>
>
> +struct qcom_smd_rpm *smd_vreg_rpm;
> +
> struct qcom_rpm_reg {
> struct device *dev;
> -
> - struct qcom_smd_rpm *rpm;
> -
> u32 type;
> u32 id;
>
> @@ -70,7 +69,7 @@ static int rpm_reg_write_active(struct qcom_rpm_reg *vreg)
> if (!reqlen)
> return 0;
>
> - ret = qcom_rpm_smd_write(vreg->rpm, QCOM_SMD_RPM_ACTIVE_STATE,
> + ret = qcom_rpm_smd_write(smd_vreg_rpm, QCOM_SMD_RPM_ACTIVE_STATE,
> vreg->type, vreg->id,
> req, sizeof(req[0]) * reqlen);
> if (!ret) {
> @@ -1391,7 +1390,7 @@ MODULE_DEVICE_TABLE(of, rpm_of_match);
> * Return: 0 on success, errno on failure
> */
> static int rpm_regulator_init_vreg(struct qcom_rpm_reg *vreg, struct device *dev,
> - struct device_node *node, struct qcom_smd_rpm *rpm,
> + struct device_node *node,
> const struct rpm_regulator_data *pmic_rpm_data)
> {
> struct regulator_config config = {};
> @@ -1409,7 +1408,6 @@ static int rpm_regulator_init_vreg(struct qcom_rpm_reg *vreg, struct device *dev
> }
>
> vreg->dev = dev;
> - vreg->rpm = rpm;
> vreg->type = rpm_data->type;
> vreg->id = rpm_data->id;
>
> @@ -1440,11 +1438,10 @@ static int rpm_reg_probe(struct platform_device *pdev)
> const struct rpm_regulator_data *vreg_data;
> struct device_node *node;
> struct qcom_rpm_reg *vreg;
> - struct qcom_smd_rpm *rpm;
> int ret;
>
> - rpm = dev_get_drvdata(pdev->dev.parent);
> - if (!rpm) {
> + smd_vreg_rpm = dev_get_drvdata(pdev->dev.parent);
> + if (!smd_vreg_rpm) {
I thought about having a mutex around (I don't remember if secondary
PMICs and/or chargers can be routed through RPM or not).
Then I went on checking other RPM and SMD-RPM drivers.
clk-rpm: global variable, field
clk-smd-rpm: struct field
regulator_qcom-smd-rpm: struct field
Probably it's worth using the same approach in all four drivers?
> dev_err(&pdev->dev, "Unable to retrieve handle to rpm\n");
> return -ENODEV;
> }
> @@ -1460,8 +1457,7 @@ static int rpm_reg_probe(struct platform_device *pdev)
> return -ENOMEM;
> }
>
> - ret = rpm_regulator_init_vreg(vreg, dev, node, rpm, vreg_data);
> -
> + ret = rpm_regulator_init_vreg(vreg, dev, node, vreg_data);
> if (ret < 0) {
> of_node_put(node);
> return ret;
>
> ---
> base-commit: 39676dfe52331dba909c617f213fdb21015c8d10
> change-id: 20231227-topic-rpm_vreg_cleanup-fa095cd528ec
>
> Best regards,
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-12-27 11:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 1:29 Konrad Dybcio
2023-12-27 11:10 ` kernel test robot
2023-12-27 11:48 ` Dmitry Baryshkov [this message]
2024-01-03 10:03 ` Konrad Dybcio
2024-01-03 18:31 ` 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=ae1c1cb6-00f9-41ce-afd1-d557fbf3034f@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.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
all inboxes | Powered by JetHome®