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. > Once the .prepare() callback of the output buffer is called, the > output buffer input mux must be set to either input from FOD or > input from previous output, it cannot be set to Disabled anymore > or the output won't work. > > Default to the input from FOD if the output buffer input mux was > Disabled and the .prepare() was called on it. > > Note that we do not set the output buffer input mux back to Disabled > in the .unprepare() callback as there is no obvious benefit of doing > so. We disable the entire output buffer in the .unprepare() callback > already. > > Signed-off-by: Marek Vasut <marek.vasut+rene...@gmail.com> > Cc: Stephen Boyd <sb...@codeaurora.org> > Cc: Alexey Firago <alexey_fir...@mentor.com> > Cc: Michael Turquette <mturque...@baylibre.com> > Cc: Laurent Pinchart <laurent.pinch...@ideasonboard.com> > Cc: linux-renesas-soc@vger.kernel.org > Tested-by: Laurent Pinchart <laurent.pinch...@ideasonboard.com> > 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
