Re: [PATCH 3/3] drm/vc4: dsi: Switch to devm_drm_of_get_bridge

2021-09-14 Thread Maxime Ripard
Hi, On Sun, Sep 12, 2021 at 09:46:46PM +0200, Sam Ravnborg wrote: > On Fri, Sep 10, 2021 at 03:09:41PM +0200, Maxime Ripard wrote: > > The new devm_drm_of_get_bridge removes most of the boilerplate we > > have to deal with. Let's switch to it. > > > > Signed-off-

[PATCH v2 0/3] clk: Implement a clock request API

2021-09-14 Thread Maxime Ripard
v5.15-rc1 Dom Cobley (1): drm/vc4: hvs: Convert to the new clock request API Maxime Ripard (2): clk: Introduce a clock request API drm/vc4: hdmi: Convert to the new clock request API drivers/clk/clk.c | 126 + drivers/gpu/drm/vc4/vc4_hd

[PATCH v2 1/3] clk: Introduce a clock request API

2021-09-14 Thread Maxime Ripard
ll the requests are done. * Similarly, clk_round_rate has been adjusted to take the requests into account and return a rate that will be greater or equal to the requested rates. Signed-off-by: Maxime Ripard --- drivers/clk/clk.c | 126 include/li

[PATCH v2 2/3] drm/vc4: hdmi: Convert to the new clock request API

2021-09-14 Thread Maxime Ripard
The new clock request API allows us to increase the rate of the HSM clock to match our pixel rate requirements while decreasing it when we're done, resulting in a better power-efficiency. Signed-off-by: Maxime Ripard --- drivers/gpu/drm/vc4/vc4_hdmi.c | 15 ++- drivers/gpu/dr

[PATCH v2 3/3] drm/vc4: hvs: Convert to the new clock request API

2021-09-14 Thread Maxime Ripard
From: Dom Cobley The new clock request API allows us to increase the rate of the core clock as required during mode set while decreasing it when we're done, resulting in a better power-efficiency. Signed-off-by: Dom Cobley Signed-off-by: Maxime Ripard --- drivers/gpu/drm/vc4/vc4_kms.

[PATCH v2 1/3] drm/probe-helper: Document drm_helper_hpd_irq_event() return value

2021-09-14 Thread Maxime Ripard
The documentation of the drm_helper_hpd_irq_event() function didn't document the value that function was returning. Add that part as well. Signed-off-by: Maxime Ripard --- Changes from v2: - new patch --- drivers/gpu/drm/drm_probe_helper.c | 3 +++ 1 file changed, 3 insertions(+)

[PATCH v2 2/3] drm/probe-helper: Create a HPD IRQ event helper for a single connector

2021-09-14 Thread Maxime Ripard
ation for each connector or use that helper and iterate over all connectors all the time. Since both are suboptimal, let's create a helper that will only perform the status detection on a single connector. Signed-off-by: Maxime Ripard --- Changes from v2: - Skip connectors with DRM_CONNECTO

[PATCH v2 3/3] drm/vc4: hdmi: Actually check for the connector status in hotplug

2021-09-14 Thread Maxime Ripard
) if it was enabled it has a side effect, and an application such as Kodi or modetest doesn't deal with hotplug events. This resulted with a black screen when Kodi or modetest was running when a screen was disconnected and then reconnected, or switched off and on. Signed-off-by: Maxime Ri

Re: [PATCH v4 02/24] drm/bridge: Document the probe issue with MIPI-DSI bridges

2021-09-14 Thread Maxime Ripard
Hi, On Mon, Sep 13, 2021 at 08:29:37AM +0200, Andrzej Hajda wrote: > > W dniu 10.09.2021 o 12:11, Maxime Ripard pisze: > > Interactions between bridges, panels, MIPI-DSI host and the component > > framework are not trivial and can lead to probing issues when > > imple

Re: [PATCH v2 3/3] drm/vc4: hdmi: Actually check for the connector status in hotplug

2021-09-14 Thread Maxime Ripard
Hi Daniel, On Tue, Sep 14, 2021 at 04:34:08PM +0200, Daniel Vetter wrote: > On Tue, Sep 14, 2021 at 12:17:24PM +0200, Maxime Ripard wrote: > > The drm_helper_hpd_irq_event() documentation states that this function > > is "useful for drivers which can't or don'

Re: [PATCH v2 2/3] drm/probe-helper: Create a HPD IRQ event helper for a single connector

2021-09-14 Thread Maxime Ripard
Hi Sam, On Tue, Sep 14, 2021 at 12:41:55PM +0200, Sam Ravnborg wrote: > On Tue, Sep 14, 2021 at 12:17:23PM +0200, Maxime Ripard wrote: > > The drm_helper_hpd_irq_event() function is iterating over all the > > connectors when an hotplug event is detected. > > > > Dur

[PULL] drm-misc-next

2021-09-16 Thread Maxime Ripard
ove obsolete DRM Support for ZTE SoCs drm: omap: remove obsolete selection of OMAP2_DSS in config DRM_OMAP Markuss Broks (2): drm/panel: Add DT bindings for Samsung S6D27A1 display panel drm/panel: s6d27a1: Add driver for Samsung S6D27A1 display panel Maxime Ripard (5): Me

Re: [PATCH] drm/sun4i: dw-hdmi: Make use of the helper function dev_err_probe()

