From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: amit.kucheria@linaro.org, edubezval@gmail.com,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-pm@vger.kernel.org, daniel.lezcano@linaro.org
Subject: Re: [PATCH v2] thermal: tsens: qcom: do not create duplicate regmap debugfs entries
Date: Tue, 1 Jan 2019 19:32:40 -0800 [thread overview]
Message-ID: <20190102033240.GA22852@builder> (raw)
In-Reply-To: <20181206093917.26610-1-srinivas.kandagatla@linaro.org>
On Thu 06 Dec 01:39 PST 2018, Srinivas Kandagatla wrote:
> Regmap would use device name to create debugfs entries. If the device
> has multiple regmaps it is recommended to use name field in regmap_config.
> Fix this by providing name to the regmap configs correctly.
>
> Without this patch we would see below error on DB820c.
>
> qcom-tsens 4a9000.thermal-sensor: Failed to create 4a9000.thermal-sensor
> debugfs directory
>
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> Acked-by: Amit Kucheria <amit.kucheria@linaro.org>
> Tested-by: Amit Kucheria <amit.kucheria@linaro.org>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Regards,
Bjorn
> ---
> Changes since v1:
> -rename tsens_config to tsens_tm_config as suggested by Amit.
>
> drivers/thermal/qcom/tsens-common.c | 17 +++++++++++++----
> 1 file changed, 13 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/thermal/qcom/tsens-common.c b/drivers/thermal/qcom/tsens-common.c
> index 3be4be2e0465..ddfdf88ffb4e 100644
> --- a/drivers/thermal/qcom/tsens-common.c
> +++ b/drivers/thermal/qcom/tsens-common.c
> @@ -113,7 +113,15 @@ int get_temp_common(struct tsens_device *tmdev, int id, int *temp)
> return 0;
> }
>
> -static const struct regmap_config tsens_config = {
> +static const struct regmap_config tsens_tm_config = {
> + .name = "tm",
> + .reg_bits = 32,
> + .val_bits = 32,
> + .reg_stride = 4,
> +};
> +
> +static const struct regmap_config tsens_srot_config = {
> + .name = "srot",
> .reg_bits = 32,
> .val_bits = 32,
> .reg_stride = 4,
> @@ -139,8 +147,8 @@ int __init init_common(struct tsens_device *tmdev)
> if (IS_ERR(srot_base))
> return PTR_ERR(srot_base);
>
> - tmdev->srot_map = devm_regmap_init_mmio(tmdev->dev,
> - srot_base, &tsens_config);
> + tmdev->srot_map = devm_regmap_init_mmio(tmdev->dev, srot_base,
> + &tsens_srot_config);
> if (IS_ERR(tmdev->srot_map))
> return PTR_ERR(tmdev->srot_map);
>
> @@ -154,7 +162,8 @@ int __init init_common(struct tsens_device *tmdev)
> if (IS_ERR(tm_base))
> return PTR_ERR(tm_base);
>
> - tmdev->tm_map = devm_regmap_init_mmio(tmdev->dev, tm_base, &tsens_config);
> + tmdev->tm_map = devm_regmap_init_mmio(tmdev->dev, tm_base,
> + &tsens_tm_config);
> if (IS_ERR(tmdev->tm_map))
> return PTR_ERR(tmdev->tm_map);
>
> --
> 2.19.2
>
prev parent reply other threads:[~2019-01-02 3:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 9:39 [PATCH v2] thermal: tsens: qcom: do not create duplicate regmap debugfs entries Srinivas Kandagatla
2019-01-02 3:32 ` Bjorn Andersson [this message]
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=20190102033240.GA22852@builder \
--to=bjorn.andersson@linaro.org \
--cc=amit.kucheria@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=edubezval@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=srinivas.kandagatla@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).