The zte zx platform had been removed in commit 89d4f98ae90d ("ARM: remove
zte zx platform"), so this driver is no longer needed.
Cc: Arnd Bergmann
Cc: Jun Nie
Cc: Shawn Guo
Signed-off-by: Zenghui Yu
---
.../devicetree/bindings/display/zte,vou.txt | 120 ---
drivers/gpu/d
On 2021/8/31 0:12, Rob Herring wrote:
On Thu, Aug 26, 2021 at 4:22 AM Daniel Vetter wrote:
I just merged another patch to delete the zte driver.
Unfortunately, that one missed the binding doc, so please send me a
patch removing the binding doc.
Okay I'll send it out today.
I've searched t
The zte zx platform was removed in commit 89d4f98ae90d ("ARM: remove zte
zx platform") and the zxdrm driver is going to be removed in v5.15 via
drm tree. Let's remove the now obsolete binding doc.
Cc: Arnd Bergmann
Cc: Jun Nie
Cc: Shawn Guo
Signed-off-by: Zenghui Yu
---
splat will be triggered at boot time (if we
compile kernel with CONFIG_DEBUG_TEST_DRIVER_REMOVE=y).
Fixes: 8e55f99c510f ("drm/i915: Invoke another _DSM to enable MUX on HP
Workstation laptops")
Cc: Kai-Heng Feng
Signed-off-by: Zenghui Yu
---
drivers/gpu/drm/i915/display/intel_acpi.c
[+linux-acpi]
ping
On 2021/9/6 11:35, Zenghui Yu wrote:
As per the comment on top of acpi_evaluate_dsm():
| * Evaluate device's _DSM method with specified GUID, revision id and
| * function number. Caller needs to free the returned object.
We should free the returned obje
atal exception
>From our non-expert analysis, fbcon ypos will sometimes over boundary and
then fbcon_putcs() access invalid VGA framebuffer address. We modify the
real_y() to make sure fbcon ypos is always less than rows.
Reported-by: Zengruan Ye
Signed-off-by: Feng Tiantian
Signed-off-by: Ze
Hi Bartlomiej,
On 2019/7/23 23:59, Bartlomiej Zolnierkiewicz wrote:
On 7/12/19 5:13 AM, Zenghui Yu wrote:
From: Feng Tiantian
While using "top" on a CentOS guest's VNC-client, then continuously press
"Shift+PgUp", the guest kernel will get panic! Backtrace is attach
ping for this obvious fix...
On 2020/5/28 21:08, Zenghui Yu wrote:
ERR_PTR() is used in the kernel to encode an usual *negative* errno code
into a pointer. Passing a positive value (ENOMEM) to it will break the
following IS_ERR() check.
Though memory allocation is unlikely to fail, it's
moving it down
after drm_dev_register() which will follow the "Display driver example"
documented by commit de99f0600a79 ("drm/drv: DOC: Add driver example
code").
Signed-off-by: Zenghui Yu
---
drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c | 5 +++--
1 file changed, 3 inser
se of ERR_PTR() in kernel.
Fixes: 25fdd5933e4c ("drm/msm: Add SDM845 DPU support")
Signed-off-by: Zenghui Yu
---
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c
b/drivers/gpu/dr
the DRM_IOCTL_VERSION ioctl to query the driver
version information but leave the name field a non-null-terminated string.
Terminate it properly to actually test against the vgem device.
Signed-off-by: Zenghui Yu
---
tools/testing/selftests/dmabuf-heaps/dmabuf-heap.c | 2 ++
1 file changed, 2
On 2024/7/9 1:49, T.J. Mercier wrote:
On Mon, Jul 8, 2024 at 6:47 AM Zenghui Yu wrote:
>
> Even if a vgem device is configured in, we will skip the import_vgem_fd()
> test almost every time.
>
> TAP version 13
> 1..11
> #
On 2024/6/12 21:52, Tomeu Vizoso wrote:
This initial version supports the NPU as shipped in the RK3588 SoC and
described in the first part of its TRM, in Chapter 36.
This NPU contains 3 independent cores that the driver can submit jobs
to.
This commit adds just hardware initialization and power
The partition device ioctl was removed during the development of the
initial version of qaic driver. Remove its description from the
documentation to avoid confusing readers.
Signed-off-by: Zenghui Yu
---
Documentation/accel/qaic/qaic.rst | 6 --
1 file changed, 6 deletions(-)
diff --git a
case there is a name like "vgemfoo" that
gets converted to "vgem\0" unexpectedly).
Signed-off-by: Zenghui Yu
---
* From v1 [1]:
- Check version.name_len is exactly 4 bytes and return early otherwise
[1] https://lore.kernel.org/r/20240708134654.1725-1-yuzeng...@huawei.com
P.S.,
On 2024/7/29 15:01, Daniel Vetter wrote:
On Mon, Jul 29, 2024 at 10:46:04AM +0800, Zenghui Yu wrote:
> Even if a vgem device is configured in, we will skip the import_vgem_fd()
> test almost every time.
>
> TAP version 13
> 1..11
> # Te
Include dmabuf-heaps selftests in the correct entry so that updates to it
can be sent to the right place.
Signed-off-by: Zenghui Yu
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 42decde38320..b7f24c9fb0e2 100644
--- a/MAINTAINERS
+++ b
Hi all,
Running the dmabuf-heap test [*] on mainline kernel triggers the
following splat:
[ cut here ]
DMA-API: platform vgem: mapping sg segment longer than device claims to
support [len=1048576] [max=65536]
WARNING: CPU: 7 PID: 1126 at kernel/dma/debug.c:1174
debug_dm
On 2025/6/9 22:53, Dmitry Baryshkov wrote:
> On 09/06/2025 17:50, Yongbang Shi wrote:
> >
> > > On Fri, May 30, 2025 at 05:54:25PM +0800, Yongbang Shi wrote:
> > > > From: Baihan Li
> > > >
> > > > The local variable of irq name is passed to
> > > > devm_request_threaded_irq(),
> > > > which will
Hi Thomas,
On 2025/6/19 00:25, Thomas Zimmermann wrote:
> Hi
>
> Am 18.06.25 um 18:03 schrieb Zenghui Yu:
> > Hi all,
> >
> > Running the dmabuf-heap test [*] on mainline kernel triggers the
> > following splat:
> >
> > [ cut here ]
s/g table fixes this problem.
>
> The other drivers based on GEM-SHMEM, imagination, lima, panfrost,
> panthor, v3d and virtio, use the s/g table of imported buffers. Neither
> driver uses the default initializer, so they won't be affected by
> this change.
>
21 matches
Mail list logo
