From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jongsung Kim Subject: Re: [PATCH v2] clk: fixed-factor: add optional dt-binding clock-flags Date: Wed, 29 Jun 2016 14:04:40 +0900 Message-ID: <577356E8.30009@lge.com> References: <20160621005910.GN1521@codeaurora.org> <1466741572-58802-1-git-send-email-neidhard.kim@lge.com> <20160628205518.GF3737@rob-hp-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <20160628205518.GF3737@rob-hp-laptop> Sender: linux-clk-owner@vger.kernel.org To: Rob Herring Cc: Maxime Ripard , Mike Turquette , Stephen Boyd , linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Chanho Min List-Id: devicetree@vger.kernel.org On 2016=EB=85=84 06=EC=9B=94 29=EC=9D=BC 05:55, Rob Herring wrote: > On Fri, Jun 24, 2016 at 01:12:52PM +0900, Jongsung Kim wrote: >> There is no way to set additional flags for a DT-initialized fixed- >> factor-clock, and it can be problematic i.e., when the clock rate >> needs to be changed. [1][2] >> >> This patch introduces an optional dt-binding named "clock-flags" to >> be used for passing any needed flags from dts. > I don't think we want this in DT. If we did, the flags would need som= e=20 > documentation about what the flags mean. Thanks for your comment. It looks not that big deal to provide a little= documentation..? Some of the flags looks safe to be removed. Thinking = of only fixed-factor-clock, most of them can be removed.