On Mon, 16 Jan 2012 13:56:34 -0800
Keith Packard wrote:
> On Mon, 16 Jan 2012 21:21:45 +0100, Daniel Vetter wrote:
> > On Mon, Jan 16, 2012 at 12:20:03PM -0800, Jesse Barnes wrote:
>
> > > Yeah looks like a good cleanup that also makes downclocking more likely.
> > >
> > > Reviewed-by: Jesse B
On Mon, 16 Jan 2012 21:21:45 +0100, Daniel Vetter wrote:
> On Mon, Jan 16, 2012 at 12:20:03PM -0800, Jesse Barnes wrote:
> > Yeah looks like a good cleanup that also makes downclocking more likely.
> >
> > Reviewed-by: Jesse Barnes
>
> Queued for -next, thanks for the patch.
Jesse -- do you t
On Mon, Jan 16, 2012 at 12:20:03PM -0800, Jesse Barnes wrote:
> On Tue, 10 Jan 2012 15:09:36 -0800
> Sean Paul wrote:
>
> > This patch enforces that the downclock clock source is the same as the
> > preferred
> > clock source for LVDS. This fixes a bug where the driver chooses a downclock
> > cl
On Tue, 10 Jan 2012 15:09:36 -0800
Sean Paul wrote:
> This patch enforces that the downclock clock source is the same as the
> preferred
> clock source for LVDS. This fixes a bug where the driver chooses a downclock
> clock source with a different P than the preferred mode clock source. This
> h
This patch enforces that the downclock clock source is the same as the preferred
clock source for LVDS. This fixes a bug where the driver chooses a downclock
clock source with a different P than the preferred mode clock source. This
happened even if the preferred clock source implemented an accepta
