Re: [PATCH] fbdev: Delay the setting of fbcon_ops to fix KASAN issues

2025-09-21 Thread Thomas Zimmermann
Hi Am 05.09.25 um 04:43 schrieb Zizhi Wo: [BUG] Recently, we encountered a KASAN warning as follows: kasan_report+0xaf/0xe0 mm/kasan/report.c:588 fb_pad_aligned_buffer+0x12f/0x150 drivers/video/fbdev/core/fbmem.c:116 ccw_putcs_aligned drivers/video/fbdev/core/fbcon_ccw.c:119 [inline] ccw_putcs+

Re: [PATCH v2 16/23] staging: media: tegra-video: tegra20: simplify format align calculations

2025-09-21 Thread Svyatoslav Ryhel
пн, 22 вер. 2025 р. о 09:23 Mikko Perttunen пише: > > On Monday, September 22, 2025 2:13 PM Svyatoslav Ryhel wrote: > > пн, 22 вер. 2025 р. о 07:44 Mikko Perttunen пише: > > > > > > On Saturday, September 6, 2025 10:53 PM Svyatoslav Ryhel wrote: > > > > Simplify format align calculations by sligh

Re: [PATCH] fbcon: fix integer overflow in fbcon_do_set_font

2025-09-21 Thread Thomas Zimmermann
Am 12.09.25 um 19:00 schrieb Samasth Norway Ananda: Fix integer overflow vulnerabilities in fbcon_do_set_font() where font size calculations could overflow when handling user-controlled font parameters. The vulnerabilities occur when: 1. CALC_FONTSZ(h, pitch, charcount) performs h * pith * ch

Re: [PATCH v2 18/23] staging: media: tegra-video: tegra20: increase maximum VI clock frequency

2025-09-21 Thread Mikko Perttunen
On Monday, September 22, 2025 1:58 PM Svyatoslav Ryhel wrote: > пн, 22 вер. 2025 р. о 07:54 Mikko Perttunen пише: > > > > On Saturday, September 6, 2025 10:53 PM Svyatoslav Ryhel wrote: > > > Increase maximum VI clock frequency to 450MHz to allow correct work with > > > high resolution camera sens

Re: [PATCH v2 23/23] staging: media: tegra-video: add CSI support for Tegra20 and Tegra30

2025-09-21 Thread Svyatoslav Ryhel
пн, 22 вер. 2025 р. о 08:16 Mikko Perttunen пише: > > On Saturday, September 6, 2025 10:53 PM Svyatoslav Ryhel wrote: > > Add support for MIPI CSI device and calibration logic found in Tegra20 and > > Tegra30 SoC. > > The patch is on the longer side. I'd add some more explanation in the commit >

Re: [PATCH v2 23/23] staging: media: tegra-video: add CSI support for Tegra20 and Tegra30

2025-09-21 Thread Mikko Perttunen
On Monday, September 22, 2025 2:19 PM Svyatoslav Ryhel wrote: > пн, 22 вер. 2025 р. о 08:16 Mikko Perttunen пише: > > > > On Saturday, September 6, 2025 10:53 PM Svyatoslav Ryhel wrote: > > > Add support for MIPI CSI device and calibration logic found in Tegra20 and > > > Tegra30 SoC. > > > > The

Re: [PATCH v2 23/23] staging: media: tegra-video: add CSI support for Tegra20 and Tegra30

2025-09-21 Thread Svyatoslav Ryhel
пн, 22 вер. 2025 р. о 08:16 Mikko Perttunen пише: > > On Saturday, September 6, 2025 10:53 PM Svyatoslav Ryhel wrote: > > Add support for MIPI CSI device and calibration logic found in Tegra20 and > > Tegra30 SoC. > > The patch is on the longer side. I'd add some more explanation in the commit >

Re: [PATCH v2 16/23] staging: media: tegra-video: tegra20: simplify format align calculations

2025-09-21 Thread Svyatoslav Ryhel
пн, 22 вер. 2025 р. о 07:44 Mikko Perttunen пише: > > On Saturday, September 6, 2025 10:53 PM Svyatoslav Ryhel wrote: > > Simplify format align calculations by slightly modifying supported formats > > structure. > > > > Signed-off-by: Svyatoslav Ryhel > > --- > > drivers/staging/media/tegra-vide

