[patch] drm/virtio: checking for NULL instead of IS_ERR

virtio_gpu_alloc_object() returns an error pointer, it never returns NULL. Fixes: dc5698e80cf7 ('Add virtio gpu driver.') Signed-off-by: Dan Carpenter diff --git a/drivers/gpu/drm/virtio/virtgpu_fb.c b/drivers/gpu/drm/virtio/virtgpu_fb.c index 25bf333..df198d9 100644 ---

[Bug 90264] [Regression, bisected] Tooltip corruption in Chrome

is mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/9192862c/attachment.html>

[Bug 90264] [Regression, bisected] Tooltip corruption in Chrome

se, so those were my starting points for bisection.) -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/183209ba/attachment.html>

[PATCH v10 00/17] drm/exynos: atomic modesetting support

On 2015년 06월 10일 20:38, Marek Szyprowski wrote: > Hello, > > On 2015-06-10 12:59, Inki Dae wrote: >> Hi Marek, >> >> On 2015년 06월 10일 19:03, Marek Szyprowski wrote: >>> Hello, >>> >>> On 2015-06-01 17:04, Gustavo Padovan wrote: From: Gustavo Padovan Hi, Here

[Bug 90264] [Regression, bisected] Tooltip corruption in Chrome

are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/909b590f/attachment.html>

[PATCH 00/21] On-demand device registration

Am 10.06.2015 um 14:23 schrieb Andrzej Hajda: > On 06/10/2015 12:19 PM, Tomeu Vizoso wrote: >> On 10 June 2015 at 09:30, Linus Walleij wrote: >>> On Tue, Jun 2, 2015 at 12:14 PM, Tomeu Vizoso >>> wrote: On 2 June 2015 at 10:48, Linus Walleij wrote: >>> > This is what systemd is doing

[PATCH v10 00/17] drm/exynos: atomic modesetting support

Hi Marek, On 2015년 06월 10일 19:03, Marek Szyprowski wrote: > Hello, > > On 2015-06-01 17:04, Gustavo Padovan wrote: >> From: Gustavo Padovan >> >> Hi, >> >> Here goes the full support for atomic modesetting on exynos. I've >> split the patches in the various phases of atomic support. > >

[Bug 90264] [Regression, bisected] Tooltip corruption in Chrome

), but no > later than 324987 (first known bad). -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/c272e6ee/attachment-0001.html>

[PATCH 9/9] drm/exynos: unify exynos_drm_plane names with drm core

On 2015년 06월 10일 19:42, Inki Dae wrote: > Hi Gustavo, > > On 2015년 06월 09일 23:27, Gustavo Padovan wrote: >> Hi Inki and Joonyoung, >> >> Any comments on this series? > > As you may know, I'm reviewing and testing iommu support patch series > posted by Marek. With the patch series, I

[Bug 90264] [Regression, bisected] Tooltip corruption in Chrome

are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/9ae71f8f/attachment.html>

[PATCH 9/9] drm/exynos: unify exynos_drm_plane names with drm core

Hi Gustavo, On 2015년 06월 09일 23:27, Gustavo Padovan wrote: > Hi Inki and Joonyoung, > > Any comments on this series? As you may know, I'm reviewing and testing iommu support patch series posted by Marek. With the patch series, I faced with page fault issue while booting like below, [

[PATCH] drm/bochs: convert bochs driver to atomic mode-setting

wang Zhao > Microprocessor Research and Develop Center > Department of Computer Science > Peking University > Beijing, 100871, PRC > -- Best regards Junwang Zhao Microprocessor Research and Develop Center Department of Computer Science Peking University Beijing, 100871, PRC -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/b9c77032/attachment.html>

[Bug 90264] [Regression, bisected] Tooltip corruption in Chrome

-- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/74f56bc1/attachment.html>

[Bug 89713] [radeon]GPU lockup in World of Tanks with gallium nine

localhost kernel: radeon :01:00.0: Wait for MC idle timedout ! -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/0ca42

[PATCH 9/9] drm/exynos: unify exynos_drm_plane names with drm core