2021-09-16 Thread Maxime Ripard
On Thu, Sep 16, 2021 at 06:56:32PM +0800, Cai Huoqing wrote: > When possible use dev_err_probe help to properly deal with the > PROBE_DEFER error, the benefit is that DEFER issue will be logged > in the devices_deferred debugfs file. > And using dev_err_probe() can reduce code size, the error value

Re: [PATCH] drm/sun4i: dsi: Make use of the helper function dev_err_probe()

2021-09-16 Thread Maxime Ripard
On Thu, Sep 16, 2021 at 06:56:24PM +0800, Cai Huoqing wrote: > When possible use dev_err_probe help to properly deal with the > PROBE_DEFER error, the benefit is that DEFER issue will be logged > in the devices_deferred debugfs file. > And using dev_err_probe() can reduce code size, the error value

Re: [PATCH v2] drm/sun4i: dw-hdmi: Fix HDMI PHY clock setup

2021-09-16 Thread Maxime Ripard
On Wed, Sep 15, 2021 at 07:58:36PM +0200, Jernej Skrabec wrote: > Recent rework, which made HDMI PHY driver a platform device, inadvertely > reversed clock setup order. HW is very touchy about it. Proper way is to > handle controllers resets and clocks first and HDMI PHYs second. > > Currently, wi

Re: [PATCH v6 4/6] drm/sprd: add Unisoc's drm display controller driver

2021-09-17 Thread Maxime Ripard
Hi, On Fri, Aug 13, 2021 at 10:53:00PM +0800, Kevin Tang wrote: > Adds DPU(Display Processor Unit) support for the Unisoc's display > subsystem. > It's support multi planes, scaler, rotation, PQ(Picture Quality) and more. > > v2: > - Use drm_xxx to replace all DRM_XXX. > - Use kzalloc to repl

Re: [PATCH v6 6/6] drm/sprd: add Unisoc's drm mipi dsi&dphy driver

2021-09-17 Thread Maxime Ripard
On Fri, Aug 13, 2021 at 10:53:02PM +0800, Kevin Tang wrote: > Adds dsi host controller support for the Unisoc's display subsystem. > Adds dsi phy support for the Unisoc's display subsystem. > Only MIPI DSI Displays supported, DP/TV/HMDI will be support > in the feature. > > v1: > - Remove dphy a

Re: [PATCH v2 3/4] dt-bindings: drm/bridge: ti-sn65dsi83: Add vcc supply bindings

2021-10-13 Thread Maxime Ripard
Hi, On Tue, Oct 12, 2021 at 08:48:42AM +0200, Alexander Stein wrote: > Add a VCC regulator which needs to be enabled before the EN pin is > released. > > Reviewed-by: Sam Ravnborg > Signed-off-by: Alexander Stein > --- > .../devicetree/bindings/display/bridge/ti,sn65dsi83.yaml | 5 + >

Re: (subset) [PATCH] drm/vc4: crtc: Make sure the HDMI controller is powered when disabling

2021-10-13 Thread Maxime Ripard
On Thu, 23 Sep 2021 20:50:13 +0200, Maxime Ripard wrote: > Since commit 875a4d536842 ("drm/vc4: drv: Disable the CRTC at boot > time"), during the initial setup of the driver we call into the VC4 HDMI > controller hooks to make sure the controller is properly disabled. > &g

Re: [PATCH v4 00/24] drm/bridge: Make panel and bridge probe order consistent

2021-10-13 Thread Maxime Ripard
Hi John, On Wed, Sep 29, 2021 at 04:29:42PM -0700, John Stultz wrote: > On Wed, Sep 29, 2021 at 2:51 PM John Stultz wrote: > > > > On Wed, Sep 29, 2021 at 2:32 PM John Stultz wrote: > > > On Wed, Sep 29, 2021 at 2:27 PM John Stultz > > > wrote: > > >

Re: [PATCH v4 00/24] drm/bridge: Make panel and bridge probe order consistent

2021-10-13 Thread Maxime Ripard
; > > > > > > > On Wed, Sep 29, 2021 at 2:32 PM John Stultz > > > > wrote: > > > > > On Wed, Sep 29, 2021 at 2:27 PM John Stultz > > > > > wrote: > > > > > > On Fri, Sep 10, 2021 at 3:12 AM Maxime Ripard &

Re: Regression with mainline kernel on rpi4

2021-10-13 Thread Maxime Ripard
On Thu, Sep 30, 2021 at 11:19:59AM +0200, Daniel Vetter wrote: > On Tue, Sep 28, 2021 at 10:34:46AM +0200, Maxime Ripard wrote: > > Hi Daniel, > > > > On Sat, Sep 25, 2021 at 12:50:17AM +0200, Daniel Vetter wrote: > > > On Fri, Sep 24, 2021 at 3:30 PM Maxime Ripard

Re: [PATCH v2 3/4] dt-bindings: drm/bridge: ti-sn65dsi83: Add vcc supply bindings

2021-10-14 Thread Maxime Ripard
On Wed, Oct 13, 2021 at 12:37:47PM +0300, Laurent Pinchart wrote: > Hi Maxime, > > On Wed, Oct 13, 2021 at 09:47:22AM +0200, Maxime Ripard wrote: > > On Tue, Oct 12, 2021 at 08:48:42AM +0200, Alexander Stein wrote: > > > Add a VCC regulator which needs to be enab

[PULL] drm-misc-next

