https://bugzilla.kernel.org/show_bug.cgi?id=202873
--- Comment #4 from Thomas (v10la...@myway.de) ---
Kernel 5.0.5 still flickers. Anyway, after watching this more closely I'm
pretty sure it's the same bug (the text cursor for entering username/password
causes flickering on SDDM, for example). Sti
https://bugs.freedesktop.org/show_bug.cgi?id=110345
Bug ID: 110345
Summary: Unrecoverable GPU crash with DiRT 4
Product: Mesa
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
On Mon, 1 Apr 2019 10:17:18 -0700, Douglas Anderson wrote:
> From: Sean Paul
>
> This patch adds a new subnode to simple-panel allowing us to override
> the typical timing expressed in the panel's display_timing.
>
> Changes in v2:
> - Split out the binding into a new patch (Rob)
> - display-
On Wed, 3 Apr 2019 10:16:25 +0200, =?UTF-8?q?Yannick=20Fertr=C3=A9?= wrote:
> This patch adds documentation of a new property phy-dsi-supply to the
> STM32 DSI controller.
>
> Signed-off-by: Yannick Fertré
> ---
> Documentation/devicetree/bindings/display/st,stm32-ltdc.txt | 3 +++
> 1 file cha
On Mon, 1 Apr 2019 13:13:08 +0300, Tomi Valkeinen wrote:
> Add DT property for defining the pin used for HPD.
>
> Signed-off-by: Tomi Valkeinen
> Cc: devicet...@vger.kernel.org
> Cc: Rob Herring
> ---
>
> * Dropped the interrupt properties
> * Renamed hpd-num to hpd-pin
> * Added toshiba prefix
On Wed, Apr 03, 2019 at 10:49:07AM +1030, Joel Stanley wrote:
> This describes the ASPEED BMC SoC's display controller.
>
> Signed-off-by: Joel Stanley
> Reviewed-by: Andrew Jeffery
> ---
> v3:
> Add Andrew's reviewed-by
>
> .../devicetree/bindings/gpu/aspeed-gfx.txt| 41 +
On Tue, Apr 02, 2019 at 10:29:14AM +0300, Jyri Sarha wrote:
> The sii902x chip family supports also HDMI audio. Add binding for
> describing the necessary i2s and mclk wiring for it.
>
> Signed-off-by: Jyri Sarha
> ---
> .../bindings/display/bridge/sii902x.txt | 37 +++
> 1
On Mon, 1 Apr 2019 12:13:35 +0200, =?UTF-8?q?Guido=20G=C3=BCnther?= wrote:
> Add support for the MIXEL DPHY IP as found on NXP's i.MX8MQ SoCs.
>
> Signed-off-by: Guido Günther
> Reviewed-by: Sam Ravnborg
> ---
> .../bindings/phy/mixel,mipi-dsi-phy.txt | 29 +++
> 1 file
On Mon, 1 Apr 2019 15:41:42 +0300, Peter Ujfalusi wrote:
> tfp410 can be connect to host processor in 24bit, single-edge (24 lines) or
> 12bit, dual-edge (12 lines).
>
> Add bus-width to the documentation so it can be used to select between the
> two connection scheme.
>
> Signed-off-by: Peter Uj
On Mon, Apr 01, 2019 at 10:56:40AM +0200, Maxime Ripard wrote:
> Hi,
>
> We've had for quite some time to hack around in our drivers to take into
> account the fact that our DMA accesses are not done through the parent
> node, but through another bus with a different mapping than the CPU for the
>
On Wed, Apr 3, 2019 at 2:53 PM Bartlomiej Zolnierkiewicz
wrote:
>
>
> On 04/02/2019 11:09 PM, Sudip Mukherjee wrote:
> > On Mon, Apr 1, 2019 at 6:41 PM Tom Li wrote:
> >>
> >> On Sun, Mar 31, 2019 at 08:08:01PM +0100, Sudip Mukherjee wrote:
> >>> Technically I donot have any problem with this, yo
https://bugzilla.kernel.org/show_bug.cgi?id=203111
Thomas (v10la...@myway.de) changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|
https://bugzilla.kernel.org/show_bug.cgi?id=203111
--- Comment #5 from Thomas (v10la...@myway.de) ---
Thanks a lot for the detailed answer. I'm still not sure if I understand
everything correctly (shouldn't the kernel driver validate the command stream
from userspace/mesa and stop bad things befor
https://bugs.freedesktop.org/show_bug.cgi?id=109692
--- Comment #20 from Andrey Grodzovsky ---
Created attachment 143883
--> https://bugs.freedesktop.org/attachment.cgi?id=143883&action=edit
0002-drm-sched-Adapt-drivers-to-new-job-destruction-logic.patch
Mikhail, attached 2 patches should help
https://bugs.freedesktop.org/show_bug.cgi?id=109692
--- Comment #19 from Andrey Grodzovsky ---
Created attachment 143882
--> https://bugs.freedesktop.org/attachment.cgi?id=143882&action=edit
0001-drm-scheduler-rework-job-destruction.patch
--
You are receiving this mail because:
You are the as
https://bugzilla.kernel.org/show_bug.cgi?id=203111
--- Comment #4 from Alex Deucher (alexdeuc...@gmail.com) ---
(In reply to Thomas from comment #3)
>
> Are you sure this could be a mesa bug? Just asking cause for me a hanging
> kernel sounds like a kernel bug.
Likely a mesa bug. Mesa submits g
On Thu, Apr 4, 2019 at 7:33 AM Thierry Reding wrote:
>
> On Thu, Apr 04, 2019 at 12:15:48PM +1000, Dave Airlie wrote:
> > On Thu, 4 Apr 2019 at 02:07, Thierry Reding
> > wrote:
> > >
> > > On Fri, Mar 22, 2019 at 02:15:17PM +0100, Thierry Reding wrote:
> > > > Hi Dave,
> > > >
> > > > The follow
https://bugzilla.kernel.org/show_bug.cgi?id=203111
Thomas (v10la...@myway.de) changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|
No functional change with this change, just fixing formatting and
spaces.
v2: Rebase.
Signed-off-by: Deepak Rawat
Reviewed-by: Thomas Hellstrom
---
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 687 +++-
1 file changed, 302 insertions(+), 385 deletions(-)
diff --git a/drivers/
Several command verifier function check if context node is present or
not and if not present print an error and return. Use a preprocessor
macro to print the message.
v2: Name-space distinction for preprocessor macro
Signed-off-by: Deepak Rawat
Reviewed-by: Thomas Hellstrom
---
drivers/gpu/drm
Whenever command verifier function returns with an error, print a debug
message using VMW_DEBUG_USER. This will make sure failing commands can
be easily tracked for debugging purpose.
Signed-off-by: Deepak Rawat
Reviewed-by: Thomas Hellstrom
---
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 7 +
Error messages or debugging message reported during user-space command
submission should not be printed to dmesg by default. So add a new
preprocessor define called VMW_DEBUG_USER which translates to
DRM_DEBUG_DRIVER.
v2: Use VMW_DEBUG_USER instead of using DRM_DEBUG_DRIVER directly.
Signed-off-b
Use preprocessor macro for repetitive device command struct format.
v2: Name-space distinction for preprocessor macro.
v3: Struct name as macro parameter and rebase.
Signed-off-by: Deepak Rawat
Reviewed-by: Thomas Hellstrom
---
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 405 ---
DRM_ERROR overwhelms dmesgi so use VMW_DEBUG_USER instead. Any malformed
command should not really go to device so WARN_ONCE to spot this.
Signed-off-by: Deepak Rawat
Reviewed-by: Thomas Hellstrom
---
drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c | 18 ++
1 file changed, 10 insertions(
Now that vmw_cmd_check prints debug message whenever a command verifier
fails, some of debug statements are unnecessary. Also rearranged some
debug print-out with this patch.
Signed-off-by: Deepak Rawat
Reviewed-by: Thomas Hellstrom
---
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 20 -
Whenever FIFO allocation fails an error message is printed to dmesg.
Since this is common operation a lot of similar messages are scattered
everywhere. Use preprocessor macro to remove this cluttering.
Signed-off-by: Deepak Rawat
Reviewed-by: Thomas Hellstrom
---
drivers/gpu/drm/vmwgfx/vmwgfx_b
From: YueHaibing
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c: In function 'vmw_cmdbuf_work_func':
drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c:514:7: warning:
variable 'restart' set but not used [-Wunused-but-set-variable]
It not used any more after commit d
From: Chengguang Xu
unlikely has already included in IS_ERR(), so just
remove redundant unlikely annotation.
Signed-off-by: Chengguang Xu
Reviewed-by: Deepak Rawat
Signed-off-by: Deepak Rawat
---
drivers/gpu/drm/vmwgfx/vmwgfx_context.c | 2 +-
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 4 ++--
From: Thomas Hellstrom
Currently we flag resources as dirty (GPU contents not yet read back to
the backing MOB) whenever they have been part of a command stream.
Obviously many resources can't be dirty and others can only be dirty when
written to by the GPU. That is when they are either bound to
https://bugs.freedesktop.org/show_bug.cgi?id=110339
--- Comment #1 from Pinky ---
kernel: Linux 5.1.0-rc2-1-next-git-g7cdd4dc58d28 #5 SMP Fri Apr 5 18:06:31 CEST
2019 x86_64 GNU/Linux
--
You are receiving this mail because:
You are the assignee for the bug.__
On Fri, 5 Apr 2019 09:33:55 -0700
Alyssa Rosenzweig wrote:
> > Since one of the primary use cases is to draw pretty graphs of the
> > system load [1], this "per-job" information isn't all that relevant (and
> > minimal performance overhead is important). And if you want to monitor
> > just one ap
https://bugs.freedesktop.org/show_bug.cgi?id=110339
Bug ID: 110339
Summary: Cursor hides and reappear in the middle of screen,
when moving mouse horizontally
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
https://bugs.freedesktop.org/show_bug.cgi?id=110214
--- Comment #75 from Diego Viola ---
(In reply to Diego Viola from comment #72)
> (In reply to Michel Dänzer from comment #51)
> > The working hypothesis is that it's a Mesa regression between 18.3 and 19.0,
> > so that makes sense?
>
> That w
On 4/3/19 10:16 AM, Yannick Fertré wrote:
> Add support of an optional regulator for the phy part of the DSI
> controller.
>
> Signed-off-by: Yannick Fertré
> ---
> drivers/gpu/drm/stm/dw_mipi_dsi-stm.c | 20
> 1 file changed, 20 insertions(+)
>
> diff --git a/drivers/g
On 4/3/19 10:16 AM, Yannick Fertré wrote:
> This patch adds documentation of a new property phy-dsi-supply to the
> STM32 DSI controller.
>
> Signed-off-by: Yannick Fertré
> ---
> Documentation/devicetree/bindings/display/st,stm32-ltdc.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff -
On 4/3/19 11:25 AM, Yannick Fertré wrote:
> Signed-off-by: Mickael Reulier
> Signed-off-by: Yannick Fertré
> ---
> drivers/gpu/drm/stm/ltdc.c | 21 -
> 1 file changed, 20 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/stm/ltdc.c b/drivers/gpu/drm/stm/ltdc.
On 4/3/19 11:24 AM, Yannick Fertré wrote:
> Display controller reset must be done as soon as possible after enable
> the clock to avoid partial refresh on screen.
>
> Signed-off-by: Yannick Fertré
> ---
> drivers/gpu/drm/stm/ltdc.c | 12 ++--
> 1 file changed, 6 insertions(+), 6 dele
Dear Yannick,
Thank you for your patch,
Acked-by: Philippe Cornu
Philippe :)
On 4/3/19 11:20 AM, Yannick Fertré wrote:
> If the number of layer is greater than LTDC_MAX_LAYER, we can have
> memory overflow when reading plane_fpsi[].
>
> Signed-off-by: Yannick Fertré
> ---
> drivers/gpu/drm/
On Mon, Apr 01, 2019 at 11:00:04PM +0530, Uma Shankar wrote:
> This series adds support for programmable gamma modes and
> exposes a property interface for the same. Also added,
> support for multi segment gamma mode introduced in ICL+
>
> It creates 2 property interfaces :
> 1. GAMMA_MODE_CAPS: T
On Wed, Apr 03, 2019 at 04:35:11PM -0300, Rodrigo Siqueira wrote:
> Hi,
>
> I’m working to add writeback support to vkms; you can see my current
> patch at the end of this email (some prints highlight the issue that I’m
> asking for help here). I’m using the Liviu Dudau and Brian Starkey IGT
> pat
https://bugs.freedesktop.org/show_bug.cgi?id=110214
--- Comment #74 from Diego Viola ---
(In reply to Diego Viola from comment #65)
> Just to make it a bit more clear:
>
> If I set that environment variable while I'm already on X:
>
> export MESA_EXTENSION_OVERRIDE="-GL_NV_texture_barrier"
>
>
Alyssa Rosenzweig writes:
>> @@ -55,6 +63,15 @@ struct drm_panfrost_submit {
>>
>> /** A combination of PANFROST_JD_REQ_* */
>> __u32 requirements;
>> +
>> +/** Pointer to a u32 array of perfmons that should be attached to the
>> job. */
>> +__u64 perfmon_handles;
>> +
>> +
https://bugs.freedesktop.org/show_bug.cgi?id=110214
--- Comment #73 from Diego Viola ---
Sorry for the confusing comments.
export MESA_EXTENSION_OVERRIDE="-GL_NV_texture_barrier" makes xterm always work
with Xpehyr git, no matter if I set that variable before or after startx.
--
You are receiv
https://bugs.freedesktop.org/show_bug.cgi?id=110214
--- Comment #72 from Diego Viola ---
(In reply to Michel Dänzer from comment #51)
> The working hypothesis is that it's a Mesa regression between 18.3 and 19.0,
> so that makes sense?
That was a mistake from my part, sorry.
Setting 'export ME
https://bugs.freedesktop.org/show_bug.cgi?id=110214
--- Comment #71 from Marek Olšák ---
(In reply to Michel Dänzer from comment #69)
> (In reply to Marek Olšák from comment #67)
> > Primitives aren't reordered with DPBB. Primitives can't also survive a
> > barrier with DPBB. DPBB has no effect o
https://bugs.freedesktop.org/show_bug.cgi?id=110214
--- Comment #70 from Diego Viola ---
(In reply to Michel Dänzer from comment #68)
> (In reply to Diego Viola from comment #65)
> > If I set that environment variable while I'm already on X:
>
> By "X" I assume you mean Xorg here?
Yes, Xorg.
-
On Wed, Apr 03, 2019 at 04:35:11PM -0300, Rodrigo Siqueira wrote:
> Hi,
Hi Rodrigo,
>
> I’m working to add writeback support to vkms; you can see my current
> patch at the end of this email (some prints highlight the issue that I’m
> asking for help here). I’m using the Liviu Dudau and Brian Sta
https://bugs.freedesktop.org/show_bug.cgi?id=110337
Michel Dänzer changed:
What|Removed |Added
Assignee|mesa-dev@lists.freedesktop. |dri-devel@lists.freedesktop
https://bugs.freedesktop.org/show_bug.cgi?id=110214
--- Comment #69 from Michel Dänzer ---
(In reply to Marek Olšák from comment #67)
> Primitives aren't reordered with DPBB. Primitives can't also survive a
> barrier with DPBB. DPBB has no effect on behavior, it just changes how PS
> wavefronts a
https://bugs.freedesktop.org/show_bug.cgi?id=110214
--- Comment #68 from Michel Dänzer ---
(In reply to Diego Viola from comment #65)
> If I set that environment variable while I'm already on X:
By "X" I assume you mean Xorg here?
> export MESA_EXTENSION_OVERRIDE="-GL_NV_texture_barrier"
>
> I
Den 05.04.2019 11.52, skrev Gerd Hoffmann:
> Time to kill some bad sample code people are copying from ;)
>
> This is a complete rewrite of the cirrus driver. The cirrus_mode_set()
> function is pretty much the only function which is carried over largely
> unmodified. Everything else is upside
> On Apr 4, 2019, at 6:39 PM, Dave Airlie wrote:
>
>> On Fri, 5 Apr 2019 at 08:43, Rodrigo Vivi wrote:
>>
>>> On Thu, Apr 04, 2019 at 03:25:38PM -0700, Rodrigo Vivi wrote:
>>> From: Rodrigo Vivi
>>
>> And it seems that I don't know how to spell my own name anymore! :)
>>
>> If you decide f
https://bugs.freedesktop.org/show_bug.cgi?id=109957
--- Comment #4 from Ricardo Ribalda ---
Created attachment 143880
--> https://bugs.freedesktop.org/attachment.cgi?id=143880&action=edit
Xorg.0.log
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=110214
--- Comment #67 from Marek Olšák ---
(In reply to Michel Dänzer from comment #63)
> (In reply to Diego Viola from comment #62)
> > export MESA_EXTENSION_OVERRIDE="-GL_NV_texture_barrier"
> >
> > This helps alleviate the problem (xterm does not
https://bugs.freedesktop.org/show_bug.cgi?id=109957
--- Comment #3 from Ricardo Ribalda ---
Created attachment 143879
--> https://bugs.freedesktop.org/attachment.cgi?id=143879&action=edit
Dmesg with drm.debug=0x3f
--
You are receiving this mail because:
You are the assignee for the bug.__
Den 05.04.2019 11.52, skrev Gerd Hoffmann:
> Simliar to drm_fb_xrgb_to_rgb565_dstclip() but converts to rgb888
Simliar -> Similar
> instead of rgb565.
>
> Signed-off-by: Gerd Hoffmann
> ---
Reviewed-by: Noralf Trønnes
___
dri-devel mailing li
Den 05.04.2019 11.52, skrev Gerd Hoffmann:
> It is a drm_fb_xrgb_to_rgb565() variant which checks the clip
> rectangle for the destination too.
>
> Common code between drm_fb_xrgb_to_rgb565() and
> drm_fb_xrgb_to_rgb565_dstclip() was factored out into the
> drm_fb_xrgb_to_rgb565_
Den 05.04.2019 11.52, skrev Gerd Hoffmann:
> It is a drm_fb_memcpy() variant which checks the clip rectangle for the
> destination too.
>
> Common code between drm_fb_memcpy() and drm_fb_memcpy_dstclip() was
> factored out into the drm_fb_memcpy_lines() helper function.
>
> Signed-off-by: Gerd
Den 05.04.2019 11.52, skrev Gerd Hoffmann:
> Also rename them from tinydrm_* to drm_fb_*
> Pure code motion, no functional change.
>
> Signed-off-by: Gerd Hoffmann
> ---
Thanks for doing this!
Reviewed-by: Noralf Trønnes
___
dri-devel mailing list
From: Janusz Krzysztofik
If there are active users of a device during driver unbind, the driver
now panics on non-empty list of free cachelines.
By design, cachelines which are not in use are kept on a list of free
cachelines associated with a timeline and removed from that list either
when in u
On Thu, Apr 4, 2019 at 11:17 PM Dave Airlie wrote:
>
> From: Dave Airlie
>
> This should help with some of the lifetime issues, and move us away
> from load/unload.
>
> Signed-off-by: Dave Airlie
Not too familiar with the usb interface stuff, but it seems to be
doing the right thing. Patches 1
As soon as a device is considered unplugged, not only prevent pending
users from accessing the device structures but also cancel all their
pending requests so all consumed resources can be cleaned up as soon
as possible.
Suggested-by: Chris Wilson
Signed-off-by: Janusz Krzysztofik
Reviewed-by: C
From: Janusz Krzysztofik
The driver does not currently support unbinding from a device which is
in use. Since open file descriptors may still be pointing into kernel
memory where the device structures used to be, entirely correct kernel
panics protect the driver from being unbound as we should n
Use drm_dev_unplug() to have device resources protected from user access
by DRM layer as soon as the driver is going to be unbound. Also, cancel
all pending work so associated resources can be quickly released.
Janusz Krzysztofik (2):
drm/i915: Use drm_dev_unplug()
drm/i915: Mark GEM wedged r
On 03/04/2019 05:57, Rob Herring wrote:
[...]
+static int panfrost_clk_init(struct panfrost_device *pfdev)
+{
+ int err;
+ unsigned long rate;
+
+ pfdev->clock = devm_clk_get(pfdev->dev, NULL);
+ if (IS_ERR(pfdev->clock)) {
The DT binding says clocks are optional, but this doesn
On Fri, Apr 05, 2019 at 02:14:35PM +0200, Neil Armstrong wrote:
> On 04/04/2019 16:31, Sean Paul wrote:
> > On Thu, Apr 04, 2019 at 10:28:29AM +0200, Neil Armstrong wrote:
> >> On 04/04/2019 08:56, Neil Armstrong wrote:
> >>> On 03/04/2019 22:56, Sean Paul wrote:
> From: Sean Paul
>
> >>
https://bugs.freedesktop.org/show_bug.cgi?id=110214
--- Comment #66 from Diego Viola ---
(In reply to Diego Viola from comment #65)
> Just to make it a bit more clear:
>
> If I set that environment variable while I'm already on X:
>
> export MESA_EXTENSION_OVERRIDE="-GL_NV_texture_barrier"
>
>
On Fri, 2019-04-05 at 13:20 +0100, Chris Wilson wrote:
> Quoting Janusz Krzysztofik (2019-04-05 13:13:31)
> > From: Janusz Krzysztofik
> >
> > If there are active users of a device during driver unbind, the
> > driver
> > now panics on non-empty list of free cachelines.
>
> This panic is there t
https://bugs.freedesktop.org/show_bug.cgi?id=110214
--- Comment #65 from Diego Viola ---
Just to make it a bit more clear:
If I set that environment variable while I'm already on X:
export MESA_EXTENSION_OVERRIDE="-GL_NV_texture_barrier"
It has no effect on Xephyr (from current git master), i.
On Fri, Apr 05, 2019 at 04:06:22PM +0530, Ramalingam C wrote:
> On 2019-04-05 at 11:23:00 +0200, Greg Kroah-Hartman wrote:
> > On Fri, Apr 05, 2019 at 02:12:54PM +0530, Ramalingam C wrote:
> > > Functions to create and remove the binary sysfs for class are added.
> > >
> > > These are getting intr
Quoting Janusz Krzysztofik (2019-04-05 13:13:31)
> From: Janusz Krzysztofik
>
> If there are active users of a device during driver unbind, the driver
> now panics on non-empty list of free cachelines.
This panic is there to say that fini is being called with active
contexts, that it is being ca
https://bugs.freedesktop.org/show_bug.cgi?id=110214
--- Comment #64 from Diego Viola ---
(In reply to Michel Dänzer from comment #63)
> (In reply to Diego Viola from comment #62)
> > export MESA_EXTENSION_OVERRIDE="-GL_NV_texture_barrier"
> >
> > This helps alleviate the problem (xterm does not
On 04/04/2019 16:31, Sean Paul wrote:
> On Thu, Apr 04, 2019 at 10:28:29AM +0200, Neil Armstrong wrote:
>> On 04/04/2019 08:56, Neil Armstrong wrote:
>>> On 03/04/2019 22:56, Sean Paul wrote:
From: Sean Paul
The file was removed in the below patch and is causing this error:
WAR
From: Janusz Krzysztofik
If there are active users of a device during driver unbind, the driver
now panics on non-empty list of free cachelines.
By design, chachelines which are not in use are kept on a list of free
chachelines associated with a timeline and rmoved from that list either
when in
On 2019-04-05 at 14:13:02 +0530, Ramalingam C wrote:
> Implements drm blob property content_protection_downstream_info
> property on HDCP capable connectors.
>
> Downstream topology info is gathered across authentication stages
> and stored in intel_hdcp. When HDCP authentication is complete,
> ne
As soon as a device is considered unplugged, not only prevent pending
users from accessing the device structures but also cancel all their
pending requests so all consumed resources can be cleaned up as soon
as possible.
Signed-off-by: Janusz Krzysztofik
Reviewed-by: Chris Wilson
---
drivers/gp
On Fri, 2019-04-05 at 09:24 +0100, Chris Wilson wrote:
> Quoting Janusz Krzysztofik (2019-04-05 09:11:54)
> > On Fri, 2019-04-05 at 08:41 +0100, Chris Wilson wrote:
> > > Quoting Janusz Krzysztofik (2019-04-05 08:26:57)
> > > > From: Janusz Krzysztofik
> > > >
> > > > The driver does not currentl
Den 05.04.2019 07.28, skrev Joel Stanley:
> When building this driver for architectures where CMA is not available.
>
> Fixes: 4f2a8f5898ec ("drm: Add ASPEED GFX driver")
> Reported-by: Stephen Rothwell
> Reported-by: kernel test robot
> Signed-off-by: Joel Stanley
> ---
> This fixes the buil
https://bugs.freedesktop.org/show_bug.cgi?id=110327
--- Comment #2 from Jens Ziller ---
Created attachment 143878
--> https://bugs.freedesktop.org/attachment.cgi?id=143878&action=edit
complete dmesg out
The added dmesg out is complete from boot. The warning during boot is new. I
never see it b
On 2019-04-05 at 11:23:00 +0200, Greg Kroah-Hartman wrote:
> On Fri, Apr 05, 2019 at 02:12:54PM +0530, Ramalingam C wrote:
> > Functions to create and remove the binary sysfs for class are added.
> >
> > These are getting introduced as DRM wants to create the common binary
> > sysfs across the drm
On 01/04/2019 20:11, Robin Murphy wrote:
On 01/04/2019 08:47, Rob Herring wrote:
ARM Mali midgard GPU is similar to standard 64-bit stage 1 page
tables, but
have a few differences. Add a new format type to represent the format.
The
input address size is 48-bits and the output address size is 4
Thanks, I'm OK with this patch.
Regards,
Qiang
On Fri, Apr 5, 2019 at 9:39 AM Dave Airlie wrote:
>
> On Fri, 5 Apr 2019 at 08:43, Rodrigo Vivi wrote:
> >
> > On Thu, Apr 04, 2019 at 03:25:38PM -0700, Rodrigo Vivi wrote:
> > > From: Rodrigo Vivi
> >
> > And it seems that I don't know how to spe
Time to kill some bad sample code people are copying from ;)
This is a complete rewrite of the cirrus driver. The cirrus_mode_set()
function is pretty much the only function which is carried over largely
unmodified. Everything else is upside down.
It is a single monster patch. But given that i
Also rename them from tinydrm_* to drm_fb_*
Pure code motion, no functional change.
Signed-off-by: Gerd Hoffmann
---
include/drm/drm_format_helper.h | 26 +++
include/drm/tinydrm/tinydrm-helpers.h | 10 -
drivers/gpu/drm/drm_format_helper.c | 180 +++
It is a drm_fb_xrgb_to_rgb565() variant which checks the clip
rectangle for the destination too.
Common code between drm_fb_xrgb_to_rgb565() and
drm_fb_xrgb_to_rgb565_dstclip() was factored out into the
drm_fb_xrgb_to_rgb565_lines() helper function.
Signed-off-by: Gerd Hoffmann
-
Simliar to drm_fb_xrgb_to_rgb565_dstclip() but converts to rgb888
instead of rgb565.
Signed-off-by: Gerd Hoffmann
---
include/drm/drm_format_helper.h | 3 ++
drivers/gpu/drm/drm_format_helper.c | 60 +
2 files changed, 63 insertions(+)
diff --git a/include/d
v3:
- move tinydrm converters to new drm_format_helpers.[ch]
- drop dstclip bool argument, use multiple functions instead (with
common code factored out into a helper).
- rewrite cirrus register access to use helpers instead of macros.
- misc minor fixes.
v2:
- It's a little series now. It
Hi Steve,
On 05/04/2019 10:42, Steven Price wrote:
First let me say congratulations to everyone working on Panfrost - it's
an impressive achievement!
Full disclosure: I used to work on the Mali kbase driver. And have been
playing around with running the Mali user-space blob with the Panfrost
ke
It is a drm_fb_memcpy() variant which checks the clip rectangle for the
destination too.
Common code between drm_fb_memcpy() and drm_fb_memcpy_dstclip() was
factored out into the drm_fb_memcpy_lines() helper function.
Signed-off-by: Gerd Hoffmann
---
include/drm/drm_format_helper.h | 2 ++
On Fri, Apr 05, 2019 at 02:12:54PM +0530, Ramalingam C wrote:
> Functions to create and remove the binary sysfs for class are added.
>
> These are getting introduced as DRM wants to create the common binary
> sysfs across the drm subsystem to handle hdcp srm.
Why do you need individual files? Th
https://bugs.freedesktop.org/show_bug.cgi?id=110214
Michel Dänzer changed:
What|Removed |Added
Version|19.0|git
--- Comment #63 from Michel Dänzer
On Sun, Mar 24, 2019 at 08:06:09PM +0100, Jernej Skrabec wrote:
> Currently resolutions with pixel clock higher than 340 MHz don't work
> with H6 HDMI controller. They just produce a blank screen.
>
> Limit maximum pixel clock rate to 340 MHz until scrambling is supported.
>
> Cc: sta...@vger.kerne
On Thu, Apr 04, 2019 at 10:52:02AM -0400, Sean Paul wrote:
> On Thu, Apr 04, 2019 at 04:43:42PM +0200, Neil Armstrong wrote:
> > This reverts commit a3f98bb22cbfaaf67717e156f79e2bfeb42d4cac.
> >
> > Patch "Documentation/gpu/meson: Remove link to meson_canvas.c" was
> > incorrectly applied on the wr
DRM API for generating uevent for a status changes of connector's
property.
This uevent will have following details related to the status change:
HOTPLUG=1, CONNECTOR= and PROPERTY=
v2:
Minor fixes at KDoc comments [Daniel]
Signed-off-by: Ramalingam C
---
drivers/gpu/drm/drm_sysfs.c | 31 +
This patch adds a optional CP downstream info blob property to the
connectors. This enables the Userspace to read the information of HDCP
authenticated downstream topology.
Driver will update this blob with all downstream information at the
end of the authentication.
In case userspace configures
Implements drm blob property content_protection_downstream_info
property on HDCP capable connectors.
Downstream topology info is gathered across authentication stages
and stored in intel_hdcp. When HDCP authentication is complete,
new blob with latest downstream topology information is updated to
Functions to create and remove the binary sysfs for class are added.
These are getting introduced as DRM wants to create the common binary
sysfs across the drm subsystem to handle hdcp srm.
Signed-off-by: Ramalingam C
cc: Greg Kroah-Hartman
cc: Daniel Vetter
---
drivers/base/class.c | 19 ++
Considering the significant size of hdcp related code in drm, all
hdcp related codes are moved into separate file called drm_hdcp.c.
Signed-off-by: Ramalingam C
Suggested-by: Daniel Vetter
---
drivers/gpu/drm/drm_connector.c | 78 ---
drivers/gpu/drm/drm_hdcp.c
This patch adds a DRM ENUM property to the selected connectors.
This property is used for mentioning the protected content's type
from userspace to kernel HDCP authentication.
Type of the stream is decided by the protected content providers.
Type 0 content can be rendered on any HDCP protected dis
A common binary sysfs called "hdcp_srm" is created at /sys/class/drm
with only write permission.
SRM table is parsed and stored at drm_hdcp.c, with functions exported
for the services for revocation check from drivers (which
implements the HDCP authentication)
This patch handles the HDCP1.4 and 2
1 - 100 of 122 matches
Mail list logo