On 06/09/2015 11:27 PM, Gustavo Padovan wrote: > Hi Inki and Joonyoung, > > Any comments on this series? I saw this series in brief and good mostly. I feel it can be better to split a atomic patch and cleanup patches, it can make to merge easier. It's problem to give late any feedback about

[PATCH 2/9] drm/exynos: add atomic asynchronous commit

On 06/03/2015 11:30 PM, Gustavo Padovan wrote: > From: Gustavo Padovan > > The atomic modesetting interfaces supports async commits that should be > implemented by the drivers. If drm core requests an async commit > exynos_atomic_commit() will schedule a work task to run the update later. > It

[PATCH v3 2/2] drm/panel: Add display timing for Okaya RS800480T-7X0GP

Add support for the Okaya RS800480T-7X0GP to the DRM simple panel driver. The RS800480T-7X0GP is a WVGA (800x480) panel with an 18-bit parallel LCD interface. It supports pixel clocks in the range of 30-40 MHz. This panel details can be found at:

[PATCH v3 1/2] of: add Okaya Electric America vendor prefix

This patch adds vendor prefix for Okaya Electronic America, a provider of LCD modules and display technologies. Signed-off-by: Gary Bisson --- Documentation/devicetree/bindings/vendor-prefixes.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v3 0/2] Add display timing for Okaya RS800480T-7X0

Hi all, This patch is the follow-up of a request from Philipp to add the Okaya display to the simple panel driver. http://lists.infradead.org/pipermail/linux-arm-kernel/2015-May/346657.html v2: - split into 2 patches, adding Okaya to the vendor prefixes should be its own patch as suggested by

drm/amdgpu: Add initial VI support

Hello Alex Deucher, The patch aaa36a976bbb: "drm/amdgpu: Add initial VI support" from Apr 20, 2015, leads to the following static checker warning: drivers/gpu/drm/amd/amdgpu/gmc_v8_0.c:260 gmc_v8_0_mc_load_microcode() warn: we tested 'running' before and it was 'false'

drm/amdgpu: add core driver (v4)

Hello Alex Deucher, This is a semi-automatic email about new static checker warnings. The patch d38ceaf99ed0: "drm/amdgpu: add core driver (v4)" from Apr 20, 2015, leads to the following Smatch complaint: drivers/gpu/drm/amd/amdgpu/atombios_i2c.c:68 amdgpu_atombios_i2c_process_i2c_ch()

[PATCH 1/1 linux-next] drm: atmel-hlcdc: use swap() in atmel_hlcdc_plane_atomic_check()

Use kernel.h macro definition. Thanks to Julia Lawall for Coccinelle scripting support. Signed-off-by: Fabian Frederick --- drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_plane.c | 9 ++--- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git

[Bug 90264] [Regression, bisected] Tooltip corruption in Chrome

An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/ce2f0d86/attachment.html>

[Bug 90264] [Regression, bisected] Tooltip corruption in Chrome

-- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/bd7f3fe7/attachment-0001.html>

[PATCH] drm/bochs: convert bochs driver to atomic mode-setting

hen all this works try turning fbdev back on. > > HTH, > Gerd > > > -- Best regards Junwang Zhao Microprocessor Research and Develop Center Department of Computer Science Peking University Beijing, 100871, PRC -- next part -- An HTML attachment was scrubb

atombios_crtc.c - make error messages distinguishable "unable to allocate a PPLL\n"

> Yes, DP needs its own clock source. However, you only need one clock source > for all DP ports so you can drive multiple DP displays from a single clock > source. The clock source used for DP cannot be shared with non-DP displays. > ... > There are additional caveats however. For example, you

[pull] amdgpu drm-next-4.2

Hi Dave, More fixes for amdgpu for 4.2. We've integrated Jerome's comments about the interface among other things. I'll be on vacation next week so Christian will be handling any updates next week. The following changes since commit ae45577324d1f749c907840247d443696ac3bc7a: virtgpu: include

[pull] radeon drm-next-4.2

