Re: [RFC PATCH v2 02/11] netdev: implement netlink api to bind dma-buf to netdevice

2023-08-13 Thread Mina Almasry
On Sun, Aug 13, 2023 at 6:10 PM David Ahern wrote: > > On 8/9/23 7:57 PM, Mina Almasry wrote: > > diff --git a/net/core/dev.c b/net/core/dev.c > > index 8e7d0cb540cd..02a25ccf771a 100644 > > --- a/net/core/dev.c > > +++ b/net/core/dev.c > > @@ -151,6 +151,8 @@ > > #include > > #include > >

Re: [RFC PATCH v2 00/11] Device Memory TCP

2023-08-13 Thread Mina Almasry
On Sun, Aug 13, 2023 at 6:12 PM David Ahern wrote: > > On 8/9/23 7:57 PM, Mina Almasry wrote: > > Changes in RFC v2: > > -- > > > > The sticking point in RFC v1[1] was the dma-buf pages approach we used to > > deliver the device memory to the TCP stack. RFC v2 is a

Re: [PATCH v3 3/4] drm/panel: ili9882t: Break out as separate driver

2023-08-13 Thread cong yang
Hi,Linus On Mon, Jul 3, 2023 at 9:21 PM Linus Walleij wrote: > > The Starry ILI9882t-based panel should never have been part of the boe > tv101wum driver, it is clearly based on the Ilitek ILI9882t display > controller and if you look at the custom command sequences for the > panel these clearly

Re: [RFC PATCH v2 00/11] Device Memory TCP

2023-08-13 Thread David Ahern
On 8/9/23 7:57 PM, Mina Almasry wrote: > Changes in RFC v2: > -- > > The sticking point in RFC v1[1] was the dma-buf pages approach we used to > deliver the device memory to the TCP stack. RFC v2 is a proof-of-concept > that attempts to resolve this by implementing scatterlist

Re: [RFC PATCH v2 02/11] netdev: implement netlink api to bind dma-buf to netdevice

2023-08-13 Thread David Ahern
On 8/9/23 7:57 PM, Mina Almasry wrote: > diff --git a/net/core/dev.c b/net/core/dev.c > index 8e7d0cb540cd..02a25ccf771a 100644 > --- a/net/core/dev.c > +++ b/net/core/dev.c > @@ -151,6 +151,8 @@ > #include > #include > #include > +#include > +#include > > #include "dev.h" > #include

Re: [RESEND v3 4/5] drm/amdgpu: Move coredump code to amdgpu_reset file

2023-08-13 Thread kernel test robot
Hi André, kernel test robot noticed the following build warnings: [auto build test WARNING on drm-misc/drm-misc-next] [also build test WARNING on drm/drm-next drm-exynos/exynos-drm-next drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-tip/drm-tip linus/master v6.5-rc5 next-20230809]

[PATCH 7/7] drm: adv7511: Add hpd_override_enable feature bit to struct adv7511_chip_info

2023-08-13 Thread Biju Das
As per spec, it is allowed to pulse the HPD signal to indicate that the EDID information has changed. Some monitors do this when they wake up from standby or are enabled. When the HPD goes low the adv7511 is reset and the outputs are disabled which might cause the monitor to go to standby again.

[PATCH 6/7] drm: adv7511: Add link_config feature bit to struct adv7511_chip_info

2023-08-13 Thread Biju Das
The ADV7511 needs link configuration whereas ADV75{33,35} does not need it. Add a feature bit link_config to struct adv7511_chip_info to handle this difference. Signed-off-by: Biju Das --- drivers/gpu/drm/bridge/adv7511/adv7511.h | 1 + drivers/gpu/drm/bridge/adv7511/adv7511_drv.c | 7

[PATCH 5/7] drm: adv7511: Add has_dsi feature bit to struct adv7511_chip_info

2023-08-13 Thread Biju Das
The ADV7533 and ADV7535 have DSI support. Add a feature bit has_dsi to struct adv7511_chip_info for handling configuration related to DSI. Signed-off-by: Biju Das --- drivers/gpu/drm/bridge/adv7511/adv7511.h | 1 + drivers/gpu/drm/bridge/adv7511/adv7511_drv.c | 20 +++- 2

