Hi Jagadeesh,
Thank you for the patch.
On Thu, Mar 28, 2019 at 02:41:56AM +0530, jagdsh.li...@gmail.com wrote:
> From: Jagadeesh Pagadala
>
> Remove duplicate headers which are included twice.
Could you, while at it, also sort the existing #include statements
alphabetically ? This should help
On Wed, Mar 27, 2019 at 11:25 AM Greg KH wrote:
>
> On Tue, Mar 05, 2019 at 12:54:29PM -0800, John Stultz wrote:
> > From: "Andrew F. Davis"
> >
> > This framework allows a unified userspace interface for dma-buf
> > exporters, allowing userland to allocate specific types of
> > memory for use in
This driver is for the ASPEED BMC SoC's GFX display hardware. This
driver runs on the ARM based BMC systems, unlike the ast driver which
runs on a host CPU and is is for a PCI graphics device.
Signed-off-by: Joel Stanley
--
Changes since RFC:
drm_fbdev_cma_init -> drm_fb_cma_fbdev_init and use g
This describes the ASPEED BMC SoC's display controller.
Signed-off-by: Joel Stanley
---
.../devicetree/bindings/gpu/aspeed-gfx.txt| 41 +++
1 file changed, 41 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpu/aspeed-gfx.txt
diff --git a/Documentation/de
ubmitted a RFC about a year ago.
https://patchwork.kernel.org/patch/10339605/
I've fixed all of the issues I had in the RFC, and made the cleanups
that Eric suggested in that review. This version is based on
next-20190327.
Joel Stanley (2):
dt-bindings: gpu: Add ASPEED GFX bindings docu
https://bugs.freedesktop.org/show_bug.cgi?id=110264
Bug ID: 110264
Summary: the drivers are not working properly
Product: DRI
Version: DRI git
Hardware: Other
OS: Windows (All)
Status: NEW
Severity: minor
Hi Dave,
The following changes since commit 0bec6219e5a0cf2dd17716949a7592807e10f3d7:
Merge tag 'drm-misc-next-2019-03-21' of
git://anongit.freedesktop.org/drm/drm-misc into drm-next (2019-03-25 11:05:12
+0100)
are available in the Git repository at:
git://linuxtv.org/pinchartl/media.git
https://bugzilla.kernel.org/show_bug.cgi?id=202799
--- Comment #8 from Clément Guérin (li...@protonmail.com) ---
Do you need anything else?
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel mailing list
dri
https://bugzilla.kernel.org/show_bug.cgi?id=202445
--- Comment #29 from Clément Guérin (li...@protonmail.com) ---
Any progress on this?
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel mailing list
dri-dev
Hi, Yongqiang:
On Wed, 2019-03-27 at 14:19 +0800, yongqiang@mediatek.com wrote:
> From: Yongqiang Niu
>
> Here is two modifition in this patch:
> 1.bls->dpi0 and rdma1->dsi are differen usecase,
> Split DISP_REG_CONFIG_DSI_SEL setting into anther usecase
> 2.remove DISP_REG_CONFIG_DPI_SEL se
Hi Dave, Daniel,
Just one fix this week for freesync.
The following changes since commit 72464382fc2d3673eb51f21a57f2c0a320c1552f:
drm/amdgpu: fix invalid use of change_bit (2019-03-19 14:01:42 -0500)
are available in the Git repository at:
git://people.freedesktop.org/~agd5f/linux drm-fix
Hi, Yongqiang:
On Wed, 2019-03-27 at 14:18 +0800, yongqiang@mediatek.com wrote:
> From: Yongqiang Niu
>
> This patch add display nodes for mt8183
I think this patch should be after binding document patch. You should
define the compatible string then you could add device node.
>
> Change-I
Hi, Yongqiang:
On Wed, 2019-03-27 at 14:19 +0800, yongqiang@mediatek.com wrote:
> From: Yongqiang Niu
>
> mutex0 SOF register offset not always 0x30.
> for mt8183, that offset will be 0x2C,
> add this regsiter offset into private data
I think you do two things in this patch. One is mutex0 S
https://bugs.freedesktop.org/show_bug.cgi?id=110258
Alex Deucher changed:
What|Removed |Added
Component|DRM/amdkfd |DRM/AMDgpu
--
You are receiving this ma
On Mon, 25 Mar 2019 at 22:49, Joonas Lahtinen
wrote:
>
> Hi Dave & Daniel,
>
> First batch of features for 5.2, tagged last week.
I asked on irc, but got no answer I saw,
/home/airlied/devel/kernel/dim/src/drivers/gpu/drm/i915/i915_gem_context.c:698:12:
warning: ‘context_barrier_task’ defined but
Hi, Yongqiang:
On Wed, 2019-03-27 at 14:18 +0800, yongqiang@mediatek.com wrote:
> From: Yongqiang Niu
>
> mutex0 MOD register offset not always 0x2C.
> for mt8183, that offset will be 0x30,
> add this regsiter offset into private data
>
> Signed-off-by: Yongqiang Niu
> ---
> drivers/gpu/d
Convert the drm filesystem to the new internal mount API as the old
one will be obsoleted and removed. This allows greater flexibility in
communication of mount parameters between userspace, the VFS and the
filesystem.
See Documentation/filesystems/mount_api.txt for more information.
Signed-off-
19. 3. 26. 오후 10:19에 Daniel Vetter 이(가) 쓴 글:
> This will give the exynos fbdev a name!
>
> v2: Rebase
>
> Signed-off-by: Daniel Vetter
Acked-by: Inki Dae
Thanks,
Inki Dae
> Cc: Inki Dae
> Cc: Joonyoung Shim
> Cc: Seung-Woo Kim
> Cc: Kyungmin Park
> Cc: Kukjin Kim
> Cc: Krzysztof Kozlo
On Mon, Mar 4, 2019 at 6:51 AM Josef Lusticky wrote:
>
S-o-b and commit msg?
> ---
> MAINTAINERS | 6 +
> drivers/gpu/drm/panel/Kconfig| 7 +
> drivers/gpu/drm/panel/Makefile | 1 +
> drivers/gpu/drm/panel/panel-ilitek-ili9341
On Mon, Mar 04, 2019 at 01:50:33PM +0100, Josef Lusticky wrote:
> ---
You need a commit message and a Signed-off-by. Run checkpatch.pl, it
will tell you these things.
> .../bindings/display/panel/ilitek,ili9341.txt | 33 +++
> 1 file changed, 33 insertions(+)
> create mode 1006
On Mon, Mar 04, 2019 at 11:58:02AM +0100, Neil Armstrong wrote:
> Add the bindings for the Bifrost family of ARM Mali GPUs.
>
> The Bifrost GPU architecture is similar to the Midgard family,
> but with a different Shader Core & Execution Engine structures.
>
> Bindings are based on the Midgard fa
Neil Armstrong writes:
> Hi,
>
> On 26/03/2019 21:40, Vasily Khoruzhick wrote:
>> Hi,
>>
>> So what's the status of it?
>
> We are waiting on ARM to give a feedback on the ARM GPU tile modifier,
> see https://patchwork.freedesktop.org/patch/292187/?series=57996&rev=1
I don't see any dependency
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #73 from Bastian ---
(In reply to Bastian from comment #69)
> Distro/Kernel: Ubuntu 18.04.2/5.0.2
> GPU AMD: Readon RX570 - Mesa 19.0
> Display: Iiyama G23530HSU 75hz
> Desktop: Gnome
>
> video: https://www.youtub
On Wed, Mar 20, 2019 at 02:38:23PM +0800, Zhaoyang Huang wrote:
> From: Zhaoyang Huang
>
> Two action for this patch:
> 1. set a batch size for system heap's shrinker, which can have it buffer
> reasonable page blocks in pool for future allocation.
> 2. reverse the order sequence when free page b
https://bugs.freedesktop.org/show_bug.cgi?id=110229
--- Comment #9 from Laurent ---
Ok I stop posting here, no one is responding. I've corrected the compilation
errors.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-d
From: Ville Syrjälä
[ Upstream commit c978ae9bde582e82a04c63a4071701691dd8b35c ]
We aren't supposed to force a stop+start between every i2c msg
when performing multi message transfers. This should eg. cause
the DDC segment address to be reset back to 0 between writing
the segment address and rea
On Tue, Mar 05, 2019 at 12:54:29PM -0800, John Stultz wrote:
> From: "Andrew F. Davis"
>
> This framework allows a unified userspace interface for dma-buf
> exporters, allowing userland to allocate specific types of
> memory for use in dma-buf sharing.
>
> Each heap is given its own device node,
From: Manfred Schlaegl
[ Upstream commit a5399db139cb3ad9b8502d8b1bd02da9ce0b9df0 ]
There is no clipping on the x or y axis for logos larger that the framebuffer
size. Therefore: a logo bigger than screen size leads to invalid memory access:
[1.254664] Backtrace:
[1.254728] [] (cfb_imag
From: Ville Syrjälä
[ Upstream commit c978ae9bde582e82a04c63a4071701691dd8b35c ]
We aren't supposed to force a stop+start between every i2c msg
when performing multi message transfers. This should eg. cause
the DDC segment address to be reset back to 0 between writing
the segment address and rea
From: Manfred Schlaegl
[ Upstream commit a5399db139cb3ad9b8502d8b1bd02da9ce0b9df0 ]
There is no clipping on the x or y axis for logos larger that the framebuffer
size. Therefore: a logo bigger than screen size leads to invalid memory access:
[1.254664] Backtrace:
[1.254728] [] (cfb_imag
From: Ville Syrjälä
[ Upstream commit c978ae9bde582e82a04c63a4071701691dd8b35c ]
We aren't supposed to force a stop+start between every i2c msg
when performing multi message transfers. This should eg. cause
the DDC segment address to be reset back to 0 between writing
the segment address and rea
From: Daniel Vetter
[ Upstream commit 934c5b32a5e43d8de2ab4f1566f91d7c3bf8cb64 ]
The correct way for legacy drivers to update properties that need to
do a full modeset, is to do a full modeset.
Note that we don't need to call the drm_mode_config_internal helper
because we're not changing any of
From: Manfred Schlaegl
[ Upstream commit a5399db139cb3ad9b8502d8b1bd02da9ce0b9df0 ]
There is no clipping on the x or y axis for logos larger that the framebuffer
size. Therefore: a logo bigger than screen size leads to invalid memory access:
[1.254664] Backtrace:
[1.254728] [] (cfb_imag
From: Ville Syrjälä
[ Upstream commit c978ae9bde582e82a04c63a4071701691dd8b35c ]
We aren't supposed to force a stop+start between every i2c msg
when performing multi message transfers. This should eg. cause
the DDC segment address to be reset back to 0 between writing
the segment address and rea
From: Daniel Vetter
[ Upstream commit 934c5b32a5e43d8de2ab4f1566f91d7c3bf8cb64 ]
The correct way for legacy drivers to update properties that need to
do a full modeset, is to do a full modeset.
Note that we don't need to call the drm_mode_config_internal helper
because we're not changing any of
From: Chris Wilson
[ Upstream commit 227ad6d957898a88b1746e30234ece64d305f066 ]
Delay the drm_modeset_acquire_init() until after we check for an
allocation failure so that we can return immediately upon error without
having to unwind.
WARNING: lock held when returning to user space!
4.20.0+ #17
From: Paul Kocialkowski
[ Upstream commit 890880ddfdbe256083170866e49c87618b706ac7 ]
When drivers pass non-empty lists of modifiers for initializing their
planes, we can infer that they allow framebuffer modifiers and set the
driver's allow_fb_modifiers mode config element.
In case the allow_fb
From: Chen-Yu Tsai
[ Upstream commit cec2b18832e26bc866bef2be22eff4e25bbc4034 ]
gpiod_get_value() gives out a warning if access to the underlying gpiochip
requires sleeping, which is common for I2C based chips:
WARNING: CPU: 0 PID: 77 at drivers/gpio/gpiolib.c:2500
gpiod_get_value+0xd0/0x1
From: Manfred Schlaegl
[ Upstream commit a5399db139cb3ad9b8502d8b1bd02da9ce0b9df0 ]
There is no clipping on the x or y axis for logos larger that the framebuffer
size. Therefore: a logo bigger than screen size leads to invalid memory access:
[1.254664] Backtrace:
[1.254728] [] (cfb_imag
From: Emil Velikov
[ Upstream commit 8059add0478e29cb641936011a8fcc9ce9fd80be ]
There are cases (in mesa and applications) where one would open the
primary node without properly authenticating the client.
Sometimes we don't check if the authentication succeeds, but there's
also cases we simply
From: Ville Syrjälä
[ Upstream commit c978ae9bde582e82a04c63a4071701691dd8b35c ]
We aren't supposed to force a stop+start between every i2c msg
when performing multi message transfers. This should eg. cause
the DDC segment address to be reset back to 0 between writing
the segment address and rea
From: Chris Wilson
[ Upstream commit 227ad6d957898a88b1746e30234ece64d305f066 ]
Delay the drm_modeset_acquire_init() until after we check for an
allocation failure so that we can return immediately upon error without
having to unwind.
WARNING: lock held when returning to user space!
4.20.0+ #17
From: Peter Wu
[ Upstream commit 00eb5b0da8d27b3c944bfc959c3344d665caae26 ]
After drm_fb_helper_fbdev_setup calls drm_fb_helper_init,
"dev->fb_helper" will be initialized (and thus drm_fb_helper_fini will
have some effect). After that, drm_fb_helper_initial_config is called
which may call the "f
From: Paul Kocialkowski
[ Upstream commit 890880ddfdbe256083170866e49c87618b706ac7 ]
When drivers pass non-empty lists of modifiers for initializing their
planes, we can infer that they allow framebuffer modifiers and set the
driver's allow_fb_modifiers mode config element.
In case the allow_fb
From: Daniel Vetter
[ Upstream commit 934c5b32a5e43d8de2ab4f1566f91d7c3bf8cb64 ]
The correct way for legacy drivers to update properties that need to
do a full modeset, is to do a full modeset.
Note that we don't need to call the drm_mode_config_internal helper
because we're not changing any of
From: Nicholas Kazlauskas
[ Upstream commit 428da2bdb05d76c48d0bd8fbfa2e4c102685be08 ]
[Why]
In order to read CRC events when CRC capture is enabled the vblank
interrput handler needs to be running for the CRTC. The handler is
enabled while there is an active vblank reference.
When running IGT
From: Shayenne Moura
[ Upstream commit def35e7c592616bc09be328de8795e5e624a3cf8 ]
kms_flip tests are breaking on vkms when simulate vblank because vblank
event sequence count returns one extra frame after arm vblank event to
make a page flip.
When vblank interrupt happens, userspace processes t
From: Chen-Yu Tsai
[ Upstream commit cec2b18832e26bc866bef2be22eff4e25bbc4034 ]
gpiod_get_value() gives out a warning if access to the underlying gpiochip
requires sleeping, which is common for I2C based chips:
WARNING: CPU: 0 PID: 77 at drivers/gpio/gpiolib.c:2500
gpiod_get_value+0xd0/0x1
On Tue, Mar 26, 2019 at 04:44:54PM -0400, Sean Paul wrote:
> From: Sean Paul
>
> This patch adds a new drm helper library to help drivers implement
> self refresh. Drivers choosing to use it will register crtcs and
> will receive callbacks when it's time to enter or exit self refresh
> mode.
>
>
From: Manfred Schlaegl
[ Upstream commit a5399db139cb3ad9b8502d8b1bd02da9ce0b9df0 ]
There is no clipping on the x or y axis for logos larger that the framebuffer
size. Therefore: a logo bigger than screen size leads to invalid memory access:
[1.254664] Backtrace:
[1.254728] [] (cfb_imag
From: Julia Lawall
[ Upstream commit 4c6d8fc20b09f9684743afd72e4dbc3f15524479 ]
Add an of_node_put when the result of of_graph_get_remote_port_parent is
not available.
Add a second of_node_put if no encoder is selected (encoder remains NULL).
The semantic match that finds the first problem is
From: Nicholas Kazlauskas
[ Upstream commit 77476360f173c127c191bfe8ca8113130ef283b8 ]
[Why]
This fixes an mpc programming error for the following sequence of
atomic commits when pipe split is enabled:
Commit 1: CRTC0 (plane 4, plane 3)
Pipe 0: old_plane_state = A0, new_plane_state = A1, new
From: Nicholas Kazlauskas
[ Upstream commit 5062b797db4103218fa00ee254417b8ecaab7401 ]
[Why]
There are opt1c lock warnings and CRTC read timeouts when running the
"igt@kms_plane@plane-position-hole-dpms-pipe-*" tests. These are
caused by trying to reprogram planes that are not in the current
con
From: Emil Velikov
[ Upstream commit 8059add0478e29cb641936011a8fcc9ce9fd80be ]
There are cases (in mesa and applications) where one would open the
primary node without properly authenticating the client.
Sometimes we don't check if the authentication succeeds, but there's
also cases we simply
From: Nicholas Kazlauskas
[ Upstream commit d8d2f174bcc2c26c3485c70e0c6fe22b27bce739 ]
[Why]
The stream->mode_changed flag can persist in the following sequence
of atomic commits:
Commit 1:
Enable CRTC0 (mode_changed = true), Enable CRTC1 (mode_changed = true)
Commit 2:
Disable CRTC1 (mode_cha
From: Ville Syrjälä
[ Upstream commit c978ae9bde582e82a04c63a4071701691dd8b35c ]
We aren't supposed to force a stop+start between every i2c msg
when performing multi message transfers. This should eg. cause
the DDC segment address to be reset back to 0 between writing
the segment address and rea
From: Chris Wilson
[ Upstream commit 227ad6d957898a88b1746e30234ece64d305f066 ]
Delay the drm_modeset_acquire_init() until after we check for an
allocation failure so that we can return immediately upon error without
having to unwind.
WARNING: lock held when returning to user space!
4.20.0+ #17
From: Peter Wu
[ Upstream commit 00eb5b0da8d27b3c944bfc959c3344d665caae26 ]
After drm_fb_helper_fbdev_setup calls drm_fb_helper_init,
"dev->fb_helper" will be initialized (and thus drm_fb_helper_fini will
have some effect). After that, drm_fb_helper_initial_config is called
which may call the "f
From: Paul Kocialkowski
[ Upstream commit 890880ddfdbe256083170866e49c87618b706ac7 ]
When drivers pass non-empty lists of modifiers for initializing their
planes, we can infer that they allow framebuffer modifiers and set the
driver's allow_fb_modifiers mode config element.
In case the allow_fb
From: Daniel Vetter
[ Upstream commit 934c5b32a5e43d8de2ab4f1566f91d7c3bf8cb64 ]
The correct way for legacy drivers to update properties that need to
do a full modeset, is to do a full modeset.
Note that we don't need to call the drm_mode_config_internal helper
because we're not changing any of
From: Chen-Yu Tsai
[ Upstream commit cec2b18832e26bc866bef2be22eff4e25bbc4034 ]
gpiod_get_value() gives out a warning if access to the underlying gpiochip
requires sleeping, which is common for I2C based chips:
WARNING: CPU: 0 PID: 77 at drivers/gpio/gpiolib.c:2500
gpiod_get_value+0xd0/0x1
From: Tetsuo Handa
[ Upstream commit b30b61ff6b1dc37f276cf56a8328b80086a3ffca ]
syzbot is hitting a lockdep warning [1] because flush_work() is called
without INIT_WORK() after kzalloc() at vkms_atomic_crtc_reset().
Commit 6c234fe37c57627a ("drm/vkms: Implement CRC debugfs API") added
INIT_WORK
From: Nicholas Kazlauskas
[ Upstream commit 428da2bdb05d76c48d0bd8fbfa2e4c102685be08 ]
[Why]
In order to read CRC events when CRC capture is enabled the vblank
interrput handler needs to be running for the CRTC. The handler is
enabled while there is an active vblank reference.
When running IGT
From: Julia Lawall
[ Upstream commit 4c6d8fc20b09f9684743afd72e4dbc3f15524479 ]
Add an of_node_put when the result of of_graph_get_remote_port_parent is
not available.
Add a second of_node_put if no encoder is selected (encoder remains NULL).
The semantic match that finds the first problem is
From: Stephen Boyd
[ Upstream commit 070e64dc1bbc879b7e0e9fffccd9dd139baf89f0 ]
Devices that make up DPU, i.e. graphics card, request their interrupts
from this "virtual" interrupt chip. The interrupt chip builds upon a GIC
SPI interrupt that raises high when any of the interrupts in the DPU's
i
From: Shayenne Moura
[ Upstream commit ba420afab565bdc7b028ddd4f60f2de7a1db ]
When the vblank irq happens, kernel time subsystem executes
`vkms_vblank_simulate`. In parallel or not, it prepares all stuff
necessary to the next vblank with arm, and it must flush these stuff
before the next vbl
From: Shayenne Moura
[ Upstream commit def35e7c592616bc09be328de8795e5e624a3cf8 ]
kms_flip tests are breaking on vkms when simulate vblank because vblank
event sequence count returns one extra frame after arm vblank event to
make a page flip.
When vblank interrupt happens, userspace processes t
From: Manfred Schlaegl
[ Upstream commit a5399db139cb3ad9b8502d8b1bd02da9ce0b9df0 ]
There is no clipping on the x or y axis for logos larger that the framebuffer
size. Therefore: a logo bigger than screen size leads to invalid memory access:
[1.254664] Backtrace:
[1.254728] [] (cfb_imag
From: Nicholas Kazlauskas
[ Upstream commit 77476360f173c127c191bfe8ca8113130ef283b8 ]
[Why]
This fixes an mpc programming error for the following sequence of
atomic commits when pipe split is enabled:
Commit 1: CRTC0 (plane 4, plane 3)
Pipe 0: old_plane_state = A0, new_plane_state = A1, new
From: Nicholas Kazlauskas
[ Upstream commit 5062b797db4103218fa00ee254417b8ecaab7401 ]
[Why]
There are opt1c lock warnings and CRTC read timeouts when running the
"igt@kms_plane@plane-position-hole-dpms-pipe-*" tests. These are
caused by trying to reprogram planes that are not in the current
con
From: Emil Velikov
[ Upstream commit 8059add0478e29cb641936011a8fcc9ce9fd80be ]
There are cases (in mesa and applications) where one would open the
primary node without properly authenticating the client.
Sometimes we don't check if the authentication succeeds, but there's
also cases we simply
From: Bas Nieuwenhuizen
[ Upstream commit 1decbf6bb0b4dc56c9da6c5e57b994ebfc2be3aa ]
Some blocks in amdgpu can have 0 rqs.
Job creation already fails with -ENOENT when entity->rq is NULL,
so jobs cannot be pushed. Without a rq there is no scheduler to
pop jobs, and rq selection already does the
From: Nicholas Kazlauskas
[ Upstream commit d8d2f174bcc2c26c3485c70e0c6fe22b27bce739 ]
[Why]
The stream->mode_changed flag can persist in the following sequence
of atomic commits:
Commit 1:
Enable CRTC0 (mode_changed = true), Enable CRTC1 (mode_changed = true)
Commit 2:
Disable CRTC1 (mode_cha
From: Mathias Fröhlich
[ Upstream commit dcd5fb82ffb484124203aa339733663ac0b059f3 ]
Reference counting in amdgpu_dm_connector for amdgpu_dm_connector::dc_sink
and amdgpu_dm_connector::dc_em_sink as well as in dc_link::local_sink seems
to be out of shape. Thus make reference counting consistent f
From: Nathan Chancellor
[ Upstream commit 672e78cab819ebe31e3b9b8abac367be8a110472 ]
Clang warns when an expression that equals zero is used as a null
pointer constant (in lieu of NULL):
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:4435:3:
warning: expression which evaluates to z
On Wed, Mar 27, 2019 at 08:07:39PM +0530, Ramalingam C wrote:
> On 2019-03-27 at 12:06:39 +0100, Daniel Vetter wrote:
> > On Fri, Mar 22, 2019 at 06:14:48AM +0530, Ramalingam C wrote:
> > > Invoking the uevent generator for the content protection property state
> > > change of a connector. This hel
On Wed, Mar 27, 2019 at 08:19:55PM +0530, Ramalingam C wrote:
> On 2019-03-27 at 11:31:12 +0100, Daniel Vetter wrote:
> > On Fri, Mar 22, 2019 at 06:14:46AM +0530, Ramalingam C wrote:
> > > Populates the downstream info for HDCP2.2 encryption also. On success
> > > of encryption Blob is updated.
>
https://bugs.freedesktop.org/show_bug.cgi?id=110229
--- Comment #8 from Laurent ---
Ok I'm trying to recompile mesa to see if the bug is fixed, but, I've
compilation errors :
In file included from ../src/gallium/state_trackers/dri/dri_helpers.h:26:0,
from ../src/gallium/state_tr
Hi,
On Wed, Mar 27, 2019 at 09:30:59AM +0100, Daniel Vetter wrote:
> On Wed, Mar 27, 2019 at 12:23:43AM +0100, Ahmed S. Darwish wrote:
> > Otherwise gcc will complain about unknown types, and declarations
> > inside parameter lists, if "drm_internal.h" is used in C files with
> > less headers than
On Wed, Mar 27, 2019 at 3:46 PM Thomas Zimmermann wrote:
>
> Hi
>
> Am 27.03.19 um 10:41 schrieb Daniel Vetter:
> >> I use the current approach because it does not require modifications to
> >> DRM or fbdev. Not copying the fbdev driver code has the advantage that
> >> any fix that goes into fbdev
https://bugs.freedesktop.org/show_bug.cgi?id=109648
--- Comment #4 from jam...@amd.com ---
Test on bench with this patch. The hung issue was fixed.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri
Noralf Trønnes writes:
> drm_dev_register() initializes internal clients like bootsplash as the
> last thing it does, so all setup needs to be done at this point.
>
> Fix by calling vc4_kms_load() before registering.
> Also check the error code returned from that function.
>
> Cc: Eric Anholt
>
Rob Herring writes:
> On Wed, Mar 27, 2019 at 4:15 AM Neil Armstrong
> wrote:
>>
>> Hi,
>>
>> On 26/03/2019 21:40, Vasily Khoruzhick wrote:
>> > Hi,
>> >
>> > So what's the status of it?
>>
>> We are waiting on ARM to give a feedback on the ARM GPU tile modifier,
>> see https://patchwork.freede
https://bugs.freedesktop.org/show_bug.cgi?id=103900
--- Comment #5 from Syfer Polski ---
Based on
https://forum.warthunder.com/index.php?/topic/422637-game-crashes-before-going-into-hangar/&do=findComment&comment=8058647,
I seems like this bug hasn't been fixed(although the user in question didn'
On Wed, 27 Mar 2019 16:01:01 +0100
Noralf Trønnes wrote:
>
>
> Den 27.03.2019 15.13, skrev Emmanuel Vadot:
> >
> > Hi Noralf,
> >
> > On Tue, 26 Mar 2019 18:55:39 +0100
> > Noralf Trønnes wrote:
> >
> >> Move the modeset commit code to drm_client.
> >> No changes except exporting API.
> >>
Den 27.03.2019 15.13, skrev Emmanuel Vadot:
>
> Hi Noralf,
>
> On Tue, 26 Mar 2019 18:55:39 +0100
> Noralf Trønnes wrote:
>
>> Move the modeset commit code to drm_client.
>> No changes except exporting API.
>>
>> Signed-off-by: Noralf Trønnes
>> ---
>> drivers/gpu/drm/drm_client.c| 236
On Wed, Mar 13, 2019 at 8:21 PM Helen Koike wrote:
>
> Async update callbacks are expected to set the old_fb in the new_state
> so prepare/cleanup framebuffers are balanced.
>
> Cc: # v4.14+
> Fixes: 224a4c970987 ("drm/msm: update cursors asynchronously through atomic")
> Suggested-by: Boris Brez
On 2019-03-27 at 11:31:12 +0100, Daniel Vetter wrote:
> On Fri, Mar 22, 2019 at 06:14:46AM +0530, Ramalingam C wrote:
> > Populates the downstream info for HDCP2.2 encryption also. On success
> > of encryption Blob is updated.
> >
> > Additional two variable are added to downstream info blob. Such
Hi
Am 27.03.19 um 10:41 schrieb Daniel Vetter:
>> I use the current approach because it does not require modifications to
>> DRM or fbdev. Not copying the fbdev driver code has the advantage that
>> any fix that goes into fbdev is also used by fbdevdrm.
>>
>> OTOH, that has some problems. At least
https://bugs.freedesktop.org/show_bug.cgi?id=110251
Yuxuan Shui changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Den 18.03.2019 12.33, skrev Gerd Hoffmann:
> This patch moves the virtio_gpu_cmd_create_resource() call (which
> notifies the host about the new resource created) into the
> virtio_gpu_object_create() function. That way we can call
> virtio_gpu_cmd_create_resource() before ttm_bo_init(), so the
From: chunhui dai
The parent rate of hdmi phy had set by DPI driver.
We should not set or change the parent rate of MT2701 hdmi phy,
as a result we should remove the flags of "CLK_SET_RATE_PARENT"
from the clock of MT2701 hdmi phy.
Signed-off-by: chunhui dai
Signed-off-by: wangyan wang
---
dr
From: chunhui dai
The factor depends on the divider of DPI in MT2701, therefore,
we should fix this factor to the right and new one.
Signed-off-by: chunhui dai
Signed-off-by: wangyan wang
---
drivers/gpu/drm/mediatek/mtk_dpi.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
dif
Sorry for the spam whosoever has got the last mail, as the last did not
get to
the mailing list, and it bounced, so sending it again.
On 3/27/2019 8:49 AM, YueHaibing wrote:
Make sure of_device_id tables are NULL terminated
Found by coccinelle spatch "misc/of_table.cocci"
Signed-off-by: YueHai
Hello,
On 2/1/19 22:05, Stefan Agner wrote:
> On 02.01.2019 18:02, Ahmad Fatoum wrote:
>> Hello,
>>
>> I got a board with the RED[0:7]/BLUE[0:7] lanes originating from the
>> LCDIF swapped and would like to describe this in the device tree:
>>
>> This first patch extends the mxsfb driver to suppor
From: Wangyan Wang
V7 adopt maintainer's suggestion.
Here is the change list between V6 & V7
1. use readl directly & delete hdmi_phy->pll_rate in
mtk_hdmi_pll_recalc_rate().
in "drm/mediatek: recalculate hdmi ..."
2. detele mtk_hdmi_phy_read() in mtk_hdmi_phy.c.
in "fix the rate of parent for
From: chunhui dai
We should not change the rate of parent for hdmi phy when
doing round_rate for this clock. The parent clock of hdmi
phy must be the same as it. We change it when doing set_rate
only.
Signed-off-by: chunhui dai
Signed-off-by: wangyan wang
---
drivers/gpu/drm/mediatek/mtk_hdmi
On 3/23/2019 8:16 AM, YueHaibing wrote:
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/gpu/drm/vmwgfx/vmwgfx_fb.c: In function 'vmw_fb_init':
drivers/gpu/drm/vmwgfx/vmwgfx_fb.c:645:29: warning:
variable 'fb_offset' set but not used [-Wunused-but-set-variable]
drivers/gpu/drm/vmwgfx/v
Hello Sam,
On 7/1/19 19:04, Sam Ravnborg wrote:
> Hi Ahmad.
>
>> On 2/1/19 22:37, Sam Ravnborg wrote:
>>> The problem with the RED/BLUE lines swapped is something I
>>> have encountered while working with DRM support for Atmel at91sam9263 too.
>>>
>>> The solution selected is to extend the endpoi
From: chunhui dai
Recalculate the rate of this clock, by querying hardware.
Signed-off-by: chunhui dai
Signed-off-by: wangyan wang
---
drivers/gpu/drm/mediatek/mtk_hdmi_phy.c| 7 ++
drivers/gpu/drm/mediatek/mtk_hdmi_phy.h| 3 +--
drivers/gpu/drm/mediatek/mtk_mt2701_hdmi_
1 - 100 of 224 matches
Mail list logo
