Re: [PATCH 01/12] kbuild: make -Woverride-init warnings more consistent

On Wed, Mar 27, 2024 at 6:23 PM Arnd Bergmann wrote: > > On Wed, Mar 27, 2024, at 08:50, Jani Nikula wrote: > > On Tue, 26 Mar 2024, "Arnd Bergmann" wrote: > >> On Tue, Mar 26, 2024, at 21:24, Jani Nikula wrote: > >>> On Tue, 26 Mar 2024, Arnd Bergmann wrote: > >> > >> It works now. > >> > >>

[PATCH 6/6] drm/sti: hqvdp: drop driver owner assignment

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/sti/sti_hqvdp.c | 1 - 1 file changed, 1 deletion(-)

[PATCH 5/6] drm/sti: hdmi: drop driver owner assignment

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- I forgot two drivers. drivers/gpu/drm/sti/sti_hdmi.c | 1 - 1 file

[PATCH] drm/etnaviv: drop driver owner assignment

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/etnaviv/etnaviv_gpu.c | 1 - 1 file changed, 1

[PATCH 11/11] drm/mediatek: padding: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/mediatek/mtk_padding.c | 1 - 1 file changed, 1

[PATCH 09/11] drm/mediatek: ethdr: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/mediatek/mtk_ethdr.c | 1 - 1 file changed, 1

[PATCH 10/11] drm/mediatek: mdp_rdma: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/mediatek/mtk_mdp_rdma.c | 1 - 1 file changed, 1

[PATCH 08/11] drm/mediatek: rdma: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/mediatek/mtk_disp_rdma.c | 1 - 1 file changed, 1

[PATCH 04/11] drm/mediatek: gamma: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/mediatek/mtk_disp_gamma.c | 1 - 1 file changed, 1

[PATCH 01/11] drm/mediatek: aal: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/mediatek/mtk_disp_aal.c | 1 - 1 file changed, 1

[PATCH 03/11] drm/mediatek: color: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/mediatek/mtk_disp_color.c | 1 - 1 file changed, 1

[PATCH 05/11] drm/mediatek: merge: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/mediatek/mtk_disp_merge.c | 1 - 1 file changed, 1

[PATCH 07/11] drm/mediatek: ovl_adaptor: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/mediatek/mtk_disp_ovl_adaptor.c | 1 - 1 file

[PATCH 02/11] drm/mediatek: ccorr: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/mediatek/mtk_disp_ccorr.c | 1 - 1 file changed, 1

[PATCH 06/11] drm/mediatek: ovl: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/mediatek/mtk_disp_ovl.c | 1 - 1 file changed, 1

[PATCH 00/11] drm/mediatek: drop driver owner initialization

: 7fdcff3312e16ba8d1419f8a18f465c5cc235ecf change-id: 20240330-b4-module-owner-drm-mediatek-aa525b70f033 Best regards, -- Krzysztof Kozlowski

[PATCH 2/4] drm/sti: hda: drop driver owner assignment

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/sti/sti_hda.c | 1 - 1 file changed, 1 deletion(-)

[PATCH 4/4] drm/sti: vtg: drop driver owner assignment

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/sti/sti_vtg.c | 1 - 1 file changed, 1 deletion(-)

[PATCH 1/4] drm/sti: dvo: drop driver owner assignment

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/sti/sti_dvo.c | 1 - 1 file changed, 1 deletion(-)

[PATCH 3/4] drm/sti: tvout: drop driver owner assignment

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/sti/sti_tvout.c | 1 - 1 file changed, 1 deletion(-)

[PATCH 08/11] drm/exynos: scaler: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/exynos/exynos_drm_scaler.c | 1 - 1 file changed, 1

[PATCH 07/11] drm/exynos: rotator: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/exynos/exynos_drm_rotator.c | 1 - 1 file changed, 1

[PATCH 06/11] drm/exynos: mic: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/exynos/exynos_drm_mic.c | 1 - 1 file changed, 1

[PATCH 01/11] drm/exynos: fimc: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/exynos/exynos_drm_fimc.c | 1 - 1 file changed, 1

