Displaying 11 results from an estimated 11 matches for "mipi_dsi_device".
2020 Feb 26
2
(no subject)
...in command mode mode->clock should probably be the actual
> > dotclock used by the display. If there's another clock for the bus
> > speed/etc. it should be stored somewhere else.
>
> Good point. For the DSI panels we have the field hs_rate
> for the HS clock in struct mipi_dsi_device which is based
> on exactly this reasoning. And that is what I actually use for
> setting the HS clock.
>
> The problem is however that we in many cases have so
> substandard documentation of these panels that we have
> absolutely no idea about the dotclock. Maybe we should
>...
2020 Feb 26
2
(no subject)
Subject: Re: [PATCH 04/12] drm: Nuke mode->vrefresh
Message-ID: <20200226115708.GH13686 at intel.com>
References: <20200219203544.31013-1-ville.syrjala at linux.intel.com>
<CGME20200219203620eucas1p24b4990a91e758dbcf3e9b943669b0c8f at eucas1p2.samsung.com>
<20200219203544.31013-5-ville.syrjala at linux.intel.com>
<0f278771-79ce-fe23-e72c-3935dbe82d24 at
2020 Feb 26
0
(no subject)
...side.
>
> IMO even in command mode mode->clock should probably be the actual
> dotclock used by the display. If there's another clock for the bus
> speed/etc. it should be stored somewhere else.
Good point. For the DSI panels we have the field hs_rate
for the HS clock in struct mipi_dsi_device which is based
on exactly this reasoning. And that is what I actually use for
setting the HS clock.
The problem is however that we in many cases have so
substandard documentation of these panels that we have
absolutely no idea about the dotclock. Maybe we should
just set it to 0 in these cases?
Y...
2020 Feb 26
0
(no subject)
...t;clock should probably be the actual
> > > dotclock used by the display. If there's another clock for the bus
> > > speed/etc. it should be stored somewhere else.
> >
> > Good point. For the DSI panels we have the field hs_rate
> > for the HS clock in struct mipi_dsi_device which is based
> > on exactly this reasoning. And that is what I actually use for
> > setting the HS clock.
> >
> > The problem is however that we in many cases have so
> > substandard documentation of these panels that we have
> > absolutely no idea about the do...
2020 Feb 25
2
[PATCH 04/12] drm: Nuke mode->vrefresh
...%u@%u\n",
> > default_mode.hdisplay, default_mode.vdisplay,
> > - default_mode.vrefresh);
> > + drm_mode_vrefresh(&default_mode));
> > return -ENOMEM;
> > }
> >
> > @@ -360,7 +359,7 @@ static int jh057n_probe(struct mipi_dsi_device *dsi)
> >
> > DRM_DEV_INFO(dev, "%ux%u@%u %ubpp dsi %udl - ready\n",
> > default_mode.hdisplay, default_mode.vdisplay,
> > - default_mode.vrefresh,
> > + drm_mode_vrefresh(&default_mode),
> > mipi_dsi_pixel_format_to_...
2020 Feb 24
0
[PATCH 04/12] drm: Nuke mode->vrefresh
...t;dev, "Failed to add mode %ux%u@%u\n",
> default_mode.hdisplay, default_mode.vdisplay,
> - default_mode.vrefresh);
> + drm_mode_vrefresh(&default_mode));
> return -ENOMEM;
> }
>
> @@ -360,7 +359,7 @@ static int jh057n_probe(struct mipi_dsi_device *dsi)
>
> DRM_DEV_INFO(dev, "%ux%u@%u %ubpp dsi %udl - ready\n",
> default_mode.hdisplay, default_mode.vdisplay,
> - default_mode.vrefresh,
> + drm_mode_vrefresh(&default_mode),
> mipi_dsi_pixel_format_to_bpp(dsi->format), dsi->l...
2020 Feb 25
0
[PATCH 04/12] drm: Nuke mode->vrefresh
...t;> default_mode.hdisplay, default_mode.vdisplay,
>>> - default_mode.vrefresh);
>>> + drm_mode_vrefresh(&default_mode));
>>> return -ENOMEM;
>>> }
>>>
>>> @@ -360,7 +359,7 @@ static int jh057n_probe(struct mipi_dsi_device *dsi)
>>>
>>> DRM_DEV_INFO(dev, "%ux%u@%u %ubpp dsi %udl - ready\n",
>>> default_mode.hdisplay, default_mode.vdisplay,
>>> - default_mode.vrefresh,
>>> + drm_mode_vrefresh(&default_mode),
>>> mipi_ds...
2020 Feb 19
5
[PATCH 04/12] drm: Nuke mode->vrefresh
...f (!mode) {
DRM_DEV_ERROR(ctx->dev, "Failed to add mode %ux%u@%u\n",
default_mode.hdisplay, default_mode.vdisplay,
- default_mode.vrefresh);
+ drm_mode_vrefresh(&default_mode));
return -ENOMEM;
}
@@ -360,7 +359,7 @@ static int jh057n_probe(struct mipi_dsi_device *dsi)
DRM_DEV_INFO(dev, "%ux%u@%u %ubpp dsi %udl - ready\n",
default_mode.hdisplay, default_mode.vdisplay,
- default_mode.vrefresh,
+ drm_mode_vrefresh(&default_mode),
mipi_dsi_pixel_format_to_bpp(dsi->format), dsi->lanes);
jh057n_debugfs_init...
2020 Apr 04
0
[PATCH v2 03/17] drm: Nuke mode->vrefresh
...gt;dev, "Failed to add mode %ux%u@%u\n",
> default_mode.hdisplay, default_mode.vdisplay,
> - default_mode.vrefresh);
> + drm_mode_vrefresh(&default_mode));
> return -ENOMEM;
> }
>
> @@ -360,7 +359,7 @@ static int jh057n_probe(struct mipi_dsi_device
> *dsi)
>
> DRM_DEV_INFO(dev, "%ux%u@%u %ubpp dsi %udl - ready\n",
> default_mode.hdisplay, default_mode.vdisplay,
> - default_mode.vrefresh,
> + drm_mode_vrefresh(&default_mode),
> mipi_dsi_pixel_format_to_bpp(dsi->format), dsi-...
2020 Apr 28
0
[PATCH v3 03/16] drm: Nuke mode->vrefresh
...f (!mode) {
DRM_DEV_ERROR(ctx->dev, "Failed to add mode %ux%u@%u\n",
default_mode.hdisplay, default_mode.vdisplay,
- default_mode.vrefresh);
+ drm_mode_vrefresh(&default_mode));
return -ENOMEM;
}
@@ -360,7 +359,7 @@ static int jh057n_probe(struct mipi_dsi_device *dsi)
DRM_DEV_INFO(dev, "%ux%u@%u %ubpp dsi %udl - ready\n",
default_mode.hdisplay, default_mode.vdisplay,
- default_mode.vrefresh,
+ drm_mode_vrefresh(&default_mode),
mipi_dsi_pixel_format_to_bpp(dsi->format), dsi->lanes);
jh057n_debugfs_init...
2020 Apr 03
3
[PATCH v2 03/17] drm: Nuke mode->vrefresh
...f (!mode) {
DRM_DEV_ERROR(ctx->dev, "Failed to add mode %ux%u@%u\n",
default_mode.hdisplay, default_mode.vdisplay,
- default_mode.vrefresh);
+ drm_mode_vrefresh(&default_mode));
return -ENOMEM;
}
@@ -360,7 +359,7 @@ static int jh057n_probe(struct mipi_dsi_device *dsi)
DRM_DEV_INFO(dev, "%ux%u@%u %ubpp dsi %udl - ready\n",
default_mode.hdisplay, default_mode.vdisplay,
- default_mode.vrefresh,
+ drm_mode_vrefresh(&default_mode),
mipi_dsi_pixel_format_to_bpp(dsi->format), dsi->lanes);
jh057n_debugfs_init...