2021-10-14 Thread Maxime Ripard
Hi Dave, Daniel, Here's this week drm-misc-next PR Maxime drm-misc-next-2021-10-14: drm-misc-next for 5.16: UAPI Changes: Cross-subsystem Changes: Core Changes: - fbdev: Fix double-free, Remove unused scrolling acceleration - locking: improve logging for contented locks without backoff

Re: [PATCH v3 5/6] drm/probe-helper: use drm_kms_helper_connector_hotplug_event

2021-10-18 Thread Maxime Ripard
Hi Simon, On Fri, Oct 15, 2021 at 04:33:45PM +, Simon Ser wrote: > If an hotplug event only updates a single connector, use > drm_kms_helper_connector_hotplug_event instead of > drm_kms_helper_hotplug_event. > > Signed-off-by: Simon Ser I guess we'd also need to update drm_connector_helper_

Re: [PATCH 1/3] drm/dp: add helpers to read link training delays

2021-10-18 Thread Maxime Ripard
Hi Jani, On Fri, Oct 15, 2021 at 06:21:35PM +0300, Jani Nikula wrote: > On Thu, 14 Oct 2021, Jani Nikula wrote: > > The link training delays are different and/or available in different > > DPCD offsets depending on: > > > > - Clock recovery vs. channel equalization > > - DPRX vs. LTTPR > > - 128b

Re: [Freedreno] [PATCH v4 00/24] drm/bridge: Make panel and bridge probe order consistent

2021-10-18 Thread Maxime Ripard
Hi Rob, On Wed, Oct 13, 2021 at 05:16:58PM -0700, Rob Clark wrote: > On Wed, Oct 13, 2021 at 7:16 AM Maxime Ripard wrote: > > > > Hi Caleb, > > > > On Thu, Sep 30, 2021 at 09:20:52PM +0100, Caleb Connolly wrote: > > > Hi, > > > > > > On 3

Re: [PATCH v2 3/4] dt-bindings: drm/bridge: ti-sn65dsi83: Add vcc supply bindings

2021-10-18 Thread Maxime Ripard
On Sat, Oct 16, 2021 at 05:34:59AM +0300, Laurent Pinchart wrote: > On Thu, Oct 14, 2021 at 09:41:10AM +0200, Maxime Ripard wrote: > > On Wed, Oct 13, 2021 at 12:37:47PM +0300, Laurent Pinchart wrote: > > > On Wed, Oct 13, 2021 at 09:47:22AM +0200, Maxime Ripard wrote: > >

Re: [PATCH v2 3/4] dt-bindings: drm/bridge: ti-sn65dsi83: Add vcc supply bindings

2021-10-19 Thread Maxime Ripard
Hi On Mon, Oct 18, 2021 at 08:48:52PM +0300, Laurent Pinchart wrote: > Hi Maxime, > > On Mon, Oct 18, 2021 at 05:20:13PM +0200, Maxime Ripard wrote: > > On Sat, Oct 16, 2021 at 05:34:59AM +0300, Laurent Pinchart wrote: > > > On Thu, Oct 14, 2021 at 09:41:10AM +0

Re: [PULL] topic/drm-dp-training-delay-helpers for drm-misc-next and drm-intel-next

2021-10-19 Thread Maxime Ripard
On Tue, Oct 19, 2021 at 12:59:57PM +0300, Jani Nikula wrote: > > Hi all - > > These are the drm dp helpers for figuring out link training delays, to > be pulled to both drm-misc-next and drm-intel-next. > > > topic/drm-dp-training-delay-helpers-2021-10-19: > Core Changes: > - drm dp helpers for

Re: [PATCH v4 5/6] drm/probe-helper: use drm_kms_helper_connector_hotplug_event

2021-10-19 Thread Maxime Ripard
e, Sam) > - Update drm_connector_helper_hpd_irq_event (Maxime) > > Signed-off-by: Simon Ser > Cc: Ville Syrjala > Cc: Sam Ravnborg > Cc: Maxime Ripard Reviewed-by: Maxime Ripard Thanks! Maxime signature.asc Description: PGP signature

[PATCH v5 00/21] drm/bridge: Make panel and bridge probe order consistent

2021-10-21 Thread Maxime Ripard
ch and _detach succeed when no callback is there Maxime Ripard (20): drm/bridge: adv7533: Switch to devm MIPI-DSI helpers drm/bridge: adv7511: Register and attach our DSI device at probe drm/bridge: anx7625: Switch to devm MIPI-DSI helpers drm/bridge: anx7625: Register and attach our DSI device

[PATCH v5 01/21] drm/bridge: adv7533: Switch to devm MIPI-DSI helpers

2021-10-21 Thread Maxime Ripard
Let's switch to the new devm MIPI-DSI function to register and attach our secondary device. This also avoids leaking the device when we detach the bridge. Acked-by: Sam Ravnborg Tested-by: John Stultz Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/adv7511/adv7511.h

[PATCH v5 02/21] drm/bridge: adv7511: Register and attach our DSI device at probe

2021-10-21 Thread Maxime Ripard
In order to avoid any probe ordering issue, the best practice is to move the secondary MIPI-DSI device registration and attachment to the MIPI-DSI host at probe time. Let's do this. Acked-by: Sam Ravnborg Tested-by: John Stultz Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/ad

[PATCH v5 03/21] drm/bridge: anx7625: Switch to devm MIPI-DSI helpers

2021-10-21 Thread Maxime Ripard
Let's switch to the new devm MIPI-DSI function to register and attach our secondary device. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/analogix/anx7625.c | 20 +--- 1 file changed, 5 insertions(+), 15 deletions(-) diff --git a/driver

