Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752334AbdGaOFI (ORCPT ); Mon, 31 Jul 2017 10:05:08 -0400 Received: from mail-oi0-f66.google.com ([209.85.218.66]:38292 "EHLO mail-oi0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752291AbdGaOFE (ORCPT ); Mon, 31 Jul 2017 10:05:04 -0400 MIME-Version: 1.0 In-Reply-To: <20170731113832.26490-1-jbrunet@baylibre.com> References: <20170731113832.26490-1-jbrunet@baylibre.com> From: Arnd Bergmann Date: Mon, 31 Jul 2017 16:05:02 +0200 X-Google-Sender-Auth: hqSneafQWDDWO7mWEaXdBekQG7M Message-ID: Subject: Re: [PATCH 0/2] clk: meson: expose clk ids To: Jerome Brunet Cc: Neil Armstrong , Michael Turquette , Stephen Boyd , Carlo Caione , Kevin Hilman , Olof Johansson , linux-clk , "open list:ARM/Amlogic Meson SoC support" , Linux ARM , Linux Kernel Mailing List , devicetree@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 902 Lines: 22 On Mon, Jul 31, 2017 at 1:38 PM, Jerome Brunet 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