[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241001063919.ekqfd4epcefh5eci@vireshk-i7>
Date: Tue, 1 Oct 2024 12:09:19 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Mark Tseng <chun-jen.tseng@...iatek.com>
Cc: "Rafael J . Wysocki" <rafael@...nel.org>,
MyungJoo Ham <myungjoo.ham@...sung.com>,
Kyungmin Park <kyungmin.park@...sung.com>,
Chanwoo Choi <cw00.choi@...sung.com>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
Project_Global_Chrome_Upstream_Group@...iatek.com
Subject: Re: [PATCH v1 1/2] PM / devfreq: mediatek: protect oop in critical
session
On 13-09-24, 18:39, Mark Tseng wrote:
> mtk_ccifreq_target() & mtk_ccifreq_opp_notifier() is re-enter funtion
> when cpufreq governor is more than one. It should add global mutex to
> protect OPP , avoid get wrong frequency & voltage.
I am not sure I understood the problem well. Can you explain clearly
why the current locking doesn't work with details call chain ?
--
viresh
Powered by blists - more mailing lists