[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <90c958bacfb77080ee524c55f5e1a01696b27017.camel@gmail.com>
Date: Sun, 13 Jun 2021 22:11:02 +0200
From: Alexander Sverdlin <alexander.sverdlin@...il.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Nikita Shubin <nikita.shubin@...uefel.me>,
Russell King <linux@...linux.org.uk>,
Hartley Sweeten <hsweeten@...ionengravers.com>,
Arnd Bergmann <arnd@...db.de>,
Linus Walleij <linus.walleij@...aro.org>,
Ard Biesheuvel <ardb@...nel.org>,
Mike Rapoport <rppt@...nel.org>,
Gregory Fong <gregory.0xf0@...il.com>,
Geert Uytterhoeven <geert+renesas@...der.be>,
YiFei Zhu <yifeifz2@...inois.edu>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/1] ep93xx: clock: convert in-place to COMMON_CLK
Hello Geert!
On Sat, 2021-06-12 at 11:18 +0200, Geert Uytterhoeven wrote:
> > WARNING: CPU: 0 PID: 36 at drivers/clk/clk.c:952 clk_core_disable+0xbc/0xd8
> > ep93xx-spi.0 already disabled
> > [<c023ee98>] (ep93xx_spi_unprepare_hardware) from [<c023c35c>] (__spi_pump_messages+0x388/0x620)
>
> These are issues in individual drivers, not in the CCF implementation.
> All drivers using the clock API should be converted from
> clk_{en,dis}able() to clk_{prepare_enable,disable_unprepare}() first.
You are right!
I'm currently testing a series, which will convert the calls.
--
Alexander Sverdlin.
Powered by blists - more mailing lists