Re: [PATCH v2 19/23] staging: media: tegra-video: tegra20: expand format support with RAW8/10 and YUV422 1X16

2025-09-21 Thread Mikko Perttunen
On Saturday, September 6, 2025 10:53 PM Svyatoslav Ryhel wrote: > Add support for Bayer formats (RAW8 and RAW10) and YUV422_8 1X16 versions > of existing YUV422_8 2X8. > > Signed-off-by: Svyatoslav Ryhel > --- > drivers/staging/media/tegra-video/tegra20.c | 72 - > 1 file cha

Re: [PATCH v2 18/23] staging: media: tegra-video: tegra20: increase maximum VI clock frequency

2025-09-21 Thread Svyatoslav Ryhel
пн, 22 вер. 2025 р. о 07:54 Mikko Perttunen пише: > > On Saturday, September 6, 2025 10:53 PM Svyatoslav Ryhel wrote: > > Increase maximum VI clock frequency to 450MHz to allow correct work with > > high resolution camera sensors. > > > > Signed-off-by: Svyatoslav Ryhel > > --- > > drivers/stagi

Re: [PATCH v2 16/23] staging: media: tegra-video: tegra20: simplify format align calculations

2025-09-21 Thread Mikko Perttunen
On Saturday, September 6, 2025 10:53 PM Svyatoslav Ryhel wrote: > Simplify format align calculations by slightly modifying supported formats > structure. > > Signed-off-by: Svyatoslav Ryhel > --- > drivers/staging/media/tegra-video/tegra20.c | 41 - > 1 file changed, 16 inser

Re: [PATCH v2 15/23] staging: media: tegra-video: tegra20: add support for second output of VI

2025-09-21 Thread Mikko Perttunen
On Saturday, September 6, 2025 10:53 PM Svyatoslav Ryhel wrote: > VI in Tegra20/Tegra30 has 2 VI outputs with different set of supported > formats. Convert output registers to macros for simpler work with both > outputs since apart formats their layout matches. > > Signed-off-by: Svyatoslav Ryhel

Re: [PATCH 05/14] drm/imx: dc-crtc: Disable at boot

2025-09-21 Thread Liu Ying
On 09/19/2025, Frank Li wrote: > On Fri, Jul 04, 2025 at 05:03:52PM +0800, Liu Ying wrote: >> CRTC(s) could still be running after the DRM device is unplugged by >> calling drm_dev_unplug(), because the CRTC disablement logic is >> protected and bypassed by the drm_dev_enter()/drm_dev_exit() pair.

[syzbot] [fbdev?] KASAN: slab-out-of-bounds Read in fb_pad_unaligned_buffer (4)

2025-09-21 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:b320789d6883 Linux 6.17-rc4 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=16ceae6258 kernel config: https://syzkaller.appspot.com/x/.config?x=d4703ac89d9e185a dashboard link: https://syzkaller.ap

Re: [PATCH v2 13/23] staging: media: tegra-video: csi: move avdd-dsi-csi-supply from VI to CSI

2025-09-21 Thread Mikko Perttunen
On Saturday, September 6, 2025 10:53 PM Svyatoslav Ryhel wrote: > The avdd-dsi-csi-supply is CSI power supply not VI, hence move it to > proper place. > > Signed-off-by: Svyatoslav Ryhel > --- > drivers/staging/media/tegra-video/csi.c | 19 ++- > drivers/staging/media/tegra-video

Re: [PATCH 07/14] drm/imx: dc: Add DPR channel support

2025-09-21 Thread Liu Ying
On 09/19/2025, Frank Li wrote: > On Fri, Jul 04, 2025 at 05:03:54PM +0800, Liu Ying wrote: >> Display Prefetch Resolve Channel(DPRC) is a part of a prefetch engine. >> It fetches display data, transforms it to linear format and stores it >> to DPRC's RTRAM. PRG, as the other part of a prefetch eng

[PATCH v6 drm-dp 0/4] Fix hibmc driver bugs

