dri-devel February 2017

dri-devel@lists.freedesktop.org

200 participants
1445 discussions

mmap with PROT_WRITE of dma-buf FD coming from eglExportDMABUFImageMESA
by Volker Vogelhuber 02 Feb '17

02 Feb '17

Hi, I'm currently trying to mmap the memory of an OpenGL texture I've created by doing the following: std::vector<EGLint> image_attribs = { EGL_WIDTH, static_cast<int>(m_texWidth & 0x7FFFFFFF), EGL_HEIGHT, static_cast<int>(m_texHeight & 0x7FFFFFFF), EGL_DRM_BUFFER_USE_MESA, EGL_DRM_BUFFER_USE_SCANOUT_MESA, EGL_DRM_BUFFER_FORMAT_MESA, EGL_DRM_BUFFER_FORMAT_ARGB32_MESA EGL_NONE }; glGenTextures(… [View More]

2 3

[drm-intel:drm-intel-nightly 1076/1086] drivers/gpu/drm/gma500/framebuffer.c:566:8: error: too few arguments to function 'drm_fb_helper_init'
by kbuild test robot 02 Feb '17

02 Feb '17

tree: git://anongit.freedesktop.org/drm-intel drm-intel-nightly head: 0f01216949002d20b9dc6d300c82df5ffa59e9a7 commit: e4563f6ba71792c77aeccb2092cc23149b44e642 [1076/1086] drm: Rely on mode_config data for fb_helper initialization config: i386-randconfig-x0-02030244 (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: git checkout e4563f6ba71792c77aeccb2092cc23149b44e642 # save the attached .config to linux build tree make ARCH=i386 Note:… [View More] the drm-intel/drm-intel-nightly HEAD 0f01216949002d20b9dc6d300c82df5ffa59e9a7 builds fine. It only hurts bisectibility. All errors (new ones prefixed by >>): drivers/gpu/drm/gma500/framebuffer.c: In function 'psb_fbdev_init': >> drivers/gpu/drm/gma500/framebuffer.c:566:8: error: too few arguments to function 'drm_fb_helper_init' ret = drm_fb_helper_init(dev, &fbdev->psb_fb_helper, ^~~~~~~~~~~~~~~~~~ In file included from drivers/gpu/drm/gma500/framebuffer.c:35:0: include/drm/drm_fb_helper.h:309:19: note: declared here static inline int drm_fb_helper_init(struct drm_device *dev, ^~~~~~~~~~~~~~~~~~ -- drivers/gpu/drm/qxl/qxl_fb.c: In function 'qxl_fbdev_init': >> drivers/gpu/drm/qxl/qxl_fb.c:401:8: error: too few arguments to function 'drm_fb_helper_init' ret = drm_fb_helper_init(&qdev->ddev, &qfbdev->helper, ^~~~~~~~~~~~~~~~~~ In file included from drivers/gpu/drm/qxl/qxl_fb.c:35:0: include/drm/drm_fb_helper.h:309:19: note: declared here static inline int drm_fb_helper_init(struct drm_device *dev, ^~~~~~~~~~~~~~~~~~ vim +/drm_fb_helper_init +566 drivers/gpu/drm/gma500/framebuffer.c 4d8d096e9 Alan Cox 2011-11-03 560 } 4d8d096e9 Alan Cox 2011-11-03 561 4d8d096e9 Alan Cox 2011-11-03 562 dev_priv->fbdev = fbdev; 10a231026 Thierry Reding 2014-06-27 563 10a231026 Thierry Reding 2014-06-27 564 drm_fb_helper_prepare(dev, &fbdev->psb_fb_helper, &psb_fb_helper_funcs); 4d8d096e9 Alan Cox 2011-11-03 565 01934c2a6 Thierry Reding 2014-12-19 @566 ret = drm_fb_helper_init(dev, &fbdev->psb_fb_helper, e4563f6ba Gabriel Krisman Bertazi 2017-02-02 567 INTELFB_CONN_LIMIT); 01934c2a6 Thierry Reding 2014-12-19 568 if (ret) 01934c2a6 Thierry Reding 2014-12-19 569 goto free; :::::: The code at line 566 was first introduced by commit :::::: 01934c2a691882185b3021d437df13bcba07711d drm/fb-helper: Propagate errors from initial config failure :::::: TO: Thierry Reding <treding(a)nvidia.com> :::::: CC: Daniel Vetter <daniel.vetter(a)ffwll.ch> --- 0-DAY kernel test infrastructure Open Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation [View Less]

1 0

[PATCH] drm: Fix build when FBDEV_EMULATION is disabled
by Gabriel Krisman Bertazi 02 Feb '17

02 Feb '17

Commit be7f735cd5ea ("drm: Rely on mode_config data for fb_helper initialization") broke the build when CONFIG_DRM_FBDEV_EMULATION is disabled because it didn't update the prototype for drm_fb_helper_init in that case. Fixes: be7f735cd5ea ("drm: Rely on mode_config data for fb_helper initialization") Signed-off-by: Gabriel Krisman Bertazi <krisman(a)collabora.co.uk> --- include/drm/drm_fb_helper.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/drm/… [View More]

2 1

[drm-tip:drm-tip 1066/1073] drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c:376:8: error: too few arguments to function 'drm_fb_helper_init'
by kbuild test robot 02 Feb '17

02 Feb '17

tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip head: 36aab92fa2091dd54ea983752aa40e427e83d113 commit: e4563f6ba71792c77aeccb2092cc23149b44e642 [1066/1073] drm: Rely on mode_config data for fb_helper initialization config: i386-randconfig-x007-201705 (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: git checkout e4563f6ba71792c77aeccb2092cc23149b44e642 # save the attached .config to linux build tree make ARCH=i386 All errors (… [View More]

1 0

drm: panel-simple: Problems to use Seiko 43WVF1G panel and DRM_MXS driver on the i.MX6SX SabreSD.
by Breno Matheus Lima 02 Feb '17

02 Feb '17

Hi, I'm trying to use the Seiko 43WVF1G panel (Datasheet link: http://www.glyn.de/data/glyn/media/doc/43wvf1g-0.pdf) and the DRM_MXS driver on the i.MX6SX SabreSD. Applying the patch below removes the old timing configuration on the dtsi and adds it to the panel-simple.c I can get the display working, but the image is out of place. Another point to note is that it's necessary to set the reg_lcd_3v3 to regulator-always-on otherwise the gpio3 27 does not get enabled. The main two problems that … [View More]I'm having at the moment are: - Gpio3 27 is not being set by the driver, function panel_simple_prepare(struct drm_panel *panel) is not being called. - The image is displaced even when using the same timing values in the datasheet. I would like to know if I'm doing something wrong on my dtsi, or if something is missing on the panel-simple.c. I would appreciate any help. Thanks! diff --git a/arch/arm/boot/dts/imx6sx-sdb.dtsi b/arch/arm/boot/dts/imx6sx-sdb.dtsi index da81552..13fcce9 100644 --- a/arch/arm/boot/dts/imx6sx-sdb.dtsi +++ b/arch/arm/boot/dts/imx6sx-sdb.dtsi @@ -24,7 +24,7 @@ reg = <0x80000000 0x40000000>; }; - backlight { + backlight_display: backlight-display { compatible = "pwm-backlight"; pwms = <&pwm3 0 5000000>; brightness-levels = <0 4 8 16 32 64 128 255>; @@ -104,6 +104,7 @@ regulator-name = "lcd-3v3"; gpio = <&gpio3 27 0>; enable-active-high; + regulator-always-on; }; reg_peri_3v3: regulator@5 { @@ -146,6 +147,19 @@ mux-int-port = <2>; mux-ext-port = <6>; }; + + panel { + compatible = "seiko,43wvf1g", "simple-panel"; + backlight = <&backlight_display>; + + power-supply = <&reg_lcd_3v3>; + + port { + panel_in: endpoint { + remote-endpoint = <&display_out>; + }; + }; + }; }; &audmux { @@ -215,33 +229,14 @@ &lcdif1 { pinctrl-names = "default"; pinctrl-0 = <&pinctrl_lcd>; - lcd-supply = <&reg_lcd_3v3>; - display = <&display0>; status = "okay"; - display0: display0 { - bits-per-pixel = <16>; - bus-width = <24>; - - display-timings { - native-mode = <&timing0>; - timing0: timing0 { - clock-frequency = <33500000>; - hactive = <800>; - vactive = <480>; - hback-porch = <89>; - hfront-porch = <164>; - vback-porch = <23>; - vfront-porch = <10>; - hsync-len = <10>; - vsync-len = <10>; - hsync-active = <0>; - vsync-active = <0>; - de-active = <1>; - pixelclk-active = <0>; - }; + port{ + display_out: endpoint { + remote-endpoint = <&panel_in>; }; }; + }; &pwm3 { diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu/drm/panel/panel-simple.c index 06aaf79..8faefee 100644 --- a/drivers/gpu/drm/panel/panel-simple.c +++ b/drivers/gpu/drm/panel/panel-simple.c @@ -863,6 +863,31 @@ static const struct panel_desc hannstar_hsd070pww1 = { .bus_format = MEDIA_BUS_FMT_RGB666_1X7X3_SPWG, }; +static const struct display_timing seiko_43wvf1g_timing = { + .pixelclock = { 33500000, 33500000, 33500000 }, + .hactive = { 800, 800, 800 }, + .hfront_porch = { 164, 164, 164 }, + .hback_porch = { 89, 89, 89 }, + .hsync_len = { 10, 10, 10 }, + .vactive = { 480, 480, 480 }, + .vfront_porch = { 10, 10, 10 }, + .vback_porch = { 23, 23, 23 }, + .vsync_len = { 10, 10, 10 }, + .flags = DISPLAY_FLAGS_DE_HIGH | DISPLAY_FLAGS_PIXDATA_NEGEDGE | + DISPLAY_FLAGS_HSYNC_LOW | DISPLAY_FLAGS_VSYNC_LOW, +}; + +static const struct panel_desc seiko_43wvf1g = { + .timings = &seiko_43wvf1g_timing, + .num_timings = 1, + .bpc = 8, + .size = { + .width = 93, + .height = 57, + }, + .bus_format = MEDIA_BUS_FMT_RGB888_1X24, +}; + static const struct display_timing hannstar_hsd100pxn1_timing = { .pixelclock = { 55000000, 65000000, 75000000 }, .hactive = { 1024, 1024, 1024 }, @@ -1853,6 +1878,9 @@ static const struct of_device_id platform_of_match[] = { .compatible = "samsung,ltn140at29-301", .data = &samsung_ltn140at29_301, }, { + .compatible = "seiko,43wvf1g", + .data = &seiko_43wvf1g, + }, { .compatible = "sharp,lq101k1ly04", .data = &sharp_lq101k1ly04, }, { -- 2.7.4 -- Breno Matheus Lima [View Less]

4 5

[pull] radeon and amdgpu drm-fixes-4.10
by Alex Deucher 02 Feb '17

02 Feb '17

Hi Dave, Just a couple of small fixes for 4.10 The following changes since commit 52b679f60e2a68af88411f12318675a2424a0e14: Merge tag 'drm-misc-fixes-2017-01-31' of git://anongit.freedesktop.org/git/drm-misc into drm-fixes (2017-02-01 08:45:27 +1000) are available in the git repository at: git://people.freedesktop.org/~agd5f/linux drm-fixes-4.10 for you to fetch changes up to 51964e9e12d0a054002a1a0d1dec4f661c7aaf28: drm/radeon: Fix vram_size/visible values in DRM_RADEON_GEM_INFO … [View More]

1 0

[PATCH v4 0/3] Allow ASYNC flip with atomic helpers.
by Andrey Grodzovsky 02 Feb '17

02 Feb '17

This series is a folow-up on https://patchwork.kernel.org/patch/9501787/ The first patch makes changes to atomic helpers to allow for drives with ASYNC flip support to use them. Patch 2 is to use this in AMDGPU/DC. Patch 3 is possible cleanup in nouveau/kms who seems to have to duplicate the helper as we did to support ASYNC flips. v2: Resend drm/atomic: Save flip flags in drm_plane_state since the original patch was incomplete. Squash 2 AMD changes into one to not break compilation. v3: … [View More]

3 6

[PATCH 1/2] drm: sti: Prevent race on fbdev initialization
by Gabriel Krisman Bertazi 02 Feb '17

02 Feb '17

Scheduling the output_poll_work before calling bind_all to create the crtcs can race the fbdev initialization with the components initialization (i.e. crtc initialization). One side effect is that we may call drm_fbdev_cma_init with a zeroed num_crtc value, crashing the fbdev allocation. I found this while auditing the code to remove the crtc_count parameter from drm_fbdev_cma_init. I don't have the hardware to actually test this change, so it'd be better covered if someone can give a try. … [View More]

3 4

[PULL] topic/vma-fix-for-4.10
by Jani Nikula 02 Feb '17

02 Feb '17

Hi Dave, here's Maarten's backport of the vma fixes for v4.10. BR, Jani. The following changes since commit 566cf877a1fcb6d6dc0126b076aad062054c2637: Linux 4.10-rc6 (2017-01-29 14:25:17 -0800) are available in the git repository at: git://anongit.freedesktop.org/git/drm-intel tags/topic/vma-fix-for-4.10-2017-02-02 for you to fetch changes up to e8fe4f4b2b7b93048729538321c681c0cff33b39: drm/i915: Track pinned vma in intel_plane_state (2017-02-01 11:45:21 +0200) ---------------------… [View More]

1 0

[PATCH] drm/i915: fix i915 running as dom0 under Xen
by Juergen Gross 02 Feb '17

02 Feb '17

Commit 920cf4194954ec ("drm/i915: Introduce an internal allocator for disposable private objects") introduced a regression for the kernel running as Xen dom0: when switching to graphics mode a GPU HANG occurred. Reason seems to be a missing adaption similar to that done in commit 7453c549f5f648 ("swiotlb: Export swiotlb_max_segment to users") to i915_gem_object_get_pages_internal(). So limit the maximum page order to be used according to the maximum swiotlb segment size instead to the … [View More]

4 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel February 2017