Hi Dave, A few more fixes for radeon for 4.2 The following changes since commit ae45577324d1f749c907840247d443696ac3bc7a: virtgpu: include linux/types.h to avoid warning. (2015-06-05 12:31:12 +1000) are available in the git repository at: git://people.freedesktop.org/~agd5f/linux

[PATCH] drm/tilcdc: panel: make better use of gpiod API

On 06/10/2015 03:59 PM, Uwe Kleine-König wrote: > On Wed, Jun 10, 2015 at 11:25:25AM +0900, Alexandre Courbot wrote: >> On 06/09/2015 06:43 PM, Uwe Kleine-König wrote: >>> Since 39b2bbe3d715 (gpio: add flags argument to gpiod_get*() functions) >>> which appeared in v3.17-rc1, the gpiod_get*

[Bug 90926] Unusable GPU

because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/33c21a74/attachment.html>

[Bug 90926] Unusable GPU

1 glxinfo | grep "OpenGL renderer" OpenGL renderer string: Gallium 0.4 on AMD HAINAN -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/26061c4b/attachment-0001.html>

[PATCH] drm: Avoid the double clflush on the last cache line in drm_clflush_virt_range()

As the clflush operates on cache lines, and we can flush any byte address, in order to flush all bytes given in the range we issue an extra clflush on the last byte to ensure the last cacheline is flushed. We can can the iteration to be over the actual cache lines to avoid this double clflush on

[PATCH 9/9] tests/exynos: handle G2D_IMGBUF_COLOR in switch statements

This fixes a compiler warning about missing handling of enum values in the switch statements. Also remove the silent mapping to G2D_IMGBUF_GEM when an unknown buffer type is encountered. We have full control about the type here, and if it's unknown then we obviously have a bug in the code.

[PATCH 8/9] tests/exynos: remove connector_find_plane

No test uses DRM planes at the moment so this function is never called. Signed-off-by: Tobias Jakobi --- tests/exynos/exynos_fimg2d_test.c | 31 --- 1 file changed, 31 deletions(-) diff --git a/tests/exynos/exynos_fimg2d_test.c b/tests/exynos/exynos_fimg2d_test.c

[PATCH 7/9] tests/exynos: simplify drm_set_crtc

We can just return 'ret' here, the goto serves no purpose. Signed-off-by: Tobias Jakobi --- tests/exynos/exynos_fimg2d_test.c | 7 +-- 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/tests/exynos/exynos_fimg2d_test.c b/tests/exynos/exynos_fimg2d_test.c index de6a2b7..1ec7340

[PATCH 6/9] tests/exynos: remove struct fimg2d_test_case

It doesn't make sense to keep this structure, since we can just call all tests directly. Signed-off-by: Tobias Jakobi --- tests/exynos/exynos_fimg2d_test.c | 42 +-- 1 file changed, 5 insertions(+), 37 deletions(-) diff --git

[PATCH 5/9] tests/exynos: remove unused define

It doesn't make sense to limit the number of test cases anyway. Signed-off-by: Tobias Jakobi --- tests/exynos/exynos_fimg2d_test.c | 1 - 1 file changed, 1 deletion(-) diff --git a/tests/exynos/exynos_fimg2d_test.c b/tests/exynos/exynos_fimg2d_test.c index 6af9277..080d178 100644 ---

[PATCH 4/9] tests/exynos: clean struct connector

Remove all unused struct members. Signed-off-by: Tobias Jakobi --- tests/exynos/exynos_fimg2d_test.c | 10 -- 1 file changed, 10 deletions(-) diff --git a/tests/exynos/exynos_fimg2d_test.c b/tests/exynos/exynos_fimg2d_test.c index 64dacfa..6af9277 100644 ---

[PATCH 3/9] exynos/fimg2d: simplify g2d_fini()

free()ing a nullptr is a noop, so remove the check. Signed-off-by: Tobias Jakobi --- exynos/exynos_fimg2d.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/exynos/exynos_fimg2d.c b/exynos/exynos_fimg2d.c index 5ea42e6..24a06d0 100644 --- a/exynos/exynos_fimg2d.c +++

[PATCH 2/9] tests/exynos: replace return by break