[PATCH 11/11] drm/exynos: mixer: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/exynos/exynos_mixer.c | 1 - 1 file changed, 1

[PATCH 09/11] drm/exynos: vidi: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/exynos/exynos_drm_vidi.c | 1 - 1 file changed, 1

[PATCH 10/11] drm/exynos: hdmi: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/exynos/exynos_hdmi.c | 1 - 1 file changed, 1

[PATCH 04/11] drm/exynos: g2d: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 1 - 1 file changed, 1

[PATCH 05/11] drm/exynos: gsc: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/exynos/exynos_drm_gsc.c | 1 - 1 file changed, 1

[PATCH 03/11] drm/exynos: dsi: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/exynos/exynos_drm_dsi.c | 1 - 1 file changed, 1

[PATCH 02/11] drm/exynos: fimd: drop driver owner initialization

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 1 - 1 file changed, 1

[PATCH 00/11] drm/exynos: drop driver owner initialization

/exynos_drm_vidi.c| 1 - drivers/gpu/drm/exynos/exynos_hdmi.c| 1 - drivers/gpu/drm/exynos/exynos_mixer.c | 1 - 11 files changed, 11 deletions(-) --- base-commit: 7fdcff3312e16ba8d1419f8a18f465c5cc235ecf change-id: 20240330-b4-module-owner-drm-exynos-d2f1b2d48af3 Best regards

[PATCH] drm/armada: drop driver owner assignment

Core in platform_driver_register() already sets the .owner, so driver does not need to. The CRTC driver is registered in different file, armada_drv.c, but that should be the same module and if the values were different core would overwrite them anyway. Signed-off-by: Krzysztof Kozlowski ---

[PATCH] drm/omap: dmm_tiler: drop driver owner assignment

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/omapdrm/omap_dmm_tiler.c | 1 - 1 file changed, 1

[PATCH] drm/rockchip: cdn-dp: drop driver owner assignment

Core in platform_driver_register() already sets the .owner, so driver does not need to. Whatever is set here will be anyway overwritten by main driver calling platform_driver_register(). Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/rockchip/cdn-dp-core.c | 1 - 1 file changed, 1

[PATCH 2/2] drm/bridge: tc358764: drop driver owner assignment

Core in mipi_dsi_driver_register() already sets the .owner, so driver does not need to. Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/bridge/tc358764.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/bridge/tc358764.c b/drivers/gpu/drm/bridge/tc358764.c index

[PATCH 1/2] drm/bridge: chipone-icn6211: drop driver owner assignment

Core in mipi_dsi_driver_register() already sets the .owner, so driver does not need to. Signed-off-by: Krzysztof Kozlowski --- drivers/gpu/drm/bridge/chipone-icn6211.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/bridge/chipone-icn6211.c

Re: [PATCH] drm/msm/dpu: make error messages at dpu_core_irq_register_callback() more sensible

- DPU_ERROR("invalid IRQ=[%d, %d]\n", > > - DPU_IRQ_REG(irq_idx), DPU_IRQ_BIT(irq_idx)); > > + DPU_ERROR("invalid IRQ=[%d, %d] irq_cb:%ps\n", > > + DPU_IRQ_REG(irq_idx), DPU_IRQ_BIT(irq_idx), irq_cb); > > return -EINVAL; > > } > > > > > > --- > > base-commit: 13ee4a7161b6fd938aef6688ff43b163f6d83e37 > > change-id: 20240330-dpu-irq-messages-5cf13fd7568c > > > > Best regards, > > -- > > Dmitry Baryshkov > >

Re: [PATCH] drm/msm/dpu: fix vblank IRQ handling for command panels

On 3/30/2024 9:49 AM, Marijn Suijten wrote: On 2024-03-30 05:52:29, Dmitry Baryshkov wrote: In case of CMD DSI panels, the vblank IRQ can be used outside of irq_enable/irq_disable pair. This results in the following kind of Can you clarify when exactly that is? Is it via

Re: [PATCH] drm/msm/dpu: make error messages at dpu_core_irq_register_callback() more sensible

