https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #112 from Shmerl ---
(In reply to Jeremy Attali from comment #111)
> I confirm I'm also still getting some hangs from time to time. Mostly I
> think after a resume from Suspend.
I wonder if on resume something is getting messed up,
Correct the "_LENTH" mispelling in the AMDGPU_MAX_TIMEOUT_PARAM_LENGTH
constant.
Signed-off-by: Wambui Karuga
---
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
b/drivers/gpu/drm/amd/amd
From: Chenwandun
drivers/gpu/drm/amd/display/dc/dce/dce_aux.c: In function
dce_aux_configure_timeout:
drivers/gpu/drm/amd/display/dc/dce/dce_aux.c: warning: variable timeout set but
not used [-Wunused-but-set-variable]
Signed-off-by: Chenwandun
---
drivers/gpu/drm/amd/display/dc/dce/dce_aux.
Make the `amdgpu_lockup_timeout` and `amdgpu_exp_hw_support` variables
static to remove the following sparse warnings:
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c:103:19: warning: symbol
'amdgpu_lockup_timeout' was not declared. Should it be static?
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c:117:18: warn
Remove unnecessary assignment for return value and have the
function return the required value directly.
Issue found by coccinelle:
@@
local idexpression ret;
expression e;
@@
-ret =
+return
e;
-return ret;
Signed-off-by: Wambui Karuga
---
drivers/gpu/drm/radeon/cik.c | 8 ++--
1 file
On Thu, Oct 17, 2019 at 04:47:20PM +, Koenig, Christian wrote:
> > get_user_pages/hmm_range_fault() and invalidate_range_start() both are
> > called while holding mm->map_sem, so they are always serialized.
>
> Not even remotely.
>
> For calling get_user_pages()/hmm_range_fault() you only ne
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #116 from Rodney A Morris ---
Created attachment 145777
--> https://bugs.freedesktop.org/attachment.cgi?id=145777&action=edit
Full journal from start to crash
Full journalctl from start to crash.
--
You are receiving this mail b
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #115 from Rodney A Morris ---
Created attachment 145776
--> https://bugs.freedesktop.org/attachment.cgi?id=145776&action=edit
Full dmesg from crash
Full dmesg from crash
--
You are receiving this mail because:
You are the assign
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #114 from Rodney A Morris ---
To rule out possible hardware issues, I purchased another Vega 64 card. This
time a factory overclocked card. Since installing the card, I have experienced
three lock ups. Two playing Stellaris and on
On 18/10/2019 17:41:20+0200, Arnd Bergmann wrote:
> The mach/hardware.h is included in lots of places, and it provides
> three different things on pxa:
>
> - the cpu_is_pxa* macros
> - an indirect inclusion of mach/addr-map.h
> - the __REG() and io_pv2() helper macros
>
> Split it up into separat
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #111 from Jeremy Attali ---
I confirm I'm also still getting some hangs from time to time. Mostly I think
after a resume from Suspend.
pacman -Q linux linux-firmware {,lib32-}{mesa-git,vulkan-radeon-git,libdrm}
linux 5.3.6.arch1-1
On Sat, 19 Oct 2019, Wambui Karuga wrote:
> From: Wambui Karuga
>
> Remove unnecessary variable `ret` in drm_dp_atomic_find_vcpi_slots()
> only used to hold the function return value and have the function
> return the value directly.
This patch applies for me, but with a huge offset. What tr
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #166 from Peter Hercek ---
I tried, 5.3.6-arch1-1 on archlinux with 3 DP monitors. It should contain the
patch based on the comment from line...@xcpp.org.
I got the crash after 4 days of use. It looks the same as before:
ring sdma0
This adds initial support for the NWL MIPI DSI Host controller found on i.MX8
SoCs.
It adds support for the i.MX8MQ but the same IP core can also be found on e.g.
i.MX8QXP. I added the necessary hooks to support other imx8 variants but since
I only have imx8mq boards to test I omitted the platform
This adds initial support for the NWL MIPI DSI Host controller found on
i.MX8 SoCs.
It adds support for the i.MX8MQ but the same IP can be found on
e.g. the i.MX8QXP.
It has been tested on the Librem 5 devkit using mxsfb.
Signed-off-by: Guido Günther
Co-developed-by: Robert Chiras
Signed-off-b
The Northwest Logic MIPI DSI IP core can be found in NXPs i.MX8 SoCs.
Signed-off-by: Guido Günther
Tested-by: Robert Chiras
Reviewed-by: Rob Herring
---
.../bindings/display/bridge/nwl-dsi.yaml | 203 ++
1 file changed, 203 insertions(+)
create mode 100644
Documentation/
Hi Andrzej,
thanks for your comments! See inline for follow ups.
On Mon, Sep 23, 2019 at 12:01:51PM +0200, Andrzej Hajda wrote:
> On 22.09.2019 18:47, Guido Günther wrote:
> > This adds initial support for the NWL MIPI DSI Host controller found on
> > i.MX8 SoCs.
> >
> > It adds support for the i.
On 10/18/19 2:57 PM, Ayan Halder wrote:
> On Fri, Oct 18, 2019 at 11:49:22AM -0700, John Stultz wrote:
>> On Fri, Oct 18, 2019 at 11:41 AM Ayan Halder wrote:
>>> On Fri, Oct 18, 2019 at 09:55:17AM +, Brian Starkey wrote:
On Thu, Oct 17, 2019 at 01:57:45PM -0700, John Stultz wrote:
> O
https://bugs.freedesktop.org/show_bug.cgi?id=111789
--- Comment #5 from usual user ---
Regression fix [1] just landed. The "@2G" workaround is no longer required.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f3057ad767542be7bbac44e548cb44017178a163
--
You ar
https://bugs.freedesktop.org/show_bug.cgi?id=111913
--- Comment #12 from Stefan Rehm ---
If I change
dcn2_0_soc.dram_clock_change_latency_us
in "rivers/gpu/drm/amd/display/dc/dcn20/dcn20_resource.c" from 404.0 to 10.0
(the value used in kernel 5.3) the messages disappear and the system behaves
On Sat, Oct 19, 2019 at 12:58 PM Bartosz Golaszewski wrote:
>
> From: Bartosz Golaszewski
>
> Remove a double newline from the driver.
>
Reviewed-by: Andy Shevchenko
> Signed-off-by: Bartosz Golaszewski
> ---
> drivers/video/backlight/gpio_backlight.c | 1 -
> 1 file changed, 1 deletion(-)
>
https://bugzilla.kernel.org/show_bug.cgi?id=204805
--- Comment #4 from ilkka.pr...@gmail.com ---
With 5.3.7 system is not locking up although KASAN reports error in amdgpu:
[ 31.792441]
==
[ 31.792718] BUG: KASAN: global-out-of-bo
On Fri, Oct 18, 2019 at 06:19:15PM -0700, Joe Perches wrote:
> On Fri, 2019-10-18 at 23:30 +0100, Sudip Mukherjee wrote:
> > On Fri, Oct 18, 2019 at 07:27:28PM +0200, Ladislav Michl wrote:
> > > On Fri, Oct 18, 2019 at 05:30:04PM +0100, Sudip Mukherjee wrote:
> > > > The build of xtensa allmodconfi
From: Bartosz Golaszewski
Add a GPIO lookup entry and a device property for GPIO backlight to the
board file. Tie them to the platform device which is now registered using
platform_device_register_full() because of the properties. These changes
are inactive now but will be used once the gpio back
From: Bartosz Golaszewski
The GPIO backlight driver currently requests the line 'as is', without
acively setting its direction. This can lead to problems: if the line
is in input mode by default, we won't be able to drive it later when
updating the status and also reading its initial value doesn'
From: Bartosz Golaszewski
While working on my other series related to gpio-backlight[1] I noticed
that we could simplify the driver if we made the only user of platform
data use GPIO lookups and device properties. This series tries to do
that.
First two patches contain minor fixes. Third patch m
From: Bartosz Golaszewski
Remove a double newline from the driver.
Signed-off-by: Bartosz Golaszewski
---
drivers/video/backlight/gpio_backlight.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/video/backlight/gpio_backlight.c
b/drivers/video/backlight/gpio_backlight.c
index 7e199
From: Bartosz Golaszewski
We no longer use any symbols from of_gpio.h. Remove this include.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Linus Walleij
Reviewed-by: Daniel Thompson
Reviewed-by: Andy Shevchenko
---
drivers/video/backlight/gpio_backlight.c | 1 -
1 file changed, 1 deletion(
From: Bartosz Golaszewski
The probe function in the gpio-backlight driver is quite short. If we
pull gpio_backlight_initial_power_state() into probe we can drop two
more fields from struct gpio_backlight and shrink the driver code.
Signed-off-by: Bartosz Golaszewski
Acked-by: Daniel Thompson
-
From: Bartosz Golaszewski
Remove the platform data fields that nobody uses.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Andy Shevchenko
Reviewed-by: Linus Walleij
Reviewed-by: Daniel Thompson
---
include/linux/platform_data/gpio_backlight.h | 3 ---
1 file changed, 3 deletions(-)
diff
From: Bartosz Golaszewski
Platform data fields other than fbdev are no longer used by the
backlight driver. Remove them.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Andy Shevchenko
Reviewed-by: Linus Walleij
---
arch/sh/boards/mach-ecovec24/setup.c | 3 ---
1 file changed, 3 deletions(-)
From: Bartosz Golaszewski
Now that the last user of platform data (sh ecovec24) defines a proper
GPIO lookup and sets the 'default-on' device property, we can drop the
platform_data-specific GPIO handling and unify a big chunk of code.
The only field used from the platform data is now the fbdev
From: Bartosz Golaszewski
Instead of dereferencing pdev each time, use a helper variable for
the associated device pointer.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Linus Walleij
Reviewed-by: Daniel Thompson
Reviewed-by: Andy Shevchenko
---
drivers/video/backlight/gpio_backlight.c |
From: Wambui Karuga
Remove unnecessary variable `ret` in drm_dp_atomic_find_vcpi_slots()
only used to hold the function return value and have the function
return the value directly.
Issue found by coccinelle:
@@
local idexpression ret;
expression e;
@@
-ret =
+return
e;
-return ret;
Signed
We get these warnings when build kernel W=1:
drivers/gpu/drm/panfrost/panfrost_perfcnt.c:35:6: warning: no previous
prototype for ‘panfrost_perfcnt_clean_cache_done’ [-Wmissing-prototypes]
drivers/gpu/drm/panfrost/panfrost_perfcnt.c:40:6: warning: no previous
prototype for ‘panfrost_perfcnt_sampl
35 matches
Mail list logo
