[v2 10/10] phy: cadence: Add driver for HDP-TX HDMI PHY

2022-11-03 Thread Sandor Yu
Add Cadence HDP-TX HDMI PHY driver. Cadence HDP-TX PHY could be put in either DP mode or HDMI mode base on the configuration chosen. HDMI PHY mode is configurated in the driver. Signed-off-by: Sandor Yu --- drivers/phy/cadence/Kconfig | 8 + drivers/phy/cadence/Makefile

[PATCH v2] drm/ingenic: Fix missing platform_driver_unregister() call in ingenic_drm_init()

2022-11-03 Thread Yuan Can
A problem about modprobe ingenic-drm failed is triggered with the following log given: [ 303.561088] Error: Driver 'ingenic-ipu' is already registered, aborting... modprobe: ERROR: could not insert 'ingenic_drm': Device or resource busy The reason is that ingenic_drm_init() returns platform_dr

[v2 09/10] dts-bindings: phy: Add Cadence HDP-TX HDMI PHY bindings

2022-11-03 Thread Sandor Yu
Add bindings for Cadence HDP-TX HDMI PHY. Signed-off-by: Sandor Yu --- .../bindings/phy/phy-cadence-hdptx-hdmi.yaml | 54 +++ 1 file changed, 54 insertions(+) create mode 100644 Documentation/devicetree/bindings/phy/phy-cadence-hdptx-hdmi.yaml diff --git a/Documentation/devic

[v2 08/10] phy: cadence: Add driver for HDP-TX DisplyPort PHY

2022-11-03 Thread Sandor Yu
Add Cadence HDP-TX DisplayPort PHY driver. Cadence HDP-TX PHY could be put in either DP mode or HDMI mode base on the configuration chosen. DisplayPort PHY mode is configurated in the driver. Signed-off-by: Sandor Yu --- drivers/phy/cadence/Kconfig| 8 + drivers/phy/cadence/Ma

[v2 07/10] dts-bindings: phy: Add Cadence HDP-TX DP PHY bindings

2022-11-03 Thread Sandor Yu
Add bindings for Cadence HDP-TX DisplayPort PHY. Signed-off-by: Sandor Yu --- .../bindings/phy/phy-cadence-hdptx-dp.yaml| 70 +++ 1 file changed, 70 insertions(+) create mode 100644 Documentation/devicetree/bindings/phy/phy-cadence-hdptx-dp.yaml diff --git a/Documentation/

[v2 06/10] drm: bridge: cadence: Add MHDP HDMI driver for i.MX8MQ

2022-11-03 Thread Sandor Yu
Add a new DRM HDMI bridge driver for Candence MHDP used in i.MX8MQ SOC. MHDP IP could support HDMI or DisplayPort standards according embedded Firmware running in the uCPU. For iMX8MQ SOC, the HDMI FW was loaded and activated by SOC ROM code. Bootload binary included HDMI FW was required for the d

[v2 05/10] dts-bindings: display: bridge: Add MHDP DP bindings for i.MX8MQ

2022-11-03 Thread Sandor Yu
Add bindings for i.MX8MQ MHDP DisplayPort. Signed-off-by: Sandor Yu --- .../display/bridge/cdns,mhdp-imx8mq-dp.yaml | 67 +++ 1 file changed, 67 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/bridge/cdns,mhdp-imx8mq-dp.yaml diff --git a/Documenta

[v2 04/10] phy: Add HDMI configuration options

2022-11-03 Thread Sandor Yu
Allow HDMI PHYs to be configured through the generic functions through a custom structure added to the generic union. The parameters added here are based on HDMI PHY implementation practices. The current set of parameters should cover the potential users. Signed-off-by: Sandor Yu --- include/l

[v2 03/10] drm: bridge: cadence: Add MHDP DP driver for i.MX8MQ

2022-11-03 Thread Sandor Yu
Add a new DRM DisplayPort bridge driver for Candence MHDP used in i.MX8MQ SOC. MHDP IP could support HDMI or DisplayPort standards according embedded Firmware running in the uCPU. For iMX8MQ SOC, the DisplayPort FW was loaded and activated by SOC ROM code. Bootload binary included HDMI FW was requ

[v2 02/10] dts-bingings: display: bridge: Add MHDP HDMI bindings for i.MX8MQ

2022-11-03 Thread Sandor Yu
Add bindings for i.MX8MQ MHDP HDMI. Signed-off-by: Sandor Yu --- .../display/bridge/cdns,mhdp-imx8mq-hdmi.yaml | 67 +++ 1 file changed, 67 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/bridge/cdns,mhdp-imx8mq-hdmi.yaml diff --git a/Documentation/

[v2 01/10] drm: bridge: cadence: convert mailbox functions to macro functions

2022-11-03 Thread Sandor Yu
Mailbox access functions could be share to other mhdp driver and HDP-TX HDMI/DP PHY drivers, move those functions to head file include/drm/bridge/cdns-mhdp-mailbox.h and convert them to macro functions. Signed-off-by: Sandor Yu --- .../drm/bridge/cadence/cdns-mhdp8546-core.c | 197 +---

[v2 0/10] Initial support for Cadence MHDP(HDMI/DP) for i.MX8MQ

2022-11-03 Thread Sandor Yu
The patch set initial support for Cadence MHDP(HDMI/DP) DRM bridge drivers and Cadence HDP-TX PHY(HDMI/DP) drivers for iMX8MQ. v2 is a completely different version compared to v1. Previous v1 can be available here [1]. v1->v2: - Reuse Cadence mailbox access functions from mhdp8546 instead of ro

[PATCH] drm/bridge: sii9234: Remove the unused function sii9234_mode_valid()