[PATCH v5 04/21] drm/bridge: anx7625: Register and attach our DSI device at probe

2021-10-21 Thread Maxime Ripard
In order to avoid any probe ordering issue, the best practice is to move the secondary MIPI-DSI device registration and attachment to the MIPI-DSI host at probe time. Let's do this. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/analogix/anx7625.c

[PATCH v5 05/21] drm/bridge: lt8912b: Switch to devm MIPI-DSI helpers

2021-10-21 Thread Maxime Ripard
Let's switch to the new devm MIPI-DSI function to register and attach our secondary device. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/lontium-lt8912b.c | 20 1 file changed, 4 insertions(+), 16 deletions(-) diff --git a/drivers/gp

[PATCH v5 06/21] drm/bridge: lt8912b: Register and attach our DSI device at probe

2021-10-21 Thread Maxime Ripard
In order to avoid any probe ordering issue, the best practice is to move the secondary MIPI-DSI device registration and attachment to the MIPI-DSI host at probe time. Let's do this. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/lontium-lt8912b.c

[PATCH v5 07/21] drm/bridge: lt9611: Switch to devm MIPI-DSI helpers

2021-10-21 Thread Maxime Ripard
Let's switch to the new devm MIPI-DSI function to register and attach our secondary device. Acked-by: Sam Ravnborg Tested-by: John Stultz Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/lontium-lt9611.c | 24 1 file changed, 4 insertions(+), 20 dele

[PATCH v5 08/21] drm/bridge: lt9611: Register and attach our DSI device at probe

2021-10-21 Thread Maxime Ripard
In order to avoid any probe ordering issue, the best practice is to move the secondary MIPI-DSI device registration and attachment to the MIPI-DSI host at probe time. Let's do this. Acked-by: Sam Ravnborg Tested-by: John Stultz Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/lo

[PATCH v5 09/21] drm/bridge: lt9611uxc: Switch to devm MIPI-DSI helpers

2021-10-21 Thread Maxime Ripard
Let's switch to the new devm MIPI-DSI function to register and attach our secondary device. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/lontium-lt9611uxc.c | 38 +- 1 file changed, 8 insertions(+), 30 deletions(-) diff --git a/driver

[PATCH v5 10/21] drm/bridge: lt9611uxc: Register and attach our DSI device at probe

2021-10-21 Thread Maxime Ripard
In order to avoid any probe ordering issue, the best practice is to move the secondary MIPI-DSI device registration and attachment to the MIPI-DSI host at probe time. Let's do this. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/lontium-lt9611uxc.c

[PATCH v5 11/21] drm/bridge: ps8640: Switch to devm MIPI-DSI helpers

2021-10-21 Thread Maxime Ripard
Let's switch to the new devm MIPI-DSI function to register and attach our secondary device. This also avoids leaking the device on removal. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/parade-ps8640.c | 15 +-- 1 file changed, 5 insertions(+

[PATCH v5 12/21] drm/bridge: ps8640: Register and attach our DSI device at probe

2021-10-21 Thread Maxime Ripard
In order to avoid any probe ordering issue, the best practice is to move the secondary MIPI-DSI device registration and attachment to the MIPI-DSI host at probe time. Let's do this. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/parade-ps8640.c

[PATCH v5 13/21] drm/bridge: sn65dsi83: Fix bridge removal

2021-10-21 Thread Maxime Ripard
ld thus be removed as part of its remove callback. Cc: Marek Vasut Fixes: 24417d5b0c00 ("drm/bridge: ti-sn65dsi83: Implement .detach callback") Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/ti-sn65dsi83.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dr

[PATCH v5 14/21] drm/bridge: sn65dsi83: Switch to devm MIPI-DSI helpers

2021-10-21 Thread Maxime Ripard
Let's switch to the new devm MIPI-DSI function to register and attach our secondary device. This also avoids leaking the device when we detach the bridge but don't remove its driver. Acked-by: Sam Ravnborg Tested-by: Laurent Pinchart Signed-off-by: Maxime Ripard --- drivers/gpu/drm

[PATCH v5 15/21] drm/bridge: sn65dsi83: Register and attach our DSI device at probe

2021-10-21 Thread Maxime Ripard
In order to avoid any probe ordering issue, the best practice is to move the secondary MIPI-DSI device registration and attachment to the MIPI-DSI host at probe time. Let's do this. Acked-by: Sam Ravnborg Tested-by: Laurent Pinchart Signed-off-by: Maxime Ripard --- drivers/gpu/drm/brid

[PATCH v5 16/21] drm/bridge: sn65dsi86: Switch to devm MIPI-DSI helpers

2021-10-21 Thread Maxime Ripard
Let's switch to the new devm MIPI-DSI function to register and attach our secondary device. This also avoids leaking the device when we detach the bridge. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/ti-sn65dsi86.c | 22 +++--- 1 file ch

[PATCH v5 17/21] drm/bridge: sn65dsi86: Register and attach our DSI device at probe

2021-10-21 Thread Maxime Ripard
In order to avoid any probe ordering issue, the best practice is to move the secondary MIPI-DSI device registration and attachment to the MIPI-DSI host at probe time. Let's do this. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/ti-sn65dsi86.c

[PATCH v5 18/21] drm/bridge: tc358775: Switch to devm MIPI-DSI helpers

2021-10-21 Thread Maxime Ripard
Let's switch to the new devm MIPI-DSI function to register and attach our secondary device. This also avoids leaking the device when we detach the bridge. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/tc358775.c | 13 - 1 file changed, 4 inser

