[PATCH 2/2] iio: dac: Fix dependencies of AD9739A

2024-06-15 Thread Alexey Makhalov
0-DAY CI Kernel Test automation reported an issue: ld: drivers/base/regmap/regmap-spi.o: in function `regmap_spi_read': regmap-spi.c:(.text+0xf): undefined reference to `spi_write_then_read' ld: drivers/base/regmap/regmap-spi.o: in function `regmap_spi_gather_write': regmap-spi.c:(.tex

[PATCH 1/2] drm/vmwgfx: Fix missing HYPERVISOR_GUEST dependency

2024-06-15 Thread Alexey Makhalov
VMWARE_HYPERCALL alternative will not work as intended without VMware guest code initialization. Reported-by: kernel test robot Closes: https://lore.kernel.org/oe-kbuild-all/202406152104.fxakp1mb-...@intel.com/ Signed-off-by: Alexey Makhalov --- drivers/gpu/drm/vmwgfx/Kconfig | 2 +- 1 file ch

Re: [PATCH 09/15] net: hbl_en: add habanalabs Ethernet driver

2024-06-15 Thread Andrew Lunn
> > +static void hbl_en_reset_stats(struct hbl_aux_dev *aux_dev, u32 port_idx) > > +{ > > + struct hbl_en_port *port = HBL_EN_PORT(aux_dev, port_idx); > > + > > + port->net_stats.rx_packets = 0; > > + port->net_stats.tx_packets = 0; > > + port->net_stats.rx_bytes = 0; > > + port->net_stat

Re: [PATCH 09/15] net: hbl_en: add habanalabs Ethernet driver

2024-06-15 Thread Andrew Lunn
On Fri, Jun 14, 2024 at 03:48:43PM -0700, Joe Damato wrote: > On Thu, Jun 13, 2024 at 11:22:02AM +0300, Omer Shpigelman wrote: > > This ethernet driver is initialized via auxiliary bus by the hbl_cn > > driver. > > It serves mainly for control operations that are needed for AI scaling. > > > > Sig

Re: [PATCH 06/13] drm/rockchip: dw_hdmi: Add max_tmds_clock validation

2024-06-15 Thread Jonas Karlman
Hi Diederik, On 2024-06-15 23:53, Diederik de Haas wrote: > On Saturday, 15 June 2024 19:03:57 CEST Jonas Karlman wrote: >> The rate limit for RK3288, RK3399 and RK3568 is based on current mpll >> table. The rate limit for RK3228 and RK3228 is based on the >> inno-hdmi-phy pre-pll table. > > I se

Re: [PATCH 06/13] drm/rockchip: dw_hdmi: Add max_tmds_clock validation

2024-06-15 Thread Diederik de Haas
On Saturday, 15 June 2024 19:03:57 CEST Jonas Karlman wrote: > The rate limit for RK3288, RK3399 and RK3568 is based on current mpll > table. The rate limit for RK3228 and RK3228 is based on the > inno-hdmi-phy pre-pll table. I see RK3228 mentioned twice; I guess the second should be RK3328? sign

Re: [PATCH v8 14/16] drm/mediatek: Support CRC in display driver

2024-06-15 Thread kernel test robot
rnel.org/r/20240606092635.27981-15-shawn.sung%40mediatek.com patch subject: [PATCH v8 14/16] drm/mediatek: Support CRC in display driver config: arm64-randconfig-r113-20240615 (https://download.01.org/0day-ci/archive/20240616/202406160407.yfz2cnh2-...@intel.com/config) compiler: aarch64-linu

[PATCH] agp: uninorth: add missing MODULE_DESCRIPTION() macro

2024-06-15 Thread Jeff Johnson
t;\t\tDefault: " DEFAULT_APERTURE_STRING "M"); MODULE_AUTHOR("Ben Herrenschmidt & Paul Mackerras"); +MODULE_DESCRIPTION("Apple UniNorth & U3 AGP support"); MODULE_LICENSE("GPL"); --- base-commit: 83a7eefedc9b56fe7bfeff13b6c7356688ffa670 change-id: 20240615-md-powerpc-drivers-char-agp-db644db58c24

[Bug 206309] Experimental amdgpu w/ Dell E6540 with HD 8790M (MARS XTX), massive performance improvement after ACPI suspend

2024-06-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206309 --- Comment #4 from jerbear3.14...@gmail.com --- Thanks for the quick reply. Guess I'll have to dust off ye ol' Windows installer and confirm once and for all who's to blame here. I'll post my findings here probably in a few weeks when I can. Than

[Bug 206309] Experimental amdgpu w/ Dell E6540 with HD 8790M (MARS XTX), massive performance improvement after ACPI suspend

2024-06-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206309 Travis Juntara (changhaitra...@gmail.com) changed: What|Removed |Added Status|NEW |RESOLVED

[PATCH RFC 5/5] drm/bridge: lt9611: switch to using the DRM HDMI codec framework

2024-06-15 Thread Dmitry Baryshkov
Make the Lontium LT9611 DSI-to-HDMI bridge driver use the DRM HDMI Codec framework. This enables programming of Audio InfoFrames using the HDMI Connector interface and also enables support for the missing features, including the ELD retrieval and better hotplug support. Signed-off-by: Dmitry Barys

[PATCH RFC 3/5] drm/connector: implement generic HDMI codec helpers

2024-06-15 Thread Dmitry Baryshkov
Several DRM drivers implement HDMI codec support (despite its name it applies to both HDMI and DisplayPort drivers). Implement generic framework to be used by these drivers. This removes a requirement to implement get_eld() callback and provides default implementation for codec's plug handling. Th

[PATCH RFC 2/5] ASoC: hdmi-codec: pass data to get_dai_id too

2024-06-15 Thread Dmitry Baryshkov
The upcoming DRM connector HDMI codec implementation is going to use codec-specific data in the .get_dai_id to get drm_connector. Pass data to the callback, as it is done with other hdmi_codec_ops callbacks. Signed-off-by: Dmitry Baryshkov --- drivers/gpu/drm/bridge/adv7511/adv7511_audio.c

[PATCH RFC 4/5] drm/bridge: connector: add support for HDMI codec framework

2024-06-15 Thread Dmitry Baryshkov
Add necessary glue code to be able to use new HDMI codec framework from the DRM bridge drivers. The drm_bridge implements a limited set of the hdmi_codec_ops interface, with the functions accepting both drm_connector and drm_bridge instead of just a generic void pointer. This framework is integrat

[PATCH RFC 1/5] drm/bridge: lt9611: use HDMI Connector helper to set InfoFrames

2024-06-15 Thread Dmitry Baryshkov
Use new HDMI Connector helpers in the Lontium LT9611 bridge driver. Program InfoFrames using the helper's callbacks. Also use TMDS char rate validation callback to filter out modes, instead of hardcoding 4k@30. The Audio InfoFrame isn't yet handled by these helpers, it requires additional drm_brid

[PATCH RFC 0/5] drm: add DRM HDMI Codec framework

2024-06-15 Thread Dmitry Baryshkov
While porting lt9611 DSI-to-HDMI bridge driver to use HDMI Connector framework, I stumbled upon an issue while handling the Audio InfoFrames. The HDMI codec callbacks weren't receiving the drm_atomic_state, so there was no simple way to get the drm_connector that stayed at the end of the bridge cha

[PATCH 08/13] drm/rockchip: dw_hdmi: Adjust cklvl & txlvl for RF/EMI

2024-06-15 Thread Jonas Karlman
From: Yakir Yang Dut to the high HDMI signal voltage driver, Mickey have meet a serious RF/EMI problem, so we decided to reduce HDMI signal voltage to a proper value. The default params for phy is cklvl = 20 & txlvl = 13 (RF/EMI failed) ck: lvl = 13, term=100, vlo = 2.71, vhi=3.14, vswing = 0.

[PATCH 07/13] drm/rockchip: dw_hdmi: Filter modes based on hdmiphy_clk

2024-06-15 Thread Jonas Karlman
RK3228 and RK3328 clock rate is being validated against a mpll config table intended for Synopsys phy, and not the inno-hdmi-phy used. Instead get a reference to the hdmiphy clk and validate rates against it to enable use of HDMI2.0 modes, e.g. 4K@60Hz, on RK3228 and RK3328. For Synopsis phy the

[PATCH 09/13] drm/rockchip: dw_hdmi: Add phy_config for 594Mhz pixel clock

2024-06-15 Thread Jonas Karlman
From: Nickey Yang Add phy_config for 594Mhz pixel clock used for HDMI2.0 display modes. Signed-off-by: Nickey Yang Signed-off-by: Jonas Karlman --- drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c b/dr

[PATCH 13/13] drm/rockchip: Load crtc devices in preferred order

2024-06-15 Thread Jonas Karlman
On RK3399 the VOPL loaded before VOPB and gets registered as crtc-0. However, on RK3288 and PX30 VOPB is gets registered as crtc-0 instead of VOPL. With VOPL registered as crtc-0 the kernel kms client is not able to enable 4K display modes for console use on RK3399. Load VOPB before VOPL to help

[PATCH 04/13] drm/rockchip: dw_hdmi: Fix reading EDID when using a forced mode

2024-06-15 Thread Jonas Karlman
EDID cannot be read on RK3328 until after read_hpd has been called and correct io voltage has been configured based on connection status. When a forced mode is used, e.g. video=1920x1080@60e, the connector detect ops, that in turn normally calls the read_hpd, never gets called. This result in rea

[PATCH 12/13] drm/rockchip: dw_hdmi: Enable 4K@60Hz mode on RK3399 and RK356x

2024-06-15 Thread Jonas Karlman
Use a maximum TMDS clock rate limit of 594MHz to enable use of HDMI2.0 modes, e.g. 4K@60Hz, on RK3399 and RK3568. Signed-off-by: Jonas Karlman --- drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/rockchip/dw_hdmi-

[PATCH 03/13] drm/rockchip: vop: Allow 4096px width scaling

2024-06-15 Thread Jonas Karlman
From: Alex Bee There is no reason to limit VOP scaling to 3840px width, the limit of RK3288, when there are newer VOP versions that support 4096px width. Change to enforce a maximum of 4096px width plane scaling, the maximum supported output width of the VOP versions supported by this driver. F

[PATCH 06/13] drm/rockchip: dw_hdmi: Add max_tmds_clock validation

2024-06-15 Thread Jonas Karlman
Add max_tmds_clock validation to prepare for additions and changes to the MPLL config table. Use the same rate restrictions that is currently applied. The rate limit for RK3288, RK3399 and RK3568 is based on current mpll table. The rate limit for RK3228 and RK3228 is based on the inno-hdmi-phy pre

[PATCH 11/13] drm/rockchip: dw_hdmi: Use auto-generated tables

2024-06-15 Thread Jonas Karlman
From: Douglas Anderson The previous tables for mpll_cfg and curr_ctrl were created using the 20-pages of example settings provided by the PHY vendor. Those example settings weren't particularly dense, so there were places where we were guessing what the settings would be for 10-bit and 12-bit (n

[PATCH 05/13] drm/rockchip: dw_hdmi: Allow High TMDS Bit Rates

2024-06-15 Thread Jonas Karlman
Call dw_hdmi_set_high_tmds_clock_ratio in phy init ops to allow support of High TMDS Bit Rates used by HDMI2.0 display modes. Signed-off-by: Jonas Karlman --- drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/rockchip/dw_hdmi-rockch

[PATCH 10/13] drm/rockchip: dw_hdmi: Set cur_ctr to 0 always

2024-06-15 Thread Jonas Karlman
From: Douglas Anderson Jitter was improved by lowering the MPLL bandwidth to account for high frequency noise in the rk3288 PLL. In each case MPLL bandwidth was lowered only enough to get us a comfortable margin. We believe that lowering the bandwidth like this is safe given sufficient testing.

[PATCH 01/13] arm64: dts: rockchip: Increase VOP clk rate on RK3328

2024-06-15 Thread Jonas Karlman
The VOP on RK3328 needs to run at a higher rate in order to produce a proper 3840x2160 signal. Change to use 300MHz for VIO clk and 400MHz for VOP clk, same rates used by vendor 4.4 kernel. Fixes: 52e02d377a72 ("arm64: dts: rockchip: add core dtsi file for RK3328 SoCs") Signed-off-by: Jonas Karlm

[PATCH 02/13] clk: rockchip: Set parent rate for DCLK_VOP clock on RK3228

2024-06-15 Thread Jonas Karlman
Similar to DCLK_LCDC on RK3328, the DCLK_VOP on RK3228 is typically parented by the hdmiphy clk and it is expected that the DCLK_VOP and hdmiphy clk rate are kept in sync. Use CLK_SET_RATE_PARENT and CLK_SET_RATE_NO_REPARENT flags, same as used on RK3328, to make full use of all possible supported

[PATCH 00/13] rockchip: Enable 4K@60Hz mode on RK3228, RK3328, RK3399 and RK356x

2024-06-15 Thread Jonas Karlman
This prepares and enable use of HDMI2.0 modes, e.g. 4K@60Hz, on RK3228, RK3328, RK3399 and RK356x. Patch 1-3 fixes some issues to help support use of high-resolution modes. Patch 4 fixes reading of EDID on RK3328 when using a forced mode. Patch 5-7 adds hdmiphy rate validation in mode_valid so t

Re: [PATCH 09/15] net: hbl_en: add habanalabs Ethernet driver

2024-06-15 Thread Zhu Yanjun
在 2024/6/13 16:22, Omer Shpigelman 写道: This ethernet driver is initialized via auxiliary bus by the hbl_cn driver. It serves mainly for control operations that are needed for AI scaling. Signed-off-by: Omer Shpigelman Co-developed-by: Abhilash K V Signed-off-by: Abhilash K V Co-developed-by:

[drm-misc:topic/rust-drm 5/21] error[E0425]: cannot find value `THIS_MODULE` in the crate root

2024-06-15 Thread kernel test robot
tree: git://anongit.freedesktop.org/drm/drm-misc topic/rust-drm head: 2e2592fb7d2165e68073020066789bd8860678d0 commit: b7222062b14f6c9e501a405305052fe88c5ff51e [5/21] rust: introduce `InPlaceModule` config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20240615/202406152203

[Bug 206309] Experimental amdgpu w/ Dell E6540 with HD 8790M (MARS XTX), massive performance improvement after ACPI suspend

2024-06-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=206309 jerbear3.14...@gmail.com changed: What|Removed |Added CC||jerbear3.14...@gmail.com --- C

Re: [PATCH v4 4/4] arm64: dts: qcom: add HDMI nodes for msm8998

2024-06-15 Thread Konrad Dybcio
On 14.06.2024 12:33 PM, Dmitry Baryshkov wrote: > On Fri, Jun 14, 2024 at 01:55:46AM GMT, Konrad Dybcio wrote: >> >> [...] >> GCC_HDMI_CLKREF_CLK is a child of xo, so you can drop the latter. >> It would also be worth confirming whether it's really powering the >> PHY and not the TX.. You can tes

Re: [PATCH v10 3/6] iio: core: Add new DMABUF interface infrastructure

2024-06-15 Thread Paul Cercueil
Le dimanche 09 juin 2024 à 10:53 +0100, Jonathan Cameron a écrit : > On Wed,  5 Jun 2024 13:08:42 +0200 > Paul Cercueil wrote: > > > Add the necessary infrastructure to the IIO core to support a new > > optional DMABUF based interface. > > > > With this new interface, DMABUF objects (externally

Re: [PATCH 09/15] net: hbl_en: add habanalabs Ethernet driver

2024-06-15 Thread Zhu Yanjun
在 2024/6/13 16:22, Omer Shpigelman 写道: This ethernet driver is initialized via auxiliary bus by the hbl_cn driver. It serves mainly for control operations that are needed for AI scaling. Signed-off-by: Omer Shpigelman Co-developed-by: Abhilash K V Signed-off-by: Abhilash K V Co-developed-by:

Re: [PATCH v4 09/12] drm/ttm/pool: Provide a helper to shrink pages

2024-06-15 Thread kernel test robot
org/drm/xe/kernel.git drm-xe-next patch link: https://lore.kernel.org/r/20240614102548.4364-10-thomas.hellstrom%40linux.intel.com patch subject: [PATCH v4 09/12] drm/ttm/pool: Provide a helper to shrink pages config: loongarch-defconfig (https://download.01.org/0day-ci/archive/20240615/20

Re: [PATCH v2 5/7] drm/panic: Convert to drm_fb_clip_offset()

2024-06-15 Thread kernel test robot
c drm-misc-next patch link: https://lore.kernel.org/r/3121082eb4beb461773ebb6f656ed9b4286967ee.1718305355.git.geert%2Brenesas%40glider.be patch subject: [PATCH v2 5/7] drm/panic: Convert to drm_fb_clip_offset() config: x86_64-randconfig-003-20240615 (https://download.01.org/0day-ci/archiv

Re: [PATCH v3 2/4] dt-bindings: display: panel: Add compatible for kingdisplay-kd101ne3

2024-06-15 Thread Krzysztof Kozlowski
On 14/06/2024 16:55, Zhaoxiong Lv wrote: > The kingdisplay-kd101ne3 is a 10.1" WXGA TFT-LCD panel with > jadard-jd9365da controller. Hence, we add a new compatible > with panel specific config. > > Signed-off-by: Zhaoxiong Lv > --- > Chage since V3: > > - 1. Abandon the V2 patch and add kingdisp

Re: [PATCH v3 1/2] dt-bindings: display: panel-simple-dsi: add Starry-er88577 DSI panel bindings

2024-06-15 Thread Krzysztof Kozlowski
On 14/06/2024 16:56, Zhaoxiong Lv wrote: > This add the bindings for the 1280x800 TFT LCD Starry-er88577 DSI panel A nit, subject: drop second/last, redundant "bindings". The "dt-bindings" prefix is already stating that these are bindings. See also: https://elixir.bootlin.com/linux/v6.7-rc8/source

[PATCH] drm/panel: raydium-rm692e5: transition to mipi_dsi wrapped functions

2024-06-15 Thread Tejas Vipin
Use functions introduced in commit 966e397e4f60 ("drm/mipi-dsi: Introduce mipi_dsi_*_write_seq_multi()") and commit f79d6d28d8fe ("drm/mipi-dsi: wrap more functions for streamline handling") for the raydium rm692e5 panel. Signed-off-by: Tejas Vipin --- drivers/gpu/drm/panel/panel-raydium-rm692e5

[PATCH] drm/tidss: Add drm_panic support

2024-06-15 Thread Javier Martinez Canillas
Add support for the drm_panic module, which displays a pretty user friendly message on the screen when a Linux kernel panic occurs. Signed-off-by: Javier Martinez Canillas --- Tested on an AM625 BeaglePlay board by triggering a panic using the `echo c > /proc/sysrq-trigger` command. drivers/gpu

[drm-misc:topic/rust-drm 3/21] error[E0050]: method `init` has 1 parameter but the declaration in trait `rust_doctest_kernel_build_assert_rs_0::kernel::Module::init` has 2

2024-06-15 Thread kernel test robot
tree: git://anongit.freedesktop.org/drm/drm-misc topic/rust-drm head: 2e2592fb7d2165e68073020066789bd8860678d0 commit: f79700d8c6eee68d6d2c0eb92113211d22501860 [3/21] rust: pass module name to `Module::init` config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20240615

Re: [PATCH v4 01/12] drm/ttm: Allow TTM LRU list nodes of different types

2024-06-15 Thread kernel test robot
rm-xe-next patch link: https://lore.kernel.org/r/20240614102548.4364-2-thomas.hellstrom%40linux.intel.com patch subject: [PATCH v4 01/12] drm/ttm: Allow TTM LRU list nodes of different types config: loongarch-randconfig-001-20240615 (https://download.01.org/0day-ci/archive/20240615/20240615151