The 'usage' function already does exit(0), so that this 'return -EINVAL' is never called. Just put a break there to avoid confusion. Signed-off-by: Tobias Jakobi --- tests/exynos/exynos_fimg2d_test.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 1/9] exynos: fimg2d: fix return codes

Even if flushing the command buffer doesn't succeed, the G2D calls would still return zero. Fix this by just passing the flush return code. Signed-off-by: Tobias Jakobi --- exynos/exynos_fimg2d.c | 20 +--- 1 file changed, 5 insertions(+), 15 deletions(-) diff --git

[PATCH 0/9] drm/exynos: cleanups and small fixes for libdrm

Hello, I've split off the Exynos specific bits, so this is just some cleanups and small fixes. Everything can be reviewed without knowledge about the Exynos platform. My hope is that I can get at least some of the patches from my last series upstream. With best wishes, Tobias Tobias Jakobi

[PULL] drm-amdkfd-next-fixes

Hi Dave, A few fixes to the two pull requests you merged for 4.2: - Make the reset wavefronts action be per process per device instead of per process, because one device can be stuck but the other one won't be - Add some missing properties to the CZ device_info structure - Rename symbols to

[PATCH] drm/bochs: convert bochs driver to atomic mode-setting

From: root convert the bochs driver to atomic mode-setting, referencing the patch serias of drm/exynos sent by Gustavo Padovan Signed-off-by: Zhao Junwang --- Hi all, I am a GSoCer of this year, and my project is to convert bochs driver and cirrus driver to atomic

[PATCH] drm/tilcdc: panel: make better use of gpiod API

On Tue, Jun 9, 2015 at 11:43 AM, Uwe Kleine-König wrote: > Since 39b2bbe3d715 (gpio: add flags argument to gpiod_get*() functions) > which appeared in v3.17-rc1, the gpiod_get* functions take an additional > parameter that allows to specify direction and initial value for output. > >

[PATCH 32/32] acpi-video: Make acpi_video_unregister_backlight() private

acpi_video_unregister_backlight() is now only used by video_detect.c which is part of the same acpi_video module as video.c, make acpi_video_unregister_backlight() private to this module. Signed-off-by: Hans de Goede --- drivers/acpi/video.c| 1 - drivers/acpi/video_detect.c | 2 ++

[PATCH 31/32] acpi-video-detect: Remove old API

Remove the old backlight interface selection API now that all drivers have been ported to the new API. Signed-off-by: Hans de Goede --- drivers/acpi/video_detect.c | 31 --- include/linux/acpi.h| 19 --- 2 files changed, 50 deletions(-) diff

[PATCH 30/32] toshiba-acpi: Port to new backlight interface selection API

Port the backlight selection logic to the new backlight interface selection API. Also fix a compiler warning about bt_present not being initialized. Signed-off-by: Hans de Goede --- drivers/platform/x86/toshiba_acpi.c | 9 +++-- 1 file changed, 3 insertions(+), 6 deletions(-) diff --git

[PATCH 29/32] thinkpad-acpi: Port to new backlight interface selection API

Port the backlight selection logic to the new backlight interface selection API. Signed-off-by: Hans de Goede --- drivers/platform/x86/thinkpad_acpi.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/platform/x86/thinkpad_acpi.c

[PATCH 28/32] sony-laptop: Port to new backlight interface selection API

Port the backlight selection logic to the new backlight interface selection API. This commit also removes various obsolete pr_xxx messages related to backlight interface selection. These are obsolete because they assume there is only a vendor or acpi backlight driver and no other choice. Also

[PATCH 27/32] samsung-laptop: Port to new backlight interface selection API

Port the backlight selection logic to the new backlight interface selection API. This commit also removes various obsolete pr_xxx messages related to backlight interface selection. These are obsolete because they assume there is only a vendor or acpi backlight driver and no other choice. Also

[PATCH 26/32] msi-wmi: Port to new backlight interface selection API

Port the backlight selection logic to the new backlight interface selection API. Signed-off-by: Hans de Goede --- drivers/platform/x86/msi-wmi.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/platform/x86/msi-wmi.c b/drivers/platform/x86/msi-wmi.c index

