[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a2=nZ3bbeguXjbFrhz0nWeUOcLM7mRudhPDrcb+jZ4VvQ@mail.gmail.com>
Date: Fri, 26 Feb 2021 15:35:20 +0100
From: Arnd Bergmann <arnd@...nel.org>
To: Rasmus Villemoes <linux@...musvillemoes.dk>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Rob Herring <robh+dt@...nel.org>,
DTML <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>,
linux-clk <linux-clk@...r.kernel.org>
Subject: Re: [PATCH 0/2] add ripple counter dt binding and driver
On Fri, Feb 26, 2021 at 3:14 PM Rasmus Villemoes
<linux@...musvillemoes.dk> wrote:
>
> So I'm thinking that the proper way to handle this is to be able to
> represent that ripple counter as a clock consumer in DT and have a
> driver do the clk_prepare_enable(), even if that driver doesn't and
> can't do anything else. But I'm certainly open to other suggestions.
How about adding support for the optional clock to the gpio_wdt driver,
would that work?
Arnd
Powered by blists - more mailing lists