2022-11-03 Thread Jiapeng Chong
The function sii9234_mode_valid() is defined in the sii9234.c file, but not called elsewhere, so remove this unused function. drivers/gpu/drm/bridge/sii9234.c:870:31: warning: unused function 'bridge_to_sii9234'. Link: https://bugzilla.openanolis.cn/show_bug.cgi?id=2735 Reported-by: Abaci Robot

[QUESTION] {start,stop}_this_handle() and lockdep annotations

2022-11-03 Thread Byungchul Park
Hello, With v6.1-rc3, a deadlock in the journal code was reported by DEPT. I'd need to understand the journal code first before deep dive into it. I found a few lockdep annotations was added into the journal code by Peterz (commit 34a3d1e8370870 lockdep: annotate journal_start()) and the commit m

Re: [PATCH] drm/ingenic: Fix missing platform_driver_unregister() call in ingenic_drm_init()

2022-11-03 Thread Yuan Can
在 2022/11/3 22:52, Paul Cercueil 写道: Hi Yuan, Le jeu. 3 nov. 2022 à 14:01:48 +, Yuan Can a écrit : A problem about modprobe ingenic-drm failed is triggered with the following log given:  [  303.561088] Error: Driver 'ingenic-ipu' is already registered, aborting...  modprobe: ERROR: cou

Re: [RFC][PATCH v3 13/33] timers: drm: Use timer_shutdown_sync() before freeing timer

2022-11-03 Thread Steven Rostedt
[ Once again, quilt fails the MIME coding ] From: "Steven Rostedt (Google)" Before a timer is freed, timer_shutdown_sync() must be called. Link: https://lore.kernel.org/all/20220407161745.7d675...@gandalf.local.home/ Cc: "Noralf Trønnes" Cc: David Airlie Cc: Daniel Vetter Cc: Jani Nikula C

Re: [RFC][PATCH v3 12/33] timers: dma-buf: Use timer_shutdown_sync() before freeing timer

2022-11-03 Thread Steven Rostedt
[ Once again, quilt fails the MIME coding ] From: "Steven Rostedt (Google)" Before a timer is freed, timer_shutdown_sync() must be called. Link: https://lore.kernel.org/all/20220407161745.7d675...@gandalf.local.home/ Cc: Sumit Semwal Cc: "Christian König" Cc: linux-me...@vger.kernel.org Cc:

[RFC][PATCH v3 12/33] timers: dma-buf: Use timer_shutdown_sync() before freeing timer

2022-11-03 Thread Steven Rostedt
From: "Steven Rostedt (Google)" Before a timer is freed, timer_shutdown_sync() must be called. Link: https://lore.kernel.org/all/20220407161745.7d675...@gandalf.local.home/ Cc: Sumit Semwal Cc: "Christian König" Cc: linux-me...@vger.kernel.org Cc: dri-devel@lists.freedesktop.org Cc: linaro-mm

[RFC][PATCH v3 00/33] timers: Use timer_shutdown*() before freeing timers

2022-11-03 Thread Steven Rostedt
Back in April, I posted an RFC patch set to help mitigate a common issue where a timer gets armed just before it is freed, and when the timer goes off, it crashes in the timer code without any evidence of who the culprit was. I got side tracked and never finished up on that patch set. Since this

[RFC][PATCH v3 13/33] timers: drm: Use timer_shutdown_sync() before freeing timer

2022-11-03 Thread Steven Rostedt
From: "Steven Rostedt (Google)" Before a timer is freed, timer_shutdown_sync() must be called. Link: https://lore.kernel.org/all/20220407161745.7d675...@gandalf.local.home/ Cc: "Noralf Trønnes" Cc: David Airlie Cc: Daniel Vetter Cc: Jani Nikula Cc: Joonas Lahtinen Cc: Rodrigo Vivi Cc: Tvr

[git pull] drm fixes for 6.1-rc4

2022-11-03 Thread Dave Airlie
Hi Linus, This is the weekly fixes for rc4. Misc fixes across rockchip, imx, amdgpu and i915. The biggest change is for amdkfd where the trap handler needs an updated fw from a header which makes it a bit larger. I hadn't noticed this particular file before so I'm going to figure out what the magi

[PATCH RESEND 13/13] omapfb: panel-sharp-ls037v7dw01: fix included headers

2022-11-03 Thread Dmitry Torokhov
The driver is using gpiod API so it should include gpio/consumer.h and not gpio.gh or of_gpio.h. Signed-off-by: Dmitry Torokhov --- drivers/video/fbdev/omap2/omapfb/displays/panel-sharp-ls037v7dw01.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/video/fbdev/omap2

[PATCH RESEND 10/13] omapfb: encoder-opa362: fix included headers

2022-11-03 Thread Dmitry Torokhov
The driver has been switched to gpiod API, so it should include gpio/consumer.h instead of gpio.h and of_gpio.h. With of_gpio.h no longer included we need mod_devicetable.h for of_device_id definition. Signed-off-by: Dmitry Torokhov --- drivers/video/fbdev/omap2/omapfb/displays/encoder-opa362.c

[PATCH RESEND 11/13] omapfb: panel-lgphilips-lb035q02: remove backlight GPIO handling

2022-11-03 Thread Dmitry Torokhov
With f048e8c1d169 ("omapfb: panel-lgphilips-lb035q02: Remove legacy boot support") it is no longer possible to specify GPIO to control the backlight. Remove code trying to request and toggle it. Signed-off-by: Dmitry Torokhov --- .../omapfb/displays/panel-lgphilips-lb035q02.c | 21 +

[PATCH RESEND 12/13] omapfb: panel-tpo-td028ttec1: stop including gpio.h

2022-11-03 Thread Dmitry Torokhov
The driver does not use gpios, so there is no need to include gpio.h. Signed-off-by: Dmitry Torokhov --- drivers/video/fbdev/omap2/omapfb/displays/panel-tpo-td028ttec1.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/video/fbdev/omap2/omapfb/displays/panel-tpo-td028ttec1.c b/drivers