[PATCH 25/32] msi-laptop: Port to new backlight interface selection API

Port the backlight selection logic to the new backlight interface selection API. This commit also removes various obsolete pr_xxx messages related to backlight interface selection. These are obsolete because they assume there is only a vendor or acpi backlight driver and no other choice. Also

[PATCH 24/32] intel-oaktrail: Port to new backlight interface selection API

Port the backlight selection logic to the new backlight interface selection API. This commit also removes various obsolete pr_xxx messages related to backlight interface selection. These are obsolete because they assume there is only a vendor or acpi backlight driver and no other choice. Also

[PATCH 23/32] ideapad-laptop: Port to new backlight interface selection API

Port the backlight selection logic to the new backlight interface selection API. Signed-off-by: Hans de Goede --- drivers/platform/x86/ideapad-laptop.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/platform/x86/ideapad-laptop.c

[PATCH 22/32] fujitsu-laptop: Port to new backlight interface selection API

Port the backlight selection logic to the new backlight interface selection API. Signed-off-by: Hans de Goede --- drivers/platform/x86/fujitsu-laptop.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/platform/x86/fujitsu-laptop.c

[PATCH 21/32] eeepc-laptop: Port to new backlight interface selection API

Port the backlight selection logic to the new backlight interface selection API. This commit also removes various obsolete pr_xxx messages related to backlight interface selection. These are obsolete because they assume there is only a vendor or acpi backlight driver and no other choice. Also

[PATCH 20/32] dell-wmi: Port to new backlight interface selection API

Port the backlight selection logic to the new backlight interface selection API. Signed-off-by: Hans de Goede --- drivers/platform/x86/dell-wmi.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/platform/x86/dell-wmi.c b/drivers/platform/x86/dell-wmi.c index

[PATCH 19/32] dell-laptop: Port to new backlight interface selection API

Port the backlight selection logic to the new backlight interface selection API. Signed-off-by: Hans de Goede --- drivers/platform/x86/dell-laptop.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/platform/x86/dell-laptop.c b/drivers/platform/x86/dell-laptop.c

[PATCH 18/32] compal-laptop: Port to new backlight interface selection API

Port the backlight selection logic to the new backlight interface selection API. Signed-off-by: Hans de Goede --- drivers/platform/x86/compal-laptop.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/platform/x86/compal-laptop.c

[PATCH 17/32] asus-wmi: Port to new backlight interface selection API

Port the backlight selection logic to the new backlight interface selection API. This commit also removes various obsolete pr_xxx messages related to backlight interface selection. These are obsolete because they assume there is only a vendor or acpi backlight driver and no other choice. Also

[PATCH 16/32] asus-laptop: Port to new backlight interface selection API

Port the backlight selection logic to the new backlight interface selection API. This commit also removes various obsolete pr_xxx messages related to backlight interface selection. These are obsolete because they assume there is only a vendor or acpi backlight driver and no other choice. Also

[PATCH 15/32] apple-gmux: Port to new backlight interface selection API

Port the backlight selection logic to the new backlight interface selection API. Signed-off-by: Hans de Goede --- drivers/platform/x86/apple-gmux.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/platform/x86/apple-gmux.c b/drivers/platform/x86/apple-gmux.c index

[PATCH 14/32] acer-wmi: Port to new backlight interface selection API

Port the backlight selection logic to the new backlight interface selection API. This commit also removes various obsolete pr_xxx messages related to backlight interface selection. These are obsolete because they assume there is only a vendor or acpi backlight driver and no other choice. Also

[PATCH 13/32] acpi-video: Fix acpi_video _register vs _unregister_backlight race

It is possible for a native backlight driver to load while acpi_video_register is running, which may lead to acpi_video_unregister_backlight being called while acpi_video_register is running and the 2 racing against eachother. The register_count variable protects against this, but not in a thread

[PATCH 12/32] acpi-video: Move dmi_check_system from module_init to acpi_video_register