2025-09-21 Thread Yongbang Shi
From: Baihan Li There are some bugfix for hibmc-drm driver. --- ChangeLog: v5 -> v6: - use HPD status in DP detect_ctx(), suggested by Dmitry Baryshkov. v4 -> v5: - Because some of patches are applied, this series only contains the rest of them. - fix the commit and DP detect_ctx(), sugges

Re: [PATCH 14/14] drm/imx: dc: Use prefetch engine

2025-09-21 Thread Liu Ying
On 09/19/2025, Frank Li wrote: > On Fri, Jul 04, 2025 at 05:04:01PM +0800, Liu Ying wrote: >> One prefetch engine consists of one DPR channel and one or two PRGs. >> Each PRG handles one planar in a pixel format. Every FetchUnit used >> by KMS may attach to a PRG and hence use a prefetch engine.

Re: [PATCH 08/14] drm/imx: dc: Use TCON operation mode

2025-09-21 Thread Liu Ying
On 09/19/2025, Frank Li wrote: > On Fri, Jul 04, 2025 at 05:03:55PM +0800, Liu Ying wrote: >> In TCON operation mode, sync signals from FrameGen are ignored, but >> a much more customized output timing can be generated by the TCON >> module. By using TCON operaton mode, generate KACHUNK signal alo

Re: [PATCH v5 4/7] drm/bridge: dw-hdmi: Add API dw_hdmi_set_sample_iec958() for iec958 format

2025-09-21 Thread Liu Ying
On 09/10/2025, Shengjiu Wang wrote: > Hi > > On Tue, Sep 9, 2025 at 2:39 PM Maxime Ripard wrote: >> >> Hi, >> >> On Wed, Sep 03, 2025 at 06:41:05PM +0800, Shengjiu Wang wrote: >>> On Tue, Sep 2, 2025 at 12:52 AM Luca Ceresoli >>> wrote: Hello Shengjiu, On Thu, 21 Aug 2025 15

[PATCH v6 drm-dp 3/4] drm/hisilicon/hibmc: fix no showing problem with loading hibmc manually

2025-09-21 Thread Yongbang Shi
From: Baihan Li When using command rmmod and insmod, there is no showing in second time insmoding. Because DP controller won't send HPD signals, if connection doesn't change or controller isn't reset. So add reset before unreset in hibmc_dp_hw_init(). And also need to move the HDCP cfg after DP

[PATCH v6 drm-dp 4/4] drm/hisilicon/hibmc: Adding reset colorbar cfg in dp init.

