https://bugs.freedesktop.org/show_bug.cgi?id=103304
--- Comment #10 from Luc ---
Well, we have solved it in our software now.
The question concerning if this case may be closed or not boils down to
following question:
Performing a texture upload on a texture ID while it is being rendered (drawn)
On 10/17/2017 02:43 PM, ayaka wrote:
On 10/12/2017 07:56 PM, Tapani Pälli wrote:
Is this one going to land soon? The discussion was a bit hard to read
but it looks like in the end consensus was that everything looks good
in this patch.
I am very sorry, I am too busy with the other dma pro
Merged.
Thanks,
Inki Dae
2017년 10월 23일 21:49에 Sylwester Nawrocki 이(가) 쓴 글:
> The hdmi-codec interface added in this patch is required to properly
> support HDMI audio. Currently the audio part of the SoC internal
> HDMI transmitter is configured with fixed values, which makes HDMI
> audio working
On Tue, Oct 17, 2017 at 01:07:50PM +0200, Marek Szyprowski wrote:
> From: Andrzej Pietrasiewicz
>
> Exynos Scaler is a hardware module, which processes graphic data fetched
> from memory and transfers the resultant dato another memory buffer.
> Graphics data can be up/down-scaled, rotated, flippe
https://bugs.freedesktop.org/show_bug.cgi?id=91221
--- Comment #5 from Chí-Thanh Christopher Nguyễn ---
As suggested by iive on #radeon, I tried to set R600_DEBUG=nodma and while the
problem still happens, the time to trigger the problem increases considerably
from a few minutes to 15 minutes or
On Tue, Oct 17, 2017 at 06:49:58AM -0400, Rob Clark wrote:
> Now that drm/msm is converted over to use msm_get_clk() everywhere (that
> matters), which handles falling back to looking for a clock with the
> "_clk" suffix, we can remove "_clk" from the documentation so that new
> dts files added do
https://bugs.freedesktop.org/show_bug.cgi?id=103408
--- Comment #1 from dwagner ---
Created attachment 135018
--> https://bugs.freedesktop.org/attachment.cgi?id=135018&action=edit
1-minute test video, smooth horizontal pan in 3840x2160 23.976 fps
For more convenient reproducability, I created
On Tue, Oct 17, 2017 at 10:07:42AM +0200, Neil Armstrong wrote:
> On reference boards and derivatives, the HDMI Logic is powered by an external
> 5V regulator.
> This regulator was set by the Vendor U-Boot, add optional support for it.
>
> Signed-off-by: Neil Armstrong
> ---
> Documentation/devi
On Tue, Oct 17, 2017 at 10:07:41AM +0200, Neil Armstrong wrote:
> The Video Processing Unit power domain was setup by the Vendor U-Boot,
> add support for an optional Power Domain phandle to setup it from the kernel.
>
> Signed-off-by: Neil Armstrong
> ---
> Documentation/devicetree/bindings/dis
Hi Noralf,
[auto build test WARNING on drm/drm-next]
[also build test WARNING on v4.14-rc6 next-20171018]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Noralf-Tr-nnes/drm-framebuffer-Add-frameb
On Fri, Oct 20, 2017 at 09:49:22AM +0200, Boris Brezillon wrote:
> Document the bindings used for the Cadence DSI bridge.
>
> Signed-off-by: Boris Brezillon
> ---
> Hi Rob,
>
> I dropped your A-b because two important things changed in this
> version:
> * the clk names have changed (they are now
On Mon, Oct 23, 2017 at 9:47 AM, Noralf Trønnes wrote:
> Add debugfs file that dumps info about the framebuffers and its planes.
> Also dump info about any connected gem object(s).
>
> Signed-off-by: Noralf Trønnes
> ---
> drivers/gpu/drm/drm_debugfs.c | 6 +
> drivers/gpu/drm/drm_frame
https://bugs.freedesktop.org/show_bug.cgi?id=91221
--- Comment #4 from jancoow ---
Dmesg info:
[ 52.191082] [drm:btc_dpm_set_power_state [radeon]] *ERROR*
rv770_restrict_performance_levels_before_switch failed
[ 112.173163] radeon :01:00.0: ring 0 stalled for more than 10283msec
[ 112.17
https://bugs.freedesktop.org/show_bug.cgi?id=91221
--- Comment #3 from jancoow ---
I'm facing the same issue:
AMD XFX HD6850 Black Edition
Intel I3 3550
If I remove the vdaup packages playblack is smootly. But when i'm trying to use
video acceleration it's choppy and eventually crash my desktop
From: Markus Elfring
Date: Mon, 23 Oct 2017 21:27:30 +0200
Add a jump target so that a call of the function "mutex_unlock" is stored
only once at the end of this function implementation.
Replace three calls by goto statements.
This issue was detected by using the Coccinelle software.
Signed-off
https://bugzilla.kernel.org/show_bug.cgi?id=193651
--- Comment #26 from fin4...@hotmail.com ---
Milo, try to set amdgpu.audio=0 to the kernel command line.
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=100666
--- Comment #7 from Lucas Riutzel ---
Dimitrios,
Good to know. Looks like my short term solution became a long term one.
I unplugged the builtin fan and ziptied on another fan and connected it to a
motherboard fan header. I might come back and
Add debugfs file that dumps info about the framebuffers and its planes.
Also dump info about any connected gem object(s).
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_debugfs.c | 6 +
drivers/gpu/drm/drm_framebuffer.c | 51 +++
drivers/gpu/dr
Thanks, applied!
On 10/16/17 10:32, Jérémy Lefaure wrote:
Using the ARRAY_SIZE macro improves the readability of the code. Also,
it's useless to use a variable to store this constant calculated at
compile time.
Found with Coccinelle with the following semantic patch:
@r depends on (org || repor
Thanks, applied! :)
On 10/16/17 06:32, Christos Gkekas wrote:
Delete variables 'gma_bottom' that are set but never used.
Signed-off-by: Christos Gkekas
---
drivers/gpu/drm/i915/gvt/cmd_parser.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/i915/gv
https://bugs.freedesktop.org/show_bug.cgi?id=103384
--- Comment #3 from Michel Dänzer ---
Please attach the Xorg log file.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.
https://bugzilla.kernel.org/show_bug.cgi?id=196247
--- Comment #5 from Michel Dänzer (mic...@daenzer.net) ---
What was the newest kernel version where this didn't happen? Can you bisect
between that and the oldest version where it first happened?
--
You are receiving this mail because:
You are w
https://bugs.freedesktop.org/show_bug.cgi?id=102809
Nicolai Hähnle changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=103384
--- Comment #2 from Max ---
(In reply to Michel Dänzer from comment #1)
> Which components did you update exactly, from which version to which?
Probably:
vmlinuz-4.4.0-83-generic -> vmlinuz-4.4.0-87-generic (and all new, include
4.10.x)
Precise
Instead a getting only one common device "/dev/ion" for
all the heaps this patch allow to create one device
entry ("/dev/ionX") per heap.
Getting an entry per heap could allow to set security rules
per heap and global ones for all heaps.
Allocation requests will be only allowed if the mask_id
matc
Make arguments checking more easy to read.
Signed-off-by: Benjamin Gaignard
Acked-by: Laura Abbott
---
drivers/staging/android/ion/ion-ioctl.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/android/ion/ion-ioctl.c
b/drivers/staging/android/ion/i
version 6:
- add platform_bus and platform_bus_type when register Ion devices
to make them appear in /sys/devices/platform.
- re-order include files in aphabetic order.
version 5:
- create a configuration flag to keep legacy Ion misc device
version 4:
- add a configuration flag to switch betwee
https://bugzilla.kernel.org/show_bug.cgi?id=196247
Mathias (mat...@yahoo.de) changed:
What|Removed |Added
Kernel Version|4.x |4.14
Regression|No
From: Ville Syrjälä
Since commit 632c6e4edef1 ("drm/vblank: Fix flip event vblank count")
even drivers that don't implement accurate vblank timestamps will end
up using drm_crtc_accurate_vblank_count(). That leads to a WARN every
time drm_crtc_arm_vblank_event() gets called. The could be as often
2017-10-18 22:07 GMT+02:00 Laura Abbott :
> On 09/27/2017 06:20 AM, Benjamin Gaignard wrote:
>> diff --git a/drivers/staging/android/ion/ion.c
>> b/drivers/staging/android/ion/ion.c
>> index 93e2c90..092b24c 100644
>> --- a/drivers/staging/android/ion/ion.c
>> +++ b/drivers/staging/android/ion/ion
Hi,
On 23-10-17 14:43, Sebastian Reichel wrote:
Hi Hans,
On Mon, Oct 23, 2017 at 09:14:19AM +0200, Hans de Goede wrote:
On some hardware the LCD panel is not mounted upright in the casing,
but upside-down or rotated 90 degrees. In this case we want the console
to automatically be rotated to co
The hdmi-codec interface added in this patch is required to properly
support HDMI audio. Currently the audio part of the SoC internal
HDMI transmitter is configured with fixed values, which makes HDMI
audio working by chance, only on boards having an external audio
codec connected in parallel with
https://bugs.freedesktop.org/show_bug.cgi?id=103393
--- Comment #7 from Ilia Mirkin ---
An updated patch fixes the issue in a more complete way (with multiple shaders
being linked together, even non-variable local sizes were broken). This is now
upstream in
commit 4d24a7cb97641cacecd371d1968f696
https://bugs.freedesktop.org/show_bug.cgi?id=103401
--- Comment #7 from Sergey Kondakov ---
(In reply to Michel Dänzer from comment #3)
> Please attach the full corresponding Xorg log file and output of glxinfo.
>
> Looks like the crash happens in Mesa.
>
> Would be helpful if you could get mor
https://bugs.freedesktop.org/show_bug.cgi?id=103401
--- Comment #6 from Sergey Kondakov ---
Created attachment 135005
--> https://bugs.freedesktop.org/attachment.cgi?id=135005&action=edit
glxinfo_20171023
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=103401
--- Comment #5 from Sergey Kondakov ---
Created attachment 135004
--> https://bugs.freedesktop.org/attachment.cgi?id=135004&action=edit
X log from startx
Not a hint for trouble.
--
You are receiving this mail because:
You are the assignee f
https://bugs.freedesktop.org/show_bug.cgi?id=103401
--- Comment #4 from Sergey Kondakov ---
Created attachment 135003
--> https://bugs.freedesktop.org/attachment.cgi?id=135003&action=edit
X log from lightdm
It's not much bigger than a snippet above.
--
You are receiving this mail because:
Yo
On 10/23/2017 03:27 AM, Inki Dae wrote:
>> +static int hdmi_audio_digital_mute(struct device *dev, void *data, bool
>> mute)
>> +{
>> +struct hdmi_context *hdata = dev_get_drvdata(dev);
>> +
>> +mutex_lock(&hdata->mutex);
>> +
>> +hdata->audio.enable = !mute;
>
> Wouldn't it be bette
https://bugs.freedesktop.org/show_bug.cgi?id=103415
Bug ID: 103415
Summary: System is accepting the invalid Username
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: NEW
S
Both patches:
Reviewed-by: Nicolai Hähnle
On 20.10.2017 16:57, Andres Rodriguez wrote:
Generated using make headers_install from:
airlied/drm-next 282dc83 Merge tag 'drm-intel-next-2017-10-12' ...
Signed-off-by: Andres Rodriguez
---
include/drm/amdgpu_drm.h | 31 ++
https://bugs.freedesktop.org/show_bug.cgi?id=103304
Nicolai Hähnle changed:
What|Removed |Added
Resolution|--- |NOTOURBUG
Status|NEW
https://bugzilla.kernel.org/show_bug.cgi?id=194761
--- Comment #90 from Jean Delvare (jdelv...@suse.de) ---
yousifjkadom, your problem has nothing to do with this bug, please create a new
bug for it.
--
You are receiving this mail because:
You are watching the assignee of the bug.
__
https://bugs.freedesktop.org/show_bug.cgi?id=103384
--- Comment #1 from Michel Dänzer ---
Which components did you update exactly, from which version to which?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mail
On 20/10/17 18:20, Sean Paul wrote:
On Wed, Oct 18, 2017 at 1:11 PM, Meghana Madhyastha
wrote:
On Mon, Oct 16, 2017 at 02:26:00PM -0400, Sean Paul wrote:
On Fri, Oct 13, 2017 at 6:42 PM, Noralf Trønnes wrote:
Den 13.10.2017 22.25, skrev Sean Paul:
On Fri, Oct 13, 2017 at 04:11:43PM +0530,
On 21/10/17 12:55, Meghana Madhyastha wrote:
Changes in v14:
- s/backlight_get/of_find_backlight/ in patch 2/3
- Change commit message in patch 3/3 from requiring to acquiring
Can you take a look at
https://www.spinics.net/lists/dri-devel/msg154459.html ? This doesn't
seem to have been acted o
https://bugs.freedesktop.org/show_bug.cgi?id=103401
Michel Dänzer changed:
What|Removed |Added
Product|xorg|Mesa
Component|Driver/AMDgpu
Hi Philipp,
On Thursday, 19 October 2017 17:54:16 EEST Philipp Zabel wrote:
> On Thu, 2017-10-19 at 16:39 +0300, Laurent Pinchart wrote:
> > On Thursday, 19 October 2017 16:01:54 EEST Philipp Zabel wrote:
> >> On Thu, 2017-10-19 at 13:26 +0200, Matthias Brugger wrote:
> >>> In theory the MMSYS dev
https://bugs.freedesktop.org/show_bug.cgi?id=103413
Bug ID: 103413
Summary: R9285 Xonotic gpu lock since radeonsi: split
si_emit_shader_pointer
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (
https://bugs.freedesktop.org/show_bug.cgi?id=103317
Michel Dänzer changed:
What|Removed |Added
CC||harry.wentl...@amd.com,
https://bugs.freedesktop.org/show_bug.cgi?id=103317
Michel Dänzer changed:
What|Removed |Added
Attachment #134943|text/x-log |text/plain
mime type|
Hi Dave,
unfortunately we found some issues with the new perfmon implementation
post-merge, so here are 2 patches to disable the feature again. It
keeps most of the code in place, so we can fix it up in-tree, but
rejects any requests from userspace using the feature.
Regards,
Lucas
The following
https://bugs.freedesktop.org/show_bug.cgi?id=102655
Marta Löfstedt changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this mail
>> ret = i2c_smbus_write_byte_data(client, offset, value);
>> -if (ret < 0) {
>> -dev_err(ctx->dev, "writebm: %4s[0x%02x] <- 0x%02x\n",
>> -sii9234_client_name[id], offset, value);
>> -ctx->i2c_error = ret;
>> -}
>> +if (!ret)
>> +
From: Andrzej Pietrasiewicz
There are two Scaler devices in Exynos5433 SoCs. Add nodes for them and
their SYSMMU controllers.
Signed-off-by: Andrzej Pietrasiewicz
Signed-off-by: Marek Szyprowski
---
arch/arm64/boot/dts/exynos/exynos5433.dtsi | 42 ++
1 file changed
This patch adapts Exynos DRM FIMC driver to new IPP v2 core API.
The side effect of this conversion is a switch to driver component API
to register properly in the Exynos DRM core.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/Kconfig | 2 +-
drivers/gpu/drm/exynos/exyno
Dear all,
This patchset performs complete rewrite of Exynos DRM IPP subsystem and
its userspace API.
Why such rewrite is needed? Exynos DRM IPP API is over-engineered in
general, but not really extensible on the other side. It is also buggy,
with significant design flaws:
- Userspace API covers m
This patch adapts Exynos DRM GScaler driver to new IPP v2 core API.
The side effect of this conversion is a switch to driver component API
to register properly in the Exynos DRM core. During the conversion
driver has been adapted to support more specific compatible strings
to distinguish between Ex
Some hardware modules, like FIMC in Exynos4 series are shared between
V4L2 (camera support) and DRM (memory-to-memory processing) subsystems.
This patch provides a simple check to let such drivers to be used in the
driver components framework.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/
From: Andrzej Pietrasiewicz
There are 3 scaler devices in Exynos5420 SoCs, all are a part of MSCL
power domain. MSCL power domain and SYSMMU controllers (two per each
scaler device) have been already added to exynos5420.dtsi earlier,
so bind them to newly added devices.
Signed-off-by: Andrzej Pi
From: Andrzej Pietrasiewicz
Exynos Scaler is a hardware module, which processes graphic data fetched
from memory and transfers the resultant dato another memory buffer.
Graphics data can be up/down-scaled, rotated, flipped and converted color
space. Scaler hardware modules are a part of Exynos542
This patch adds Exynos IPP v2 subsystem and userspace API.
New userspace API is focused ONLY on memory-to-memory image processing.
The two remainging IPP operation modes (framebuffer writeback and
local-path output with image processing) can be implemented using
standard DRM features: writeback co
Exynos IPP will be rewritten, so remove current IPP core code and mark
existing drivers as BROKEN.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/Kconfig | 11 +-
drivers/gpu/drm/exynos/Makefile |1 -
drivers/gpu/drm/exynos/exynos_drm_drv.c | 12 -
drivers/gp
This patch adapts Exynos DRM rotator driver to new IPP v2 core API.
The side effect of this conversion is a switch to driver component API
to register properly in the Exynos DRM core.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/Kconfig | 2 +-
drivers/gpu/drm/exynos
https://bugs.freedesktop.org/show_bug.cgi?id=103403
--- Comment #4 from korbenpl ---
Comment on attachment 134989
--> https://bugs.freedesktop.org/attachment.cgi?id=134989
specs included
[rafal@rafal-pc ~]$ inxi -Fxzc0
System: Host: rafal-pc Kernel: 4.9.53-1-MANJARO x86_64
bits: 64 gcc: 7.2.0
https://bugs.freedesktop.org/show_bug.cgi?id=103403
--- Comment #3 from korbenpl ---
Comment on attachment 134989
--> https://bugs.freedesktop.org/attachment.cgi?id=134989
specs included
[rafal@rafal-pc ~]$ inxi -Fxzc0
System: Host: rafal-pc Kernel: 4.9.53-1-MANJARO x86_64
bits: 64 gcc: 7.2.0
https://bugs.freedesktop.org/show_bug.cgi?id=103403
--- Comment #2 from korbenpl ---
Comment on attachment 134989
--> https://bugs.freedesktop.org/attachment.cgi?id=134989
specs included
[rafal@rafal-pc ~]$ inxi -Fxzc0
System: Host: rafal-pc Kernel: 4.9.53-1-MANJARO x86_64
bits: 64 gcc: 7.2.0
https://bugs.freedesktop.org/show_bug.cgi?id=103403
--- Comment #1 from korbenpl ---
Created attachment 134999
--> https://bugs.freedesktop.org/attachment.cgi?id=134999&action=edit
a vid of the glitch
--
You are receiving this mail because:
You are the assignee for the bug.___
On 20/10/17 20:09, Tony Lindgren wrote:
> # lsmod
> Module Size Used by
> omapdrm69632 0
> drm_kms_helper163840 1 omapdrm
> cfbfillrect16384 1 drm_kms_helper
> syscopyarea16384 1 drm_kms_helper
> cfbimgblt 16384 1
On some hardware the LCD panel is not mounted upright in the casing,
but rotated by 90 degrees. In this case we want the console to
automatically be rotated to compensate.
The drm subsys has a quirk table for this, use the
drm_get_panel_orientation_quirk function to get the panel orientation
and s
Ideally we could use the VBT for this, that would be simple, in
intel_dsi_init() check dev_priv->vbt.dsi.config->rotation, set
connector->display_info.panel_orientation accordingly and call
drm_connector_init_panel_orientation_property(), done.
Unfortunately vbt.dsi.config->rotation is always 0 ev
On some hardware the LCD panel is not mounted upright in the casing,
but upside-down or rotated 90 degrees. In this case we want the console
to automatically be rotated to compensate.
The fbdev-driver may know about the need to rotate. Add a new
fbcon_rotate_hint field to struct fb_info, which get
On Tue, Oct 17, 2017 at 11:06:22AM +0200, Maxime Ripard wrote:
> The TCON supports the LVDS interface to output to a panel or a bridge.
> Let's add support for it.
>
> Signed-off-by: Maxime Ripard
> ---
> drivers/gpu/drm/sun4i/Makefile | 1 +-
> drivers/gpu/drm/sun4i/sun4i_lvds.c | 183 +++
Some x86 clamshell design devices use portrait tablet screens and a display
engine which cannot rotate in hardware, so the firmware just leaves things
as is and we cannot figure out that the display is oriented non upright
from the hardware.
So at least on x86, we need a quirk table for this. This
This is now all handled in the drivers and communicated through
fb_info.fbcon_rotate_hint.
Signed-off-by: Hans de Goede
---
drivers/video/fbdev/core/Makefile | 3 -
drivers/video/fbdev/core/fbcon.c| 4 +-
drivers/video/fbdev/core/fbcon.h| 6 --
drivers/vid
Hi All,
Here is v3 of my series to add a "panel orientation" property to
the drm-connector for the LCD panel to let userspace know about LCD
panels which are not mounted upright, as well as detecting upside-down
panels without needing quirks (like we do for 90 degree rotated screens).
As requeste
Hi Maxime,
On 17 October 2017 at 20:06, Maxime Ripard
wrote:
> The TCON supports the LVDS interface to output to a panel or a bridge.
> Let's add support for it.
>
> Signed-off-by: Maxime Ripard
> ---
> drivers/gpu/drm/sun4i/Makefile | 1 +-
> drivers/gpu/drm/sun4i/sun4i_lvds.c | 183
Apply the "panel orientation" drm connector prop to the primary plane so
that fbcon and fbdev using userspace programs display the right way up.
Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=94894
Signed-off-by: Hans de Goede
---
Changes in v2:
-New patch in v2 of this patch-set
Changes in
On some devices the LCD panel is mounted in the casing in such a way that
the up/top side of the panel does not match with the top side of the
device (e.g. it is mounted upside-down).
This commit adds the necessary infra for lcd-panel drm_connector-s to
have a "panel orientation" property to commu
On Sun, Oct 22, 2017 at 09:32:46PM +0200, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 22 Oct 2017 21:21:44 +0200
>
> * Add a jump target so that a bit of exception handling can be better
> reused at the end of this function.
>
> This issue was detected by using the Coccinell
79 matches
Mail list logo
