On Wed, Feb 6, 2019 at 10:12 PM Maxime Ripard wrote:
>
> Hi Chen-Yu,
>
> On Wed, Feb 06, 2019 at 12:48:21AM +0800, Chen-Yu Tsai wrote:
> > On Wed, Jan 30, 2019 at 11:23 AM Chen-Yu Tsai wrote:
> > >
> > > On Wed, Jan 23, 2019 at 11:54 PM Maxime Ripard
> > > wrote:
> > > >
> > > > The current
Hi Chen-Yu,
On Wed, Feb 06, 2019 at 12:48:21AM +0800, Chen-Yu Tsai wrote:
> On Wed, Jan 30, 2019 at 11:23 AM Chen-Yu Tsai wrote:
> >
> > On Wed, Jan 23, 2019 at 11:54 PM Maxime Ripard
> > wrote:
> > >
> > > The current calculation for the video start delay in the current DSI
> > > driver
> > >
On Wed, Jan 30, 2019 at 11:23 AM Chen-Yu Tsai wrote:
>
> On Wed, Jan 23, 2019 at 11:54 PM Maxime Ripard
> wrote:
> >
> > The current calculation for the video start delay in the current DSI driver
> > is that it is the total vertical size, minus the backporch and sync length,
> > plus 1.
> >
> >
On Wed, Jan 23, 2019 at 11:54 PM Maxime Ripard
wrote:
>
> The current calculation for the video start delay in the current DSI driver
> is that it is the total vertical size, minus the backporch and sync length,
> plus 1.
>
> However, the Allwinner code has it as the active vertical size, plus
Hi,
On Wed, 2019-01-23 at 16:54 +0100, Maxime Ripard wrote:
> The current calculation for the video start delay in the current DSI driver
> is that it is the total vertical size, minus the backporch and sync length,
> plus 1.
>
> However, the Allwinner code has it as the active vertical size,
The current calculation for the video start delay in the current DSI driver
is that it is the total vertical size, minus the backporch and sync length,
plus 1.
However, the Allwinner code has it as the active vertical size, plus the
back porch and the sync length. This doesn't make any difference