[PATCH v5 19/21] drm/bridge: tc358775: Register and attach our DSI device at probe

2021-10-21 Thread Maxime Ripard
In order to avoid any probe ordering issue, the best practice is to move the secondary MIPI-DSI device registration and attachment to the MIPI-DSI host at probe time. Let's do this. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/tc358775.c

[PATCH v5 21/21] drm/msm/dsi: Adjust probe order

2021-10-21 Thread Maxime Ripard
From: Rob Clark Switch to the documented order dsi-host vs bridge probe. Tested-by: Amit Pundir Tested-by: Caleb Connolly Tested-by: John Stultz Signed-off-by: Rob Clark Signed-off-by: Maxime Ripard --- drivers/gpu/drm/msm/dsi/dsi.c | 50 --- drivers/gpu

[PATCH v5 20/21] drm/kirin: dsi: Adjust probe order

2021-10-21 Thread Maxime Ripard
following the same conventions, resulting in various incompatibilities between DSI hosts and devices. Now that we have a sequence agreed upon and documented, let's convert kirin to it. Tested-by: John Stultz Signed-off-by: Maxime Ripard --- drivers/gpu/drm/hisilicon/kirin/dw_drm_dsi.c

Re: [PATCH v5 1/7] of: Make of_graph_get_port_by_id take a const device_node

2021-10-21 Thread Maxime Ripard
On Tue, Oct 19, 2021 at 03:02:13PM +0300, Laurent Pinchart wrote: > Hi Maxime, > > Thank you for the patch. > > On Wed, Sep 29, 2021 at 10:42:28AM +0200, Maxime Ripard wrote: > > of_graph_get_port_by_id doesn't modify the device_node pointer it takes > > as a

Re: (subset) [PATCH] drm/sun4i: virtual CMA addresses are not needed

2021-10-21 Thread Maxime Ripard
On Tue, 19 Oct 2021 20:10:28 +0200, Jernej Skrabec wrote: > Driver never uses virtual address of DRM CMA buffers. Switch to CMA > helpers which don't deal with virtual mapping. > > This was actually already the case before commit ad408c766cef > ("drm/sun4i: Use DRM_GEM_CMA_VMAP_DRIVER_OPS for GEM

Re: [PATCH v6 6/6] drm/sprd: add Unisoc's drm mipi dsi&dphy driver

