On Fri, Nov 23, 2018 at 01:48:08PM +0200, Laurent Pinchart wrote:
> Group start/stop is controlled by the DRES and DEN bits of DSYSR0 for
> the first group and DSYSR2 for the second group. On most DU instances,
> this maps to the first CRTC of the group. On M3-N, however, DU2 doesn't
> exist, but
Dear Laurent-san
Thank you for your comments on my patches! I understand.
With this patch, the problem has been improved.
CC Simon-san
If you wait a little longer, the error log will look like this:
[ 2.825800] [drm] No driver support for vblank timestamp query.
[ 13.027591]
Hello Hoan-san,
On Monday, 26 November 2018 11:46:56 EET Hoan wrote:
> Dear Laurent-san
>
> Thank you for your comments on my patches! I understand.
>
> With this patch, the problem has been improved.
>
> CC Simon-san
>
> If you wait a little longer, the error log will look like this:
There
Hi Laurent,
Thank you for the patch.
On 23/11/2018 11:48, Laurent Pinchart wrote:
> Group start/stop is controlled by the DRES and DEN bits of DSYSR0 for
> the first group and DSYSR2 for the second group. On most DU instances,
> this maps to the first CRTC of the group. On M3-N, however, DU2
Group start/stop is controlled by the DRES and DEN bits of DSYSR0 for
the first group and DSYSR2 for the second group. On most DU instances,
this maps to the first CRTC of the group. On M3-N, however, DU2 doesn't
exist, but DSYSR2 does. There is no CRTC object there that maps to the
correct DSYSR
