https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #45 from Mathieu Belanger ---
Just an update : Still no new "random" crash since patch applied.
The only crash I got since patch applied are some partial and recoverable crash
that occurred due to insufficient voltage to the
On Sun, Sep 15, 2019 at 2:18 PM Mark Brown wrote:
>
> Hi all,
Hi Mark,
> Today's linux-next merge of the drm tree got a conflict in:
>
> drivers/gpu/drm/lima/lima_gem.c
>
> between commit:
>
> 21670bd78a25001cf8e ("drm/lima: fix lima_gem_wait() return value")
>
> from the drm-misc-fixes
On Wed, 11 Sep 2019 at 07:53, Thierry Reding wrote:
>
> On Sat, Sep 07, 2019 at 09:58:46PM -0400, Ilia Mirkin wrote:
> > On Wed, Aug 21, 2019 at 7:55 AM Thierry Reding
> > wrote:
> > >
> > > On Wed, Aug 21, 2019 at 04:33:58PM +1000, Ben Skeggs wrote:
> > > > On Wed, 14 Aug 2019 at 20:14, Gerd
Hi Jitao,
On Thu, Sep 12, 2019 at 5:04 PM Jitao Shi wrote:
>
> Add driver to support panel innolux,p097pfg with bridge ssd2858.
> SSD2858 can spilt dsi 4 lanes to 8 lanes.
>
> Jitao Shi (3):
> drm/panel: panel-innolux: Allow 2 reset pins for panel
> dt-bindings: display: Add documentation
https://bugzilla.kernel.org/show_bug.cgi?id=202445
--- Comment #33 from Clément Guérin (li...@protonmail.com) ---
It looks like the luminance flickering situation is much improved when using
linux 5.3 with this "LFC behaviour" patch applied:
Add dcumentation for boe,tv101wum-n53, which is mipi dsi video panel
and resolution is 1200x1920.
Signed-off-by: Jitao Shi
---
.../display/panel/boe,tv101wum-n53.txt| 34 +++
1 file changed, 34 insertions(+)
create mode 100644
Auo,auo,b101uan08.3's connector is same as boe,tv101wum-nl6.
The most codes can be reuse.
So auo,b101uan08.3 and boe,tv101wum-nl6 use one driver file.
Add the different parts in driver data.
Signed-off-by: Jitao Shi
---
.../gpu/drm/panel/panel-boe-tv101wum-nl6.c| 78 +++
1
Add dcumentation for auo,b101uan08.3, which is mipi dsi video panel
and resolution is 1200x1920.
Signed-off-by: Jitao Shi
---
.../display/panel/auo,b101uan08.3.txt | 34 +++
1 file changed, 34 insertions(+)
create mode 100644
Auo,kd101n80-45na's connector is same as boe,tv101wum-nl6.
The most codes can be reuse.
So auo,kd101n80-45na and boe,tv101wum-nl6 use one driver file.
Add the different parts in driver data.
Signed-off-by: Jitao Shi
---
drivers/gpu/drm/panel/Kconfig | 6 +-
Add driver for BOE tv101wum-nl6 panel is a 10.1" 1200x1920 panel.
Signed-off-by: Jitao Shi
Reviewed-by: Sam Ravnborg
---
drivers/gpu/drm/panel/Kconfig | 9 +
drivers/gpu/drm/panel/Makefile| 1 +
.../gpu/drm/panel/panel-boe-tv101wum-nl6.c| 709
Add documentation for boe tv101wum-n16 panel.
Signed-off-by: Jitao Shi
Reviewed-by: Sam Ravnborg
---
.../display/panel/boe,tv101wum-nl6.txt| 34 +++
1 file changed, 34 insertions(+)
create mode 100644
Boe,tv101wum-n53's connector is same as boe,tv101wum-nl6.
The most codes can be reuse.
So boe,tv101wum-n53 and boe,tv101wum-nl6 use one driver file.
Add the different parts in driver data.
Signed-off-by: Jitao Shi
---
.../gpu/drm/panel/panel-boe-tv101wum-nl6.c| 31 +++
1
Add documentation for auo kd101n80-45na panel.
Signed-off-by: Jitao Shi
Reviewed-by: Sam Ravnborg
---
.../display/panel/auo,kd101n80-45na.txt | 34 +++
1 file changed, 34 insertions(+)
create mode 100644
Changes since v4:
- add auo,b101uan08.3 panel for this driver.
- add boe,tv101wum-n53 panel for this driver.
Changes since v3:
- remove check enable_gpio.
- fine tune the auo,kd101n80-45na panel's power on timing.
Changes since v2:
- correct the panel size
- remove blank line in Kconfig
-
> -Original Message-
> From: Liviu Dudau
> Sent: 2019年9月12日 22:47
> To: Wen He
> Cc: linux-de...@linux.nxdi.nxp.com; Brian Starkey ;
> David Airlie ; Daniel Vetter ; Rob Herring
> ; Mark Rutland ;
> dri-devel@lists.freedesktop.org; devicet...@vger.kernel.org;
>
https://bugzilla.kernel.org/show_bug.cgi?id=204611
--- Comment #3 from tones...@hotmail.com ---
I'm still working on trying to bisect the problem, but it's been challenging.
Following the advice at
https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues
I turned on
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #44 from Marko Popovic ---
Another Update:
Unfortunately even with WIP patch applied I got another random desktop freeze
in Gnome shell of SDMA type.
Turned back the nodma tweak in order to avoid having those until further fixes
Hi all,
Today's linux-next merge of the drm tree got a conflict in:
drivers/gpu/drm/amd/display/dc/dml/Makefile
between commit:
54b8ae66ae1a345 ("kbuild: change *FLAGS_.o to take the path
relative to $(obj)")
from the kbuild tree and commits:
0f0727d971f6fdf ("drm/amd/display: readd
Hi all,
Today's linux-next merge of the drm tree got a conflict in:
drivers/gpu/drm/amd/powerplay/inc/amdgpu_smu.h
between commit:
03dce35deb8575 ("drm/amd/powerplay: remove duplicate macro
smu_get_uclk_dpm_states in amdgpu_smu.h")
from the amdgpu tree and commit:
eee3258e8f8be8
Hi all,
Today's linux-next merge of the drm tree got a conflict in:
drivers/gpu/drm/lima/lima_gem.c
between commit:
21670bd78a25001cf8e ("drm/lima: fix lima_gem_wait() return value")
from the drm-misc-fixes tree and commit:
52791eeec1d9f4a7e7f ("dma-buf: rename reservation_object to
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #43 from Marko Popovic ---
(In reply to Marko Popovic from comment #42)
> Ok I came home from vacation and got my hands on the WIP patch.
>
> Rocket-League startup SDMA-type freeze is completely gone.
>
> I will continue testing
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #42 from Marko Popovic ---
Ok I came home from vacation and got my hands on the WIP patch.
Rocket-League startup SDMA-type freeze is completely gone.
I will continue testing the desktop usage without nodma enabled and will report
On Mon, 9 Sep 2019 at 14:15, Koenig, Christian wrote:
>
> I agree with Daniels analysis.
>
> It looks like the problem is simply that PM turns of a block before all
> work is done on that block.
>
> Have you opened a bug report yet? If not then that would certainly help
> cause it is really hard
https://bugs.freedesktop.org/show_bug.cgi?id=111689
Bug ID: 111689
Summary: gnome-shell stuck because of amdgpu driver 5.3 kernel
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
All error handling paths before and after this one go to the
'clk_disable' label in order to free some resources.
So the same here.
Fixes: ca5be902a87d ("drm/mcde: Fix uninitialized variable")
Signed-off-by: Christophe JAILLET
---
drivers/gpu/drm/mcde/mcde_drv.c | 3 ++-
1 file changed, 2
The ulterior motive to switching the booleans over to bitops is to
allow use of the allocated flag as a bitlock.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/drm_mm.c | 36 +++
.../gpu/drm/i915/gem/i915_gem_execbuffer.c| 6 ++--
Make dma_fence_enable_sw_signaling() behave like its
dma_fence_add_callback() and dma_fence_default_wait() counterparts and
perform the test to enable signaling under the fence->lock, along with
the action to do so. This ensure that should an implementation be trying
to flush the cb_list (by
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #41 from Shmerl ---
Just FYI, I just just used latest firmware from here (2019-09-13):
https://people.freedesktop.org/~agd5f/radeon_ucode/navi10/
It didn't make a difference, ksysguard is still causing those powerplay errors.
--
Hi,
On Sun, 15 Sep 2019 18:52:04 +0200
Pavel Machek wrote:
> Hi!
>
> > > > > Is this needed?
> > > > >
> > > > > This is a remove path, not a power management path, and we have no
> > > > > idea
> > > > > what the original status of the pin was anyway?
> > > > >
> > > >
> > > > Looking
Hi!
> > > > Is this needed?
> > > >
> > > > This is a remove path, not a power management path, and we have no idea
> > > > what the original status of the pin was anyway?
> > > >
> > >
> > > Looking at Ishdn on page 5 of the datasheet, switching it off everytime
> > > possible seems not
On Sun, Sep 15, 2019 at 8:12 AM Dave Airlie wrote:
>
> I've been manually writing the subject lines, seems I need to fix my brain.
Note that my "find git pull requests" logic doesn't need it in the
subject line at all, so if you just change whatever script you use to
generate the email body to
Hi,
On 15-09-2019 17:00, Noralf Trønnes wrote:
Hi Hans,
Den 15.09.2019 16.32, skrev Hans de Goede:
Hi Noralf,
While doing a "make htmldocs" I just noticed the following errors:
Error: Cannot open file ./drivers/gpu/drm/tinydrm/core/tinydrm-helpers.c
Error: Cannot open file
On Sun, 15 Sep 2019 at 04:58, Linus Torvalds
wrote:
>
> On Thu, Sep 12, 2019 at 8:56 AM Dave Airlie wrote:
> >
> > Hey Linus,
> >
> > From the maintainer summit, just some last minute fixes for final,
> > details in the tag.
>
> So because my mailbox was more unruly than normal (because of same
Hi Hans,
Den 15.09.2019 16.32, skrev Hans de Goede:
> Hi Noralf,
>
> While doing a "make htmldocs" I just noticed the following errors:
>
> Error: Cannot open file ./drivers/gpu/drm/tinydrm/core/tinydrm-helpers.c
> Error: Cannot open file ./drivers/gpu/drm/tinydrm/core/tinydrm-helpers.c
>
Hi Noralf,
While doing a "make htmldocs" I just noticed the following errors:
Error: Cannot open file ./drivers/gpu/drm/tinydrm/core/tinydrm-helpers.c
Error: Cannot open file ./drivers/gpu/drm/tinydrm/core/tinydrm-helpers.c
Error: Cannot open file ./drivers/gpu/drm/tinydrm/core/tinydrm-pipe.c
https://bugs.freedesktop.org/show_bug.cgi?id=111077
--- Comment #41 from rol...@rptd.ch ---
EDIT: to sum up:
1) GIT master + patch => bug present
2) GIT master - patch + revert-commit => bug fixed
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=111077
--- Comment #40 from rol...@rptd.ch ---
I tested the patch now against the master GIT from mesa. It makes no
difference. RAM consumption still sky-rockets and application then crashes.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #40 from Shmerl ---
With that patch, I get stutters, but not hard freeze when using ksysguard with
reading amdgpu sensors. I see such errors in dmesg when that happens:
14889.400985] amdgpu: [powerplay] Failed to export SMU metrics
We do not really need to use API that fetches GPIO data from an
arbitrary device tree node, as we are dealing with device tree node
assigned to the device structure. We can easily switch to
devm_gpiod_get_optional() plus gpiod_set_consumer_name() and clean up
the code.
Note this is part of
https://bugzilla.kernel.org/show_bug.cgi?id=204849
Bug ID: 204849
Summary: amdgpu (RX560X) traceboot in dmesg boot output, system
instability
Product: Drivers
Version: 2.5
Kernel Version: 5.3-rc8
Hardware: All
40 matches
Mail list logo
