[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <05e6d2d6dd8805c4cded28f85ac873b96bc1467e.camel@icenowy.me>
Date: Sat, 22 Jul 2023 20:13:45 +0800
From: Icenowy Zheng <uwu@...nowy.me>
To: Daniel Lezcano <daniel.lezcano@...aro.org>,
"Rafael J . Wysocki" <rafael@...nel.org>,
Amit Kucheria <amitk@...nel.org>,
Zhang Rui <rui.zhang@...el.com>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
Kang Chen <void0red@...t.edu.cn>,
Dongliang Mu <dzm91@...t.edu.cn>
Cc: linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH 0/2] thermal/drivers/mediatek: fix a regression
affecting other subsystems
在 2023-06-13星期二的 10:44 +0200,Daniel Lezcano写道:
> On 29/05/2023 18:20, Icenowy Zheng wrote:
> > In the commit I reverted as the first commit of this patchset, the
> > of_iomap function call, which allows multiple mapping of the same
> > physical memory space, is replaced to calling devm_of_iomap, which
> > registers exclusivity, and on my system (mt8173-elm), preventing
> > display
> > from working.
> >
> > So I reverted it, and to really solve the problem that the original
> > commit wants to solve, I read the source of auxadc-thermal and
> > realized
> > that the address of these two memory blocks are not saved after
> > probe,
> > and they're only used when initializing the thermal sensors. This
> > leads
> > to my final fix, which is the second commit here, that adds
> > of_iounmap
> > just to the probe function.
> >
> > Icenowy Zheng (2):
> > Revert "thermal/drivers/mediatek: Use devm_of_iomap to avoid
> > resource
> > leak in mtk_thermal_probe"
> > thermal/drivers/mediatek: unmap foreign MMIO after probing
> >
> > drivers/thermal/mediatek/auxadc_thermal.c | 46 ++++++++++++------
> > -----
> > 1 file changed, 24 insertions(+), 22 deletions(-)
>
> I'll apply only the revert and let you revisit the patch 2 which
> could
> be improved.
Sorry, is the first patch applied? I didn't see it in any kernel
trees...
I have no current idea about how to fix in patch 2.
>
Powered by blists - more mailing lists