On Tue, May 17, 2016 at 01:18:44AM +0800, Chen-Yu Tsai wrote:
Hi,
On Mon, May 16, 2016 at 8:47 PM, Maxime Ripard maxime.ripard@free-electrons.com wrote:
The pixel clock being only a divider of its parent clock, depending on the resolution, it's expected to change its parent rate. Add that flag so that the clock framework knows it.
This should be squashed into the previous patch. Otherwise, the previous one doesn't really fix things, and probably makes things worse as it assumes the parent clock would be changed.
Merged the two patches and applied, thanks! Maxime