[PATCH 4/7] drm: adv7511: Add supply_names and num_supplies variables to struct adv7511_chip_info

2023-08-13 Thread Biju Das
The ADV7511 has 5 power supplies compared to 7 that of ADV75{33,35}. Add supply_names and num_supplies variables to struct adv7511_chip_info to handle this difference. Signed-off-by: Biju Das --- drivers/gpu/drm/bridge/adv7511/adv7511.h | 3 +- drivers/gpu/drm/bridge/adv7511/adv7511_drv.c

[PATCH 3/7] drm: adv7511: Add max_lane_freq variable to struct adv7511_chip_info

2023-08-13 Thread Biju Das
The ADV7533 supports a maximum lane clock of 800MHz whereas it is 891MHz for ADV7535. Add max_lane_freq variable to struct adv7511_chip_info to handle this difference. While at it, drop the unused local variable max_lane_freq. Signed-off-by: Biju Das ---

[PATCH 2/7] drm: adv7511: Add max_mode_clock variable to struct adv7511_chip_info

2023-08-13 Thread Biju Das
The ADV7533 supports a maximum pixel clock of 80MHz whereas it is 148.5MHz for ADV7535. Add max_mode_clock variable to struct adv7511_chip_info to handle this difference. Signed-off-by: Biju Das --- drivers/gpu/drm/bridge/adv7511/adv7511.h | 1 +

[PATCH 1/7] drm: adv7511: Add struct adv7511_chip_info and use i2c_get_match_data()

2023-08-13 Thread Biju Das
Add struct adv7511_chip_info to handle hw differences between various chips rather checking against the 'type' variable in various places. Replace 'adv->type'->'info->type' by moving variable 'type' from struct adv7511 to struct adv7511_chip_info. Replace of_device_get_match_data() and ID lookup

[PATCH 0/7] ADV7511 driver enhancements

2023-08-13 Thread Biju Das
This patch series aims to improve ADV7511 driver by adding feature bits and data instead of comparing enum adv7511_type for various hardware differences between ADV7511, ADV7533 and ADV7535. This patch series tested with[1] on RZ/G2L SMARC EVK which embeds ADV7535. [1]

Re: [PATCH] drm: bridge: it66121: Extend match support for OF tables

2023-08-13 Thread Laurent Pinchart
Hi Biju, Thank you for the patch. On Sun, Aug 13, 2023 at 09:05:20AM +0100, Biju Das wrote: > The driver has OF match table, still it uses ID lookup table for > retrieving match data. Replace ID look up with i2c_get_match_data() > for retrieving OF/ACPI/I2C match data by adding similar match

[PATCH AUTOSEL 5.10 23/25] staging: fbtft: ili9341: use macro FBTFT_REGISTER_SPI_DRIVER

2023-08-13 Thread Sasha Levin
From: Raphael Gallais-Pou [ Upstream commit 4912649e1cf0317bf563f91655e04a303cacaf8d ] Using FBTFT_REGISTER_DRIVER resolves to a NULL struct spi_device_id. This ultimately causes a warning when the module probes. Fixes it. Signed-off-by: Raphael Gallais-Pou Link:

[PATCH AUTOSEL 5.10 19/25] drm/amd/display: Exit idle optimizations before attempt to access PHY

2023-08-13 Thread Sasha Levin
From: Leo Chen [ Upstream commit de612738e9771bd66aeb20044486c457c512f684 ] [Why & How] DMUB may hang when powering down pixel clocks due to no dprefclk. It is fixed by exiting idle optimization before the attempt to access PHY. Reviewed-by: Nicholas Kazlauskas Acked-by: Alex Hung

[PATCH AUTOSEL 5.15 25/31] drm/amd/display: Exit idle optimizations before attempt to access PHY

2023-08-13 Thread Sasha Levin
From: Leo Chen [ Upstream commit de612738e9771bd66aeb20044486c457c512f684 ] [Why & How] DMUB may hang when powering down pixel clocks due to no dprefclk. It is fixed by exiting idle optimization before the attempt to access PHY. Reviewed-by: Nicholas Kazlauskas Acked-by: Alex Hung

