Hi Geert.
On Thu, Jan 02, 2020 at 03:12:45PM +0100, Geert Uytterhoeven wrote:
> If the resolution of the TFT display is smaller than the maximum
> resolution supported by the display controller, the display may be
> connected to the driver output arrays with a horizontal and/or vertical
> offset,
Hi Geert.
Good to see we add more functionality to the smallest driver in DRM.
The patch triggered a few comments - see below.
Some comments relates to the original driver - and not your changes.
Sam
On Thu, Jan 02, 2020 at 03:12:46PM +0100, Geert Uytterhoeven wrote:
> Add support for th
Hi Jitao.
On Sat, Oct 12, 2019 at 11:07:12AM +0800, Jitao Shi wrote:
> Changes since v6:
> - fix boe_panel_init err uninit.
> - adjust the delay of backlight on.
>
> Changes since v5:
> - covert the documents to yaml
> - fine tune boe, tv101wum-n53 panel video timine
I finally found some tim
Hi Jitao.
On Sat, Oct 12, 2019 at 11:07:14AM +0800, Jitao Shi wrote:
> Add driver for BOE tv101wum-nl6 panel is a 10.1" 1200x1920 panel.
>
> Signed-off-by: Jitao Shi
> Reviewed-by: Sam Ravnborg
> ---
> +
> +struct boe_panel {
> + struct drm_panel base;
> + struct mipi_dsi_device *dsi;
Hi Jitao.
A few comments in the following.
Sam
On Sat, Oct 12, 2019 at 11:07:16AM +0800, Jitao Shi wrote:
> Auo,kd101n80-45na's connector is same as boe,tv101wum-nl6.
> The most codes can be reuse.
> So auo,kd101n80-45na and boe,tv101wum-nl6 use one driver file.
> Add the different parts
Hi Jitao.
Looks good.
On Sat, Oct 12, 2019 at 11:07:18AM +0800, Jitao Shi wrote:
> Boe,tv101wum-n53's connector is same as boe,tv101wum-nl6.
> The most codes can be reuse.
> So boe,tv101wum-n53 and boe,tv101wum-nl6 use one driver file.
> Add the different parts in driver data.
>
> Signed-off-by:
Hi Jitao.
Looks good.
On Sat, Oct 12, 2019 at 11:07:20AM +0800, Jitao Shi wrote:
> Auo,auo,b101uan08.3's connector is same as boe,tv101wum-nl6.
> The most codes can be reuse.
> So auo,b101uan08.3 and boe,tv101wum-nl6 use one driver file.
> Add the different parts in driver data.
>
> Signed-off-b
https://bugzilla.kernel.org/show_bug.cgi?id=206017
--- Comment #6 from udo (udo...@xs4all.nl) ---
5.4.8 also suffers from the hard hang, Firefox is involded playing youtube and
such.
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
https://bugzilla.kernel.org/show_bug.cgi?id=206017
--- Comment #7 from udo (udo...@xs4all.nl) ---
And it happened again, without youtube playing but while browsing.
5.3.18 takes a lot longer to crash/hang or whatever.
--
You are receiving this mail because:
You are watching the assignee of the b
Am Dienstag, 24. Dezember 2019, 15:38:49 CET schrieb Miquel Raynal:
> Hello,
>
> This series aims at supporting LVDS on PX30.
>
> A first couple of patches update the documentation with the new
> compatible and the presence of a PHY. Then, the existing Rockchip
> driver is cleaned and extended to
https://bugzilla.kernel.org/show_bug.cgi?id=206017
--- Comment #8 from udo (udo...@xs4all.nl) ---
Does the screen corruption I see now and then have something to do with this
issue?
--
You are receiving this mail because:
You are watching the assignee of the bug.
Hi,
On 03-01-2020 20:38, Rodrigo Vivi wrote:
On Mon, Dec 16, 2019 at 12:51:58PM +0100, Hans de Goede wrote:
If the new video=... panel_orientation option is set for a connector, honor
it and setup a matching "panel orientation" property on the connector.
BugLink: https://gitlab.freedesktop.org
From: Derek Basehore
Not every platform needs quirk detection for panel orientation, so
split the drm_connector_init_panel_orientation_property into two
functions. One for platforms without the need for quirks, and the
other for platforms that need quirks.
Hans de Goede (changes in v2):
Rename
If the new video=... panel_orientation option is set for a connector, honor
it and setup a matching "panel orientation" property on the connector.
Changes in v2:
-Improve DRM_INFO message to make it clear that the panel_orientation is
being forced from the commandline
BugLink: https://gitlab.fre
Hi!
It would be good to get LED backlight to work in clean way for 5.6
kernel.
As far as I can see, these are neccessary (but not enough; it does not
work for me): lm3532 changes to register LED with of node, plus device
tree changes for droid 4, and these generic changes:
commit d457d0c97d6d55f
On Thu, 2 Jan 2020 at 04:48, Daniel Vetter wrote:
>
> On Tue, Dec 31, 2019 at 11:56:07PM +0300, Wambui Karuga wrote:
> > The local variable `pclks` is defined and set but not used and can
> > therefore be removed.
> > Issue found by coccinelle.
> >
> > Signed-off-by: Wambui Karuga
> > ---
> > dr
On Thu, 2 Jan 2020 at 04:51, Daniel Vetter wrote:
>
> On Tue, Dec 31, 2019 at 11:57:34PM +0300, Wambui Karuga wrote:
> > Replace the use of 0 in the pointer assignment with NULL to address the
> > following sparse warning:
> > drivers/gpu/drm/nouveau/nouveau_hwmon.c:744:29: warning: Using plain
>
Hi!
> > It would be good to get LED backlight to work in clean way for 5.6
> > kernel.
>
> I agree, this is badly needed for many devices.
>
> > [If you have an idea what else is needed, it would be welcome; it
> > works for me in development tree but not in tree I'd like to
> > upstream.]
>
>
Hi!
> > It would be good to get LED backlight to work in clean way for 5.6
> > kernel.
>
> I agree, this is badly needed for many devices.
>
> > [If you have an idea what else is needed, it would be welcome; it
> > works for me in development tree but not in tree I'd like to
> > upstream.]
>
>
Hi Paul.
On Mon, Dec 02, 2019 at 04:41:23PM +0100, Paul Cercueil wrote:
> The FRD350H54004 is a simple 3.5" 320x240 24-bit TFT panel, found for
> instance inside the Anbernic RG-350 handheld gaming console.
>
> v2: Order alphabetically
>
> Signed-off-by: Paul Cercueil
> ---
> drivers/gpu/drm/p
On Mon, 30 Dec 2019 at 12:48, YueHaibing wrote:
>
> match_string() returns the array index of a matching string.
> Use it instead of the open-coded implementation.
>
> Signed-off-by: YueHaibing
Thanks!
> ---
> drivers/gpu/drm/nouveau/dispnv04/tvnv17.c | 13 +
> 1 file changed, 5 ins
On Fri, 3 Jan 2020 at 05:29, Wambui Karuga wrote:
>
> Explicitly declare constants as unsigned long long to address the
> following sparse warnings:
> warning: constant is so big it is long
>
> v2: convert to unsigned long long for compatibility with 32-bit
> architectures.
>
> Signed-off-by: Wamb
On Tue, 17 Dec 2019 at 10:57, James Jones wrote:
>
> Turing introduced a new simplified page kind
> scheme, reducing the number of possible page
> kinds from 256 to 16. It also is the first
> NVIDIA GPU in which the highest possible page
> kind value is not reserved as an "invalid" page
> kind.
>
On Tue, 17 Dec 2019 at 10:45, James Jones wrote:
>
> Make sure framebuffer dimensions and tiling
> parameters will not result in accesses beyond the
> end of the GEM buffer they are bound to.
>
> Signed-off-by: James Jones
> ---
> drivers/gpu/drm/nouveau/nouveau_display.c | 93 ++
On Tue, 17 Dec 2019 at 10:44, James Jones wrote:
>
> This series modifies the NV5x+ nouveau display backends to advertise
> appropriate format modifiers on their display planes in atomic mode
> setting blobs.
>
> Corresponding modifications to Mesa/userspace are available here:
>
> https://gitlab.
Hi, Fabien:
On Fri, 2020-01-03 at 15:24 +0100, Fabien Parent wrote:
> Fix indentation in the Makefile by replacing spaces with tabs.
>
Applied to mediatek-drm-next-5.6 [1], thanks.
[1]
https://github.com/ckhu-mediatek/linux.git-tags/commits/mediatek-drm-next-5.6
Regards,
cK
> Signed-off-by: F
[AMD Public Use]
> -原始郵件-
> 寄件者: Lyude Paul
> 寄件日期: Saturday, January 4, 2020 4:35 AM
> 收件者: Lin, Wayne ; dri-
> de...@lists.freedesktop.org; amd-...@lists.freedesktop.org
> 副本: Kazlauskas, Nicholas ; Wentland,
> Harry ; Lipski, Mikita ;
> Zuo, Jerry ; sta...@vger.kernel.org
> 主旨: Re: [
On Fri, 27 Dec 2019 15:41:24 +0100
Boris Brezillon wrote:
> Commit 05193dc38197 ("drm/bridge: Make the bridge chain a double-linked
> list") patched the bridge chain logic to use a double-linked list instead
> of a single-linked list. This change induced changes to the Exynos driver
> which was m
Fix inconsistent IS_ERR and PTR_ERR in intel_modeset_all_tiles().
The proper pointer to be passed as argument is crtc_state.
This bug was detected with the help of Coccinelle.
Fixes: a603f5bd1691 ("drm/i915/dp: Make sure all tiled connectors get added to
the state with full modeset")
Signed-off
29 matches
Mail list logo