2021-10-21 Thread Maxime Ripard
Hi, On Wed, Oct 20, 2021 at 06:09:32PM +0800, Kevin Tang wrote: > Maxime Ripard 于2021年9月28日周二 下午5:28写道: > > > > > +static int sprd_dsi_find_panel(struct sprd_dsi *dsi) > > > > > +{ > > > > > + struct device *dev = dsi->host.dev; &g

Re: [PATCH v2 3/7] drm/bridge: Add drm_atomic_get_new_crtc_for_bridge() helper

2021-10-22 Thread Maxime Ripard
dated description, fixed kernel-doc and exported the symbol > > Signed-off-by: Sam Ravnborg > Suggested-by: Laurent Pinchart > Cc: Laurent Pinchart > Cc: Maarten Lankhorst > Cc: Maxime Ripard > Cc: Thomas Zimmermann > Cc: Andrzej Hajda > Cc: Neil Armstrong > Cc: Ro

[PATCH 0/9] drm/vc4: Introduce locking and remove !KMS state access

2021-10-25 Thread Maxime Ripard
hat you think, Maxime Maxime Ripard (9): drm/vc4: crtc: Drop feed_txp from state drm/vc4: Fix non-blocking commit getting stuck forever drm/vc4: crtc: Copy assigned channel to the CRTC drm/vc4: hdmi: Add a spinlock to protect register access drm/vc4: hdmi: Use a mutex to prevent concurr

[PATCH 1/9] drm/vc4: crtc: Drop feed_txp from state

2021-10-25 Thread Maxime Ripard
in struct vc4_crtc if we happen to be the TXP, and drop the flag from our private state structure. Link: https://lore.kernel.org/all/YWgteNaNeaS9uWDe@phenom.ffwll.local/ Fixes: 008095e065a8 ("drm/vc4: Add support for the transposer block") Signed-off-by: Maxime Ripard --- driver

[PATCH 4/9] drm/vc4: hdmi: Add a spinlock to protect register access

2021-10-25 Thread Maxime Ripard
rotect the register access of the HDMI controller. Fixes: c8b75bca92cb ("drm/vc4: Add KMS support for Raspberry Pi.") Signed-off-by: Maxime Ripard --- drivers/gpu/drm/vc4/vc4_hdmi.c | 202 ++-- drivers/gpu/drm/vc4/vc4_hdmi.h | 5 + drivers/gpu/drm/vc4/v

[PATCH 5/9] drm/vc4: hdmi: Use a mutex to prevent concurrent framework access

2021-10-25 Thread Maxime Ripard
looks like CEC should be able to recover from this if it was to happen. Fixes: bb7d78568814 ("drm/vc4: Add HDMI audio support") Signed-off-by: Maxime Ripard --- drivers/gpu/drm/vc4/vc4_hdmi.c | 118 +++-- drivers/gpu/drm/vc4/vc4_hdmi.h | 14 2 files chan

[PATCH 7/9] drm/vc4: hdmi: Check the device state in prepare()

2021-10-25 Thread Maxime Ripard
startup() to a helper and call it from prepare(). Fixes: 91e99e113929 ("drm/vc4: hdmi: Register HDMI codec") Signed-off-by: Maxime Ripard --- drivers/gpu/drm/vc4/vc4_hdmi.c | 35 +++--- 1 file changed, 28 insertions(+), 7 deletions(-) diff --git a/d

[PATCH 2/9] drm/vc4: Fix non-blocking commit getting stuck forever

2021-10-25 Thread Maxime Ripard
cal/ Fixes: 56d1fe0979dc ("drm/vc4: Make pageflip completion handling more robust.") Signed-off-by: Maxime Ripard --- drivers/gpu/drm/vc4/vc4_crtc.c | 5 - drivers/gpu/drm/vc4/vc4_drv.h | 14 ++ drivers/gpu/drm/vc4/vc4_hvs.c | 7 +-- 3 files changed, 23 insertion

[PATCH 3/9] drm/vc4: crtc: Copy assigned channel to the CRTC

2021-10-25 Thread Maxime Ripard
ffwll.local/ Fixes: 87ebcd42fb7b ("drm/vc4: crtc: Assign output to channel automatically") Signed-off-by: Maxime Ripard --- drivers/gpu/drm/vc4/vc4_crtc.c | 4 ++-- drivers/gpu/drm/vc4/vc4_drv.h | 9 + drivers/gpu/drm/vc4/vc4_hvs.c | 12 drivers/gpu/drm/vc4/vc4_t

[PATCH 6/9] drm/vc4: hdmi: Prevent access to crtc->state outside of KMS

2021-10-25 Thread Maxime Ripard
nce that part is shared between KMS and other paths, we need to protect it using our mutex. Link: https://lore.kernel.org/all/YWgteNaNeaS9uWDe@phenom.ffwll.local/ Fixes: bb7d78568814 ("drm/vc4: Add HDMI audio support") Signed-off-by: Maxime Ripard --- drivers/gpu/drm/v

[PATCH 8/9] drm/vc4: hdmi: Introduce an output_enabled flag

2021-10-25 Thread Maxime Ripard
in place now, let's just create a flag that we toggle to report whether the controller is currently enabled and use that instead of encoder->crtc in ALSA. Signed-off-by: Maxime Ripard --- drivers/gpu/drm/vc4/vc4_hdmi.c | 16 drivers/gpu/drm/vc4/vc4_hdmi.h | 6 ++ 2 f

[PATCH 9/9] drm/vc4: hdmi: Introduce a scdc_enabled flag

2021-10-25 Thread Maxime Ripard
s one user of our copy of the CRTC adjusted mode outside of KMS (since vc4_hdmi_disable_scrambling() might be called from the hotplug interrupt handler). It also removes our last user of the legacy encoder->crtc pointer. Signed-off-by: Maxime Ripard --- drivers/gpu/drm/vc4/vc

Re: Regression with mainline kernel on rpi4

2021-10-25 Thread Maxime Ripard
Hi, On Thu, Oct 14, 2021 at 03:15:36PM +0200, Daniel Vetter wrote: > On Wed, Oct 13, 2021 at 05:01:03PM +0200, Maxime Ripard wrote: > > On Thu, Sep 30, 2021 at 11:19:59AM +0200, Daniel Vetter wrote: > > > On Tue, Sep 28, 2021 at 10:34:46AM +0200, Maxime Ripard wrote:

[PATCH v6 01/21] drm/bridge: adv7533: Switch to devm MIPI-DSI helpers

2021-10-25 Thread Maxime Ripard
Let's switch to the new devm MIPI-DSI function to register and attach our secondary device. This also avoids leaking the device when we detach the bridge. Acked-by: Sam Ravnborg Tested-by: John Stultz Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/adv7511/adv7511.h

[PATCH v6 00/21] drm/bridge: Make panel and bridge probe order consistent

2021-10-25 Thread Maxime Ripard
were reverting that commit - Add some documentation - Make drm_panel_attach and _detach succeed when no callback is there Maxime Ripard (20): drm/bridge: adv7533: Switch to devm MIPI-DSI helpers drm/bridge: adv7511: Register and attach our DSI device at probe drm/bridge: anx7625: Switch

[PATCH v6 02/21] drm/bridge: adv7511: Register and attach our DSI device at probe

2021-10-25 Thread Maxime Ripard
In order to avoid any probe ordering issue, the best practice is to move the secondary MIPI-DSI device registration and attachment to the MIPI-DSI host at probe time. Let's do this. Acked-by: Sam Ravnborg Tested-by: John Stultz Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/ad

[PATCH v6 04/21] drm/bridge: anx7625: Register and attach our DSI device at probe

2021-10-25 Thread Maxime Ripard
In order to avoid any probe ordering issue, the best practice is to move the secondary MIPI-DSI device registration and attachment to the MIPI-DSI host at probe time. Let's do this. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/analogix/anx7625.c

[PATCH v6 05/21] drm/bridge: lt8912b: Switch to devm MIPI-DSI helpers

2021-10-25 Thread Maxime Ripard
Let's switch to the new devm MIPI-DSI function to register and attach our secondary device. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/lontium-lt8912b.c | 20 1 file changed, 4 insertions(+), 16 deletions(-) diff --git a/drivers/gp

[PATCH v6 03/21] drm/bridge: anx7625: Switch to devm MIPI-DSI helpers

2021-10-25 Thread Maxime Ripard
Let's switch to the new devm MIPI-DSI function to register and attach our secondary device. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/analogix/anx7625.c | 20 +--- 1 file changed, 5 insertions(+), 15 deletions(-) diff --git a/driver

[PATCH v6 08/21] drm/bridge: lt9611: Register and attach our DSI device at probe

2021-10-25 Thread Maxime Ripard
In order to avoid any probe ordering issue, the best practice is to move the secondary MIPI-DSI device registration and attachment to the MIPI-DSI host at probe time. Let's do this. Acked-by: Sam Ravnborg Tested-by: John Stultz Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/lo

[PATCH v6 07/21] drm/bridge: lt9611: Switch to devm MIPI-DSI helpers

2021-10-25 Thread Maxime Ripard
Let's switch to the new devm MIPI-DSI function to register and attach our secondary device. Acked-by: Sam Ravnborg Tested-by: John Stultz Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/lontium-lt9611.c | 24 1 file changed, 4 insertions(+), 20 dele

[PATCH v6 10/21] drm/bridge: lt9611uxc: Register and attach our DSI device at probe

2021-10-25 Thread Maxime Ripard
In order to avoid any probe ordering issue, the best practice is to move the secondary MIPI-DSI device registration and attachment to the MIPI-DSI host at probe time. Let's do this. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/lontium-lt9611uxc.c

[PATCH v6 09/21] drm/bridge: lt9611uxc: Switch to devm MIPI-DSI helpers

2021-10-25 Thread Maxime Ripard
Let's switch to the new devm MIPI-DSI function to register and attach our secondary device. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/lontium-lt9611uxc.c | 38 +- 1 file changed, 8 insertions(+), 30 deletions(-) diff --git a/driver

[PATCH v6 06/21] drm/bridge: lt8912b: Register and attach our DSI device at probe

2021-10-25 Thread Maxime Ripard
In order to avoid any probe ordering issue, the best practice is to move the secondary MIPI-DSI device registration and attachment to the MIPI-DSI host at probe time. Let's do this. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/lontium-lt8912b.c

[PATCH v6 17/21] drm/bridge: sn65dsi86: Register and attach our DSI device at probe

2021-10-25 Thread Maxime Ripard
In order to avoid any probe ordering issue, the best practice is to move the secondary MIPI-DSI device registration and attachment to the MIPI-DSI host at probe time. Let's do this. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/ti-sn65dsi86.c

[PATCH v6 15/21] drm/bridge: sn65dsi83: Register and attach our DSI device at probe

2021-10-25 Thread Maxime Ripard
In order to avoid any probe ordering issue, the best practice is to move the secondary MIPI-DSI device registration and attachment to the MIPI-DSI host at probe time. Let's do this. Acked-by: Sam Ravnborg Tested-by: Laurent Pinchart Signed-off-by: Maxime Ripard --- drivers/gpu/drm/brid

[PATCH v6 14/21] drm/bridge: sn65dsi83: Switch to devm MIPI-DSI helpers

2021-10-25 Thread Maxime Ripard
Let's switch to the new devm MIPI-DSI function to register and attach our secondary device. This also avoids leaking the device when we detach the bridge but don't remove its driver. Acked-by: Sam Ravnborg Tested-by: Laurent Pinchart Signed-off-by: Maxime Ripard --- drivers/gpu/drm

[PATCH v6 12/21] drm/bridge: ps8640: Register and attach our DSI device at probe

2021-10-25 Thread Maxime Ripard
In order to avoid any probe ordering issue, the best practice is to move the secondary MIPI-DSI device registration and attachment to the MIPI-DSI host at probe time. Let's do this. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/parade-ps8640.c

[PATCH v6 16/21] drm/bridge: sn65dsi86: Switch to devm MIPI-DSI helpers

2021-10-25 Thread Maxime Ripard
Let's switch to the new devm MIPI-DSI function to register and attach our secondary device. This also avoids leaking the device when we detach the bridge. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/ti-sn65dsi86.c | 22 +++--- 1 file ch

[PATCH v6 13/21] drm/bridge: sn65dsi83: Fix bridge removal

2021-10-25 Thread Maxime Ripard
ld thus be removed as part of its remove callback. Acked-by: Sam Ravnborg Reviewed-by: Marek Vasut Fixes: 24417d5b0c00 ("drm/bridge: ti-sn65dsi83: Implement .detach callback") Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/ti-sn65dsi83.c | 2 +- 1 file changed, 1 insertion(+),

[PATCH v6 11/21] drm/bridge: ps8640: Switch to devm MIPI-DSI helpers

2021-10-25 Thread Maxime Ripard
Let's switch to the new devm MIPI-DSI function to register and attach our secondary device. This also avoids leaking the device on removal. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/parade-ps8640.c | 15 +-- 1 file changed, 5 insertions(+

[PATCH v6 18/21] drm/bridge: tc358775: Switch to devm MIPI-DSI helpers

2021-10-25 Thread Maxime Ripard
Let's switch to the new devm MIPI-DSI function to register and attach our secondary device. This also avoids leaking the device when we detach the bridge. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/tc358775.c | 13 - 1 file changed, 4 inser

[PATCH v6 21/21] drm/msm/dsi: Adjust probe order

2021-10-25 Thread Maxime Ripard
From: Rob Clark Switch to the documented order dsi-host vs bridge probe. Tested-by: Amit Pundir Tested-by: Caleb Connolly Tested-by: John Stultz Signed-off-by: Rob Clark Signed-off-by: Maxime Ripard --- drivers/gpu/drm/msm/dsi/dsi.c | 50 --- drivers/gpu

[PATCH v6 19/21] drm/bridge: tc358775: Register and attach our DSI device at probe

2021-10-25 Thread Maxime Ripard
In order to avoid any probe ordering issue, the best practice is to move the secondary MIPI-DSI device registration and attachment to the MIPI-DSI host at probe time. Let's do this. Acked-by: Sam Ravnborg Signed-off-by: Maxime Ripard --- drivers/gpu/drm/bridge/tc358775.c

[PATCH v6 20/21] drm/kirin: dsi: Adjust probe order

2021-10-25 Thread Maxime Ripard
following the same conventions, resulting in various incompatibilities between DSI hosts and devices. Now that we have a sequence agreed upon and documented, let's convert kirin to it. Tested-by: John Stultz Signed-off-by: Maxime Ripard --- drivers/gpu/drm/hisilicon/kirin/dw_drm_dsi.c

Re: [PATCH v5 00/21] drm/bridge: Make panel and bridge probe order consistent

2021-10-25 Thread Maxime Ripard
Hi Sam, On Thu, Oct 21, 2021 at 05:22:55PM +0200, Sam Ravnborg wrote: > Hi Maxime, > > > Let me know what you think, > > apply the lot to drm-misc-next. Maybe wait for an r-b or a-b on the kirin > patch but the rest is IMO good to go. I had a compilation error since the rebase of the v4, so I s

[PATCH v8 00/10] drm/vc4: hdmi: Support the 4k @ 60Hz modes

2021-10-25 Thread Maxime Ripard
icate HDMI_14_MAX_TMDS_CLK define - Warn about enable_hdmi_4kp60 only if there's some modes that can't be reached - Rework the BVB clock computation Maxime Ripard (10): drm/vc4: hdmi: Remove the DDC probing for status detection drm/vc4: hdmi: Fix HPD GPIO detection

[PATCH v8 01/10] drm/vc4: hdmi: Remove the DDC probing for status detection

2021-10-25 Thread Maxime Ripard
both, the display during the HPD pulse will clear its scrambler status, and since we won't detect the disconnect/reconnect cycle we will never enable the scrambler back. As our main reason for that DDC probing is gone, let's just remove it. Signed-off-by: Maxime Ripard --- drivers/gp

[PATCH v8 04/10] drm/vc4: crtc: Add encoder to vc4_crtc_config_pv prototype

2021-10-25 Thread Maxime Ripard
vc4_crtc_config_pv() retrieves the encoder again, even though its only caller, vc4_crtc_atomic_enable(), already did. Pass the encoder pointer as an argument instead of going through all the connectors to retrieve it again. Signed-off-by: Maxime Ripard --- drivers/gpu/drm/vc4/vc4_crtc.c | 7

[PATCH v8 02/10] drm/vc4: hdmi: Fix HPD GPIO detection

2021-10-25 Thread Maxime Ripard
high, and would fall back to the other methods otherwise. Since we can read the EDIDs when the HPD signal is low on some displays, we changed the detection status from disconnected to connected, and we would ignore an HPD pulse. Fixes: 6800234ceee0 ("drm/vc4: hdmi: Convert to gpiod") S

[PATCH v8 03/10] drm/vc4: Make vc4_crtc_get_encoder public

2021-10-25 Thread Maxime Ripard
We'll need that function in vc4_kms to compute the core clock rate requirements. Signed-off-by: Maxime Ripard --- drivers/gpu/drm/vc4/vc4_crtc.c | 8 drivers/gpu/drm/vc4/vc4_drv.h | 5 + 2 files changed, 9 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/vc4/vc4_c

[PATCH v8 07/10] drm/vc4: Leverage the load tracker on the BCM2711

2021-10-25 Thread Maxime Ripard
against them, and prevent the debugfs file to enable it from being created. Signed-off-by: Maxime Ripard --- drivers/gpu/drm/vc4/vc4_debugfs.c | 7 +-- drivers/gpu/drm/vc4/vc4_drv.h | 3 --- drivers/gpu/drm/vc4/vc4_kms.c | 16 +--- drivers/gpu/drm/vc4/vc4_plane.c | 5 -

[PATCH v8 05/10] drm/vc4: crtc: Rework the encoder retrieval code (again)

2021-10-25 Thread Maxime Ripard
thus our encoder retrieval code will not match on anything. We can however simplify the code by using drm_for_each_encoder_mask, the drm_crtc_state storing the encoders a given CRTC is connected to directly and without relying on any other state. Signed-off-by: Maxime Ripard --- drivers/gpu/drm/vc4

[PATCH v8 06/10] drm/vc4: crtc: Add some logging

2021-10-25 Thread Maxime Ripard
The encoder retrieval code has been a source of bugs and glitches in the past and the crtc <-> encoder association been wrong in a number of different ways. Add some logging to quickly spot issues if they occur. Signed-off-by: Maxime Ripard --- drivers/gpu/drm/vc4/vc4_crtc.c | 6 ++

[PATCH v8 10/10] drm/vc4: Increase the core clock based on HVS load

2021-10-25 Thread Maxime Ripard
Depending on a given HVS output (HVS to PixelValves) and input (planes attached to a channel) load, the HVS needs for the core clock to be raised above its boot time default. Failing to do so will result in a vblank timeout and a stalled display pipeline. Signed-off-by: Maxime Ripard

<    4   5   6   7   8   9   10   11   12   13   >