[PATCH AUTOSEL 6.1 45/47] staging: fbtft: ili9341: use macro FBTFT_REGISTER_SPI_DRIVER

2023-08-13 Thread Sasha Levin
From: Raphael Gallais-Pou [ Upstream commit 4912649e1cf0317bf563f91655e04a303cacaf8d ] Using FBTFT_REGISTER_DRIVER resolves to a NULL struct spi_device_id. This ultimately causes a warning when the module probes. Fixes it. Signed-off-by: Raphael Gallais-Pou Link:

[PATCH AUTOSEL 6.1 39/47] drm/amd/display: Exit idle optimizations before attempt to access PHY

2023-08-13 Thread Sasha Levin
From: Leo Chen [ Upstream commit de612738e9771bd66aeb20044486c457c512f684 ] [Why & How] DMUB may hang when powering down pixel clocks due to no dprefclk. It is fixed by exiting idle optimization before the attempt to access PHY. Reviewed-by: Nicholas Kazlauskas Acked-by: Alex Hung

[PATCH AUTOSEL 6.1 37/47] drm/amd/smu: use AverageGfxclkFrequency* to replace previous GFX Curr Clock

2023-08-13 Thread Sasha Levin
From: Jane Jian [ Upstream commit 4a37c55b859a69f429bfa7fab4fc43ee470b60ed ] Report current GFX clock also from average clock value as the original CurrClock data is not valid/accurate any more as per FW team Signed-off-by: Jane Jian Reviewed-by: Lijo Lazar Signed-off-by: Alex Deucher

[PATCH AUTOSEL 6.1 38/47] drm/amd/display: Guard DCN31 PHYD32CLK logic against chip family

2023-08-13 Thread Sasha Levin
From: George Shen [ Upstream commit 25b054c3c89cb6a7106a7982f0f70e83d0797dab ] [Why] Current yellow carp B0 PHYD32CLK logic is incorrectly applied to other ASICs. [How] Add guard to check chip family is yellow carp before applying logic. Reviewed-by: Hansen Dsouza Acked-by: Alex Hung

[PATCH AUTOSEL 6.4 50/54] staging: fbtft: ili9341: use macro FBTFT_REGISTER_SPI_DRIVER

2023-08-13 Thread Sasha Levin
From: Raphael Gallais-Pou [ Upstream commit 4912649e1cf0317bf563f91655e04a303cacaf8d ] Using FBTFT_REGISTER_DRIVER resolves to a NULL struct spi_device_id. This ultimately causes a warning when the module probes. Fixes it. Signed-off-by: Raphael Gallais-Pou Link:

[PATCH AUTOSEL 6.4 44/54] drm/amd/display: Exit idle optimizations before attempt to access PHY

2023-08-13 Thread Sasha Levin
From: Leo Chen [ Upstream commit de612738e9771bd66aeb20044486c457c512f684 ] [Why & How] DMUB may hang when powering down pixel clocks due to no dprefclk. It is fixed by exiting idle optimization before the attempt to access PHY. Reviewed-by: Nicholas Kazlauskas Acked-by: Alex Hung

[PATCH AUTOSEL 6.4 43/54] drm/amd/display: Guard DCN31 PHYD32CLK logic against chip family

2023-08-13 Thread Sasha Levin
From: George Shen [ Upstream commit 25b054c3c89cb6a7106a7982f0f70e83d0797dab ] [Why] Current yellow carp B0 PHYD32CLK logic is incorrectly applied to other ASICs. [How] Add guard to check chip family is yellow carp before applying logic. Reviewed-by: Hansen Dsouza Acked-by: Alex Hung

[PATCH AUTOSEL 6.4 42/54] drm/amd/smu: use AverageGfxclkFrequency* to replace previous GFX Curr Clock

2023-08-13 Thread Sasha Levin
From: Jane Jian [ Upstream commit 4a37c55b859a69f429bfa7fab4fc43ee470b60ed ] Report current GFX clock also from average clock value as the original CurrClock data is not valid/accurate any more as per FW team Signed-off-by: Jane Jian Reviewed-by: Lijo Lazar Signed-off-by: Alex Deucher

