On Fri, Jun 21, 2019 at 2:51 AM Jagan Teki wrote:
>
> On Tue, Jun 18, 2019 at 8:15 PM Chen-Yu Tsai wrote:
> >
> > On Tue, Jun 18, 2019 at 8:11 PM Jagan Teki
> > wrote:
> > >
> > > On Tue, Jun 18, 2019 at 5:13 PM Chen-Yu Tsai wrote:
> > > >
> > > > On Tue, Jun 18, 2019 at 6:51 PM Jagan Teki
>
On Tue, Jun 18, 2019 at 8:15 PM Chen-Yu Tsai wrote:
>
> On Tue, Jun 18, 2019 at 8:11 PM Jagan Teki wrote:
> >
> > On Tue, Jun 18, 2019 at 5:13 PM Chen-Yu Tsai wrote:
> > >
> > > On Tue, Jun 18, 2019 at 6:51 PM Jagan Teki
> > > wrote:
> > > >
> > > > On Fri, Jun 14, 2019 at 8:15 PM Maxime Ripar
On Tue, Jun 18, 2019 at 8:11 PM Jagan Teki wrote:
>
> On Tue, Jun 18, 2019 at 5:13 PM Chen-Yu Tsai wrote:
> >
> > On Tue, Jun 18, 2019 at 6:51 PM Jagan Teki
> > wrote:
> > >
> > > On Fri, Jun 14, 2019 at 8:15 PM Maxime Ripard
> > > wrote:
> > > >
> > > > On Fri, Jun 14, 2019 at 12:03:13PM +05
On Tue, Jun 18, 2019 at 5:13 PM Chen-Yu Tsai wrote:
>
> On Tue, Jun 18, 2019 at 6:51 PM Jagan Teki wrote:
> >
> > On Fri, Jun 14, 2019 at 8:15 PM Maxime Ripard
> > wrote:
> > >
> > > On Fri, Jun 14, 2019 at 12:03:13PM +0530, Jagan Teki wrote:
> > > > On Thu, Jun 13, 2019 at 6:56 PM Maxime Ripar
On Tue, Jun 18, 2019 at 6:51 PM Jagan Teki wrote:
>
> On Fri, Jun 14, 2019 at 8:15 PM Maxime Ripard
> wrote:
> >
> > On Fri, Jun 14, 2019 at 12:03:13PM +0530, Jagan Teki wrote:
> > > On Thu, Jun 13, 2019 at 6:56 PM Maxime Ripard
> > > wrote:
> > > >
> > > > On Wed, Jun 05, 2019 at 01:17:11PM +
On Fri, Jun 14, 2019 at 8:15 PM Maxime Ripard wrote:
>
> On Fri, Jun 14, 2019 at 12:03:13PM +0530, Jagan Teki wrote:
> > On Thu, Jun 13, 2019 at 6:56 PM Maxime Ripard
> > wrote:
> > >
> > > On Wed, Jun 05, 2019 at 01:17:11PM +0530, Jagan Teki wrote:
> > > > On Tue, Jun 4, 2019 at 3:30 PM Maxime
On Fri, Jun 14, 2019 at 12:03:13PM +0530, Jagan Teki wrote:
> On Thu, Jun 13, 2019 at 6:56 PM Maxime Ripard
> wrote:
> >
> > On Wed, Jun 05, 2019 at 01:17:11PM +0530, Jagan Teki wrote:
> > > On Tue, Jun 4, 2019 at 3:30 PM Maxime Ripard
> > > wrote:
> > > >
> > > > On Wed, May 29, 2019 at 11:44:
On Thu, Jun 13, 2019 at 6:56 PM Maxime Ripard wrote:
>
> On Wed, Jun 05, 2019 at 01:17:11PM +0530, Jagan Teki wrote:
> > On Tue, Jun 4, 2019 at 3:30 PM Maxime Ripard
> > wrote:
> > >
> > > On Wed, May 29, 2019 at 11:44:56PM +0530, Jagan Teki wrote:
> > > > On Wed, May 29, 2019 at 8:24 PM Maxime
On Wed, Jun 05, 2019 at 01:17:11PM +0530, Jagan Teki wrote:
> On Tue, Jun 4, 2019 at 3:30 PM Maxime Ripard
> wrote:
> >
> > On Wed, May 29, 2019 at 11:44:56PM +0530, Jagan Teki wrote:
> > > On Wed, May 29, 2019 at 8:24 PM Maxime Ripard
> > > wrote:
> > > >
> > > > On Fri, May 24, 2019 at 03:48:
On Tue, Jun 4, 2019 at 3:30 PM Maxime Ripard wrote:
>
> On Wed, May 29, 2019 at 11:44:56PM +0530, Jagan Teki wrote:
> > On Wed, May 29, 2019 at 8:24 PM Maxime Ripard
> > wrote:
> > >
> > > On Fri, May 24, 2019 at 03:48:51PM +0530, Jagan Teki wrote:
> > > > On Fri, May 24, 2019 at 2:04 AM Maxime
On Wed, May 29, 2019 at 11:44:56PM +0530, Jagan Teki wrote:
> On Wed, May 29, 2019 at 8:24 PM Maxime Ripard
> wrote:
> >
> > On Fri, May 24, 2019 at 03:48:51PM +0530, Jagan Teki wrote:
> > > On Fri, May 24, 2019 at 2:04 AM Maxime Ripard
> > > wrote:
> > > >
> > > > On Mon, May 20, 2019 at 02:33
On Wed, May 29, 2019 at 8:24 PM Maxime Ripard wrote:
>
> On Fri, May 24, 2019 at 03:48:51PM +0530, Jagan Teki wrote:
> > On Fri, May 24, 2019 at 2:04 AM Maxime Ripard
> > wrote:
> > >
> > > On Mon, May 20, 2019 at 02:33:08PM +0530, Jagan Teki wrote:
> > > > According to "DRM kernel-internal disp
On Fri, May 24, 2019 at 03:48:51PM +0530, Jagan Teki wrote:
> On Fri, May 24, 2019 at 2:04 AM Maxime Ripard
> wrote:
> >
> > On Mon, May 20, 2019 at 02:33:08PM +0530, Jagan Teki wrote:
> > > According to "DRM kernel-internal display mode structure" in
> > > include/drm/drm_modes.h the current dri
On Fri, May 24, 2019 at 2:04 AM Maxime Ripard wrote:
>
> On Mon, May 20, 2019 at 02:33:08PM +0530, Jagan Teki wrote:
> > According to "DRM kernel-internal display mode structure" in
> > include/drm/drm_modes.h the current driver is trying to include
> > sync timings along with front porch value wh
On Mon, May 20, 2019 at 02:33:08PM +0530, Jagan Teki wrote:
> According to "DRM kernel-internal display mode structure" in
> include/drm/drm_modes.h the current driver is trying to include
> sync timings along with front porch value while checking and
> computing drq set bits in non-burst mode.
>
>
According to "DRM kernel-internal display mode structure" in
include/drm/drm_modes.h the current driver is trying to include
sync timings along with front porch value while checking and
computing drq set bits in non-burst mode.
mode->hsync_end - mode->hdisplay => horizontal front porch + sync
Wit
16 matches
Mail list logo