On 10/30/22 22:26, Jiapeng Chong wrote:
> No functional modification involved.
>
> drivers/gpu/drm/xlnx/zynqmp_dp.c:793: warning: expecting prototype for
> zynqmp_dp_link_train(). Prototype was for zynqmp_dp_train() instead.
>
Note that this warning is from scripts/kernel-doc.
Acked-by:
No functional modification involved.
drivers/gpu/drm/xlnx/zynqmp_dp.c:793: warning: expecting prototype for
zynqmp_dp_link_train(). Prototype was for zynqmp_dp_train() instead.
Link: https://bugzilla.openanolis.cn/show_bug.cgi?id=2666
Reported-by: Abaci Robot
Signed-off-by: Jiapeng Chong
---
FIELD_PREP and REG_FIELD_PREP have checks requiring a compile time constant
mask. When the mask comes in as the argument of a function these checks can
can fail depending on the compiler (gcc vs clang), optimization level,
etc. Use a simpler local version of FIELD_PREP which skips these
checks.
On 10/30/22 6:37 AM, Dawei Li wrote:
Racing conflict could be:
task A task B
list_for_each_entry
strcmp(h->name))
list_for_each_entry
strcmp(h->name)
kzallockzalloc
.. .
device_create
Hi Ivaylo,
it took a while until I found time to test newer kernels (mainline + Letux
additions)
on the OMAP5 Pyra but unfortunately I did not get screen display for v6.1. Even
worse,
the console was flooded by
[ 39.419846] WARNING: CPU: 0 PID: 3673 at drivers/bus/omap_l3_noc.c:139
On Wed, Oct 26, 2022 at 12:29 PM Christian König
wrote:
>
> Attached is the original test patch rebased on current amd-staging-drm-next.
>
> Can you test if this is enough to make sure that the games start without
> crashing by fetching the userptrs?
1. Over the past week the list of games
On Sat, Oct 29, 2022 at 03:48:50PM -0300, antoniospg wrote:
> Test plan:
>
> * Turn off:
> echo 1 > /sys/class/backlight/nv_backlight/bl_power
>
> * Turn on:
> echo 0 > /sys/class/backlight/nv_backlight/bl_power
>
> Signed-off-by: antoniospg
> ---
> drivers/gpu/drm/nouveau/nouveau_backlight.c
The pull request you sent on Sun, 30 Oct 2022 18:08:30 +0100:
> http://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git
> tags/fbdev-for-6.1-rc3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/b72018ab8236c3ae427068adeb94bdd3f20454ec
Thank you!
--
From: Randy Li
The pixel formats used in Synpatics video smart platform
are too many. It is impossible to store them in fourcc
namespace.
Signed-off-by: Randy Li
---
.../media/v4l/pixfmt-synaptics.rst| 80 +++
.../userspace-api/media/v4l/pixfmt.rst| 1 +
2
From: "Hsia-Jun(Randy) Li"
Memory Traffic Reduction(MTR) is a module in Synaptics
VideoSmart platform could process lossless compression image
and cache the tile memory line.
Those modifiers only record the parameters would effort pixel
layout or memory layout. Whether physical memory page
From: "Hsia-Jun(Randy) Li"
Those pixel formats are used in Synaptics's VideoSmart series SoCs,
likes VS640, VS680. I just disclose the pixel formats used in the video
codecs and display pipeline this time. Actually any device connected to
the MTR module could support those tiled and compressed
Hi Linus,
please pull some fbdev fixes for kernel 6.1-rc3.
A use-after-free bugfix in the smscufx driver.
The other patches are minor.
Thanks,
Helge
The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
are available in the
https://bugzilla.kernel.org/show_bug.cgi?id=213145
--- Comment #27 from nvaert1986 (nvaert1...@hotmail.com) ---
(In reply to rv1sr from comment #24)
> Do you guys by any chance use KWin?
>
> Had experienced this exact issue on a daily basis (kernel 5.19 + amdgpu),
> especially while running
The dma_buf_detach() locks attach->dmabuf->resv and then unlocks
dmabuf->resv, which could be a two different locks from a static
code checker perspective. In particular this triggers Smatch to
report the "double unlock" error. Make the locking pointers consistent.
Reported-by: Dan Carpenter
The drm_gem_vunmap() will crash with a NULL dereference if the passed
object pointer is NULL. It wasn't a problem before we added the locking
support to drm_gem_vunmap function because the mapping argument was always
NULL together with the object. Make drm_client_buffer_delete() to check
whether
Hello,
Here are the two patches fixing minor problems introduced by my
"dma-buf locking convention" series. Thanks to Dan Carpenter who
checked linux-next with Smatch and reported the found issues.
Changelog:
v2: - Added ack from Christian König to the dma-buf patch and improved
the
Dave Airlie 于2022年10月27日周四 13:12写道:
> I'll add some more people who can probably look at it.
>
> Dave.
Got it, Thanks Dave.
Regards,
Zheng Wang
On Thu, Oct 27, 2022 at 2:10 PM Ville Syrjälä
wrote:
>
> On Thu, Oct 27, 2022 at 01:55:39PM -0600, jim.cro...@gmail.com wrote:
> > On Thu, Oct 27, 2022 at 9:59 AM Ville Syrjälä
> > wrote:
> > >
> > > On Thu, Oct 27, 2022 at 09:37:52AM -0600, jim.cro...@gmail.com wrote:
> > > > On Thu, Oct 27,
On Sat, Oct 29, 2022 at 03:48:50PM -0300, antoniospg wrote:
> Test plan:
>
> * Turn off:
> echo 1 > /sys/class/backlight/nv_backlight/bl_power
>
> * Turn on:
> echo 0 > /sys/class/backlight/nv_backlight/bl_power
>
You sent this patch twice, so I reply to the latest one.
What is it doing?
Racing conflict could be:
task A task B
list_for_each_entry
strcmp(h->name))
list_for_each_entry
strcmp(h->name)
kzallockzalloc
.. .
device_create device_create
list_add
add return-value check of ftell to improve robustness(and avoid abnormal
behavior)
Signed-off-by: SPeak
Signed-off-by: shenyanfeng
---
drivers/gpu/drm/radeon/mkregtable.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/radeon/mkregtable.c
Test plan:
* Turn off:
echo 1 > /sys/class/backlight/nv_backlight/bl_power
* Turn on:
echo 0 > /sys/class/backlight/nv_backlight/bl_power
Signed-off-by: antoniospg
---
drivers/gpu/drm/nouveau/nouveau_backlight.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git
There are some devices on which amdgpu won't allow user to set brightness
to sufficiently low values even though the hardware would support it just
fine.
This usually happens in two cases when either configuration of brightness
levels via ACPI/ATIF is not available and amdgpu falls back to
Test plan:
* Turn off:
echo 1 > /sys/class/backlight/nv_backlight/bl_power
* Turn on:
echo 0 > /sys/class/backlight/nv_backlight/bl_power
Signed-off-by: antoniospg
---
drivers/gpu/drm/nouveau/nouveau_backlight.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git
24 matches
Mail list logo