Hi Christophe JAILLET,
2024년 7월 14일 (일) 오후 4:37, Christophe JAILLET
님이 작성:
>
> 'struct exynos_drm_ipp_funcs' are not modified in these drivers.
>
> Constifying this structure moves some data to a read-only section, so
> increase overall security.
>
> On a x86_64, with allmodconfig, as an example:
Instead of directly casting and returning an error-valued pointer,
use ERR_CAST to make the error handling more explicit and improve
code clarity.
Signed-off-by: Yu Jiaoliang
---
drivers/gpu/drm/xe/xe_sa.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/xe/xe_
Hi Kwanghoon,
2024년 8월 14일 (수) 오후 12:57, Kwanghoon Son 님이 작성:
>
> Function usage exynos_atomic_commit was removed in
> commit 41cbf0fdaa28 ("drm/exynos: use atomic helper commit").
> Remove unnecessary function declare.
It's true. Applied.
Thanks,
Inki Dae
>
> Signed-off-by: Kwanghoon Son
> --
Hi Yuesong Li,
2024년 8월 22일 (목) 오후 6:09, Yuesong Li 님이 작성:
>
> cocci reported a double assignment problem. Upon reviewing previous
> commits, it appears this may actually be an incorrect assignment.
>
> Fixes: 8b9550344d39 ("drm/ipp: clean up debug messages")
> Signed-off-by: Yuesong Li
> ---
>
Include rockchip_drm_drv.h to fix the follow sparse warning:
drivers/gpu/drm/rockchip/rockchip_vop2_reg.c:502:24: sparse:
warning: symbol 'vop2_platform_driver' was not declared.
Should it be static?
No functional change intended.
Signed-off-by: Min-Hua Chen
---
drivers/gpu/drm/rockchip/rockch
On Fri, Sep 06, 2024 at 04:17:41AM +0300, Cristian Ciocaltea wrote:
> Rockchip RK3588 SoC integrates the Synopsys DesignWare HDMI 2.1
> Quad-Pixel (QP) TX controller IP.
>
> Since this is a new IP block, quite different from those used in the
> previous generations of Rockchip SoCs, add a dedicate
On Thu, Sep 05, 2024 at 08:23:51PM GMT, Adam Ford wrote:
> On Wed, Sep 4, 2024 at 3:31 AM Dominique Martinet
> wrote:
> >
> > This allows the hdmi driver to pick e.g. 64.8MHz instead of 65Mhz when we
> > cannot output the exact frequency, enabling the imx8mp HDMI output to
> > support more modes
>
On 05/09/2024 17:22, John Ogness wrote:
On 2024-08-01, John Ogness wrote:
On 2024-08-01, Jocelyn Falempe wrote:
I think I can also register one console for each drm driver, which
will simplify drm_log even further. (currently it would mean having a
circular buffer and work function for each d
This series removes most dependencies on fbdev from the lcd subsystem
and its drivers.
Patches 1 to 3 rework the fbdev notifier, the fbdev's fb_info can
now refer to a dedicated lcd device, and lcd defines constants for
power states. These changes resemble similar changes to the backlight
code.
P
First acquire the ops_lock and do all tests while holding it. Rearranges
the code in lcd's fb_notifier_callback() to resemble the callback in
the backlight module. This will simplify later changes to these tests.
v2:
- avoid gotos by using guard(mutex) (Daniel)
- fix typos in commit description (D
Add struct fb_info.lcd_dev for fbdev drivers to store a reference to
their lcd device. Update the lcd's fb_notifier_callback() to test for
this field. The lcd module can now detect if an lcd device belongs to
an fbdev device.
This works similar to the bl_dev for backlights and will allow for
the r
Duplicate FB_BLANK_ constants as LCD_POWER_ constants in the lcd
header file. Allows lcd drivers to avoid including the fbdev header
file and removes a compile-time dependency between the two subsystems.
The new LCD_POWER_ constants have the same values as their
FB_BLANK_ counterparts. Hence seman
Replace FB_BLANK_ constants with their counterparts from the
lcd subsystem. The values are identical, so there's no change
in functionality.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/backlight/corgi_lcd.c | 12 ++--
1 file changed, 6 insertions(+),
Replace FB_BLANK_ constants with their counterparts from the
lcd subsystem. The values are identical, so there's no change
in functionality.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/backlight/l4f00242t03.c | 32 +--
1 file changed,
Replace FB_BLANK_ constants with their counterparts from the
lcd subsystem. The values are identical, so there's no change
in functionality.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/backlight/ili922x.c | 7 +++
1 file changed, 3 insertions(+), 4 deleti
This lcd driver is independent from the backlight code.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/backlight/lms501kf03.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/video/backlight/lms501kf03.c
b/drivers/video/backlight/lms501kf03.c
index 8a
Replace FB_BLANK_ constants with their counterparts from the
lcd subsystem. The values are identical, so there's no change
in functionality.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/backlight/ili9320.c | 15 +++
1 file changed, 7 insertions(+),
Avoids the proxy include via .
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/backlight/jornada720_lcd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/video/backlight/jornada720_lcd.c
b/drivers/video/backlight/jornada720_lcd.c
index 5c64fa61e810..
The match_fb callback in struct plat_lcd_data is unused. Remove it.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/backlight/platform_lcd.c | 4
include/video/platform_lcd.h | 3 ---
2 files changed, 7 deletions(-)
diff --git a/drivers/video/back
Replace FB_BLANK_ constants with their counterparts from the
lcd subsystem. The values are identical, so there's no change
in functionality.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/backlight/hx8357.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Replace FB_BLANK_ constants with their counterparts from the
lcd subsystem. The values are identical, so there's no change
in functionality.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/backlight/lms283gf05.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(
This lcd driver does not depend on backlight interfaces. Remove the
include statement.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/backlight/platform_lcd.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/video/backlight/platform_lcd.c
b/drivers/vi
With the exception of fb_notifier_callback(), none of the lcd code
uses fbdev; especially not the lcd drivers. Remove the include
statement for from the public lcd header.
v2:
- fix typos in commit description
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
include/linux/lcd
Store the lcd device in struct fb_info.lcd_dev. The lcd subsystem can
now detect the lcd's fbdev device from this field.
This makes the implementation of check_fb in imxfb_lcd_ops obsolete.
Remove it.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/fbdev/imxfb.c
Rename check_fb in struct lcd_ops to controls_device. The callback
is now independent from fbdev's struct fb_info and tests if an lcd
device controls a hardware display device. The new naming and semantics
follow similar functionality for backlight devices.
v2:
- fix typos in commit description (D
Replace FB_BLANK_ constants with their counterparts from the
lcd subsystem. The values are identical, so there's no change
in functionality.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/backlight/otm3225a.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Replace FB_BLANK_ constants with their counterparts from the
lcd subsystem. The values are identical, so there's no change
in functionality.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/backlight/platform_lcd.c | 4 ++--
1 file changed, 2 insertions(+), 2 dele
Store the lcd device in struct fb_info.lcd_dev. The lcd subsystem can
now detect the lcd's fbdev device from this field.
This makes the implementation of check_fb in picolcd_lcdops obsolete.
Remove it.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
Acked-by: Jiri Kosina
---
dri
Replace FB_BLANK_ constants with their counterparts from the
lcd subsystem. The values are identical, so there's no change
in functionality.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/backlight/tdo24m.c | 14 +++---
1 file changed, 7 insertions(+), 7
Replace FB_BLANK_ constants with their counterparts from the
lcd subsystem. The values are identical, so there's no change
in functionality.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/backlight/lms501kf03.c | 23 +++
1 file changed, 11 in
Replace FB_BLANK_ constants with their counterparts from the
lcd subsystem. The values are identical, so there's no change
in functionality.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/fbdev/clps711x-fb.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletio
Replace FB_BLANK_ constants with their counterparts from the
lcd subsystem. The values are identical, so there's no change
in functionality.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/backlight/ltv350qv.c | 15 +++
1 file changed, 7 insertions(+)
Replace FB_BLANK_ constants with their counterparts from the
lcd subsystem. The values are identical, so there's no change
in functionality.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/backlight/jornada720_lcd.c | 9 -
1 file changed, 4 insertions(+),
Implementations of struct lcd_ops.set_mode only require the resolution
from struct fb_videomode. Pass the xres and yres fields, but remove the
dependency on the fbdev data structure.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/backlight/corgi_lcd.c | 5 ++---
Replace FB_BLANK_ constants with their counterparts from the
lcd subsystem. The values are identical, so there's no change
in functionality.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/fbdev/omap/lcd_ams_delta.c | 8
1 file changed, 4 insertions(+),
Replace FB_BLANK_ constants with their counterparts from the
lcd subsystem. The values are identical, so there's no change
in functionality.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/fbdev/imxfb.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Store the lcd device in struct fb_info.lcd_dev. The lcd subsystem can
now detect the lcd's fbdev device from this field.
This makes the implementation of check_fb in clps711x_lcd_ops obsolete.
Remove it.
Signed-off-by: Thomas Zimmermann
Reviewed-by: Daniel Thompson
---
drivers/video/fbdev/clps
> Subject: i.MX8MP IMX-LCDIF Underrun Question(s)
>
> I have been testing various settings on the HDMI out of the i.MX8MP.
>
> I noticed that sometimes my monitor would not sync, but sometimes it
> would on the same resolution/refresh rate. Frieder noted the LCDIF
> was sometimes underflowing, s
Hi Huan,
> Subject: [PATCH v5 1/7] udmabuf: pre-fault when first page fault
>
> The current udmabuf mmap uses a page fault to populate the vma.
>
> However, the current udmabuf has already obtained and pinned the folio
> upon completion of the creation.This means that the physical memory has
> a
As commit cbe16f35bee6 ("genirq: Add IRQF_NO_AUTOEN for request_irq/nmi()")
said, reqeust_irq() and then disable_irq() is unsafe. In the small time gap
between request_irq() and disable_irq(), interrupts can still come.
IRQF_NO_AUTOEN flag can be used by drivers to request_irq(). It prevents
the a
disable_irq() after request_irq() still has a time gap in which
interrupts can come. request_irq() with IRQF_NO_AUTOEN flag will
disable IRQ auto-enable when request IRQ.
Fixes: 9021c317b770 ("drm/imx: Add initial support for DCSS on iMX8MQ")
Signed-off-by: Jinjie Ruan
---
drivers/gpu/drm/imx/dc
disable_irq() after request_irq() still has a time gap in which
interrupts can come. request_irq() with IRQF_NO_AUTOEN flag will
disable IRQ auto-enable when request IRQ.
Fixes: 9021c317b770 ("drm/imx: Add initial support for DCSS on iMX8MQ")
Signed-off-by: Jinjie Ruan
---
drivers/gpu/drm/imx/dc
disable_irq() after request_irq() still has a time gap in which
interrupts can come. request_irq() with IRQF_NO_AUTOEN flag will
disable IRQ auto-enable when request IRQ.
Fixes: 47b1be5c0f4e ("staging: imx/drm: request irq only after adding the crtc")
Signed-off-by: Jinjie Ruan
---
drivers/gpu/d
disable_irq() after request_irq() still has a time gap in which
interrupts can come. request_irq() with IRQF_NO_AUTOEN flag will
disable IRQ auto-enable when request IRQ.
Fixes: 4b565ca5a2cb ("drm/msm: Add A6XX device support")
Signed-off-by: Jinjie Ruan
---
drivers/gpu/drm/msm/adreno/a6xx_gmu.c
disable_irq() after request_irq() still has a time gap in which
interrupts can come. request_irq() with IRQF_NO_AUTOEN flag will
disable IRQ auto-enable when request IRQ.
Fixes: 9e532b3ad9a7 ("drm/tegra: dpaux: Disable interrupt when detached")
Signed-off-by: Jinjie Ruan
---
drivers/gpu/drm/tegr
Hi Huan,
> Subject: [PATCH v5 4/7] udmabuf: udmabuf_create pin folio codestyle
> cleanup
>
> This patch split pin folios into single function: udmabuf_pin_folios.
>
> When record folio and offset into udmabuf_folio and offsets, the outer
> loop of this patch iterates through folios, while the in
On Wed, Sep 04, 2024 at 02:45:36PM -0700, Stephen Boyd wrote:
> Quoting Tzung-Bi Shih (2024-09-04 02:36:45)
> > On Sat, Aug 31, 2024 at 09:06:56PM -0700, Stephen Boyd wrote:
> > > +static void cros_typec_inject_hpd(struct cros_typec_data *typec,
> > > + struct ec_respo
Hi Huan,
> Subject: [PATCH v5 5/7] udmabuf: introduce udmabuf init and deinit helper
>
> After udmabuf is allocated, its resources need to be initialized,
> including various array structures. The current array structure has
> already been greatly expanded.
>
> Also, before udmabuf needs to be k
Hi Huan,
> Subject: [PATCH v5 6/7] udmabuf: remove udmabuf_folio
>
> Currently, udmabuf handles folio by creating an unpin list to record
> each folio obtained from the list and unpinning them when released. To
> maintain this approach, many data structures have been established.
>
> However, ma
Il 01/09/24 16:32, Chun-Kuang Hu ha scritto:
In order to have fine-grained control, use cmdq_pkt_eoc() and
cmdq_pkt_jump_rel() to replace cmdq_pkt_finalize().
Signed-off-by: Chun-Kuang Hu
Reviewed-by: AngeloGioacchino Del Regno
Il 01/09/24 16:32, Chun-Kuang Hu ha scritto:
Use cmdq_pkt_create() and cmdq_pkt_destroy() common function
instead of implementing mdp3 version.
Signed-off-by: Chun-Kuang Hu
Reviewed-by: AngeloGioacchino Del Regno
Hi Huan,
> Subject: [PATCH v5 7/7] udmabuf: reuse folio array when pin folios
>
> When invoke memfd_pin_folios, we need offer an array to save each folio
> which we pinned.
>
> The currently way is dynamic alloc an array, get folios, save into
> udmabuf and then free.
>
> If the size is tiny, a
Il 01/09/24 16:32, Chun-Kuang Hu ha scritto:
In order to have fine-grained control, use cmdq_pkt_eoc() and
cmdq_pkt_jump_rel() to replace cmdq_pkt_finalize().
Signed-off-by: Chun-Kuang Hu
I'll pick this one after the media patches will be mainlined to avoid issues.
In the meanwhile, mainly a
On 2024-09-06, Jocelyn Falempe wrote:
>> It would be great to see a version of drm_log that only implements
>> write_thread() and does not do any of its own buffering with workqueue
>> and also does not need to track multiple graphic loggers at the same
>> time.
>
> Thanks for the head-up.
> I wil
Il 02/09/24 15:36, Liankun Yang ha scritto:
Update efuse data for MT8188 displayport.
The DP monitor can not display when DUT connected to USB-c to DP dongle.
Analysis view is invalid DP efuse data.
Fixes: 350c3fe907fb ("drm/mediatek: dp: Add support MT8188 dp/edp function")
Changes in V2:
- A
在 2024/9/6 16:17, Kasireddy, Vivek 写道:
Hi Huan,
Subject: [PATCH v5 4/7] udmabuf: udmabuf_create pin folio codestyle
cleanup
This patch split pin folios into single function: udmabuf_pin_folios.
When record folio and offset into udmabuf_folio and offsets, the outer
loop of this patch iterate
On Fri, Sep 06, 2024 at 08:58:15AM +0900, Masahiro Yamada wrote:
> On Thu, Sep 5, 2024 at 5:56 PM Daniel Gomez wrote:
> >
> > On Mon, Sep 02, 2024 at 01:15:01AM +0900, Masahiro Yamada wrote:
> > > On Sat, Aug 31, 2024 at 4:54 AM Nicolas Schier wrote:
> > > >
> > > > On Sat, Aug 24, 2024 at 12:54:
在 2024/9/6 16:12, Kasireddy, Vivek 写道:
Hi Huan,
Subject: [PATCH v5 1/7] udmabuf: pre-fault when first page fault
The current udmabuf mmap uses a page fault to populate the vma.
However, the current udmabuf has already obtained and pinned the folio
upon completion of the creation.This means
Hi Mikko,
On 31/05/2024 08:07, Mikko Perttunen wrote:
From: Mikko Perttunen
Syncpoint IRQs are currently requested in a code path that runs
during resume. Due to this, we get multiple overlapping registered
interrupt handlers as host1x is suspended and resumed.
Rearrange interrupt code to onl
在 2024/9/6 16:20, Kasireddy, Vivek 写道:
Hi Huan,
Subject: [PATCH v5 5/7] udmabuf: introduce udmabuf init and deinit helper
After udmabuf is allocated, its resources need to be initialized,
including various array structures. The current array structure has
already been greatly expanded.
Also
在 2024/9/6 16:22, Kasireddy, Vivek 写道:
Hi Huan,
Subject: [PATCH v5 6/7] udmabuf: remove udmabuf_folio
Currently, udmabuf handles folio by creating an unpin list to record
each folio obtained from the list and unpinning them when released. To
maintain this approach, many data structures have
在 2024/9/6 16:23, Kasireddy, Vivek 写道:
Hi Huan,
Subject: [PATCH v5 7/7] udmabuf: reuse folio array when pin folios
When invoke memfd_pin_folios, we need offer an array to save each folio
which we pinned.
The currently way is dynamic alloc an array, get folios, save into
udmabuf and then fre
Hi all,
On Mon, 26 Aug 2024 15:59:16 +1000 Stephen Rothwell
wrote:
>
> After merging the amdgpu tree, today's linux-next build (htmldocs)
> produced this warning:
>
> drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c:2785: warning: Function parameter or
> struct member 'ts' not described in 'amdgpu_vm_ha
On 2024-09-06, John Ogness wrote:
> Your device_lock()/device_unlock() callbacks probably just need to
> lock/unlock your mutex @drm_log_lock.
Sorry, forgot to mention that the device_lock() callback must also
disable migration. Since you are using a mutex, you will need to
manually do that as we
On Fri, Sep 6, 2024 at 12:05 AM Alex Deucher wrote:
>
> On Tue, Sep 3, 2024 at 5:53 AM sikkamukul wrote:
> >
> > From: Bob Zhou
> >
> > [ Upstream commit 50151b7f1c79a09117837eb95b76c2de76841dab ]
> >
> > Check return value and conduct null pointer handling to avoid null pointer
> > dereference
This is v4 of the MT8186 Chromebook device tree series.
---
Changes in v4:
- PATCH 1/2: Add more info for Ponyta custom label in commit.
- Link to
v3:https://lore.kernel.org/all/20240904081501.2060933-1-cengjian...@huaqin.corp-partner.google.com/
Changes in v3:
- PATCH 0/2: Add the modify records
Ponyta is a custom label Chromebook based on MT8186. It is a
self-developed project of Huaqin and has no fixed OEM.
Signed-off-by: Jianeng Ceng
---
Changes in v4:
- PATCH 1/2: Add more info for Ponyta custom label in commit.
- Link to
v3:https://lore.kernel.org/all/20240904081501.2060933-1-cengj
MT8186 ponyta, known as huaqin custom label, is a
MT8186 based laptop. It is based on the "corsola" design.
It includes LTE, touchpad combinations.
Signed-off-by: Jianeng Ceng
---
Changes in v2:
- PATCH 2/2: Modify the dtb name without rev2.
- Link to
v1:https://lore.kernel.org/all/2024090212550
Hi Marek,
On Mi, 2024-07-24 at 02:19 +0200, Marek Vasut wrote:
> Introduce dedicated memory-to-memory IPUv3 VDI deinterlacer driver.
> Currently the IPUv3 can operate VDI in DIRECT mode, from sensor to
> memory. This only works for single stream, that is, one input from
> one camera is deinterlace
Hi Dave and Daniel,
Just three cleanups and one fixup.
Please kindly let me know if there is any problem.
Thanks,
The following changes since commit b1aa0491fad27f030c94ed42c873c3f46f5e7364:
drm/xe: Fix merge fails related to display runtime PM (2024-09-02 14:14:07
+0200)
are available
On Fri Sep 6, 2024 at 2:42 AM CEST, Andy Yan wrote:
> At 2024-09-06 06:38:50, "Min-Hua Chen" wrote:
> >Include rockchip_drm_drv.h to fix the follow sparse warning:
> >
> >drivers/gpu/drm/rockchip/rockchip_vop2_reg.c:502:24: sparse:
> >warning: symbol 'vop2_platform_driver' was not declared.
> >Sho
The version number output when loading the firmware is actually the
interface version not the version of the firmware itself. Update the
message to make this clearer.
However, the firmware binary has a git SHA embedded into it which can be
used to identify which firmware binary is being loaded. So
This series introduces device wedged event in DRM subsystem and uses
it in xe and i915 drivers. Detailed description in commit message.
This was earlier attempted as xe specific uevent in v1 and v2.
https://patchwork.freedesktop.org/series/136909/
v2: Change authorship to Himal (Aravind)
Add
Introduce device wedged event, which will notify userspace of wedged
(hanged/unusable) state of the DRM device through a uevent. This is
useful especially in cases where the device is in unrecoverable state
and requires userspace intervention for recovery.
Purpose of this implementation is to be v
This was previously attempted as xe specific reset uevent but dropped
in commit 77a0d4d1cea2 ("drm/xe/uapi: Remove reset uevent for now")
as part of refactoring.
Now that we have device wedged event supported by DRM core, make use
of it. With this in place userspace will be notified of wedged devi
Now that we have device wedged event supported by DRM core, make use
of it. With this in place, userspace will be notified of wedged device
on gt reset failure.
Signed-off-by: Raag Jadav
---
drivers/gpu/drm/i915/gt/intel_reset.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/d
Hi，
At 2024-09-06 17:28:33, "Diederik de Haas" wrote:
>On Fri Sep 6, 2024 at 2:42 AM CEST, Andy Yan wrote:
>> At 2024-09-06 06:38:50, "Min-Hua Chen" wrote:
>> >Include rockchip_drm_drv.h to fix the follow sparse warning:
>> >
>> >drivers/gpu/drm/rockchip/rockchip_vop2_reg.c:502:24: sparse:
>> >
On Fri, Sep 06, 2024 at 04:23:25PM GMT, Jinjie Ruan wrote:
> disable_irq() after request_irq() still has a time gap in which
> interrupts can come. request_irq() with IRQF_NO_AUTOEN flag will
> disable IRQ auto-enable when request IRQ.
>
> Fixes: 4b565ca5a2cb ("drm/msm: Add A6XX device support")
>
On Fri, Sep 06, 2024 at 04:23:22PM GMT, Jinjie Ruan wrote:
> disable_irq() after request_irq() still has a time gap in which
> interrupts can come. request_irq() with IRQF_NO_AUTOEN flag will
> disable IRQ auto-enable when request IRQ.
>
> Fixes: 9021c317b770 ("drm/imx: Add initial support for DCS
On Fri, Sep 06, 2024 at 04:23:23PM GMT, Jinjie Ruan wrote:
> disable_irq() after request_irq() still has a time gap in which
> interrupts can come. request_irq() with IRQF_NO_AUTOEN flag will
> disable IRQ auto-enable when request IRQ.
>
> Fixes: 47b1be5c0f4e ("staging: imx/drm: request irq only a
On Fri, Sep 06, 2024 at 04:23:21PM GMT, Jinjie Ruan wrote:
> disable_irq() after request_irq() still has a time gap in which
> interrupts can come. request_irq() with IRQF_NO_AUTOEN flag will
> disable IRQ auto-enable when request IRQ.
>
> Fixes: 9021c317b770 ("drm/imx: Add initial support for DCS
This series adds basic drm_panic support for nouveau.
Patches 1-2 Add missing bits in drm_panic (ABGR2101010, private data for
set_pixel())
Patch 3 registers nouveau to drm_panic, and handle tiling.
I've tested on a GTX1650, while running Gnome/Wayland desktop.
It should work on other nv50+ cards
It can be set to a private structure in get_scanout_buffer(), and
used later in set_pixel() or in panic_flush().
Signed-off-by: Jocelyn Falempe
---
include/drm/drm_panic.h | 7 +++
1 file changed, 7 insertions(+)
diff --git a/include/drm/drm_panic.h b/include/drm/drm_panic.h
index 54085d5d0
Add support for ABGR2101010, used by the nouveau driver.
Signed-off-by: Jocelyn Falempe
---
drivers/gpu/drm/drm_panic.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/gpu/drm/drm_panic.c b/drivers/gpu/drm/drm_panic.c
index 74412b7bf936..0a9ecc1380d2 100644
--- a/drivers/
Add drm_panic support, for nv50+ cards.
It's enough to get the panic screen while running Gnome/Wayland on a
GTX 1650.
It doesn't support multi-plane or compressed format.
Support for other formats and older cards will come later.
Tiling is only tested on GTX1650, and might be wrong for other cards
On 05/09/2024 18:32, Mary Guillemard wrote:
> Expose allowed group priorities with a new device query.
>
> This new uAPI will be used in Mesa to properly report what priorities a
> user can use for EGL_IMG_context_priority.
>
> Since this extends the uAPI and because userland needs a way to
> adv
Hi Dave & Sima,
Here goes the final drm-intel-gt-next towards 6.12.
Primarily addition of fan speed hwmon, W/A fixups for ARL, add missing register
for userspace into DG2/MTL/ARL. Then a few smaller fixes.
Regards, Joonas
***
drm-intel-gt-next-2024-09-06:
Driver Changes:
- Expose fan speed
14,6 +14,7 @@ config DRM_IMX_PARALLEL_DISPLAY
depends on DRM_IMX
select DRM_BRIDGE
select DRM_PANEL_BRIDGE
+ select DRM_IMX_LEGACY_BRIDGE
select VIDEOMODE_HELPERS
config DRM_IMX_TVE
---
base-commit: 8a8a31205e62b57f1fb844d790d682286121f729
change-id: 20240906-imx-par
From: Daniel Gomez
The uuid_t struct defined in sys/types.h on macOS hosts conflicts with
the one defined in file2alias, resulting in the typedef redefinition
error below. To resolve this conflict, define the _UUID_T and
__GETHOSTUUID_ in file2alias HOSTCFLAGS.
Error:
HOSTCC scripts/mod/file2
From: Daniel Gomez
Use getprogname() [1] instead of program_invocation_short_name() [2]
for macOS hosts.
[1]:
https://www.gnu.org/software/gnulib/manual/html_node/
program_005finvocation_005fshort_005fname.html
[2]:
https://developer.apple.com/library/archive/documentation/System/
Conceptual/Ma
From: Daniel Gomez
endian.h header is not provided by default in macOS. Use pkg-config with
the new development package 'bee-headers' [1] to find the path where the
headers are installed.
[1] Bee Headers Project links:
https://github.com/bee-headers/headers
https://github.com/bee-headers/homebre
From: Nick Desaulniers
When building the Linux kernel on an aarch64 macOS based host, if we don't
specify a value for ARCH when invoking make, we default to arm and thus
multi_v7_defconfig rather than the expected arm64 and arm64's defconfig.
This is because subarch.include invokes `uname -m` wh
From: Masahiro Yamada
Commit bfc5e3a6af39 ("selinux: use the kernel headers when building
scripts/selinux") is not the right thing to do.
It is clear from the warning in include/uapi/linux/types.h:
#ifndef __EXPORTED_HEADERS__
#warning "Attempt to use kernel headers from user space, see
ht
From: Daniel Gomez
endian.h header is not provided by default in macOS. Use pkg-config with
the new development package 'bee-headers' [1] to find the path where the
headers are installed.
[1] Bee Headers Project links:
https://github.com/bee-headers/headers
https://github.com/bee-headers/homebre
From: Masahiro Yamada
This tool is only used in security/selinux/Makefile.
There is no reason to keep it under scripts/.
Signed-off-by: Masahiro Yamada
---
scripts/remove-stale-files| 3 +++
scripts/selinux/Makefile | 2
From: Daniel Gomez
Add documentation under kbuild/llvm to inform about the experimental
support for building the Linux kernel in macOS hosts environments.
Signed-off-by: Daniel Gomez
---
Documentation/kbuild/llvm.rst | 78 +++
1 file changed, 78 insertio
This patch set allows for building the Linux kernel for arm64 in macOS
with LLVM.
Patches are based on previous Nick's work and suggestions [1][2][3] to
enable the Linux kernel build system on macOS hosts.
macOS does not provide certain headers that are available in a GNU/Linux
distribution with
Hi,
On Fri Sep 6, 2024 at 11:50 AM CEST, Andy Yan wrote:
> At 2024-09-06 17:28:33, "Diederik de Haas" wrote:
> >On Fri Sep 6, 2024 at 2:42 AM CEST, Andy Yan wrote:
> >> At 2024-09-06 06:38:50, "Min-Hua Chen" wrote:
> >> >Include rockchip_drm_drv.h to fix the follow sparse warning:
> >> >
> >> >d
The parameter dev_priv is actually not used in macro PORT_ALPM_CTL
and PORT_ALPM_LFPS_CTL,so remove it to simplify the code.
Reviewed-by: Jani Nikula
Signed-off-by: He Lugang
---
drivers/gpu/drm/i915/display/intel_alpm.c | 4 ++--
drivers/gpu/drm/i915/display/intel_psr.c | 2 +-
driver
On Fri, 6 Sept 2024 at 09:39, Alexander Stein
wrote:
>
> When drm/bridge-connector was moved to DRM_DISPLAY_HELPER not all
> users were updated. Add missing Kconfig selections.
>
> Fixes: 9da7ec9b19d8 ("drm/bridge-connector: move to DRM_DISPLAY_HELPER
> module")
> Signed-off-by: Alexander Stein
1 - 100 of 184 matches
Mail list logo