On 3/29/2024 8:53 PM, Dmitry Baryshkov wrote: There is little point in using %ps to print a value known to be NULL. On the other hand it makes sense to print the callback symbol in the 'invalid IRQ' message. Correct those two error messages to make more sense. Fixes: 6893199183f8

Re: [PATCH net-next v5 1/3] net: ethernet: ti: Add accessors for struct k3_cppi_desc_pool members

On Thu, Mar 28, 2024 at 12:06:56PM +, Naveen Mamindlapalli wrote: > > diff --git a/drivers/net/ethernet/ti/k3-cppi-desc-pool.c > > b/drivers/net/ethernet/ti/k3- > > cppi-desc-pool.c > > index 05cc7aab1ec8..fe8203c05731 100644 > > --- a/drivers/net/ethernet/ti/k3-cppi-desc-pool.c > > +++

Re: [PATCH v2 1/3] dt-bindings: panel: Add LG SW43408 MIPI-DSI panel

On 30/03/2024 16:00, Dmitry Baryshkov wrote: > From: Sumit Semwal > > LG SW43408 is 1080x2160, 4-lane MIPI-DSI panel present on Google Pixel 3 > phones. > > Signed-off-by: Vinod Koul > Signed-off-by: Sumit Semwal > [caleb: convert to yaml] > Signed-off-by: Caleb Connolly > Signed-off-by:

Re: [PATCH] drm/msm/dpu: fix vblank IRQ handling for command panels

On 2024-03-30 05:52:29, Dmitry Baryshkov wrote: > In case of CMD DSI panels, the vblank IRQ can be used outside of > irq_enable/irq_disable pair. This results in the following kind of Can you clarify when exactly that is? Is it via ops.control_vblank_irq in dpu_encoder_toggle_vblank_for_crtc()?

[PATCH v2 3/3] drm: panel: Add LG sw43408 panel driver

From: Sumit Semwal LG SW43408 is 1080x2160, 4-lane MIPI-DSI panel, used in some Pixel3 phones. Signed-off-by: Sumit Semwal [vinod: Add DSC support] Signed-off-by: Vinod Koul [caleb: cleanup and support turning off the panel] Signed-off-by: Caleb Connolly [DB: partially rewrote the driver and

[PATCH v2 0/3] drm/panel: add support for LG SW43408 panel

) - Changed dsc_en to be an array (Marijn) - Added comment regiarding slice_width and slice_count (Marijn) - Link to v1: https://lore.kernel.org/r/20240330-lg-sw43408-panel-v1-0-f5580fc9f...@linaro.org --- Dmitry Baryshkov (1): drm/mipi-dsi: add mipi_dsi_compression_mode_raw() Sumit Semwal (2

[PATCH v2 2/3] drm/mipi-dsi: add mipi_dsi_compression_mode_raw()

The LG SW43408 panel requires sending non-standard data as a part of the MIPI_DSI_COMPRESSION_MODE packet. Rather than hacking existing mipi_dsi_compression_mode() add mipi_dsi_compression_mode_raw(), which accepts raw data buffer and length. Signed-off-by: Dmitry Baryshkov ---

[PATCH v2 1/3] dt-bindings: panel: Add LG SW43408 MIPI-DSI panel

From: Sumit Semwal LG SW43408 is 1080x2160, 4-lane MIPI-DSI panel present on Google Pixel 3 phones. Signed-off-by: Vinod Koul Signed-off-by: Sumit Semwal [caleb: convert to yaml] Signed-off-by: Caleb Connolly Signed-off-by: Dmitry Baryshkov --- .../bindings/display/panel/lg,sw43408.yaml

[PATCH v5 2/2] backlight: Add new lm3509 backlight driver

This is a general driver for LM3509 backlight chip of TI. LM3509 is High Efficiency Boost for White LEDs and/or OLED Displays with Dual Current Sinks. This driver supports OLED/White LED select, brightness control and sub/main control. The datasheet can be found at

[PATCH v5 1/2] dt-bindings: backlight: Add Texas Instruments LM3509

Add Device Tree bindings for Texas Instruments LM3509 - a High Efficiency Boost for White LED's and/or OLED Displays Signed-off-by: Patrick Gansterer Reviewed-by: Krzysztof Kozlowski Reviewed-by: Daniel Thompson --- .../bindings/leds/backlight/ti,lm3509.yaml| 139 ++ 1