[GIT PULL] mediatek drm next for 6.6

2023-08-13 Thread Chun-Kuang Hu
Hi, Dave & Daniel: This includes: 1. Small mtk-dpi cleanups 2. DisplayPort: support eDP and aux-bus 3. Fix uninitialized symbol 4. Do not check for 0 return after calling platform_get_irq() 5. Convert to platform remove callback returning void 6. Fix coverity issues 7. Fix potential memory leak

Re: [REGRESSION] HDMI connector detection broken in 6.3 on Intel(R) Celeron(R) N3060 integrated graphics

2023-08-13 Thread Linux regression tracking (Thorsten Leemhuis)
On 11.08.23 20:10, Mikhail Rudenko wrote: > On 2023-08-11 at 08:45 +02, Thorsten Leemhuis > wrote: >> On 10.08.23 21:33, Mikhail Rudenko wrote: >>> The following is a copy an issue I posted to drm/i915 gitlab [1] two >>> months ago. I repost it to the mailing lists in hope that it will help >>>

Re: [PATCH v2 1/6] drm/tests: Test default pitch fallback

2023-08-13 Thread Maira Canal
Hi Arthur, On 8/11/23 15:17, Arthur Grillo wrote: Test the default pitch fallback when NULL is passed as the dst_pitch on the conversion procedures. Signed-off-by: Arthur Grillo Reviewed-by: Maíra Canal Best Regards, - Maíra --- drivers/gpu/drm/tests/drm_format_helper_test.c | 126

Re: [PATCH v2 4/6] drm/tests: Add KUnit tests for drm_fb_build_fourcc_list()

2023-08-13 Thread Maira Canal
On 8/11/23 15:17, Arthur Grillo wrote: Insert parameterized test for the drm_fb_build_fourcc_list() to ensure correctness and prevent future regressions. Signed-off-by: Arthur Grillo --- drivers/gpu/drm/tests/drm_format_helper_test.c | 148 + 1 file changed, 148

Re: [PATCH v2 6/6] drm/tests: Add KUnit tests for drm_fb_memcpy()

2023-08-13 Thread Maira Canal
Hi Arthur, On 8/11/23 15:17, Arthur Grillo wrote: Insert parameterized test for the drm_fb_memcpy() to ensure correctness and prevent future regressions. The test case can accept different formats. Signed-off-by: Arthur Grillo --- drivers/gpu/drm/tests/drm_format_helper_test.c | 391

Re: [RFC PATCH v2 02/11] netdev: implement netlink api to bind dma-buf to netdevice

2023-08-13 Thread Leon Romanovsky
On Wed, Aug 09, 2023 at 06:57:38PM -0700, Mina Almasry wrote: > Add a netdev_dmabuf_binding struct which represents the > dma-buf-to-netdevice binding. The netlink API will bind the dma-buf to > an rx queue on the netdevice. On the binding, the dma_buf_attach > & dma_buf_map_attachment will occur.

[PATCH] drm/bridge/analogix/anx78xx: Extend match data support for ID table

2023-08-13 Thread Biju Das
The driver has ID table, but still it uses device_get_match_data() for retrieving match data. Replace device_get_match_data-> i2c_get_match_data() for retrieving OF/ACPI/I2C match data by adding match data for ID table similar to OF table. Signed-off-by: Biju Das --- This patch is only compile

[PATCH] drm: bridge: it66121: Extend match support for OF tables

2023-08-13 Thread Biju Das
The driver has OF match table, still it uses ID lookup table for retrieving match data. Replace ID look up with i2c_get_match_data() for retrieving OF/ACPI/I2C match data by adding similar match data for OF table. While at it, drop unused local varibale id from probe(). Signed-off-by: Biju Das

[syzbot] [dri?] [reiserfs?] WARNING: bad unlock balance in vkms_vblank_simulate

2023-08-13 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:71cd4fc492ec Add linux-next specific files for 20230808 git tree: linux-next console+strace: https://syzkaller.appspot.com/x/log.txt?x=11faa1eda8 kernel config: https://syzkaller.appspot.com/x/.config?x=e36b5ba725f7349d