When builtin there is no guarantee in which order module_init functions are run, so acpi_video_register() may get called from the i915 driver (if it is also builtin) before acpi_video_init() gets called, resulting in the dmi quirks not yet being parsed. This commit moves the dmi_check_system()

[PATCH 11/32] acpi-video: Move backlight notifier to video_detect.c

Move the unregistering of the acpi backlight interface on registering of a native backlight from video.c to video_detect.c where it belongs. Note this removes support for re-registering the acpi backlight interface when the native interface goes away. In practice this never happens and it

[PATCH 10/32] acpi-video: Port to new backlight interface selection API

Most of the patch is moving the dmi quirks for forcing use of the acpi-video / the native backlight interface to video_detect.c. What remains is a nice cleanup. Signed-off-by: Hans de Goede --- drivers/acpi/video.c| 178 +++-

[PATCH 09/32] drm: i915: Port to new backlight interface selection API

This results in a nice cleanup, as we can replace the complicated logic from should_ignore_backlight_request() with a simple check for the type being native. Signed-off-by: Hans de Goede --- drivers/gpu/drm/i915/intel_opregion.c | 12 +--- 1 file changed, 1 insertion(+), 11 deletions(-)

[PATCH 08/32] acpi-video-detect: Unregister acpi_video backlight when dmi quirks are added

Make acpi_video_set_dmi_backlight_type() call acpi_video_unregister_backlight() when the new dmi quirk results in the desired backlight interface being of a type other then acpi_backlight_video. This avoid the need for the second if in the following construction which is currently found in many

[PATCH 07/32] acpi-video-detect: Rewrite backlight interface selection logic

Currently we have 2 kernel commandline options + dmi-quirks in 3 places all interacting (in interesting ways) to select which which backlight interface to use. On the commandline we've acpi_backlight=[video|vendor] and video.use_native_backlight=[0|1]. DMI quirks we have in acpi/video-detect.c,

[PATCH 06/32] acpi-video-detect: video: Make video_detect code part of the video module

This is a preparation patch for the backlight interface selection logic cleanup, there are 2 reasons to not always build the video_detect code into the kernel: 1) In order for the video_detect.c to also deal with / select native backlight interfaces on win8 systems, instead of doing this in

[PATCH 05/32] acpi-video-detect: Move acpi_osi_is_win8 to osl.c

acpi_osi_is_win8 needs access to acpi_gbl_osi_data which is not exported, so move it to osl.c. Alternatively we could export acpi_gbl_osi_data but that seems undesirable. This allows video_detect.c to be build as a module, besides that acpi_osi_is_win8() is something which does not really belong

[PATCH 04/32] acpi-video-detect: Move acpi_is_video_device() to acpi/scan.c

This allows video_detect.c to be build as a module, this is a preparation patch for the backlight interface selection logic cleanup. Note this commit also causes acpi_is_video_device() to always be build indepedent of CONFIG_ACPI_VIDEO, as there is no reason to make its building depend on

[PATCH 03/32] acpi-video-detect: Make acpi_video_get_capabilities a private function

acpi_video_get_capabilities() is only used inside video_detect.c so make it static. While at it also remove the prototype for the non existent acpi_video_display_switch_support function from acpi.h Signed-off-by: Hans de Goede --- drivers/acpi/video_detect.c | 3 +-- include/linux/acpi.h

[PATCH 02/32] acpi-video-detect: Remove the unused acpi_video_dmi_demote_vendor() function

Remove the now unused acpi_video_dmi_demote_vendor() function, this was never a proper counter part of acpi_video_dmi_promote_vendor() since the calls to acpi_video_dmi_promote_vendor() are not counted. Signed-off-by: Hans de Goede --- drivers/acpi/video_detect.c | 9 -

[PATCH 01/32] apple-gmux: Stop using acpi_video_dmi_demote_vendor()

acpi_video_dmi_demote_vendor() is going away as part of the cleanup of the code for determinging which backlight class driver(s) to register. The call to acpi_video_dmi_demote_vendor() was meant to undo the call to acpi_video_dmi_promote_vendor() when the gmux device is removed, this is

[PATCH 00/32] acpi-video: Rewrite backlight interface selection logic

