Re: [Freedreno] [v2] drm/msm/disp/dpu1: set default group ID for CTL.

2021-10-29 Thread Stephen Boyd
Quoting Kalyan Thota (2021-10-29 05:30:19) > New required programming in CTL for SC7280. Group ID informs > HW of which VM owns that CTL. Force this group ID to > default/disabled until virtualization support is enabled in SW. > > Changes in v1: > - Fix documentation and add descritpion for the

Re: [Freedreno] [PATCH v3 6/6] drm/msm/dp: Remove the hpd init delay for eDP

2021-10-29 Thread khsieh
On 2021-10-27 23:38, Stephen Boyd wrote: Quoting Sankeerth Billakanti (2021-10-27 18:54:48) DP driver needs a 10 second delay before phy_init so that the usb combo phy initializes and sets up the necessary clocks for usb devices such as keyboard and mouse. eDP controller uses a standalone phy

Re: [Freedreno] [PATCH v3 12/14] dt-bindings: msm/dp: Add bindings for HDCP registers

2021-10-29 Thread Sean Paul
On Mon, Oct 04, 2021 at 02:58:41PM -0500, Bjorn Andersson wrote: > On Fri 01 Oct 10:11 CDT 2021, Sean Paul wrote: > > > From: Sean Paul > > > > This patch adds the bindings for the MSM DisplayPort HDCP registers > > which are required to write the HDCP key into the display controller as > >

Re: [Freedreno] [v2] drm/msm/disp/dpu1: set default group ID for CTL.

2021-10-29 Thread Dmitry Baryshkov
On Fri, 29 Oct 2021 at 15:30, Kalyan Thota wrote: > > New required programming in CTL for SC7280. Group ID informs > HW of which VM owns that CTL. Force this group ID to > default/disabled until virtualization support is enabled in SW. > > Changes in v1: > - Fix documentation and add descritpion

[Freedreno] [v2] drm/msm/disp/dpu1: set default group ID for CTL.

2021-10-29 Thread Kalyan Thota
New required programming in CTL for SC7280. Group ID informs HW of which VM owns that CTL. Force this group ID to default/disabled until virtualization support is enabled in SW. Changes in v1: - Fix documentation and add descritpion for the change (Stephen) Signed-off-by: Kalyan Thota ---

Re: [Freedreno] [PATCH 1/4] dma-buf: add dma_fence_describe and dma_resv_describe

2021-10-29 Thread kernel test robot
Hi "Christian, I love your patch! Yet something to improve: [auto build test ERROR on drm-tip/drm-tip] [also build test ERROR on next-20211028] [cannot apply to drm/drm-next drm-intel/for-linux-next drm-exynos/exynos-drm-next tegra-drm/drm/tegra/for-next linus/master airlied/drm-next

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

2021-10-29 Thread Maxime Ripard
On Fri, Oct 29, 2021 at 10:36:00AM +0200, Marek Szyprowski wrote: > Hi Mexime, > > On 29.10.2021 10:05, Maxime Ripard wrote: > > On Fri, Oct 29, 2021 at 08:23:45AM +0200, Marek Szyprowski wrote: > >> On 25.10.2021 17:15, Maxime Ripard wrote: > >>> In order to avoid any probe ordering issue, the

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

2021-10-29 Thread Marek Szyprowski
Hi Mexime, On 29.10.2021 10:05, Maxime Ripard wrote: > On Fri, Oct 29, 2021 at 08:23:45AM +0200, Marek Szyprowski wrote: >> On 25.10.2021 17:15, Maxime Ripard wrote: >>> In order to avoid any probe ordering issue, the best practice is to move >>> the secondary MIPI-DSI device registration and

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

2021-10-29 Thread Maxime Ripard
Hi Marek, On Fri, Oct 29, 2021 at 08:23:45AM +0200, Marek Szyprowski wrote: > Hi, > > On 25.10.2021 17:15, Maxime Ripard wrote: > > 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

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

2021-10-29 Thread Marek Szyprowski
Hi, On 25.10.2021 17:15, Maxime Ripard wrote: > 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 >