[PATCH RESEND 07/13] omapfb: panel-nec-nl8048hl11: switch to using gpiod API

2022-11-03 Thread Dmitry Torokhov
Switch the driver from legacy gpio API that is deprecated to the newer gpiod API that respects line polarities described in ACPI/DT. Note that because existing DTSes specify incorrect polarity of reset lines (active high) and GPU drivers have adopted to this, we follow the suit and use inverted va

[PATCH RESEND 08/13] omapfb: panel-dpi: remove support for platform data

2022-11-03 Thread Dmitry Torokhov
There are no users of panel_dpi_platform_data in the mainline kernel so support for it can be removed from the panel driver. Signed-off-by: Dmitry Torokhov --- .../video/fbdev/omap2/omapfb/displays/panel-dpi.c | 83 ++ include/video/omap-panel-data.h| 21

[PATCH RESEND 09/13] omapfb: connector-analog-tv: remove support for platform data

2022-11-03 Thread Dmitry Torokhov
There are no users of connector_atv_platform_data in the mainline kernel so support for it can be removed from the panel driver. Signed-off-by: Dmitry Torokhov --- .../omap2/omapfb/displays/connector-analog-tv.c| 60 +++--- include/video/omap-panel-data.h|

[PATCH RESEND 06/13] omapfb: panel-tpo-td043mtea1: switch to using gpiod API

2022-11-03 Thread Dmitry Torokhov
Switch the driver from legacy gpio API that is deprecated to the newer gpiod API that respects line polarities described in ACPI/DT. Signed-off-by: Dmitry Torokhov --- .../omap2/omapfb/displays/panel-tpo-td043mtea1.c | 59 ++ 1 file changed, 16 insertions(+), 43 deletions(-

[PATCH RESEND 05/13] omapfb: panel-dsi-cm: switch to using gpiod API

2022-11-03 Thread Dmitry Torokhov
Switch the driver from legacy gpio API that is deprecated to the newer gpiod API that respects line polarities described in ACPI/DT. Note that because existing DTSes specify incorrect polarity of reset lines (active high) and GPU drivers have adopted to this, we follow the suit and use inverted va

[PATCH RESEND 04/13] omapfb: encoder-tfp410: switch to using gpiod API

2022-11-03 Thread Dmitry Torokhov
Switch the driver from legacy gpio API that is deprecated to the newer gpiod API that respects line polarities described in ACPI/DT. Signed-off-by: Dmitry Torokhov --- .../fbdev/omap2/omapfb/displays/encoder-tfp410.c | 67 +++--- 1 file changed, 22 insertions(+), 45 deletions(-

[PATCH RESEND 01/13] omapfb: connector-hdmi: switch to using gpiod API

2022-11-03 Thread Dmitry Torokhov
Switch the driver from legacy gpio API that is deprecated to the newer gpiod API that respects line polarities described in ACPI/DT. Signed-off-by: Dmitry Torokhov --- .../fbdev/omap2/omapfb/displays/connector-hdmi.c | 49 +++--- 1 file changed, 14 insertions(+), 35 deletions(-

[PATCH RESEND 03/13] omapfb: panel-sony-acx565akm: switch to using gpiod API

2022-11-03 Thread Dmitry Torokhov
Switch the driver from legacy gpio API that is deprecated to the newer gpiod API that respects line polarities described in ACPI/DT. Note that because existing DTSes specify incorrect polarity of reset lines (active high) and GPU drivers have adopted to this, we follow the suit and use inverted va

[PATCH RESEND 02/13] omapfb: panel-sony-acx565akm: remove support for platform data

2022-11-03 Thread Dmitry Torokhov
There are no users of panel_acx565akm_platform_data in the mainline kernel so support for it can be removed from the panel driver. Signed-off-by: Dmitry Torokhov --- .../omap2/omapfb/displays/panel-sony-acx565akm.c | 45 +++--- include/video/omap-panel-data.h

[PATCH RESEND 00/13] Convert omapfb drivers to gpiod API

2022-11-03 Thread Dmitry Torokhov
| 71 - 13 files changed, 170 insertions(+), 541 deletions(-) --- base-commit: 61c3426aca2c71052ddcd06c32e29d92304990fd change-id: 20221103-omapfb-gpiod-87ca2550bd90 -- Dmitry

[PATCH] $drm/nouveau: Fix kernel-doc

2022-11-03 Thread Jiapeng Chong
No functional modification involved. drivers/gpu/drm/nouveau/nouveau_ioc32.c:52: warning: expecting prototype for Called whenever a 32-bit process running under a 64(). Prototype was for nouveau_compat_ioctl() instead. Link: https://bugzilla.openanolis.cn/show_bug.cgi?id=2730 Reported-by: Abaci

[syzbot] KASAN: use-after-free Read in drm_gem_handle_delete

2022-11-03 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:b229b6ca5abb Merge tag 'perf-tools-fixes-for-v6.1-2022-10-.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=14dddf5e88 kernel config: https://syzkaller.appspot.com/x/.config?x=a66c6c673fb555e8 das

Re: [PATCH v2 0/7] vfio-ccw parent rework

2022-11-03 Thread Matthew Rosato
On 11/3/22 5:56 PM, Alex Williamson wrote: > On Wed, 2 Nov 2022 16:01:45 +0100 > Eric Farman wrote: > >> Hi all, >> >> Here is an update to the vfio-ccw lifecycle changes that have been discussed >> in various forms over the past year [1][2] or so, and which I dusted off >> recently. >> >> Patch

Re: [PATCH v2 7/7] vfio: Remove vfio_free_device

2022-11-03 Thread Matthew Rosato
On 11/2/22 11:01 AM, Eric Farman wrote: > With the "mess" sorted out, we should be able to inline the > vfio_free_device call introduced by commit cb9ff3f3b84c > ("vfio: Add helpers for unifying vfio_device life cycle") > and remove them from driver release callbacks. > > Signed-off-by: Eric Farma

Re: [PATCH v2 6/7] vfio/ccw: replace vfio_init_device with _alloc_

2022-11-03 Thread Matthew Rosato
On 11/2/22 11:01 AM, Eric Farman wrote: > Now that we have a reasonable separation of structs that follow > the subchannel and mdev lifecycles, there's no reason we can't > call the official vfio_alloc_device routine for our private data, > and behave like everyone else. > > Signed-off-by: Eric Fa

Re: [PATCH v2 5/7] vfio/ccw: remove release completion

2022-11-03 Thread Matthew Rosato
On 11/2/22 11:01 AM, Eric Farman wrote: > There's enough separation between the parent and private structs now, > that it is fine to remove the release completion hack. > > Signed-off-by: Eric Farman > Reviewed-by: Kevin Tian Reviewed-by: Matthew Rosato > --- > drivers/s390/cio/vfio_ccw_ops.

Re: [PATCH v2 4/7] vfio/ccw: move private to mdev lifecycle

2022-11-03 Thread Matthew Rosato
On 11/2/22 11:01 AM, Eric Farman wrote: > Now that the mdev parent data is split out into its own struct, > it is safe to move the remaining private data to follow the > mdev probe/remove lifecycle. The mdev parent data will remain > where it is, and follow the subchannel and the css driver > inter

linux-next: manual merge of the drm-misc tree with Linus' tree

2022-11-03 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the drm-misc tree got a conflict in: include/drm/gpu_scheduler.h between commit: 7b476affcccf ("drm/sched: add DRM_SCHED_FENCE_DONT_PIPELINE flag") from Linus' tree and commit: 4d5230b50dd4 ("drm/scheduler: add drm_sched_job_add_resv_dependencies") f

Re: [PATCH v2 1/7] vfio/ccw: create a parent struct

2022-11-03 Thread Matthew Rosato
On 11/2/22 11:01 AM, Eric Farman wrote: > Move the stuff associated with the mdev parent (and thus the > subchannel struct) into its own struct, and leave the rest in > the existing private structure. > > The subchannel will point to the parent, and the parent will point > to the private, for the

Re: [RFC PATCH v2 1/3] drivers/accel: define kconfig and register a new major

2022-11-03 Thread Randy Dunlap
On 11/3/22 13:39, Oded Gabbay wrote: > On Thu, Nov 3, 2022 at 3:31 PM Oded Gabbay wrote: >> >> On Thu, Nov 3, 2022 at 2:31 AM Greg Kroah-Hartman >> wrote: >>> >>> On Wed, Nov 02, 2022 at 10:34:03PM +0200, Oded Gabbay wrote: --- /dev/null +++ b/drivers/accel/Kconfig @@ -0,0 +1,24

Re: [PATCH 00/13] Convert omapfb drivers to gpiod API

2022-11-03 Thread Dmitry Torokhov
/displays/panel-tpo-td028ttec1.c | 1 - > .../omap2/omapfb/displays/panel-tpo-td043mtea1.c | 59 +++ > include/video/omap-panel-data.h | 71 - > 13 files changed, 170 insertions(+), 541 deletions(-) > --- > base-commit: 61c3426aca2c71052ddcd06c32e29d92304990fd > change-id: 20221103-omapfb-gpiod-87ca2550bd90 > > -- > Dmitry > -- Dmitry

[PATCH 12/13] omapfb: panel-tpo-td028ttec1: stop including gpio.h

2022-11-03 Thread Dmitry Torokhov
The driver does not use gpios, so there is no need to include gpio.h. Signed-off-by: Dmitry Torokhov --- drivers/video/fbdev/omap2/omapfb/displays/panel-tpo-td028ttec1.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/video/fbdev/omap2/omapfb/displays/panel-tpo-td028ttec1.c b/drivers

[PATCH 13/13] omapfb: panel-sharp-ls037v7dw01: stop i

2022-11-03 Thread Dmitry Torokhov
The driver is using gpiod API so it should include gpio/consumer.h and not gpio.gh or of_gpio.h. Signed-off-by: Dmitry Torokhov --- drivers/video/fbdev/omap2/omapfb/displays/panel-sharp-ls037v7dw01.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/video/fbdev/omap2

[PATCH 13/13] omapfb: panel-sharp-ls037v7dw01: fix included headers

2022-11-03 Thread Dmitry Torokhov
The driver is using gpiod API so it should include gpio/consumer.h and not gpio.gh or of_gpio.h. Signed-off-by: Dmitry Torokhov --- drivers/video/fbdev/omap2/omapfb/displays/panel-sharp-ls037v7dw01.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/video/fbdev/omap2

[PATCH 10/13] omapfb: encoder-opa362: fix included headers

2022-11-03 Thread Dmitry Torokhov
The driver has been switched to gpiod API, so it should include gpio/consumer.h instead of gpio.h and of_gpio.h. With of_gpio.h no longer included we need mod_devicetable.h for of_device_id definition. Signed-off-by: Dmitry Torokhov --- drivers/video/fbdev/omap2/omapfb/displays/encoder-opa362.c

[PATCH 09/13] omapfb: connector-analog-tv: remove support for platform data

2022-11-03 Thread Dmitry Torokhov
There are no users of connector_atv_platform_data in the mainline kernel so support for it can be removed from the panel driver. Signed-off-by: Dmitry Torokhov --- .../omap2/omapfb/displays/connector-analog-tv.c| 60 +++--- include/video/omap-panel-data.h|

[PATCH 07/13] omapfb: panel-nec-nl8048hl11: switch to using gpiod API

2022-11-03 Thread Dmitry Torokhov
Switch the driver from legacy gpio API that is deprecated to the newer gpiod API that respects line polarities described in ACPI/DT. Note that because existing DTSes specify incorrect polarity of reset lines (active high) and GPU drivers have adopted to this, we follow the suit and use inverted va

[PATCH 11/13] omapfb: panel-lgphilips-lb035q02: remove backlight GPIO handling

2022-11-03 Thread Dmitry Torokhov
With f048e8c1d169 ("omapfb: panel-lgphilips-lb035q02: Remove legacy boot support") it is no longer possible to specify GPIO to control the backlight. Remove code trying to request and toggle it. Signed-off-by: Dmitry Torokhov --- .../omapfb/displays/panel-lgphilips-lb035q02.c | 21 +

[PATCH 08/13] omapfb: panel-dpi: remove support for platform data

2022-11-03 Thread Dmitry Torokhov
There are no users of panel_dpi_platform_data in the mainline kernel so support for it can be removed from the panel driver. Signed-off-by: Dmitry Torokhov --- .../video/fbdev/omap2/omapfb/displays/panel-dpi.c | 83 ++ include/video/omap-panel-data.h| 21

[PATCH 05/13] omapfb: panel-dsi-cm: switch to using gpiod API

2022-11-03 Thread Dmitry Torokhov
Switch the driver from legacy gpio API that is deprecated to the newer gpiod API that respects line polarities described in ACPI/DT. Note that because existing DTSes specify incorrect polarity of reset lines (active high) and GPU drivers have adopted to this, we follow the suit and use inverted va

[PATCH 06/13] omapfb: panel-tpo-td043mtea1: switch to using gpiod API

2022-11-03 Thread Dmitry Torokhov
Switch the driver from legacy gpio API that is deprecated to the newer gpiod API that respects line polarities described in ACPI/DT. Signed-off-by: Dmitry Torokhov --- .../omap2/omapfb/displays/panel-tpo-td043mtea1.c | 59 ++ 1 file changed, 16 insertions(+), 43 deletions(-

[PATCH 03/13] omapfb: panel-sony-acx565akm: switch to using gpiod API

2022-11-03 Thread Dmitry Torokhov
Switch the driver from legacy gpio API that is deprecated to the newer gpiod API that respects line polarities described in ACPI/DT. Note that because existing DTSes specify incorrect polarity of reset lines (active high) and GPU drivers have adopted to this, we follow the suit and use inverted va

[PATCH 04/13] omapfb: encoder-tfp410: switch to using gpiod API

2022-11-03 Thread Dmitry Torokhov
Switch the driver from legacy gpio API that is deprecated to the newer gpiod API that respects line polarities described in ACPI/DT. Signed-off-by: Dmitry Torokhov --- .../fbdev/omap2/omapfb/displays/encoder-tfp410.c | 67 +++--- 1 file changed, 22 insertions(+), 45 deletions(-

[PATCH 02/13] omapfb: panel-sony-acx565akm: remove support for platform data

2022-11-03 Thread Dmitry Torokhov
There are no users of panel_acx565akm_platform_data in the mainline kernel so support for it can be removed from the panel driver. Signed-off-by: Dmitry Torokhov --- .../omap2/omapfb/displays/panel-sony-acx565akm.c | 45 +++--- include/video/omap-panel-data.h

[PATCH 01/13] omapfb: connector-hdmi: switch to using gpiod API

2022-11-03 Thread Dmitry Torokhov
Switch the driver from legacy gpio API that is deprecated to the newer gpiod API that respects line polarities described in ACPI/DT. Signed-off-by: Dmitry Torokhov --- .../fbdev/omap2/omapfb/displays/connector-hdmi.c | 49 +++--- 1 file changed, 14 insertions(+), 35 deletions(-

[PATCH 0/7] Convert omapfb drivers to gpiod API

2022-11-03 Thread Dmitry Torokhov
| 105 ++- .../omap2/omapfb/displays/panel-tpo-td043mtea1.c | 59 +++ include/video/omap-panel-data.h| 16 --- 7 files changed, 151 insertions(+), 333 deletions(-) --- base-commit: 61c3426aca2c71052ddcd06c32e29d92304990fd change-id: 20221103-omapfb

[PATCH 00/13] Convert omapfb drivers to gpiod API

2022-11-03 Thread Dmitry Torokhov
| 71 - 13 files changed, 170 insertions(+), 541 deletions(-) --- base-commit: 61c3426aca2c71052ddcd06c32e29d92304990fd change-id: 20221103-omapfb-gpiod-87ca2550bd90 -- Dmitry

Re: KUnit issues - Was: [igt-dev] [PATCH RFC v2 8/8] drm/i915: check if current->mm is not NULL

2022-11-03 Thread Daniel Latypov
On Thu, Nov 3, 2022 at 8:23 AM Mauro Carvalho Chehab wrote: > > Hi, > > I'm facing a couple of issues when testing KUnit with the i915 driver. > > The DRM subsystem and the i915 driver has, for a long time, his own > way to do unit tests, which seems to be added before KUnit. > > I'm now checking

Re: [PATCH 3/9] drm/i915: Use kmap_local_page() in gem/i915_gem_shmem.c

2022-11-03 Thread Fabio M. De Francesco
On lunedì 17 ottobre 2022 11:37:19 CET Zhao Liu wrote: > From: Zhao Liu > > The use of kmap_atomic() is being deprecated in favor of > kmap_local_page()[1]. > > The main difference between atomic and local mappings is that local > mappings doesn't disable page faults or preemption. > > In drm/i

Re: Try to address the DMA-buf coherency problem

2022-11-03 Thread Nicolas Dufresne
Le mercredi 02 novembre 2022 à 12:18 +0100, Christian König a écrit : > Am 01.11.22 um 22:09 schrieb Nicolas Dufresne: > > [SNIP] > > > > But the client is just a video player. It doesn't understand how to > > > > allocate BOs for Panfrost or AMD or etnaviv. So without a universal > > > > allocator

Re: [PATCH v2 0/7] vfio-ccw parent rework

2022-11-03 Thread Alex Williamson
On Wed, 2 Nov 2022 16:01:45 +0100 Eric Farman wrote: > Hi all, > > Here is an update to the vfio-ccw lifecycle changes that have been discussed > in various forms over the past year [1][2] or so, and which I dusted off > recently. > > Patches 1-5 rework the behavior of the vfio-ccw driver's pr

Re: [PATCH v27 6/7] drm/mediatek: add drm ovl_adaptor sub driver for MT8195

2022-11-03 Thread Nícolas F . R . A . Prado
On Thu, Nov 03, 2022 at 11:26:09AM +0800, Nancy.Lin wrote: > Add drm ovl_adaptor sub driver. Bring up ovl_adaptor sub driver if > the component exists in the path. > > Signed-off-by: Nancy.Lin > Reviewed-by: AngeloGioacchino Del Regno > > Reviewed-by: CK Hu > Tested-by: AngeloGioacchino Del Re

Re: [PATCH v27 2/7] drm/mediatek: add ETHDR support for MT8195

2022-11-03 Thread Nícolas F . R . A . Prado
On Thu, Nov 03, 2022 at 11:26:05AM +0800, Nancy.Lin wrote: [..] > --- /dev/null > +++ b/drivers/gpu/drm/mediatek/mtk_ethdr.h [..] > +void mtk_ethdr_unregister_vblank_cb(struct device *dev); > +void mtk_ethdr_enable_vblank(struct device *dev); > +void mtk_ethdr_disable_vblank(struct device *dev); >

Re: [PATCH v27 08/11] soc: mediatek: mmsys: add mmsys for support 64 reset bits

2022-11-03 Thread Nícolas F . R . A . Prado
On Thu, Nov 03, 2022 at 11:25:09AM +0800, Nancy.Lin wrote: > Add mmsys for support 64 reset bits. It is a preparation for MT8195 > vdosys1 HW reset. MT8195 vdosys1 has more than 32 reset bits. > > 1. Add the number of reset bits in mmsys private data > 2. move the whole "reset register code sectio

Re: [RFC PATCH v2 1/3] drivers/accel: define kconfig and register a new major

2022-11-03 Thread Oded Gabbay
On Thu, Nov 3, 2022 at 3:31 PM Oded Gabbay wrote: > > On Thu, Nov 3, 2022 at 2:31 AM Greg Kroah-Hartman > wrote: > > > > On Wed, Nov 02, 2022 at 10:34:03PM +0200, Oded Gabbay wrote: > > > --- /dev/null > > > +++ b/drivers/accel/Kconfig > > > @@ -0,0 +1,24 @@ > > > +# SPDX-License-Identifier: GPL-

Re: [PATCH v27 05/11] soc: mediatek: refine code to use mtk_mmsys_update_bits API

2022-11-03 Thread Nícolas F . R . A . Prado
On Thu, Nov 03, 2022 at 11:25:06AM +0800, Nancy.Lin wrote: [..] > --- a/drivers/soc/mediatek/mtk-mmsys.c > +++ b/drivers/soc/mediatek/mtk-mmsys.c [..] > +static void mtk_mmsys_update_bits(struct mtk_mmsys *mmsys, u32 offset, u32 > mask, u32 val) > +{ > + u32 tmp; > + > + tmp = readl_relaxe

Re: [PATCH v27 06/11] soc: mediatek: add mtk-mmsys config API for mt8195 vdosys1

2022-11-03 Thread Nícolas F . R . A . Prado
On Thu, Nov 03, 2022 at 11:25:07AM +0800, Nancy.Lin wrote: > Add four mmsys config APIs. The config APIs are used for config > mmsys reg. Some mmsys regs need to be set according to the > HW engine binding to the mmsys simultaneously. > > 1. mtk_mmsys_merge_async_config: config merge async width/h

Re: [PATCH v27 01/11] dt-bindings: arm: mediatek: mmsys: add vdosys1 compatible for MT8195

2022-11-03 Thread Nícolas F . R . A . Prado
On Thu, Nov 03, 2022 at 11:25:02AM +0800, Nancy.Lin wrote: > Add vdosys1 mmsys compatible for MT8195 platform. > > For MT8195, VDOSYS0 and VDOSYS1 are 2 display HW pipelines binding to > 2 different power domains, different clock drivers and different > mediatek-drm drivers. > > Signed-off-by: Na

Re: [Intel-gfx] [PATCH] drm/i915: Don't wait forever in drop_caches

2022-11-03 Thread John Harrison
On 11/3/2022 03:45, Jani Nikula wrote: On Wed, 02 Nov 2022, John Harrison wrote: On 11/2/2022 07:20, Tvrtko Ursulin wrote: On 02/11/2022 12:12, Jani Nikula wrote: On Tue, 01 Nov 2022, john.c.harri...@intel.com wrote: From: John Harrison At the end of each test, IGT does a drop caches ca

Re: [Intel-gfx] [PATCH] drm/i915: Don't wait forever in drop_caches

2022-11-03 Thread John Harrison
On 11/3/2022 02:18, Tvrtko Ursulin wrote: On 03/11/2022 01:33, John Harrison wrote: On 11/2/2022 07:20, Tvrtko Ursulin wrote: On 02/11/2022 12:12, Jani Nikula wrote: On Tue, 01 Nov 2022, john.c.harri...@intel.com wrote: From: John Harrison At the end of each test, IGT does a drop caches cal

Re: [PATCH 1/9] drm/i915: Use kmap_local_page() in gem/i915_gem_object.c

2022-11-03 Thread Fabio M. De Francesco
On giovedì 3 novembre 2022 17:51:23 CET Ira Weiny wrote: > On Sat, Oct 29, 2022 at 01:17:03PM +0200, Fabio M. De Francesco wrote: > > On lunedì 17 ottobre 2022 11:37:17 CEST Zhao Liu wrote: > > > From: Zhao Liu > > > > > > The use of kmap_atomic() is being deprecated in favor of > > > kmap_local_

Re: [Intel-gfx] [PATCH] drm/i915: Don't wait forever in drop_caches

2022-11-03 Thread John Harrison
On 11/3/2022 02:38, Tvrtko Ursulin wrote: On 03/11/2022 09:18, Tvrtko Ursulin wrote: On 03/11/2022 01:33, John Harrison wrote: On 11/2/2022 07:20, Tvrtko Ursulin wrote: On 02/11/2022 12:12, Jani Nikula wrote: On Tue, 01 Nov 2022, john.c.harri...@intel.com wrote: From: John Harrison At the

Re: [PATCH 7/9] drm/i915: Use memcpy_from_page() in gt/uc/intel_uc_fw.c

2022-11-03 Thread Ira Weiny
On Mon, Oct 17, 2022 at 05:37:23PM +0800, Zhao Liu wrote: > From: Zhao Liu > > The use of kmap_atomic() is being deprecated in favor of > kmap_local_page()[1]. > > The main difference between atomic and local mappings is that local > mappings doesn't disable page faults or preemption. > > In dr

Re: [PATCH] drm/i915/guc: Remove excessive line feeds in state dumps

2022-11-03 Thread Umesh Nerlige Ramappa
On Mon, Oct 31, 2022 at 03:00:07PM -0700, john.c.harri...@intel.com wrote: From: John Harrison Some of the GuC state dump messages were adding extra line feeds. When printing via a DRM printer to dmesg, for example, that messes up the log formatting as it loses any prefixing from the printer. G

Re: [PATCH v7 07/10] drm: bridge: samsung-dsim: Add atomic_get_input_bus_fmts

2022-11-03 Thread Marek Vasut
On 11/3/22 18:27, Jagan Teki wrote: On Thu, Nov 3, 2022 at 9:56 PM Marek Vasut wrote: On 11/3/22 10:39, Jagan Teki wrote: On Sun, Oct 16, 2022 at 3:31 AM Marek Vasut wrote: On 10/5/22 17:13, Jagan Teki wrote: [...] @@ -1321,6 +1322,32 @@ static void samsung_dsim_atomic_post_disable(stru

Re: [Intel-gfx] [PATCH v2 2/2] drm/i915/guc: Don't deadlock busyness stats vs reset

2022-11-03 Thread Umesh Nerlige Ramappa
On Thu, Nov 03, 2022 at 11:45:57AM -0700, John Harrison wrote: On 11/3/2022 04:31, Tvrtko Ursulin wrote: On 02/11/2022 19:21, john.c.harri...@intel.com wrote: From: John Harrison The engine busyness stats has a worker function to do things like 64bit extend the 32bit hardware counters. The Gu

Re: [Intel-gfx] [PATCH v2 2/2] drm/i915/guc: Don't deadlock busyness stats vs reset

2022-11-03 Thread John Harrison
On 11/3/2022 04:31, Tvrtko Ursulin wrote: On 02/11/2022 19:21, john.c.harri...@intel.com wrote: From: John Harrison The engine busyness stats has a worker function to do things like 64bit extend the 32bit hardware counters. The GuC's reset prepare function flushes out this worker function to e

[PATCH] drm/amd/display: don't enable DRM CRTC degamma property for DCE

2022-11-03 Thread Melissa Wen
DM maps DRM CRTC degamma to DPP (pre-blending) degamma block, but DCE doesn't support programmable degamma curve anywhere. Currently, a custom degamma is accepted by DM but just ignored by DCE driver and degamma correction isn't actually applied. There is no way to map custom degamma in DCE, theref

[PATCH v2] drm/i915/mtl: Add Wa_14017073508 for SAMedia

2022-11-03 Thread Badal Nilawar
This workaround is added for Media tile of MTL A step. It is to help pcode workaround which handles the hardware issue seen during package C2/C3 transitions due to RC6 entry/exit transitions on Media tile. As a part of workaround pcode expect kmd to send mailbox message "media busy" when components

Re: [PATCH 1/2] component: Add helper for device nodes

2022-11-03 Thread Mark Brown
On Thu, Nov 03, 2022 at 02:22:21PM -0400, Sean Anderson wrote: > There is a common case where component_patch_add_release is called with > component_release_of/component_compare_of and a device node. Add a > helper and convert existing users. The usual pattern here would be to split adding the he

Re: [PATCH] drm: rcar_du: DRM_RCAR_DU optionally depends on RCAR_MIPI_DSI

2022-11-03 Thread Javier Martinez Canillas
On 11/3/22 17:26, Randy Dunlap wrote: [...] >> >> Randy, I think that it's more idiomatic though to it express as following: >> >> depends on DRM_RCAR_MIPI_DSI || !DRM_RCAR_MIPI_DSI > > I count just over 200 of each idiom (but my grep strings could be > too crude). I guess that you want a v2 wit

[PATCH 2/2] drm: Convert users of drm_of_component_match_add to component_match_add_of

2022-11-03 Thread Sean Anderson
Every user of this function either uses component_compare_of or something equivalent. Most of them immediately put the device node as well. Convert these users to component_match_add_of and remove drm_of_component_match_add. Signed-off-by: Sean Anderson --- .../gpu/drm/arm/display/komeda/komeda

[PATCH 0/2] drm: Add component_match_add_of and convert users of drm_of_component_match_add

2022-11-03 Thread Sean Anderson
This series adds a new function component_match_add_of to simplify the common case of calling component_match_add_release with component_release_of and component_compare_of. There is already drm_of_component_match_add, which allows for a custom compare function. However, all existing users just use

[PATCH 1/2] component: Add helper for device nodes

2022-11-03 Thread Sean Anderson
There is a common case where component_patch_add_release is called with component_release_of/component_compare_of and a device node. Add a helper and convert existing users. Signed-off-by: Sean Anderson --- drivers/iommu/mtk_iommu.c| 3 +-- drivers/iommu/mtk_iommu_v1.c | 3 +-- include/linu

Re: [PATCH v7 07/10] drm: bridge: samsung-dsim: Add atomic_get_input_bus_fmts

2022-11-03 Thread Jagan Teki
On Thu, Nov 3, 2022 at 9:56 PM Marek Vasut wrote: > > On 11/3/22 10:39, Jagan Teki wrote: > > On Sun, Oct 16, 2022 at 3:31 AM Marek Vasut wrote: > >> > >> On 10/5/22 17:13, Jagan Teki wrote: > >> > >> [...] > >> > >>> @@ -1321,6 +1322,32 @@ static void > >>> samsung_dsim_atomic_post_disable(stru

Re: [PATCH 1/9] drm/i915: Use kmap_local_page() in gem/i915_gem_object.c

2022-11-03 Thread Ira Weiny
On Sat, Oct 29, 2022 at 01:17:03PM +0200, Fabio M. De Francesco wrote: > On lunedì 17 ottobre 2022 11:37:17 CEST Zhao Liu wrote: > > From: Zhao Liu > > > > The use of kmap_atomic() is being deprecated in favor of > > kmap_local_page()[1]. > > > > The main difference between atomic and local mapp

Re: [PATCH 3/9] drm/i915: Use kmap_local_page() in gem/i915_gem_shmem.c

2022-11-03 Thread Ira Weiny
On Mon, Oct 17, 2022 at 05:37:19PM +0800, Zhao Liu wrote: > From: Zhao Liu > > The use of kmap_atomic() is being deprecated in favor of > kmap_local_page()[1]. > > The main difference between atomic and local mappings is that local > mappings doesn't disable page faults or preemption. > > In dr

Re: [PATCH] drm: rcar_du: DRM_RCAR_DU optionally depends on RCAR_MIPI_DSI

2022-11-03 Thread Randy Dunlap
Hi, On 11/3/22 04:53, Javier Martinez Canillas wrote: > Hello Kieran, > > On 11/3/22 11:59, Kieran Bingham wrote: >> Hi Randy, >> >> Quoting Randy Dunlap (2022-11-03 06:06:45) >>> ping. I have verified (on linux-next-20221103) that this is still needed. &

Re: [PATCH v7 07/10] drm: bridge: samsung-dsim: Add atomic_get_input_bus_fmts

2022-11-03 Thread Marek Vasut
On 11/3/22 08:40, Jagan Teki wrote: On Mon, Oct 17, 2022 at 12:54 PM Marek Vasut wrote: On 10/17/22 05:58, Jagan Teki wrote: On Sun, Oct 16, 2022 at 3:31 AM Marek Vasut wrote: On 10/5/22 17:13, Jagan Teki wrote: [...] @@ -1321,6 +1322,32 @@ static void samsung_dsim_atomic_post_disable(s

Re: [PATCH v7 07/10] drm: bridge: samsung-dsim: Add atomic_get_input_bus_fmts

2022-11-03 Thread Marek Vasut
On 11/3/22 10:39, Jagan Teki wrote: On Sun, Oct 16, 2022 at 3:31 AM Marek Vasut wrote: On 10/5/22 17:13, Jagan Teki wrote: [...] @@ -1321,6 +1322,32 @@ static void samsung_dsim_atomic_post_disable(struct drm_bridge *bridge, pm_runtime_put_sync(dsi->dev); } +#define MAX_INPUT_SEL

Re: [PATCH v7 1/2] dt-bindings: it6505: add properties to restrict output bandwidth

2022-11-03 Thread Krzysztof Kozlowski
On 03/11/2022 05:12, allen wrote: > From: allen chen > > Currently there are no "upstream" users. So, no existing users to break. > Add properties to restrict dp output data-lanes and clock. > > Signed-off-by: Pin-Yen Lin > Signed-off-by: Allen Chen Reviewed-by: Krzysztof Kozlowski Best re

[PATCH] drm: sti: Make array en_di static const

2022-11-03 Thread Colin Ian King
Don't populate the read-only array en_di on the stack but instead make it static. Also makes the object code a little smaller. Signed-off-by: Colin Ian King --- drivers/gpu/drm/sti/sti_hdmi.c | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/sti/sti_h

Re: [PATCH v2 02/12] dt-bindings: display: mediatek: add MT8195 hdmi bindings

2022-11-03 Thread Krzysztof Kozlowski
On 03/11/2022 11:17, Guillaume Ranquet wrote: > On Thu, 03 Nov 2022 13:45, Krzysztof Kozlowski >>> This is an i2c adapter, not a device. >>> And as it lives inside the HDMI hw block, I've omitted using an address >>> here. >>> >>> Is this valid? or should this be expressed differently? >> >> What

KUnit issues - Was: [igt-dev] [PATCH RFC v2 8/8] drm/i915: check if current->mm is not NULL

2022-11-03 Thread Mauro Carvalho Chehab
Hi, I'm facing a couple of issues when testing KUnit with the i915 driver. The DRM subsystem and the i915 driver has, for a long time, his own way to do unit tests, which seems to be added before KUnit. I'm now checking if it is worth start using KUnit at i915. So, I wrote a RFC with some patche

[PATCH v3 15/23] drm/fb-helper: Disconnect damage worker from update logic

2022-11-03 Thread Thomas Zimmermann
The fbdev helpers implement a damage worker that forwards fbdev updates to the DRM driver. The worker's update logic depends on the generic fbdev emulation. Separate the two via function pointer. The generic fbdev emulation sets struct drm_fb_helper_funcs.fb_dirty, a new callback that hides the up

  1   2   >