[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6494a76f-7282-cc39-c02a-0f1b2a8d83ff@baylibre.com>
Date: Tue, 1 Aug 2017 14:00:22 +0200
From: Neil Armstrong <narmstrong@...libre.com>
To: Arnd Bergmann <arnd@...db.de>, Jerome Brunet <jbrunet@...libre.com>
Cc: Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...eaurora.org>,
Carlo Caione <carlo@...one.org>,
Kevin Hilman <khilman@...libre.com>,
Olof Johansson <olof@...om.net>,
linux-clk <linux-clk@...r.kernel.org>,
"open list:ARM/Amlogic Meson SoC support"
<linux-amlogic@...ts.infradead.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
devicetree@...r.kernel.org
Subject: Re: [PATCH 0/2] clk: meson: expose clk ids
On 07/31/2017 04:05 PM, Arnd Bergmann wrote:
> On Mon, Jul 31, 2017 at 1:38 PM, Jerome Brunet <jbrunet@...libre.com> wrote:
>> In previous cycles, concerns have been raised about the way clocks are
>> exposed for the meson clock controller, only when validated and required
>> in DT.
>>
>> Instead, this patchset expose all the known clocks which may be needed in
>> DT later on. The clocks left out are internal clocks which should never be
>> used directly in DT. These are mostly internal muxes and dividers of
>> composite clocks.
>>
>> While this should reduce the patch flow on the related header files, It
>> won't stop it completely. There are still many clocks we don't know about
>> yet. We tend discover a few in every cycle.
>>
>> This patchset depends on these fixes [0] to avoid issues when adding new
>> clk ids.
>>
>> [0]: https://lkml.kernel.org/r/20170727161755.10393-1-jbrunet@baylibre.com
>
> Thanks a lot!
>
> Acked-by: Arnd Bergmann <arnd@...db.de>
>
Applied to clk-meson's next/headers with arnd's ack.
Powered by blists - more mailing lists