Hi All, Here is the long promised rewrite / cleanup of the acpi-video (and platform/x86) backlight interface selection logic. Reviewers do not be alarmed by the large number of patches, the gist of the series is in patches 6-13, the earlier ones are a few simple prepararion patches, and the

[PATCH RFC] drm/i2c: tda998x: dead-code or unhandled error condition ?

ire --- Can't really determine what the right fix for this would be - someone that knows this driver would need to check - in any case the current code seems broken. Patch was compile tested with x86_64_defconfig + CONFIG_DRM_I2C_SIL164=m Patch is against 4.1-rc7 (localversion-next is -next-20150

[PATCH] drm/msm/dp: use flags argument of devm_gpiod_get to set direction

On Tue, Jun 9, 2015 at 11:38 AM, Uwe Kleine-König wrote: > Since 39b2bbe3d715 (gpio: add flags argument to gpiod_get*() functions) > which appeared in v3.17-rc1, the gpiod_get* functions take an additional > parameter that allows to specify direction and initial value for output. > > Use this

[PATCH 00/21] On-demand device registration

On 06/10/2015 12:19 PM, Tomeu Vizoso wrote: > On 10 June 2015 at 09:30, Linus Walleij wrote: >> On Tue, Jun 2, 2015 at 12:14 PM, Tomeu Vizoso >> wrote: >>> On 2 June 2015 at 10:48, Linus Walleij wrote: >> This is what systemd is doing in userspace for starting services: ask for your

[PATCH] drm/bochs: convert bochs driver to atomic mode-setting

On Mi, 2015-06-10 at 19:39 +0800, John Hunter wrote: > Hi Gerd, > I have tried what you told me. > 1. Turn off fbdev support: > static bool enable_fbdev = false; Good. > 2. configure a serial console: > - add something like "console=ttyS0, 9600n8" to the grub menuentry Good. You can

[PATCH] DRM: Armada: fixup wait_event_timeout being ignored

On Wed, 10 Jun 2015, Russell King - ARM Linux wrote: > On Wed, Jun 10, 2015 at 01:07:08PM +0200, Nicholas Mc Guire wrote: > > The calling side seems to assume 0 as success and <0 as error so > > returning -ETIME should be fine here. > > The idea here is to allow the remainder of the code to

[PATCH v10 00/17] drm/exynos: atomic modesetting support

Hello, On 2015-06-10 12:59, Inki Dae wrote: > Hi Marek, > > On 2015년 06월 10일 19:03, Marek Szyprowski wrote: >> Hello, >> >> On 2015-06-01 17:04, Gustavo Padovan wrote: >>> From: Gustavo Padovan >>> >>> Hi, >>> >>> Here goes the full support for atomic modesetting on exynos. I've >>> split

[PATCH 2/2] drm/msm/dsi: Rename *dual panel* to *dual DSI*

The current term of *dual panel* in DSI driver code causes confusion. It is supposed to indicate the panel using two DSI links. Rename it to *dual DSI*. Signed-off-by: Hai Li --- Documentation/devicetree/bindings/drm/msm/dsi.txt | 12 ++-- drivers/gpu/drm/msm/dsi/dsi_manager.c | 84

[PATCH 1/2] drm/msm/dsi: Update source PLL selection in DSI PHY

The source PLL to be used by each DSI PHY should be decided by DSI manager based on dual DSI information, while the register programming to select PLL is different from one type of PHY to another. This change adds the H/W difference to PHY configuration and updates the interface between DSI

[PATCH 0/2] drm/msm/dsi: Miscellaneous patches

These changes are for code cleanup and better support new targets in the future. Hai Li (2): drm/msm/dsi: Update source PLL selection in DSI PHY drm/msm/dsi: Rename *dual panel* to *dual DSI* Documentation/devicetree/bindings/drm/msm/dsi.txt | 12 +-- drivers/gpu/drm/msm/dsi/dsi.h

[PATCH] DRM: Armada: fixup wait_event_timeout being ignored

