From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Anand Moon <linux.amoon@gmail.com>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
"open list:SAMSUNG THERMAL DRIVER" <linux-pm@vger.kernel.org>,
"open list:SAMSUNG THERMAL DRIVER"
<linux-samsung-soc@vger.kernel.org>,
"moderated list:ARM/SAMSUNG S3C,
S5P AND EXYNOS ARM ARCHITECTURES"
<linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:CLANG/LLVM BUILD SUPPORT:Keyword:b(?i:clang|llvm)b"
<llvm@lists.linux.dev>
Subject: Re: [PATCH v6 0/4] Exynos Thermal code improvement
Date: Thu, 15 May 2025 15:28:55 +0200 [thread overview]
Message-ID: <92c2949e-2fc1-40e9-9dea-e3d9f7aa571d@linaro.org> (raw)
In-Reply-To: <CANAwSgSA-JHMRD7-19wijOY=TSWD-sv6yyrT=mH+wkUJuvxFAw@mail.gmail.com>
On 5/15/25 13:10, Anand Moon wrote:
> Hi Daniel,
>
> On Wed, 14 May 2025 at 16:53, Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>>
>> On Wed, Apr 30, 2025 at 06:02:56PM +0530, Anand Moon wrote:
>>> Hi All,
>>
>> Hi Anand,
>>
>> if the goal of the changes is to do cleanups, I recommend to rework
>> how the code is organized. Instead of having the data->soc check all
>> around the functions, write per platform functions and store them in
>> struct of_device_id data field instead of the soc version.
>>
>> Basically get rid of exynos_map_dt_data by settings the different ops
>> in a per platform structure.
>>
>> Then the initialization routine would be simpler to clean.
>>
>
> Thanks, I had previously attempted this approach.
> The goal is to split the exynos_tmu_data structure to accommodate
> SoC-specific callbacks for initialization and configuration.
>
> In my earlier attempt, I tried to refactor the code to achieve this.
> However, the main challenge I encountered was that the
> exynos_sensor_ops weren’t being correctly mapped for each SoC.
>
> Some SoC have multiple sensor
> exynos4x12
> tmu: tmu@100c0000
> exynos5420
> tmu_cpu0: tmu@10060000
> tmu_cpu1: tmu@10064000
> tmu_cpu2: tmu@10068000
> tmu_cpu3: tmu@1006c000
> tmu_gpu: tmu@100a0000
> exynos5433
> tmu_atlas0: tmu@10060000
> tmu_atlas1: tmu@10068000
> tmu_g3d: tmu@10070000
> exynos7
> tmu@10060000
>
> It could be a design issue of the structure.or some DTS issue.
> So what I found in debugging it is not working correctly.
>
> static const struct thermal_zone_device_ops exynos_sensor_ops = {
> .get_temp = exynos_get_temp,
> .set_emul_temp = exynos_tmu_set_emulation,
> .set_trips = exynos_set_trips,
> };
>
> The sensor callback will not return a valid pointer and soc id for the get_temp.
>
> Here is my earlier version of local changes.
> [1] https://pastebin.com/bbEP04Zh exynos_tmu.c
> [2] https://pastebin.com/PzNz5yve Odroid U3 dmesg.log
> [3] https://pastebin.com/4Yjt2d2u Odroid Xu4 dmesg.log
>
> I want to re-model the structure to improve the code.
> Once Its working condition I will send this for review.
>
> If you have some suggestions please let me know.
I suggest to do the conversion step by step beginning by
exynos4210_tmu_clear_irqs, then by exynos_map_dt_data as the first
cleanup iteration
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2025-05-15 13:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 12:32 [PATCH v6 0/4] Exynos Thermal code improvement Anand Moon
2025-04-30 12:32 ` [PATCH v6 1/4] thermal/drivers/exynos: Refactor clk_sec initialization inside SOC-specific case Anand Moon
2025-04-30 12:32 ` [PATCH v6 2/4] thermal/drivers/exynos: Use devm_clk_get_enabled() helpers Anand Moon
[not found] ` <CGME20250702120029eucas1p21cb8337b313f134047817c2e5d5790b8@eucas1p2.samsung.com>
2025-07-02 12:00 ` Mateusz Majewski
2025-04-30 12:32 ` [PATCH v6 3/4] thermal/drivers/exynos: Remove redundant IS_ERR() checks for clk_sec clock Anand Moon
2025-04-30 12:33 ` [PATCH v6 4/4] thermal/drivers/exynos: Fixed the efuse min max value for exynos5422 Anand Moon
2025-05-08 6:14 ` [PATCH v6 0/4] Exynos Thermal code improvement Anand Moon
2025-05-08 6:26 ` Krzysztof Kozlowski
2025-05-08 11:36 ` Anand Moon
2025-05-14 11:23 ` Daniel Lezcano
2025-05-15 11:10 ` Anand Moon
2025-05-15 13:28 ` Daniel Lezcano [this message]
2025-05-15 18:01 ` Anand Moon
2025-05-16 14:45 ` Daniel Lezcano
2025-05-17 19:41 ` Anand Moon
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=92c2949e-2fc1-40e9-9dea-e3d9f7aa571d@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=bzolnier@gmail.com \
--cc=justinstitt@google.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux.amoon@gmail.com \
--cc=llvm@lists.linux.dev \
--cc=lukasz.luba@arm.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=rafael@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).