Hello,
lately I've been trying to make the Himax HX8837 chip that drives the OLPC
LCD display work with Armada DRM driver. I've been advised to create a
bridge driver and not an encoder driver since the silicon is separate from
the LCDC.
The Armada DRM driver (and, I think, the i.MX one) creates
On Thu, Jan 3, 2019 at 9:55 AM Maarten Lankhorst
wrote:
>
> Op 30-12-2018 om 07:21 schreef syzbot:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:903b77c63167 Merge tag 'linux-kselftest-4.21-rc1' of git:/..
> > git tree: upstream
> > console output: https://s
Hi,
On Wed, 2018-12-19 at 10:13 +0100, Daniel Vetter wrote:
> On Wed, Dec 19, 2018 at 9:40 AM Lubomir Rintel wrote:
> > Hi,
> >
> > here are patches that make the Armada DRM work on an OLPC XO-1.75.
> > They build on patches previously submitted by Russel King (included here for
> > completeness
Add support the Evervision VGG804821 800x480 5.0" WVGA TFT panel.
Signed-off-by: Marco Felsch
---
drivers/gpu/drm/panel/panel-simple.c | 30
1 file changed, 30 insertions(+)
diff --git a/drivers/gpu/drm/panel/panel-simple.c
b/drivers/gpu/drm/panel/panel-simple.c
in
On 1/3/19 1:17 PM, Kuehling, Felix wrote:
On 2019-01-03 12:34 p.m., Gustavo A. R. Silva wrote:
Fix boolean expressions by using logical AND operator '&&'
instead of bitwise operator '&'.
This issue was detected with the help of Coccinelle.
Fixes: c8c5e569c5b0 ("drm/amdgpu: Consolidate visibl
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
irq status register are triggered. From the kernel's perspective this is
a chained i
This small series adds the support for the Evervision VGG804821 panels.
The patches are rebased ontop of the current drm_misc/drm-misc-next.
Marco Felsch (3):
dt-bindings: add vendor prefix for Evervision Electronics
dt-bindings: drm/panel: simple: add Evervision VGG804821
drm/panel: simple:
Fix boolean expressions by using logical AND operator '&&'
instead of bitwise operator '&'.
This issue was detected with the help of Coccinelle.
Fixes: 9a4b7d4c769e ("drm/amdgpu: Add vm context module param")
Cc: sta...@vger.kernel.org
Reviewed-by: Felix Kuehling
Signed-off-by: Gustavo A. R. Sil
Joonas Lahtinen wrote:
> Quoting Eric Wong (2018-12-27 13:49:48)
> > I just got a used Thinkpad X201 (Core i5 M 520, Intel QM57
> > chipset) and hit some kernel panics while trying to view
> > image/animation-intensive stuff in Firefox (X11) unless I use
> > "iommu_intel=igfx_off".
> >
> > With D
Add support for the Evervision VG804821 800x480 5.0" LCD TFT parallel
panel to DRM simple panel driver.
Signed-off-by: Marco Felsch
---
.../bindings/display/panel/evervision,vgg804821.txt | 12
1 file changed, 12 insertions(+)
create mode 100644
Documentation/devicetree/bindings/
Lenovo Ideapad D330 Pentium CPU version has 1920x1200 LCD. Console
ouput gets rotated at boot as Miix 310.
Signed-off-by: David Santamaría Rogado
---
drivers/gpu/drm/drm_panel_orientation_quirks.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/gpu/drm/drm_panel_orient
>-Original Message-
>From: Laura Abbott [mailto:labb...@redhat.com]
>Sent: Thursday, January 03, 2019 6:31 AM
>To: Zengtao (B) ; sumit.sem...@linaro.org
>Cc: Greg Kroah-Hartman ; Arve Hjønnevåg
>; Todd Kjos ; Martijn Coenen
>; Joel Fernandes ;
>de...@driverdev.osuosl.org; dri-devel@lists.fr
It‘s an end user. That means bisecting isn‘t possible.
— Christian
Sent from my iPhone
> On 3. Jan 2019, at 12:03, Michel Dänzer wrote:
>
>> On 2019-01-01 4:03 p.m., Christian Zigotzky wrote:
>> Hello,
>>
>> An end user reportet that his ATI FirePro 2260 doesn't work anymore with
>> the lates
On Thu, 2019-01-03 at 13:15 +, Russell King - ARM Linux wrote:
> On Tue, Dec 18, 2018 at 04:37:38PM +0100, Lubomir Rintel wrote:
> > This makes it possible to choose a different pixel format for the
> > endpoint. Modelled after what other LCD controllers use, including
> > marvell,pxa2xx-lcdc a
Fix boolean expressions by using logical AND operator '&&'
instead of bitwise operator '&'.
This issue was detected with the help of Coccinelle.
Fixes: c8c5e569c5b0 ("drm/amdgpu: Consolidate visible vs. real vram check v2.")
Cc: sta...@vger.kernel.org
Signed-off-by: Gustavo A. R. Silva
---
driv
On 1/2/19 10:05 PM, Stefan Agner wrote:
> On a quick glance patch 1 looks good.
>
> However, patch 2/3 are probably unnecessary when using of graph/panel
> support. E.g. panel-simple.c supports bus formats.
>
> Is the display you are using regular RGB and only the board/connectors
> happen to sw
Fix boolean expression by using logical AND operator '&&'
instead of bitwise operator '&'.
This issue was detected with the help of Coccinelle.
Fixes: 6d04ee9dc101 ("drm/amd/display: Restructuring and cleaning up DML")
Cc: sta...@vger.kernel.org
Signed-off-by: Gustavo A. R. Silva
---
drivers/gp
On 1/3/19 3:11 PM, Wentland, Harry wrote:
On 2019-01-03 2:48 p.m., Gustavo A. R. Silva wrote:
Fix boolean expression by using logical AND operator '&&'
instead of bitwise operator '&'.
This issue was detected with the help of Coccinelle.
Fixes: 6d04ee9dc101 ("drm/amd/display: Restructuring a
Evervision Electronics is a panel manufacturer from Taipei.
http://www.evervisionlcd.com/index.php?lang=en
Signed-off-by: Marco Felsch
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.t
Quoting Eric Wong (2019-01-04 03:06:26)
> Joonas Lahtinen wrote:
> > Quoting Eric Wong (2018-12-27 13:49:48)
> > > I just got a used Thinkpad X201 (Core i5 M 520, Intel QM57
> > > chipset) and hit some kernel panics while trying to view
> > > image/animation-intensive stuff in Firefox (X11) unless
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_modifiers element was not set (some drivers tend
to set them after registering planes),
https://bugzilla.kernel.org/show_bug.cgi?id=199139
--- Comment #22 from mista...@gmail.com ---
I got rid of the issue by clean installation of Xubuntu 18.04.1 with 4.15. Same
kernel on old installation (xubuntu being upgraded over the years from 15.04 to
18.04.1) that I mentioned on 2018-09-14 sti
https://bugs.freedesktop.org/show_bug.cgi?id=109182
--- Comment #6 from fin4...@hotmail.com ---
Comment on attachment 142963
--> https://bugs.freedesktop.org/attachment.cgi?id=142963
dmesg
No rendering problems with my system. If you are compiling Mesa by your self,
it is waste of time and good
https://bugzilla.kernel.org/show_bug.cgi?id=201497
--- Comment #4 from Daniel Andersson (engyw...@gmail.com) ---
Created attachment 280261
--> https://bugzilla.kernel.org/attachment.cgi?id=280261&action=edit
4.20 didn't fix this
Still an issue on 4.20
--
You are receiving this mail because:
Y
https://bugs.freedesktop.org/show_bug.cgi?id=109224
Bug ID: 109224
Summary: OpenCL in darktable with AMD Turks doesn't works
Product: Mesa
Version: 18.3
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=108992
--- Comment #26 from chris ---
Hi,
many thanks for that bisect.
I googled the commit and found the following in addition which seems to be the
same issue ?
https://bugzilla.kernel.org/show_bug.cgi?id=201727
Hope that helps.
Many thanks !
Chr
Hi Linus,
Please pull fbdev changes for v4.21. This time the pull request is
really small. The most notable changes are fixing fbcon to not cause
crash on unregister_framebuffer() operation when there is more than
one framebuffer, adding config option to center the bootup logo and
making FB_BACKL
On Wed, Dec 14, 2016 at 06:20:39PM +0100, Alban Bedel wrote:
> The audio setting implementation was limited to a few specific pixel
> clocks. This prevented HDMI audio from working on several test devices
> as they need a pixel clock that is not supported by this implementation.
>
> Fix this by im
https://bugs.freedesktop.org/show_bug.cgi?id=109224
Jan Vesely changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=108992
Jan Vesely changed:
What|Removed |Added
See Also||https://bugzilla.kernel.org
https://bugs.freedesktop.org/show_bug.cgi?id=109049
Martin Peres changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #7 from Martin Peres
https://bugs.freedesktop.org/show_bug.cgi?id=109224
--- Comment #2 from Andy Costanza ---
do you need extra info of my laptop to solve this issue? lspci, clinfo,...?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-deve
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 9a4b7d4c769e drm/amdgpu: Add vm context module param.
The bot has tested the following trees: v4.20.0, v4.19.13, v4.14.91,
v4.20.0: Build OK!
v4.19.13: Build OK!
v4.14.91: Failed
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #2 from David Francis ---
Could you give me a list of all files in /lib/firmware/amdgpu/?
And if it contains a file called raven_dmcu.bin, please attach that file.
--
You are receiving this mail because:
You are the assignee for th
https://bugs.freedesktop.org/show_bug.cgi?id=108763
Martin Peres changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #4 from Martin Peres
https://bugs.freedesktop.org/show_bug.cgi?id=108591
Martin Peres changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #11 from Martin Peres
https://bugs.freedesktop.org/show_bug.cgi?id=109224
--- Comment #3 from Jan Vesely ---
(In reply to Andy Costanza from comment #2)
> do you need extra info of my laptop to solve this issue? lspci, clinfo,...?
no,
it's just a ton of work and there's too little time/too few people working on
clove
Register cpufreq notifier after we have initialized the crtc and
unregister it before we remove the ctrc. Receiving a cpufreq notify
without crtc causes a crash.
Reported-by: Peter Ujfalusi
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/tilcdc/tilcdc_drv.c | 34 ++---
1 f
tree: git://people.freedesktop.org/~agd5f/linux.git amd-18.50
head: 6b02d4906a8c5b3e4a268516057e5b77bbc5f559
commit: a26f88704ef76f0213692b3b04f210de6e9e8676 [1284/1418] drm/scheduler: fix
build error due to change in scheduler struct
config: riscv-allyesconfig (attached as .config)
compiler:
Hi Marco.
On Thu, Jan 03, 2019 at 07:26:57PM +0100, Marco Felsch wrote:
> Add support for the Evervision VG804821 800x480 5.0" LCD TFT parallel
> panel to DRM simple panel driver.
>
> Signed-off-by: Marco Felsch
> ---
> .../bindings/display/panel/evervision,vgg804821.txt | 12
> 1
Hi Marco.
In $subject pannel => panel
Other than that, bonus points for specifying
all of .flags, .bus_format and .bus_flags
Sam
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Hey Gustavo,
On Thu, 3 Jan 2019 at 17:25, Gustavo A. R. Silva wrote:
>
> Fix boolean expressions by using logical AND operator '&&'
> instead of bitwise operator '&'.
>
> This issue was detected with the help of Coccinelle.
>
> Fixes: 9a4b7d4c769e ("drm/amdgpu: Add vm context module param")
> Cc:
On Thu, Jan 3, 2019 at 3:21 PM Gustavo A. R. Silva
wrote:
>
> Fix boolean expressions by using logical AND operator '&&'
> instead of bitwise operator '&'.
>
> This issue was detected with the help of Coccinelle.
>
> Fixes: 9a4b7d4c769e ("drm/amdgpu: Add vm context module param")
> Cc: sta...@vger
https://bugs.freedesktop.org/show_bug.cgi?id=105910
--- Comment #10 from Michel Dänzer ---
Things are increasingly pointing to this being an i3 bug. It creates a cairo
surface with cairo_xcb_surface_create and copies from that to its parent
window. But according to /usr/include/cairo/cairo.h, cai
I added xcb capture to my ffmpeg build: I made a video of the glitches
available for download there:
http://dl.free.fr/r1ENiiJ3C
(it's a french hosting service for big files, let me know if you are unable to
download it)
___
dri-devel mailing list
dri-d
https://bugs.freedesktop.org/show_bug.cgi?id=109182
--- Comment #7 from Sylvain BERTRAND ---
I added xcb capture to my ffmpeg build: I made a video of the glitches
available for download there:
http://dl.free.fr/r1ENiiJ3C
(it's a french hosting service for big files, let me know if you are unable
https://bugs.freedesktop.org/show_bug.cgi?id=109182
--- Comment #8 from Michel Dänzer ---
Please attach the file here directly, should work AFAICT.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri
Hi Linus,
Happy New Year, just decloaking from leave to get this stuff in before rc1.
Some stuff from the last week:
core:
two regression fixes for damage blob and atomic
i915 gvt:
Some missed GVT fixes from the original pull
amdgpu:
new PCI IDs
SR-IOV fixes
DC fixes
Vega20 fixes
Dave.
drm-ne
Quoting Rajendra Nayak (2019-01-03 00:45:53)
>
> On 12/29/2018 6:59 AM, Stephen Boyd wrote:
> >> So I am guessing the conclusion is to use a fallback "operating-points-v2"
> >> compatible*only* when we do have opp-hz along with qcom,level (as in the
> >> case with gpu) and not have a fallback com
https://bugs.freedesktop.org/show_bug.cgi?id=109182
--- Comment #9 from Sylvain BERTRAND ---
Created attachment 142976
--> https://bugs.freedesktop.org/attachment.cgi?id=142976&action=edit
capture.mkv
--
You are receiving this mail because:
You are the assignee for the bug.___
Fix spelling mistake: "lenght" -> "length"
Signed-off-by: Matteo Croce
---
drivers/gpu/drm/amd/include/atombios.h | 2 +-
drivers/gpu/drm/omapdrm/dss/hdmi4_core.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/amd/include/atombios.h
b/drivers/gpu/drm/am
Fix spelling mistake: "lenght" -> "length"
Signed-off-by: Matteo Croce
---
drivers/video/fbdev/omap2/omapfb/dss/hdmi4_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/video/fbdev/omap2/omapfb/dss/hdmi4_core.c
b/drivers/video/fbdev/omap2/omapfb/dss/hdmi4_core.c
On Fri, Jan 4, 2019 at 10:41 PM Matteo Croce wrote:
>
> Fix spelling mistake: "lenght" -> "length"
>
> Signed-off-by: Matteo Croce
> ---
> drivers/gpu/drm/amd/include/atombios.h | 2 +-
> drivers/gpu/drm/omapdrm/dss/hdmi4_core.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
Hi,
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #3 from grak...@gmail.com ---
Created attachment 142978
--> https://bugs.freedesktop.org/attachment.cgi?id=142978&action=edit
List of files in /lib/firmware/amdgpu
--
You are receiving this mail because:
You are the assignee for t
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #4 from grak...@gmail.com ---
Created attachment 142979
--> https://bugs.freedesktop.org/attachment.cgi?id=142979&action=edit
Raven dmcu firmware
--
You are receiving this mail because:
You are the assignee for the bug.___
While this isn't a complete fix, this will improve the reliability of
drm_dp_get_last_connected_port_and_mstb() pretty significantly during
hotplug events, since there's a chance that the in-memory topology tree
may not be fully updated when drm_dp_get_last_connected_port_and_mstb()
is called and t
s/drm_dp_get_validated_port_ref/drm_dp_mst_topology_get_port_validated/
s/drm_dp_put_port/drm_dp_mst_topology_put_port/
s/drm_dp_get_validated_mstb_ref/drm_dp_mst_topology_get_mstb_validated/
s/drm_dp_put_mst_branch_device/drm_dp_mst_topology_put_mstb/
This is a much more consistent naming scheme,
The current way of handling refcounting in the DP MST helpers is really
confusing and probably just plain wrong because it's been hacked up many
times over the years without anyone actually going over the code and
seeing if things could be simplified.
To the best of my understanding, the current s
This is the series I've been working on for a while now to get all of
the atomic DRM drivers in the tree to use the atomic MST helpers, and to
make the atomic MST helpers actually idempotent. Turns out it's a lot
more difficult to do that without also fixing how port and branch device
refcounting w
Up until now, freeing payloads on remote MST hubs that just had ports
removed has almost never worked because we've been relying on port
validation in order to stop us from accessing ports that have already
been freed from memory, but ports which need their payloads released due
to being removed wi
So that the ports stay around until we've destroyed the connectors, in
order to ensure that we don't pass an invalid pointer to any MST helpers
once we introduce the new MST VCPI helpers.
Changes since v1:
* Move drm_dp_mst_get_port_malloc() to where we assign
intel_connector->port - danvet
Sig
Trying to destroy the connector using mstc->connector.funcs->destroy()
if connector initialization fails is wrong: there is no possible
codepath in nv50_mstc_new where nv50_mstm_add_connector() would return
<0 and mstc would be non-NULL.
Signed-off-by: Lyude Paul
Cc: Daniel Vetter
Cc: David Airl
Now that we finally have a sane way to keep port allocations around, use
it to fix the potential unchecked ->port accesses that nouveau makes by
making sure we keep the mst port allocated for as long as it's
drm_connector is accessible.
Additionally, now that we've guaranteed that mstc->port is al
Going through the currently programmed payloads isn't safe without
holding mgr->payload_lock, so actually do that and warn if anyone tries
calling nv50_msto_payload() in the future without grabbing the right
locks.
Signed-off-by: Lyude Paul
Cc: Daniel Vetter
Cc: David Airlie
Cc: Jerry Zuo
Cc:
There is no need to look at the port's VCPI allocation before calling
drm_dp_mst_deallocate_vcpi(), as we already have msto->disabled to let
us avoid cleaning up an msto more then once. The DP MST core will never
call drm_dp_mst_deallocate_vcpi() on it's own, which is presumably what
these checks a
This has never actually worked, and isn't needed anyway: the driver's
always going to try to deallocate VCPI when it tears down the display
that the VCPI belongs to.
Signed-off-by: Lyude Paul
Cc: Daniel Vetter
Cc: David Airlie
Cc: Jerry Zuo
Cc: Harry Wentland
Cc: Juston Li
---
drivers/gpu/d
Just like i915 and nouveau, it's a good idea for us to hold a malloc
reference to the port here so that we never pass a freed pointer to any
of the DP MST helper functions.
Also, we stop unsetting aconnector->port in
dm_dp_destroy_mst_connector(). There's literally no point to that
assignment that
There has been a TODO waiting for quite a long time in
drm_dp_mst_topology.c:
/* We cannot rely on port->vcpi.num_slots to update
* topology_state->avail_slots as the port may not exist if the parent
* branch device was unplugged. This should be fixed by tracking
Currently, nouveau uses the yolo method of setting up MST displays: it
uses the old VCPI helpers (drm_dp_find_vcpi_slots()) for computing the
display configuration. These helpers don't take care to make sure they
take a reference to the mstb port that they're checking, and
additionally don't actual
Same as we did for i915, but for nouveau this time. Additionally, we
grab a malloc reference to the port that lasts for the entire lifetime
of nv50_mstc, which gives us the guarantee that mstc->port will always
point to valid memory for as long as the mstc stays around.
Signed-off-by: Lyude Paul
Changes since v6:
- Move EXPORT_SYMBOL() for drm_dp_mst_topology_state_funcs to this
commit
- Document __drm_dp_mst_state_iter_get() and note that it shouldn't be
called directly
Signed-off-by: Lyude Paul
Reviewed-by: Daniel Vetter
Cc: David Airlie
Cc: Jerry Zuo
Cc: Harry Wentland
Cc:
It occurred to me that we never actually check this! So let's start
doing that.
Signed-off-by: Lyude Paul
Reviewed-by: Daniel Vetter
Cc: David Airlie
Cc: Jerry Zuo
Cc: Harry Wentland
Cc: Juston Li
---
drivers/gpu/drm/drm_dp_mst_topology.c | 8 +++-
1 file changed, 7 insertions(+), 1 del
https://bugzilla.kernel.org/show_bug.cgi?id=201727
--- Comment #14 from tones...@hotmail.com ---
I'm experiencing this bug on a Lenovo E585. My boot logs also show only "256M
of VRAM memory ready" when running 4.19.12 or commit 284dec4317c8. 4.19.12
boots fine, but the commit in question causes
Hi Jason,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.20 next-20190103]
[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/Jaso
https://bugs.freedesktop.org/show_bug.cgi?id=109001
--- Comment #13 from Matt Garman ---
If I set amdgpu.dc=0 on my Ryzen 5 2400g, the system hard-locks as soon as X
starts (i.e. hard reset via physical power button required).
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=109182
--- Comment #10 from Sylvain BERTRAND ---
Created attachment 142981
--> https://bugs.freedesktop.org/attachment.cgi?id=142981&action=edit
capture.mkv
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=109182
Sylvain BERTRAND changed:
What|Removed |Added
Attachment #142981|video/x-mastroska |video/x-matroska
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=109182
Sylvain BERTRAND changed:
What|Removed |Added
Attachment #142976|0 |1
is obsolete|
78 matches
Mail list logo