event API conformance testing with coccinelle spatches are being used to locate API usage inconsistencies this triggert with: ./drivers/gpu/drm/armada/armada_overlay.c:153 incorrect check for negative return Return type of wait_event_timeout is signed long not int and the return type is

[PATCH] treewide: Fix typo compatability -> compatibility

On Wed, Jun 10, 2015 at 7:27 AM, Mauro Carvalho Chehab wrote: > Em Wed, 27 May 2015 15:05:42 +0300 > Laurent Pinchart escreveu: > >> Even though 'compatability' has a dedicated entry in the Wiktionary, >> it's listed as 'Mispelling of compatibility'. Fix it. >> >> Signed-off-by: Laurent Pinchart

[Bug 90264] [Regression, bisected] Tooltip corruption in Chrome

-- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/cf0a707e/attachment.html>

[Bug 90264] [Regression, bisected] Tooltip corruption in Chrome

this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/a3a91a1e/attachment.html>

[PATCH] DRM: Armada: fixup wait_event_timeout being ignored

On Wed, Jun 10, 2015 at 01:07:08PM +0200, Nicholas Mc Guire wrote: > The calling side seems to assume 0 as success and <0 as error so > returning -ETIME should be fine here. The idea here is to allow the remainder of the code to execute when the condition succeeds _or_ times out. If it times

[PATCH 00/21] On-demand device registration

On 10 June 2015 at 09:30, Linus Walleij wrote: > On Tue, Jun 2, 2015 at 12:14 PM, Tomeu Vizoso > wrote: >> On 2 June 2015 at 10:48, Linus Walleij wrote: > >>> This is what systemd is doing in userspace for starting services: >>> ask for your dependencies and wait for them if they are not >>>

[PATCH v10 00/17] drm/exynos: atomic modesetting support

Hello, On 2015-06-01 17:04, Gustavo Padovan wrote: > From: Gustavo Padovan > > Hi, > > Here goes the full support for atomic modesetting on exynos. I've > split the patches in the various phases of atomic support. Thanks for this patchses, however I've noticed a problem after applying them.

[Bug 89713] [radeon]GPU lockup in World of Tanks with gallium nine

-- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/2584c955/attachment.html>

[PATCH] drm/tilcdc: panel: make better use of gpiod API

On 06/09/2015 06:43 PM, Uwe Kleine-König wrote: > Since 39b2bbe3d715 (gpio: add flags argument to gpiod_get*() functions) > which appeared in v3.17-rc1, the gpiod_get* functions take an additional > parameter that allows to specify direction and initial value for output. > > Furthermore there is

[PATCH] drm/msm/dp: use flags argument of devm_gpiod_get to set direction

On 06/09/2015 06:38 PM, Uwe Kleine-König wrote: > Since 39b2bbe3d715 (gpio: add flags argument to gpiod_get*() functions) > which appeared in v3.17-rc1, the gpiod_get* functions take an additional > parameter that allows to specify direction and initial value for output. > > Use this to simplify

[PATCH 3/3] drm/exynos: remove SoC checking code

Hi Andrzej, On Tue, 09 Jun 2015 16:46:52 -0300 Gustavo Padovan wrote: > Hi Andrzej, > > 2015-06-08 Andrzej Hajda : > > > SoC checking code is not necessary anymore, as exynos_drm_match_add > > and exynos_drm_platform_probe already properly handles situation > > when there are no Exynos DRM

[PATCH] drm/exynos: mixer: remove chained calls to enable/disable planes

From: Gustavo Padovan With atomic modesetting all the control for CRTC, Planes, Encoders and Connectors should come from DRM core, so the driver is not allowed to disable planes from inside the crtc_disable() call. This patch removes this chainned calls from

[PATCH 9/9] drm/exynos: Convert g2d_userptr_get_dma_addr() to use get_vaddr_frames()

For unclear reasons my SoB was missing in my pull request. So add it now: Signed-off-by: Hans Verkuil Regards, Hans On 05/13/15 15:08, Jan Kara wrote: > Convert g2d_userptr_get_dma_addr() to pin pages using get_vaddr_frames(). > This removes the knowledge about vmas and mmap_sem

  1   2   >