From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 12 Jul 2017 16:10:20 -0700 From: Stephen Boyd To: Marek Vasut Cc: linux-clk@vger.kernel.org, Marek Vasut , Alexey Firago , Michael Turquette , Laurent Pinchart , linux-renesas-soc@vger.kernel.org Subject: Re: [PATCH V3 3/8] clk: vc5: Do not warn about disabled output buffer input muxes Message-ID: <20170712231020.GI22780@codeaurora.org> References: <20170709132814.2339-1-marek.vasut+renesas@gmail.com> <20170709132814.2339-3-marek.vasut+renesas@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20170709132814.2339-3-marek.vasut+renesas@gmail.com> List-ID: On 07/09, Marek Vasut wrote: > The output buffer input mux can be configured in either of three > states -- disabled, input from FOD, input from previous output. > If the output buffer input mux is set to disabled, the code in > vc5_clk_out_get_parent() would consider this an invalid setting > and warn about it, which is not necessarily the case. > > In case the output buffer input mux is disabled, default to input > from FOD to have some parent and don't print the warning. > > Signed-off-by: Marek Vasut > Cc: Stephen Boyd > Cc: Alexey Firago > Cc: Michael Turquette > Cc: Laurent Pinchart > Cc: linux-renesas-soc@vger.kernel.org > Tested-by: Laurent Pinchart > on Salvator-XS with the display LVDS output. > --- Applied to clk-next -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project