[PATCH v5 0/2] backlight: Add new lm3509 backlight driver

This is a general driver for LM3509 backlight chip of TI. LM3509 is High Efficiency Boost for White LEDs and/or OLED Displays with Dual Current Sinks. This driver supports OLED/White LED select, brightness control and sub/main control. The datasheet can be found at

Re: [PATCH 3/3] drm: panel: Add LG sw43408 panel driver

On Sat, 30 Mar 2024 at 12:27, Marijn Suijten wrote: > > On 2024-03-30 05:59:30, Dmitry Baryshkov wrote: > > From: Sumit Semwal > > > > LG SW43408 is 1080x2160, 4-lane MIPI-DSI panel, used in some Pixel3 > > phones. > > > > Whatever init sequence we have for this panel isn't capable of > >

[PATCH] nouveau/gsp: Avoid addressing beyond end of rpc->entries

Using the end of rpc->entries[] for addressing runs into both compile-time and run-time detection of accessing beyond the end of the array. Use the base pointer instead, since was allocated with the additional bytes for storing the strings. Avoids the following warning in future GCC releases with

Re: [PATCH 1/4] dt-bindings: display/msm: sm8150-mdss: add DP node

On 27/03/2024 11:11, Krzysztof Kozlowski wrote: > On 26/03/2024 21:02, Dmitry Baryshkov wrote: >> As Qualcomm SM8150 got support for the DisplayPort, add displayport@ >> node as a valid child to the MDSS node. >> >> Signed-off-by: Dmitry Baryshkov >> --- > > Reviewed-by: Krzysztof Kozlowski If

Re: [PATCH v2 2/3] dt-bindings: display: msm: sm6350-mdss: document DP controller subnode

On 29/03/2024 08:45, Luca Weiss wrote: > Document the displayport controller subnode of the SM6350 MDSS. > > Signed-off-by: Luca Weiss > --- Reviewed-by: Krzysztof Kozlowski Best regards, Krzysztof

Re: [PATCH] drm/msm/dpu: make error messages at dpu_core_irq_register_callback() more sensible

> - DPU_ERROR("invalid IRQ=[%d, %d]\n", > - DPU_IRQ_REG(irq_idx), DPU_IRQ_BIT(irq_idx)); > + DPU_ERROR("invalid IRQ=[%d, %d] irq_cb:%ps\n", > + DPU_IRQ_REG(irq_idx), DPU_IRQ_BIT(irq_idx), irq_cb); >

Re: [PATCH 3/3] drm: panel: Add LG sw43408 panel driver

On 2024-03-30 05:59:30, Dmitry Baryshkov wrote: > From: Sumit Semwal > > LG SW43408 is 1080x2160, 4-lane MIPI-DSI panel, used in some Pixel3 > phones. > > Whatever init sequence we have for this panel isn't capable of > initialising it completely, toggling the reset gpio ever causes the > panel

Patch "fbdev: Select I/O-memory framebuffer ops for SBus" has been added to the 6.8-stable tree

This is a note to let you know that I've just added the patch titled fbdev: Select I/O-memory framebuffer ops for SBus to the 6.8-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is:

Re: [PATCH v3 8/9] dt-bindings: xlnx: Add VTC and TPG bindings

On 30/03/2024 03:02, Klymenko, Anatoliy wrote: >>> >>> Sorry, I didn't explain properly what I'm trying to achieve. I need to >>> create a DT node property that represents video signal format, one of >>> MEDIA_BUS_FMT_* from include/uapi/linux/media-bus-format.h. It would >> be >>> nice to

Re: [PATCH 1/3] dt-bindings: panel: Add LG SW43408 MIPI-DSI panel

On 30/03/2024 04:59, Dmitry Baryshkov wrote: > From: Sumit Semwal > > LG SW43408 is 1080x2160, 4-lane MIPI-DSI panel present on Google Pixel 3 > phones. ... Few nits, which could be ignored, and one thing which is blocking - missing example. > + > +maintainers: > + - Caleb Connolly > + >