[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfNHkJp-SMacKdaSuy3gDECs=u4BNMNe2KjYkrDiwb8jg@mail.gmail.com>
Date: Sun, 28 Feb 2021 11:29:05 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Rasmus Villemoes <linux@...musvillemoes.dk>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Rob Herring <robh+dt@...nel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>,
"linux-clk@...r.kernel.org" <linux-clk@...r.kernel.org>
Subject: Re: [PATCH 2/2] drivers: misc: add ripple counter driver
On Sun, Feb 28, 2021 at 11:07 AM Andy Shevchenko
<andy.shevchenko@...il.com> wrote:
> On Friday, February 26, 2021, Rasmus Villemoes <linux@...musvillemoes.dk> wrote:
>>
>> The only purpose of this driver is to serve as a consumer of the input
>> clock, to prevent it from being disabled by clk_disable_unused().
>
> We have a clock API to do the same (something like marking it used or so) why do you need a driver?
Example:
https://elixir.bootlin.com/linux/latest/source/drivers/platform/x86/pmc_atom.c#L365
If it's a DT based platform I think you can make it somehow work thru DT.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists