From: Amjad Ouled-Ameur <aouledameur@baylibre.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Amit Kucheria <amitk@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Fabien Parent <fparent@baylibre.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Rob Herring <robh@kernel.org>,
Markus Schneider-Pargmann <msp@baylibre.com>,
Hsin-Yi Wang <hsinyi@chromium.org>,
Michael Kao <michael.kao@mediatek.com>
Subject: Re: [PATCH v9 2/5] thermal: mediatek: control buffer enablement tweaks
Date: Fri, 27 Jan 2023 23:21:05 +0100 [thread overview]
Message-ID: <df39cc8c-29db-f401-e1a2-1a3b7e962a7e@baylibre.com> (raw)
In-Reply-To: <eb3b9439-172b-daea-8f0f-53c8fe7648f9@linaro.org>
On 1/27/23 22:48, Daniel Lezcano wrote:
> On 27/01/2023 16:44, Amjad Ouled-Ameur wrote:
>> From: Markus Schneider-Pargmann <msp@baylibre.com>
>>
>> Add logic in order to be able to turn on the control buffer on MT8365.
>> This change now allows to have control buffer support for MTK_THERMAL_V1,
>> and it allows to define the register offset, and mask used to enable it.
>>
>> Signed-off-by: Markus Schneider-Pargmann <msp@baylibre.com>
>> Signed-off-by: Fabien Parent <fparent@baylibre.com>
>> Signed-off-by: Amjad Ouled-Ameur <aouledameur@baylibre.com>
>> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
>> ---
>> drivers/thermal/mtk_thermal.c | 25 ++++++++++++++++++-------
>> 1 file changed, 18 insertions(+), 7 deletions(-)
>>
>> diff --git a/drivers/thermal/mtk_thermal.c b/drivers/thermal/mtk_thermal.c
>> index 8440692e3890..d8ddceb75372 100644
>> --- a/drivers/thermal/mtk_thermal.c
>> +++ b/drivers/thermal/mtk_thermal.c
>> @@ -271,6 +271,9 @@ struct mtk_thermal_data {
>> bool need_switch_bank;
>> struct thermal_bank_cfg bank_data[MAX_NUM_ZONES];
>> enum mtk_thermal_version version;
>> + u32 apmixed_buffer_ctl_reg;
>> + u32 apmixed_buffer_ctl_mask;
>> + u32 apmixed_buffer_ctl_set;
>> };
>> struct mtk_thermal {
>> @@ -514,6 +517,9 @@ static const struct mtk_thermal_data mt7622_thermal_data = {
>> .adcpnp = mt7622_adcpnp,
>> .sensor_mux_values = mt7622_mux_values,
>> .version = MTK_THERMAL_V2,
>> + .apmixed_buffer_ctl_reg = APMIXED_SYS_TS_CON1,
>> + .apmixed_buffer_ctl_mask = GENMASK(31, 6) | BIT(3),
>> + .apmixed_buffer_ctl_set = BIT(0),
>> };
>> /*
>> @@ -963,14 +969,18 @@ static const struct of_device_id mtk_thermal_of_match[] = {
>> };
>> MODULE_DEVICE_TABLE(of, mtk_thermal_of_match);
>> -static void mtk_thermal_turn_on_buffer(void __iomem *apmixed_base)
>> +static void mtk_thermal_turn_on_buffer(struct mtk_thermal *mt,
>> + void __iomem *apmixed_base)
>> {
>> - int tmp;
>> + u32 tmp;
>> +
>> + if (!mt->conf->apmixed_buffer_ctl_reg)
>> + return;
>> - tmp = readl(apmixed_base + APMIXED_SYS_TS_CON1);
>> - tmp &= ~(0x37);
>> - tmp |= 0x1;
>> - writel(tmp, apmixed_base + APMIXED_SYS_TS_CON1);
>> + tmp = readl(apmixed_base + mt->conf->apmixed_buffer_ctl_reg);
>> + tmp &= mt->conf->apmixed_buffer_ctl_mask;
>> + tmp |= mt->conf->apmixed_buffer_ctl_set;
>> + writel(tmp, apmixed_base + mt->conf->apmixed_buffer_ctl_reg);
>> udelay(200);
>> }
>> @@ -1070,8 +1080,9 @@ static int mtk_thermal_probe(struct platform_device *pdev)
>> goto err_disable_clk_auxadc;
>> }
>> + mtk_thermal_turn_on_buffer(mt, apmixed_base);
>> +
>> if (mt->conf->version == MTK_THERMAL_V2) {
>> - mtk_thermal_turn_on_buffer(apmixed_base);
>> mtk_thermal_release_periodic_ts(mt, auxadc_base);
>> }
>
> This change conflicts with commit 4f2ee0aa2e706
>
> I fixed it with:
>
> - if (mt->conf->version != MTK_THERMAL_V1) {
> - mtk_thermal_turn_on_buffer(apmixed_base);
> + mtk_thermal_turn_on_buffer(apmixed_base);
> +
> + if (mt->conf->version != MTK_THERMAL_V1)
> mtk_thermal_release_periodic_ts(mt, auxadc_base);
> - }
>
I think it's rather MTK_THERMAL_V2 and not MTK_THERMAL_V1. Other than that, it looks
fine by me, thanks.
Amjad
> Let me know if there is something wrong.
>
>
next prev parent reply other threads:[~2023-01-27 22:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 15:44 [PATCH v9 0/5] thermal: mediatek: Add support for MT8365 SoC Amjad Ouled-Ameur
2023-01-27 15:44 ` [PATCH v9 1/5] dt-bindings: thermal: mediatek: add binding documentation " Amjad Ouled-Ameur
2023-01-27 15:44 ` [PATCH v9 2/5] thermal: mediatek: control buffer enablement tweaks Amjad Ouled-Ameur
2023-01-27 21:48 ` Daniel Lezcano
2023-01-27 22:21 ` Amjad Ouled-Ameur [this message]
2023-01-28 7:52 ` Daniel Lezcano
2023-03-09 17:14 ` Amjad Ouled-Ameur
2023-01-27 15:44 ` [PATCH v9 3/5] thermal: mediatek: add support for MT8365 SoC Amjad Ouled-Ameur
2023-01-27 15:44 ` [PATCH v9 4/5] thermal: mediatek: add callback for raw to mcelsius conversion Amjad Ouled-Ameur
2023-01-27 21:56 ` Daniel Lezcano
2023-01-27 15:44 ` [PATCH v9 5/5] thermal: mediatek: add delay after thermal banks initialization Amjad Ouled-Ameur
2023-01-27 21:03 ` Daniel Lezcano
2023-01-27 21:59 ` [PATCH v9 0/5] thermal: mediatek: Add support for MT8365 SoC Daniel Lezcano
2023-01-27 22:23 ` Amjad Ouled-Ameur
2023-03-06 10:13 ` Amjad Ouled-Ameur
2023-03-08 18:00 ` Daniel Lezcano
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=df39cc8c-29db-f401-e1a2-1a3b7e962a7e@baylibre.com \
--to=aouledameur@baylibre.com \
--cc=amitk@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=fparent@baylibre.com \
--cc=hsinyi@chromium.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=michael.kao@mediatek.com \
--cc=msp@baylibre.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.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).