org/archives/dri-devel/attachments/20150610/522512b6/attachment.html>
Am Dienstag, 9. Juni 2015, 09:53:32 schrieb Thierry Reding:
> On Mon, Jun 08, 2015 at 05:34:21PM +0100, Russell King - ARM Linux wrote:
> > On Mon, Jun 08, 2015 at 05:44:53PM +0200, Thierry Reding wrote:
> > > On Mon, Jun 08, 2015 at 03:29:26PM +0100, Russell King - ARM Linux
wrote:
> > > > You're
On Wed, Jun 10, 2015 at 01:29:43AM +0200, Heiko Stübner wrote:
> Allthough from the discussion and explanations I've now also got the "don't
> make it worse" feeling, so am somehow reluctant to add supplies that also
> might describe this inadequately.
>
> The Rockchip-specific documentation on
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 com
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 t
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 d
--
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/2584c955/attachment.html>
https://bugzilla.kernel.org/show_bug.cgi?id=99651
--- Comment #2 from Gluzskiy Alexandr ---
Created attachment 179381
--> https://bugzilla.kernel.org/attachment.cgi?id=179381&action=edit
xrandr --verbose on 4.0.4
all working fine here, just for monitor info
--
You are receiving this mail bec
https://bugzilla.kernel.org/show_bug.cgi?id=99651
--- Comment #3 from Gluzskiy Alexandr ---
Created attachment 179391
--> https://bugzilla.kernel.org/attachment.cgi?id=179391&action=edit
xorg log on 4.0.4
xorg log on working system, just to get config info
--
You are receiving this mail beca
https://bugzilla.kernel.org/show_bug.cgi?id=99651
--- Comment #4 from Gluzskiy Alexandr ---
Created attachment 179401
--> https://bugzilla.kernel.org/attachment.cgi?id=179401&action=edit
xrandr --verbose on 4.0.5
on broken system, third monitor does not work, the one with 1280x1024
resolution
https://bugzilla.kernel.org/show_bug.cgi?id=99651
--- Comment #5 from Gluzskiy Alexandr ---
Created attachment 179411
--> https://bugzilla.kernel.org/attachment.cgi?id=179411&action=edit
xorg log on 4.0.5
on broken system, third monitor does not work, the one with 1280x1024
resolution
--
You
https://bugzilla.kernel.org/show_bug.cgi?id=99651
--- Comment #6 from Gluzskiy Alexandr ---
i have reverted both commits and it's fixes a problem
--
You are receiving this mail because:
You are watching the assignee of the bug.
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* functions take an additional
> >parameter that allows to sp
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* funct
Hello,
Cc += dri-devel at lists.freedesktop.org + kernel at pengutronix.de, forgot
that for the original submission. Also added (hopefully the right)
Geert.
On Mon, Jun 08, 2015 at 11:45:17AM +0200, Uwe Kleine-König wrote:
> Hello,
>
> On Fri, Jun 05, 2015 at 04:46:25PM +0200, Thierry Reding wr
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 mode-setting.
I converted th
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
>> there. So drivers ask for resources and wait for them. It al
In case there are multiple pipelines and deferred probe occurs, only components
of the first pipeline were bound. As a result only one pipeline was available.
The main cause of this issue was dynamic generation of component match table -
every component driver during probe registered itself on help
Hi,
> As far as I know, the convertion got some problem, and after I
> add the bochs driver when I boot the qemu VM, it just can not
> start up, works fine if I delete bochs-drm.ko from it's directory.
With fbdev enabled alot initialization happens with some important
console lock taken, which
n HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/35ec771b/attachment.html>
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 lockin
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 al
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 patc
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.
The
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
>>> the
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,
[1
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 f
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.
>
> T
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 >=
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 out
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 t
gt; Best regards
> Junwang Zhao
> Microprocessor Research and Develop Center
> Department of Computer Science &Technology
> Peking University
> Beijing, 100871, PRC
>
--
Best regards
Junwang Zhao
Microprocessor Research and Develop Center
Department of Computer Science &Technology
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>
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 g
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 use
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 de
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
iving 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>
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 to
--
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/cf0a707e/attachment.html>
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 later
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
questionab
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 -
include/linux/acp
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
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 CONFIG_A
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 i
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 video.
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, acp
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 pl
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(-)
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 +++-
drivers/acpi/video_de
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 needless
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() cal
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
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 they
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 a
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 they
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 they
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
b/drivers/platform/x86/compal-lapto
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
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 6512a06.
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 they
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
b/drivers/platform/x86/fujitsu-
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
b/drivers/platform/x86/ideapad-lapt
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 they
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 they
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 6d2bac0..9
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 they
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 they
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
b/drivers/platform/x86/thinkpad_ac
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 a/
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 -
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 ++
incl
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.
>
> Furthermore
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-
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 (9
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 a/exynos/exy
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 a/tests/exynos/exynos_fimg2d_t
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
+++ b/exyno
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
--- a/tests/exynos/exynos_fimg2
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
--- a/tests/e
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 a/tests/exynos/exynos_fimg2d_test
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 10
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
in
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.
Signed
On Wed, Jun 10, 2015, at 10:01, Hans de Goede wrote:
> Port the backlight selection logic to the new backlight interface
> selection API.
>
> Signed-off-by: Hans de Goede
Acked-by: Henrique de Moraes Holschuh
> ---
> drivers/platform/x86/thinkpad_acpi.c | 5 +++--
> 1 file changed, 3 insertio
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 mixer code letting only DRM core touch
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 th
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()
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'
drivers/gp
e:radeon
$ DRI_PRIME=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>
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>
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
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 manager
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 +
--
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/bd7f3fe7/attachment-0001.html>
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/ce2f0d86/attachment.html>
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
--
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150610/74f56bc1/attachment.html>
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
--- a/drivers/gpu/drm/virti
The goto is correct, and we never reach the return statement so just
delete the dead code.
Signed-off-by: Dan Carpenter
diff --git a/drivers/gpu/drm/virtio/virtgpu_ttm.c
b/drivers/gpu/drm/virtio/virtgpu_ttm.c
index e0e74c6..b092d7b 100644
--- a/drivers/gpu/drm/virtio/virtgpu_ttm.c
+++ b/drivers
1 - 100 of 123 matches
Mail list logo