2025-09-21 Thread Yongbang Shi
From: Baihan Li Add colorbar disable operation before reset chontroller, to make sure colorbar status is clear in the DP init, so if rmmod the driver and the previous colorbar configuration will not affect the next time insmod the driver. Fixes: 3c7623fb5bb6 ("drm/hisilicon/hibmc: Enable this ho

[PATCH v6 drm-dp 2/4] drm/hisilicon/hibmc: add dp mode valid check

2025-09-21 Thread Yongbang Shi
From: Baihan Li If DP is connected, check the DP BW in mode_valid_ctx() to ensure that DP's link rate supports high-resolution data transmission. Fixes: 0ab6ea261c1f ("drm/hisilicon/hibmc: add dp module in hibmc") Signed-off-by: Baihan Li Signed-off-by: Yongbang Shi Reviewed-by: Dmitry Baryshk

[PATCH v6 drm-dp 1/4] drm/hisilicon/hibmc: fix dp probabilistical detect errors after HPD irq

2025-09-21 Thread Yongbang Shi
From: Baihan Li The issue is that drm_connector_helper_detect_from_ddc() returns wrong status when plugging or unplugging the monitor. Use HPD pin status in DP's detect_ctx() for real physcal monitor in/out, and keep using detect_frome_ddc() if it's the first time to call detect because of insmod

[PATCH v4 0/7] Add Type-C DP support for RK3399 EVB IND board

2025-09-21 Thread Chaoyi Chen
From: Chaoyi Chen This series focuses on adding Type-C DP support for USBDP PHY and DP driver. The USBDP PHY and DP will perceive the changes in cable status based on the USB PD and Type-C state machines provided by TCPM. Before this, the USBDP PHY and DP controller of RK3399 sensed cable state c

[PATCH v4 6/7] arm64: dts: rockchip: Add missing dp_out port for RK3399 CDN-DP

2025-09-21 Thread Chaoyi Chen
From: Chaoyi Chen Let's make the ports nodes of cdn_dp in the same style as the other display interface, and match the style of ports's yaml. Signed-off-by: Chaoyi Chen --- Changes in v4: - Remove unnecessary #address/#size-cells (no changes since v1) arch/arm64/boot/dts/rockchip/rk3399-bas

[PATCH v4 5/7] drm/rockchip: cdn-dp: Add multiple bridges to support PHY port selection

2025-09-21 Thread Chaoyi Chen
From: Chaoyi Chen The RK3399 has two USB/DP combo PHY and one CDN-DP controller. And the CDN-DP can be switched to output to one of the PHYs. If both ports are plugged into DP, DP will select the first port for output. This patch adds support for multiple bridges, enabling users to flexibly sele

[PATCH v4 4/7] drm/rockchip: cdn-dp: Support handle lane info without extcon

2025-09-21 Thread Chaoyi Chen
From: Chaoyi Chen This patch add support for get PHY lane info without help of extcon. There is no extcon needed if the Type-C controller is present. In this case, the lane info can be get from PHY instead of extcon. The extcon device should still be supported if Type-C controller is not presen

[PATCH v4 2/7] dt-bindings: phy: rockchip: rk3399-typec-phy: Support mode-switch

2025-09-21 Thread Chaoyi Chen
From: Chaoyi Chen The RK3399 SoC integrates two USB/DP combo PHYs, each of which supports software-configurable pin mapping and DisplayPort lane assignment. These capabilities enable the PHY itself to handle both mode switching and orientation switching, based on the Type-C plug orientation and U

[PATCH v4 1/7] usb: typec: Add default HPD device when register DisplayPort altmode

2025-09-21 Thread Chaoyi Chen
From: Chaoyi Chen Add default DRM AUX HPD bridge device when register DisplayPort altmode. That makes it redundant for each Type-C driver to implement a similar registration process in embedded scenarios. Signed-off-by: Chaoyi Chen --- drivers/usb/typec/altmodes/displayport.c | 27

[PATCH v4 7/7] arm64: dts: rockchip: rk3399-evb-ind: Add support for DisplayPort

2025-09-21 Thread Chaoyi Chen
From: Chaoyi Chen The RK3399 EVB IND board has a Type-C interface DisplayPort. It use fusb302 chip as Type-C controller. fusb302 chip ---> USB/DP PHY0 <> CDN-DP controller Signed-off-by: Chaoyi Chen --- (no changes since v4) Changes in v3: - Fix wrong vdo value. - Fix port node in usb-c-

[PATCH 3/4] drm/mipi-dsi: remove deprecated mipi_dsi_dcs_write_buffer_chatty

2025-09-21 Thread rtapadia730
From: Rajeev Tapadia The mipi_dsi_dcs_write_buffer_chatty() helper is redundant and non-intuitive. It has been removed in favour of mipi_dsi_dcs_write_buffer_multi(), which handles multiple DSI writes with proper error accumulation. Signed-off-by: Rajeev Tapadia --- drivers/gpu/drm/drm_mipi_ds

Re: [PATCH v2 1/4] clk: tegra20: reparent dsi clock to pll_d_out0

2025-09-21 Thread Stephen Boyd
Quoting Svyatoslav Ryhel (2025-09-06 06:16:52) > Reparent DSI clock to PLLD_OUT0 instead of directly descend from PLLD. > > Signed-off-by: Svyatoslav Ryhel > --- Acked-by: Stephen Boyd

Re: [PATCH v2 19/20] clk: sp7021: switch to FIELD_PREP_WM16 macro

2025-09-21 Thread Stephen Boyd
Quoting Nicolas Frattaroli (2025-06-23 09:05:47) > The sp7021 clock driver has its own shifted high word mask macro, > similar to the ones many Rockchip drivers have. > > Remove it, and replace instances of it with hw_bitfield.h's > FIELD_PREP_WM16 macro, which does the same thing except in a comm

Re: [PATCH 00/27 5.10.y] Backport minmax.h updates from v6.17-rc6

2025-09-21 Thread Greg KH
On Fri, Sep 19, 2025 at 10:17:00AM +, Eliav Farber wrote: > This series includes a total of 27 patches, to align minmax.h of > v5.15.y with v6.17-rc6. > > The set consists of 24 commits that directly update minmax.h: > 1) 92d23c6e9415 ("overflow, tracing: Define the is_signed_type() macro >

[PATCH v2 1/8] dt-bindings: vendor-prefixes: add verisilicon

2025-09-21 Thread Icenowy Zheng
VeriSilicon is a Silicon IP vendor, which is the current owner of Vivante series video-related IPs and Hantro series video codec IPs. Add a vendor prefix for this company. Signed-off-by: Icenowy Zheng --- No changes in v2. Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++ 1 file c

Re: [PATCH v2 3/5] clk: bcm: rpi: Maximize V3D clock

2025-09-21 Thread Stephen Boyd
Quoting Maíra Canal (2025-07-31 14:06:19) > Although minimizing the clock rate is the best for most scenarios, as > stated in commit 4d85abb0fb8e ("clk: bcm: rpi: Enable minimize for all > firmware clocks"), when it comes to the GPU, it's ideal to have the > maximum rate allowed. > > Add an option

Re: [PATCH v2 2/5] clk: bcm: rpi: Turn firmware clock on/off when preparing/unpreparing

2025-09-21 Thread Stephen Boyd
Quoting Maíra Canal (2025-07-31 14:06:18) > Currently, when we prepare or unprepare RPi's clocks, we don't actually > enable/disable the firmware clock. This means that > `clk_disable_unprepare()` doesn't actually change the clock state at > all, nor does it lowers the clock rate. > > From the Mai

Re: [PATCH v2 1/5] clk: bcm: rpi: Add missing logs if firmware fails

2025-09-21 Thread Stephen Boyd
Quoting Maíra Canal (2025-07-31 14:06:17) > From: Stefan Wahren > > In contrary to raspberrypi_fw_set_rate(), the ops for is_prepared() and > recalc_rate() silently ignore firmware errors by just returning 0. > Since these operations should never fail, add at least error logs > to inform the user

Re: [PATCH 25/37] clk: clk-apple-nco: Add "apple, t8103-nco" compatible

2025-09-21 Thread Stephen Boyd
Quoting Janne Grunau (2025-08-28 07:01:44) > After discussion with the devicetree maintainers we agreed to not extend > lists with the generic compatible "apple,nco" anymore [1]. Use > "apple,t8103-nco" as base compatible as it is the SoC the driver and > bindings were written for. > > [1]: > htt

Re: [PATCH 26/37] dt-bindings: clock: apple, nco: Add t6020-nco compatible

2025-09-21 Thread Stephen Boyd
Quoting Janne Grunau (2025-08-28 07:01:45) > After discussion with the devicetree maintainers we agreed to not extend > lists with the generic compatible "apple,nco" anymore [1]. Use > "apple,t8103-nco" as base compatible as it is the SoC the driver and > bindings were written for. > > The block f

[PATCH] drm/amdgpu: remove leading space before square bracket

2025-09-21 Thread Shreyas Muppana
remove a space before an open square bracket, fixes a linter error Signed-off-by: Shreyas Muppana --- drivers/gpu/drm/amd/amdgpu/amdgpu_aca.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_aca.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_aca.c ind

[PATCH RESEND v4 1/3] dt-bindings: lcdif: Document a imx6sx-lcdif fallback

2025-09-21 Thread Fabio Estevam
imx6sx.dtsi has the following lcdif entries: compatible = "fsl,imx6sx-lcdif", "fsl,imx28-lcdif"; This causes the following dt-schema warning: ['fsl,imx6sx-lcdif', 'fsl,imx28-lcdif'] is too long To keep DT compatibility, document 'fsl,imx28-lcdif' as a possible 'fsl,imx6sx-lcdif' fallback. Sign

[v6 01/15] mm/zone_device: support large zone device private folios

2025-09-21 Thread Balbir Singh
Add routines to support allocation of large order zone device folios and helper functions for zone device folios, to check if a folio is device private and helpers for setting zone device data. When large folios are used, the existing page_free() callback in pgmap is called when the folio is freed

[PATCH v3 24/39] drm/mediatek: Switch to drm_atomic_get_new_crtc_state()

2025-09-21 Thread Maxime Ripard
The mediatek atomic_check implementation uses the deprecated drm_atomic_get_existing_crtc_state() helper. This hook is called as part of the global atomic_check, thus before the states are swapped. The existing state thus points to the new state, and we can use drm_atomic_get_new_crtc_state() inst

Re: [PATCH v4 1/6] nova-core: bitfield: Move bitfield-specific code from register! into new macro

2025-09-21 Thread Danilo Krummrich
On Sun Sep 21, 2025 at 11:36 AM CEST, Greg KH wrote: > Your example code using this is nice, and it shows how to set up, and > query these bits, but that's not anything anyone actually does in the > kernel, what they want to do is read/write from hardware with this. > > So, how does that work? Whe

Re: [PATCH v4 1/6] nova-core: bitfield: Move bitfield-specific code from register! into new macro

2025-09-21 Thread Danilo Krummrich
On Sun Sep 21, 2025 at 2:45 PM CEST, Greg KH wrote: > Again, regmap handles this all just fine, why not just make bindings to > that api here instead? The idea is to use this for the register!() macro, e.g. register!(NV_PMC_BOOT_0 @ 0x, "Basic revision information about the GPU"

[PATCH v2 2/8] dt-bindings: display: add verisilicon,dc

2025-09-21 Thread Icenowy Zheng
Verisilicon has a series of display controllers prefixed with DC and with self-identification facility like their GC series GPUs. Add a device tree binding for it. Depends on the specific DC model, it can have either one or two display outputs, and each display output could be set to DPI signal o

Re: [PATCH v4 1/6] nova-core: bitfield: Move bitfield-specific code from register! into new macro

2025-09-21 Thread Greg KH
On Sun, Sep 21, 2025 at 02:33:56PM +0200, Benno Lossin wrote: > On Sun Sep 21, 2025 at 11:36 AM CEST, Greg KH wrote: > > On Sat, Sep 20, 2025 at 02:22:27PM -0400, Joel Fernandes wrote: > >> The bitfield-specific into new macro. This will be used to define > >> structs with bitfields, similar to C l

Re: [PATCH v4 1/6] nova-core: bitfield: Move bitfield-specific code from register! into new macro

2025-09-21 Thread Benno Lossin
On Sun Sep 21, 2025 at 11:36 AM CEST, Greg KH wrote: > On Sat, Sep 20, 2025 at 02:22:27PM -0400, Joel Fernandes wrote: >> The bitfield-specific into new macro. This will be used to define >> structs with bitfields, similar to C language. >> >> Reviewed-by: Elle Rhumsaa >> Signed-off-by: Joel Fern

Re: [PATCH v3 5/5] rust: Add KUNIT tests for bitfield

2025-09-21 Thread Miguel Ojeda
On Sat, Sep 20, 2025 at 2:39 AM Joel Fernandes wrote: > > The C checks use BUILD_BUG_ON, in rust-for-linux we have build_assert but it > is fragile and depends on the value being a constant. What do you mean? `build_assert!` works essentially like `BUILD_BUG_ON`, i.e. after the optimizer, and do

Re: [PATCH v4 1/6] nova-core: bitfield: Move bitfield-specific code from register! into new macro

2025-09-21 Thread Greg KH
On Sun, Sep 21, 2025 at 11:59:05AM +0200, Miguel Ojeda wrote: > On Sun, Sep 21, 2025 at 11:36 AM Greg KH wrote: > > > > And where does this allow us to define things like BIT(2) for values? > > (ok, that's kind of not the point of this patch series, but it will come > > up over time...) > > We ha

Re: [PATCH v4 1/6] nova-core: bitfield: Move bitfield-specific code from register! into new macro

2025-09-21 Thread Miguel Ojeda
On Sun, Sep 21, 2025 at 11:36 AM Greg KH wrote: > > And where does this allow us to define things like BIT(2) for values? > (ok, that's kind of not the point of this patch series, but it will come > up over time...) We have the `bits` module since 6.17: https://rust.docs.kernel.org/kernel/bi

[PATCH v2 5/8] drm/bridge: add a driver for T-Head TH1520 HDMI controller

2025-09-21 Thread Icenowy Zheng
T-Head TH1520 SoC contains a Synopsys DesignWare HDMI controller (paired with DesignWare HDMI TX PHY Gen2) that takes the "DP" output from the display controller. Add a driver for this controller utilizing the common DesignWare HDMI code in the kernel. Signed-off-by: Icenowy Zheng --- Changes in

Re: [PATCH v4 1/6] nova-core: bitfield: Move bitfield-specific code from register! into new macro

2025-09-21 Thread Greg KH
On Sat, Sep 20, 2025 at 02:22:27PM -0400, Joel Fernandes wrote: > The bitfield-specific into new macro. This will be used to define > structs with bitfields, similar to C language. > > Reviewed-by: Elle Rhumsaa > Signed-off-by: Joel Fernandes > --- > drivers/gpu/nova-core/bitfield.rs| 314 +

[PATCH v2 4/8] dt-bindings: display/bridge: add binding for TH1520 HDMI controller

2025-09-21 Thread Icenowy Zheng
T-Head TH1520 SoC contains a Synopsys DesignWare HDMI controller paired with DesignWare HDMI PHY, with an extra clock gate for HDMI pixel clock and two reset controls. Add a device tree binding to it. Signed-off-by: Icenowy Zheng Reviewed-by: Krzysztof Kozlowski --- Changes in v2: - Re-aligned

[PATCH v2 6/8] riscv: dts: thead: add DPU and HDMI device tree nodes

2025-09-21 Thread Icenowy Zheng
T-Head TH1520 SoC contains a Verisilicon DC8200 display controller (called DPU in manual) and a Synopsys DesignWare HDMI TX controller. Add device tree nodes to them. Signed-off-by: Icenowy Zheng --- No changes in v2. arch/riscv/boot/dts/thead/th1520.dtsi | 70 +++ 1 fi

[PATCH v2 0/8] Verisilicon DC8200 driver (and adaption to TH1520)

2025-09-21 Thread Icenowy Zheng
This patchset tries to add a driver for Verisilicon DC8200 driver, and demonstrates the driver on T-Head TH1520 with its HDMI output. This display controller IP is used on StarFive JH7110 too, but as the HDMI controller used there isn't as common as the DesignWare one, I choose to use TH1520 in th

[PATCH v2 7/8] riscv: dts: thead: lichee-pi-4a: enable HDMI

2025-09-21 Thread Icenowy Zheng
Lichee Pi 4A board features a HDMI Type-A connector connected to the HDMI TX controller of TH1520 SoC. Add a device tree node describing the connector, connect it to the HDMI controller, and enable everything on this display pipeline. Signed-off-by: Icenowy Zheng --- No changes in v2. .../boot

[PATCH v2 8/8] MAINTAINERS: assign myself as maintainer for verisilicon DC driver

2025-09-21 Thread Icenowy Zheng
As I am the author of this rewritten driver, it makes sense for me to be the maintainer. Confirm this in MAINTAINERS file. Signed-off-by: Icenowy Zheng --- No changes in v2. MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 98af9dd3664f5..34

[PATCH v2 3/8] drm: verisilicon: add a driver for Verisilicon display controllers

2025-09-21 Thread Icenowy Zheng
This is a from-scratch driver targeting Verisilicon DC-series display controllers, which feature self-identification functionality like their GC-series GPUs. Only DC8200 is being supported now, and only the main framebuffer is set up (as the DRM primary plane). Support for more DC models and more

[PATCH v2 2/2] drm: renesas: rz-du: Set DSI divider based on target MIPI device

2025-09-21 Thread Chris Brandt
Before the MIPI DSI clock source can be configured, the target divide ratio needs to be known. Signed-off-by: Chris Brandt --- v1->v2: - Add spaces around '/' in comments - Add target argument in new API --- drivers/gpu/drm/renesas/rz-du/rzg2l_mipi_dsi.c | 18 ++ 1 file changed,