Re: Fence wait in mmu_interval_notifier_ops::invalidate

On 12/11/20 1:46 PM, Jason Gunthorpe wrote: On Fri, Dec 11, 2020 at 08:50:53AM +0100, Thomas Hellström (Intel) wrote: My understanding of this particular case is that hardware would continue to DMA to orphaned pages that are pinned until the driver is done with DMA, mmu notifier replaces pinn

Re: [PATCH v2, 03/17] dt-bindings: mediatek: add description for mt8192 display

Hi, Yongqiang: Yongqiang Niu 於 2020年12月12日 週六 下午12:12寫道： > > add description for mt8192 display Reviewed-by: Chun-Kuang Hu > > Signed-off-by: Yongqiang Niu > --- > Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > >

Re: [PATCH v2, 15/17] soc: mediatek: mmsys: add mt8192 mmsys support

Hi, Yongqiang: Yongqiang Niu 於 2020年12月12日 週六 下午12:22寫道： > > add mt8192 mmsys support > > Signed-off-by: Yongqiang Niu > --- > drivers/soc/mediatek/mmsys/Makefile | 1 + > drivers/soc/mediatek/mmsys/mt8192-mmsys.c | 119 > ++ > include/linux/soc/mediatek/mtk

Re: [PATCH v3 5/5] phy: freescale: phy-fsl-imx8-mipi-dphy: Add i.MX8qxp LVDS PHY mode support

Hi, On Fri, Dec 11, 2020 at 09:46:22AM +0800, Liu Ying wrote: > i.MX8qxp SoC embeds a Mixel MIPI DPHY + LVDS PHY combo which supports > either a MIPI DSI display or a LVDS display. The PHY mode is controlled > by SCU firmware and the driver would call a SCU firmware function to > configure the PHY

Re: [PATCH v3 4/5] dt-bindings: phy: mixel: mipi-dsi-phy: Add Mixel combo PHY support for i.MX8qxp

Hi, On Fri, Dec 11, 2020 at 09:46:21AM +0800, Liu Ying wrote: > Add support for Mixel MIPI DPHY + LVDS PHY combo IP > as found on Freescale i.MX8qxp SoC. > > Cc: Guido Günther > Cc: Kishon Vijay Abraham I > Cc: Vinod Koul > Cc: Rob Herring > Cc: NXP Linux Team > Signed-off-by: Liu Ying > ---

Re: [PATCH v3 3/5] dt-bindings: phy: Convert mixel,mipi-dsi-phy to json-schema

Hi, On Fri, Dec 11, 2020 at 09:46:20AM +0800, Liu Ying wrote: > This patch converts the mixel,mipi-dsi-phy binding to > DT schema format using json-schema. > > Comparing to the plain text version, the new binding adds > the 'assigned-clocks', 'assigned-clock-parents' and > 'assigned-clock-rates' p

[PATCH] drm/damage_helper: Check if damage clips has valid values

Userspace can set a damage clip with a negative coordinate, negative width or height or larger than the plane. This invalid values could cause issues in some HW or even worst enable security flaws. Cc: Gwan-gyeong Mun Cc: Sean Paul Cc: Fabio Estevam Cc: Deepak Rawat Cc: dri-devel@lists.freedes

Re: [PATCH] drm/damage_helper: Check if damage clips has valid values

Can you add some drm_dbg_atomic logs when the damage is invalid, to make it easier for user-space to understand why an atomic commit failed? ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-deve

Re: [PATCH] drm/damage_helper: Check if damage clips has valid values

On Sun, 2020-12-13 at 17:22 +, Simon Ser wrote: > Can you add some drm_dbg_atomic logs when the damage is invalid, to make it > easier for user-space to understand why an atomic commit failed? sure, this is enough? will wait for a couple of more days before send another version. diff --git

[PATCH v5 1/6] drm/damage_helper: Check if damage clips has valid values

Userspace can set a damage clip with a negative coordinate, negative width or height or larger than the plane. This invalid values could cause issues in some HW or even worst enable security flaws. v2: - add debug messages to let userspace know why atomic commit failed due invalid damage clips Cc

[RESEND PATCH] drm/rockchip: dsi: remove extra component_del() call

commit cf6d100dd238 ("drm/rockchip: dsi: add dual mipi support") added this devcnt field and call to component_del(). However, these both appear to be erroneous changes left over from an earlier version of the patch. In the version merged, nothing ever modifies devcnt, meaning component_del() runs

[RESEND PATCH] drm/rockchip: dsi: move all lane config except LCDC mux to bind()

When we first enable the DSI encoder, we currently program some per-chip configuration that we look up in rk3399_chip_data based on the device tree compatible we match. This data configures various parameters of the MIPI lanes, including on RK3399 whether DSI1 is slaved to DSI0 in a dual-mode confi

[Bug 201539] AMDGPU R9 390 automatic fan speed control in Linux 4.19/4.20/5.0

https://bugzilla.kernel.org/show_bug.cgi?id=201539 --- Comment #71 from mirh (m...@protonmail.ch) --- Cool! This landed in 5.10. By the way, I was wondering, is there any way to override the default minimum 20~26% minimum speed value? I see that MinimumPWMLimit and zero rpm only landed with late

linux-next: manual merge of the drm tree with the crypto tree

Hi all, Today's linux-next merge of the drm tree got a conflict in: MAINTAINERS between commit: 885743324513 ("crypto: keembay - Add support for Keem Bay OCS AES/SM4") from the crypto tree and commit: ed794057b052 ("drm/kmb: Build files for KeemBay Display driver") from the drm tree.

Re: [PATCH v15 1/4] RDMA/umem: Support importing dma-buf as user memory region

Hi Jianxin, Thank you for the patch! Yet something to improve: [auto build test ERROR on rdma/for-next] [also build test ERROR on next-20201211] [cannot apply to tegra-drm/drm/tegra/for-next v5.10] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch,