[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a28nb8QsJC8V4+SJM0gz70BDOv8jAczRWoCF+HfvkwJfA@mail.gmail.com>
Date: Mon, 31 Jul 2017 16:05:02 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Jerome Brunet <jbrunet@...libre.com>
Cc: Neil Armstrong <narmstrong@...libre.com>,
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 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>
Powered by blists - more mailing lists