Re: [PATCH] staging: fbtft: Remove prohibited spaces before ')'

Hi Marcio, Thank you for the patch! Yet something to improve: [auto build test ERROR on staging/staging-testing] [also build test ERROR on tegra-drm/drm/tegra/for-next v5.6-rc5 next-20200310] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW

X.Org GSoC 2020 - call for project ideas and mentors

Hello! Once again X.Org has been fortunate to have been chosen to be part of GSoC! Starting March 16 (this Monday) students will be able to register and submit their applications for GSoC. If you can spare a moment, please take a look at our current "idea" page which help students to start

[PATCH -next 019/491] Hyper-V CORE AND DRIVERS: Use fallthrough;

Convert the various uses of fallthrough comments to fallthrough; Done via script Link: https://lore.kernel.org/lkml/b56602fcf79f849e733e7b521bb0e17895d390fa.1582230379.git.joe.com/ Signed-off-by: Joe Perches --- drivers/hv/hv_kvp.c | 4 +--- drivers/hv/vmbus_drv.c | 2 +-

[PATCH -next 025/491] AMD POWERPLAY: Use fallthrough;

Convert the various uses of fallthrough comments to fallthrough; Done via script Link: https://lore.kernel.org/lkml/b56602fcf79f849e733e7b521bb0e17895d390fa.1582230379.git.joe.com/ Signed-off-by: Joe Perches --- drivers/gpu/drm/amd/powerplay/hwmgr/smu7_hwmgr.c | 6 +++--- 1 file changed, 3

[PATCH -next 024/491] AMD DISPLAY CORE: Use fallthrough;

Convert the various uses of fallthrough comments to fallthrough; Done via script Link: https://lore.kernel.org/lkml/b56602fcf79f849e733e7b521bb0e17895d390fa.1582230379.git.joe.com/ Signed-off-by: Joe Perches --- drivers/gpu/drm/amd/display/dc/bios/bios_parser2.c | 4 ++--

[PATCH -next 023/491] AMD KFD: Use fallthrough;

Convert the various uses of fallthrough comments to fallthrough; Done via script Link: https://lore.kernel.org/lkml/b56602fcf79f849e733e7b521bb0e17895d390fa.1582230379.git.joe.com/ Signed-off-by: Joe Perches --- drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_arcturus.c | 2 +- 1 file changed, 1

[PATCH -next 026/491] INTEL GVT-g DRIVERS (Intel GPU Virtualization): Use fallthrough;

Convert the various uses of fallthrough comments to fallthrough; Done via script Link: https://lore.kernel.org/lkml/b56602fcf79f849e733e7b521bb0e17895d390fa.1582230379.git.joe.com/ Signed-off-by: Joe Perches --- drivers/gpu/drm/i915/gvt/handlers.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH -next 013/491] INGENIC JZ47xx SoCs: Use fallthrough;

Convert the various uses of fallthrough comments to fallthrough; Done via script Link: https://lore.kernel.org/lkml/b56602fcf79f849e733e7b521bb0e17895d390fa.1582230379.git.joe.com/ Signed-off-by: Joe Perches --- drivers/gpu/drm/ingenic/ingenic-drm.c | 2 +-

[PATCH 1/3] dma-buf: add dma_fence_array_for_each (v2)

From: Christian König Add a helper to iterate over all fences in a dma_fence_array object. v2 (Jason Ekstrand) - Return NULL from dma_fence_array_first if head == NULL. This matches the iterator behavior of dma_fence_chain_for_each in that it iterates zero times if head == NULL. -

[PATCH 2/3] dma-buf: add dma_resv_get_singleton (v2)

From: Christian König Add a helper function to get a single fence representing all fences in a dma_resv object. This fence is either the only one in the object or all not signaled fences of the object in a flatted out dma_fence_array. v2 (Jason Ekstrand): - Take reference of fences both for

[PATCH 3/3] RFC: dma-buf: Add an API for importing and exporting sync files (v4)

Explicit synchronization is the future. At least, that seems to be what most userspace APIs are agreeing on at this point. However, most of our Linux APIs (both userspace and kernel UAPI) are currently built around implicit synchronization with dma-buf. While work is ongoing to change many of

Re: [PATCH] RFC: dma-buf: Add an API for importing and exporting sync files

On Mon, Mar 9, 2020 at 11:21 AM Christian König wrote: > > Am 05.03.20 um 16:54 schrieb Jason Ekstrand: > > On Thu, Mar 5, 2020 at 7:06 AM Christian König > > wrote: > >> [SNIP] > >> Well as far as I can see this won't work because it would break the > >> semantics of the timeline sync. > > I'm

linux-next: manual merge of the drm-intel tree with the drm-intel-fixes tree

Hi all, Today's linux-next merge of the drm-intel tree got a conflict in: drivers/gpu/drm/i915/gvt/vgpu.c between commit: 04d6067f1f19 ("drm/i915/gvt: Fix unnecessary schedule timer when no vGPU exits") from the drm-intel-fixes tree and commit: 12d5861973c7 ("drm/i915/gvt: Make WARN*

[GIT PULL v2] exynos-drm-fixes

Hi Dave, Just one fixup to IOMMU initialization failure and memory leak detected by kmemleak detector. Please kindly let me know if there is any problem. Thanks, Inki Dae The following changes since commit 513dc792d6060d5ef572e43852683097a8420f56: vgacon: Fix a UAF in

Re: [PATCH] spi: spi-fsl-dspi: fix DMA mapping

Am 2020-03-10 14:02, schrieb Vladimir Oltean: On Tue, 10 Mar 2020 at 10:12, Michael Walle wrote: Am 2020-03-10 08:40, schrieb Michael Walle: > Am 2020-03-10 08:33, schrieb Michael Walle: >> Use the correct device to request the DMA mapping. Otherwise the IOMMU >> doesn't get the mapping and

[PATCH v2 15/17] drm: make various debugfs_init() functions return 0

Since commit 987d65d01356 (drm: debugfs: make drm_debugfs_create_files() never fail), drm_debugfs_create_files() never fails and should return void. Therefore, remove its use as the return value of various debugfs_init() functions in drm, and have these functions return 0 directly. v2: convert

Re: [PATCH v11 3/5] soc: mediatek: Move mt8173 MMSYS to platform driver

Hi all, On 10/3/20 10:40, Matthias Brugger wrote: > > > On 09/03/2020 23:50, Stephen Boyd wrote: >> Quoting Enric Balletbo Serra (2020-03-06 14:09:50) >>> Missatge de Stephen Boyd del dia dv., 6 de mar >>> 2020 a les 22:37: Quoting Enric Balletbo i Serra (2020-03-06 08:30:16) >

[PATCH v2 06/17] drm/arm: make hdlcd_debugfs_init() return 0

Since commit 987d65d01356 (drm: debugfs: make drm_debugfs_create_files() never fail), drm_debugfs_create_files() never fails and should return void. Therefore, remove its use as the return value of hdlcd_debugfs_init() and have the latter function return 0 directly. v2: make hdlcd_debugfs_init()

[PATCH v2 17/17] drm: convert .debugfs_init() hook to return void.

As a result of commit 987d65d01356 (drm: debugfs: make drm_debugfs_create_files() never fail) and changes to various debugfs functions in drm/core and across various drivers, there is no need for the drm_driver.debugfs_init() hook to have a return value. Therefore, declare it as void. This also

Re: [linux-sunxi] [PATCH 2/2] ARM: dts: sun4i: Add support for Topwise A721 tablet

On Tue, Mar 10, 2020 at 11:27:24AM +0100, Pascal Roeleven wrote: > The Topwise A721/LY-F1 tablet is a tablet sold around 2012 under > different brands. The mainboard mentions A721 clearly, so this tablet > is best known under this name. > > Signed-off-by: Pascal Roeleven > --- >

[PATCH v2 10/17] drm/vram-helper: make drm_vram_mm_debugfs_init() return 0

Since 987d65d01356 (drm: debugfs: make drm_debugfs_create_files() never fail), drm_debugfs_create_files() never fails and should return void. Therefore, remove its use as the return value of drm_vram_mm_debugfs_init(), and have the function return 0 directly. v2: have drm_vram_mm_debugfs_init()

[PATCH v2 01/17] drm/tegra: remove checks for debugfs functions return value

Since 987d65d01356 (drm: debugfs: make drm_debugfs_create_files() never fail) there is no need to check the return value of drm_debugfs_create_files(). Therefore, remove the return checks and error handling of the drm_debugfs_create_files() function from various debugfs init functions in drm/tegra

[PATCH v2 04/17] drm/vc4: remove check of return value of drm_debugfs functions

Since 987d65d01356 (drm: debugfs: make drm_debugfs_create_files() never fail), drm_debugfs_create_files() never fails and should return void. Therefore, remove unnecessary check and error handling for the return value of drm_debugfs_create_files() in vc4_debugfs_init(). v2: remove conversion of

[PATCH v3 0/2] Add LVDS panel support to HiHope RZ/G2M

Dear All, The HiHope RZ/G2M is advertised as supporting panel idk-1110wr from Advantech, but the panel doesn't come with the board, it has to purchased separatey, therefore this series adds panel support to a new DT. The v2 version somehow missed being merged. v2->v3 * Included Reviewed-by

[PATCH 0/2] Add support for Topwise A721 tablet

This series add support for the Topwise A721 tablet and it's display. It is an old tablet (around 2012) but it might be useful as reference as the devicetree is pretty complete. Pascal Roeleven (2): drm/panel: Add Starry KR070PE2T ARM: dts: sun4i: Add support for Topwise A721 tablet

Re: [PATCH] spi: spi-fsl-dspi: fix DMA mapping

On Tue, 10 Mar 2020 at 10:12, Michael Walle wrote: > > Am 2020-03-10 08:40, schrieb Michael Walle: > > Am 2020-03-10 08:33, schrieb Michael Walle: > >> Use the correct device to request the DMA mapping. Otherwise the IOMMU > >> doesn't get the mapping and it will generate a page fault. > >> > >>

[PATCH v8] dt-bindings: display: Add idk-2121wr binding

From: Fabrizio Castro Add binding for the idk-2121wr LVDS panel from Advantech. Some panel-specific documentation can be found here: https://buy.advantech.eu/Displays/Embedded-LCD-Kits-High-Brightness/model-IDK-2121WR-K2FHA2E.htm Signed-off-by: Fabrizio Castro Signed-off-by: Lad Prabhakar

[PATCH v2 13/17] drm/omap: remove checks for return value of drm_debugfs functions

Since 987d65d01356 (drm: debugfs: make drm_debugfs_create_files() never fail), there is no need to ever check the return value for drm_debugfs_create_files(). Therefore remove the checks for the return value and subsequent error handling in omap_debugfs_init(). These changes also enables the

Re: [PATCH v7 12/13] backlight: pwm_bl: Use 64-bit division macros for period and duty cycle

On Tue, Mar 10, 2020 at 02:34:32PM +, Daniel Thompson wrote: > This patch looks like it is a tiny change to get the pwm_backlight to > perform 64-bit division. Most of the above text is completely irrelevant > to the change contained in this patch. No need to justify the change in > the PWM

[PATCH v2 02/17] drm/tilcdc: remove check for return value of debugfs functions.

Since 987d65d01356 (drm: debugfs: make drm_debugfs_create_files() never fail), drm_debugfs_create_files() never fails. Therefore, remove the check and error handling of the return value of drm_debugfs_create_files() as it is not needed in tilcdc_debugfs_init(). Also remove local variables that

RE: [PATCH v8] dt-bindings: display: Add idk-2121wr binding

Hi Sam, > -Original Message- > From: Sam Ravnborg > Sent: 10 March 2020 19:54 > To: Prabhakar Mahadev Lad > Cc: Thierry Reding ; David Airlie > ; Daniel Vetter ; Rob Herring > ; Mark Rutland ; dri- > de...@lists.freedesktop.org; devicet...@vger.kernel.org; linux- >

Re: [PATCH] spi: spi-fsl-dspi: fix DMA mapping

On Tue, 10 Mar 2020 at 19:14, Mark Brown wrote: > > On Tue, Mar 10, 2020 at 03:12:45PM +0100, Michael Walle wrote: > > Am 2020-03-10 14:02, schrieb Vladimir Oltean: > > > > I'm testing LS1028A with IOMMU_DEFAULT_PASSTHROUGH=y and I didn't have > > > time to change my setup now. I've also sent a

[PATCH v2] fbdev: s1d13xxxfb: add missed unregister_framebuffer in remove

The driver calls register_framebuffer() in probe but does not call unregister_framebuffer() in remove. Rename current remove to __s1d13xxxfb_remove() for error handler. Then add a new remove to call unregister_framebuffer(). Signed-off-by: Chuhong Yuan --- Changes in v2: - Rename the existing

[PATCH v2 12/17] drm/pl111: make pl111_debugfs_init return 0

Since 987d65d01356 (drm: debugfs: make drm_debugfs_create_files() never fail) drm_debugfs_create_files() should return void. Therefore, remove its use as the return value in pl111_debugfs_init(), and have the function return 0 directly. v2: have pl111_debugfs_init() return 0 instead of void to

[PATCH v2 08/17] drm/msm: remove checks for return value of drm_debugfs_create_files()

Since commit 987d65d01356 (drm: debugfs: make drm_debugfs_create_files() never fail), drm_debugfs_create_files never fails and only returns 0. Therefore, the unnecessary checks for its return value and error handling in various debugfs_init() functions in drm/msm and have the functions return 0

[PATCH v2 03/17] drm/v3d: make v3d_debugfs_init() return 0

Since commit 987d65d01356 (drm: debugfs: make drm_debugfs_create_files() never fail), drm_debugfs_create_files() never fails and should return void. Therefore, remove its use as the return value of v3d_debugfs_init() and have the function return 0 directly instead. v2: remove conversion of

[PATCH v2 16/17] drm/debugfs: remove checks for return value of drm_debugfs functions.

Since 987d65d01356 (drm: debugfs: make drm_debugfs_create_files() never fail), there is no need to check the return value of drm_debugfs_create_files(). Therefore, remove remove unnecessary checks and error handling statement blocks for its return value. These changes also enable changing

[PATCH v3 1/2] dt-bindings: display: Add idk-1110wr binding

From: Fabrizio Castro Add binding for the idk-1110wr LVDS panel from Advantech. Some panel-specific documentation can be found here: https://buy.advantech.eu/Displays/Embedded-LCD-Kits-LCD-Kit-Modules/model-IDK-1110WR-55WSA1E.htm Signed-off-by: Fabrizio Castro Reviewed-by: Rob Herring

[PATCH 2/2] ARM: dts: sun4i: Add support for Topwise A721 tablet

The Topwise A721/LY-F1 tablet is a tablet sold around 2012 under different brands. The mainboard mentions A721 clearly, so this tablet is best known under this name. Signed-off-by: Pascal Roeleven --- arch/arm/boot/dts/Makefile | 3 +-

Re: [PATCH] drm/rockchip: rgb: don't count non-existent devices when determining subdrivers

Hi Heiko, Heiko Stuebner wrote on Tue, 21 Jan 2020 23:48:28 +0100: > From: Heiko Stuebner > > rockchip_drm_endpoint_is_subdriver() may also return error codes. > For example if the target-node is in the disabled state, so no > platform-device is getting created for it. > > In that case

[PATCH v2 14/17] drm/i915: have *_debugfs_init() functions return void.

Since commit 987d65d01356 (drm: debugfs: make drm_debugfs_create_files() never fail), drm_debugfs_create_files() never fails and should return void. Therefore, remove its use as the return value of debugfs_init() functions and have the functions return void. v2: convert

[PATCH v3] video: fbdev: arcfb: add missed free_irq and fix the order of request_irq

The driver forgets to free irq in remove which is requested in probe. Add the missed call to fix it. Also, the position of request_irq() in probe should be put before register_framebuffer(). Signed-off-by: Chuhong Yuan --- Changes in v3: - Add missed variable par in remove.

[PATCH v2 07/17] drm/etnaviv: remove check for return value of drm_debugfs_create_files()

Since commit 987d65d01356 (drm: debugfs: make drm_debugfs_create_files() never fail), drm_debugfs_create_files() never fails and only returns 0. Therefore, remove the unnecessary check of its return value and error handling in etnaviv_debugfs_init() and have the function return 0 directly. v2:

Re: [linux-sunxi] [PATCH 2/2] ARM: dts: sun4i: Add support for Topwise A721 tablet

Hello Pascal, On Tue, Mar 10, 2020 at 11:27:24AM +0100, Pascal Roeleven wrote: > The Topwise A721/LY-F1 tablet is a tablet sold around 2012 under > different brands. The mainboard mentions A721 clearly, so this tablet > is best known under this name. > > Signed-off-by: Pascal Roeleven > --- >

[PATCH v2 00/17] drm: subsytem-wide debugfs functions refactor

This series includes work on various debugfs functions both in drm/core and across various drivers in the subsystem. Since commit 987d65d01356 (drm: debugfs: make drm_debugfs_create_files() never fail), drm_debugfs_create_files() does not fail and only returns zero. This series therefore removes

[PATCH v2 09/17] drm/sti: remove use of drm_debugfs functions as return values

Since commit 987d65d01356 (drm: debugfs: make drm_debugfs_create_files() never fail), drm_debugfs_create_files() never fails, and should return void. This change therefore removes it uses as a return value in various functions across drm/sti. With these changes, the affected functions have been

[PATCH v2 05/17] drm/arc: make arcgpu_debugfs_init() return 0.

Since commit 987d65d01356 (drm: debugfs: make drm_debugfs_create_files() never fail), drm_debugfs_create_files() never fails and should return void. Therefore, remove its use as the return value of arcpgu_debugfs_init() and have the latter function return 0 directly. v2: convert the function to

[PATCH 1/2] drm/panel: Add Starry KR070PE2T

The KR070PE2T is a 7" panel with a resolution of 800x480. KR070PE2T is the marking present on the ribbon cable. As this panel is probably available under different brands, this marking will catch most devices. Signed-off-by: Pascal Roeleven --- .../display/panel/starry,kr070pe2t.txt|

Re: [PATCH v11 3/5] soc: mediatek: Move mt8173 MMSYS to platform driver

On 09/03/2020 23:50, Stephen Boyd wrote: > Quoting Enric Balletbo Serra (2020-03-06 14:09:50) >> Missatge de Stephen Boyd del dia dv., 6 de mar >> 2020 a les 22:37: >>> >>> Quoting Enric Balletbo i Serra (2020-03-06 08:30:16) On 5/3/20 22:01, Stephen Boyd wrote: > Quoting Enric

[PATCH v2 11/17] drm/nouveau: make nouveau_drm_debugfs_init() return 0

Since 987d65d01356 (drm: debugfs: make drm_debugfs_create_files() never fail), there is no need to ever check for the the return value of debugfs_create_file() and drm_debugfs_create_files(). Therefore, remove unnecessary checks and error handling in nouveau_drm_debugfs_init() and have the

[PATCH v3 2/2] arm64: dts: renesas: Add HiHope RZ/G2M board with idk-1110wr display

From: Fabrizio Castro The HiHope RZ/G2M is advertised as compatible with panel idk-1110wr from Advantech, however the panel isn't sold alongside the board. A new dts, adding everything that's required to get the panel to work the HiHope RZ/G2M, is the most convenient way to support the HiHope

[PATCH v6 2/2] drm/edid: Add function to parse EDID descriptors for monitor range

Adaptive Sync is a VESA feature so add a DRM core helper to parse the EDID's detailed descritors to obtain the adaptive sync monitor range. Store this info as part fo drm_display_info so it can be used across all drivers. This part of the code is stripped out of amdgpu's function

[PATCH v6 1/2] drm/edid: Name the detailed monitor range flags

This patch adds defines for the detailed monitor range flags as per the EDID specification. v2: * Rename the flags with DRM_EDID_ (Jani N) Suggested-by: Ville Syrjälä Cc: Ville Syrjälä Cc: Harry Wentland Cc: Clinton A Taylor Cc: Kazlauskas Nicholas Cc: Jani Nikula Signed-off-by: Manasi

Re: [RFC PATCH 0/8] *** Per context fencing ***

On Tue, Mar 10, 2020 at 12:43 AM Gerd Hoffmann wrote: > On Mon, Mar 09, 2020 at 06:08:10PM -0700, Gurchetan Singh wrote: > > We don't want fences from different 3D contexts/processes (GL, VK) to > > be on the same timeline. Sending this out as a RFC to solicit feedback > > on the general

[pull] amdgpu, amdkfd, scheduler drm-next-5.7

Hi Dave, Daniel, Updates for 5.7. The following changes since commit 60347451ddb0646c1a9cc5b9581e5bcf648ad1aa: Merge tag 'drm-misc-next-2020-02-27' of git://anongit.freedesktop.org/drm/drm-misc into drm-next (2020-02-28 16:22:41 +1000) are available in the Git repository at:

Re: [DPU PATCH v4 1/5] dt-bindings: msm/dp: add bindings of DP/DP-PLL driver for Snapdragon

On Wed, Mar 04, 2020 at 04:10:24PM -0800, Vara Reddy wrote: > From: Chandan Uddaraju > > Add bindings for Snapdragon DisplayPort and > display-port PLL driver. > > Changes in V2: > Provide details about sel-gpio > > Changes in V4: > Provide details about max dp lanes > Change the commit text >

Re: [PATCH v3] drm/i915/mst: Hookup DRM DP MST late_register/early_unregister callbacks

On Tue, Mar 10, 2020 at 03:51:21PM -0400, Lyude Paul wrote: > i915 can enable aux device nodes for DP MST by calling > drm_dp_mst_connector_late_register()/drm_dp_mst_connector_early_unregister(), > so let's hook that up. > > Changes since v1: > * Call intel_connector_register/unregister() from >

Re: [PATCH v8] dt-bindings: display: Add idk-2121wr binding

Hi Prabhakar On Tue, Mar 10, 2020 at 07:39:29PM +, Lad Prabhakar wrote: > From: Fabrizio Castro > > Add binding for the idk-2121wr LVDS panel from Advantech. > > Some panel-specific documentation can be found here: >

[PATCH v3] drm/i915/mst: Hookup DRM DP MST late_register/early_unregister callbacks

i915 can enable aux device nodes for DP MST by calling drm_dp_mst_connector_late_register()/drm_dp_mst_connector_early_unregister(), so let's hook that up. Changes since v1: * Call intel_connector_register/unregister() from intel_dp_mst_connector_late_register/unregister() so we don't lose

Re: [PATCH v2] drm/i915/mst: Hookup DRM DP MST late_register/early_unregister callbacks

On Tue, 2020-03-10 at 21:06 +0200, Ville Syrjälä wrote: > On Tue, Mar 10, 2020 at 02:54:16PM -0400, Lyude Paul wrote: > > i915 can enable aux device nodes for DP MST by calling > > drm_dp_mst_connector_late_register()/drm_dp_mst_connector_early_unregister > > (), > > so let's hook that up. > > >

[PATCH v7] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges

Fixes the infamous 'runtime PM' bug many users are facing on Laptops with Nvidia Pascal GPUs by skipping said PCI power state changes on the GPU. Depending on the used kernel there might be messages like those in demsg: "nouveau :01:00.0: Refused to change power state, currently in D3"

Re: [PATCH v5 2/2] drm/edid: Add function to parse EDID descriptors for adaptive sync limits

On Tue, Mar 10, 2020 at 09:13:30PM +0200, Ville Syrjälä wrote: > On Tue, Mar 10, 2020 at 12:08:33PM -0700, Manasi Navare wrote: > > Hi Ville, > > > > Please find answers to your concerns below: > > > > On Mon, Mar 09, 2020 at 02:39:40PM -0700, Manasi Navare wrote: > > > Adaptive Sync is a VESA

Re: [PATCH v5 2/2] drm/edid: Add function to parse EDID descriptors for adaptive sync limits

On Tue, Mar 10, 2020 at 12:08:33PM -0700, Manasi Navare wrote: > Hi Ville, > > Please find answers to your concerns below: > > On Mon, Mar 09, 2020 at 02:39:40PM -0700, Manasi Navare wrote: > > Adaptive Sync is a VESA feature so add a DRM core helper to parse > > the EDID's detailed descritors

Re: [PATCH 1/2] drm/panel: Add Starry KR070PE2T

On Tue, Mar 10, 2020 at 07:54:23PM +0100, Sam Ravnborg wrote: > Hi Pascal. > > Thanks for submitting. > > On Tue, Mar 10, 2020 at 11:27:23AM +0100, Pascal Roeleven wrote: > > The KR070PE2T is a 7" panel with a resolution of 800x480. > > > > KR070PE2T is the marking present on the ribbon cable.

Re: [PATCH v5 1/2] drm/edid: Name the detailed monitor range flags

On Tue, Mar 10, 2020 at 06:20:27PM +0200, Ville Syrjälä wrote: > On Mon, Mar 09, 2020 at 02:39:39PM -0700, Manasi Navare wrote: > > This patch adds defines for the detailed monitor > > range flags as per the EDID specification. > > > > v2: > > * Rename the flags with DRM_EDID_ (Jani N) > > > >

Re: [PATCH v5 2/2] drm/edid: Add function to parse EDID descriptors for adaptive sync limits

Hi Ville, Please find answers to your concerns below: On Mon, Mar 09, 2020 at 02:39:40PM -0700, Manasi Navare wrote: > Adaptive Sync is a VESA feature so add a DRM core helper to parse > the EDID's detailed descritors to obtain the adaptive sync monitor range. > Store this info as part fo

Re: [PATCH v2] drm/i915/mst: Hookup DRM DP MST late_register/early_unregister callbacks

On Tue, Mar 10, 2020 at 02:54:16PM -0400, Lyude Paul wrote: > i915 can enable aux device nodes for DP MST by calling > drm_dp_mst_connector_late_register()/drm_dp_mst_connector_early_unregister(), > so let's hook that up. > > Changes since v1: > * Call intel_connector_register/unregister() from >

[PATCH v2] drm/i915/mst: Hookup DRM DP MST late_register/early_unregister callbacks

i915 can enable aux device nodes for DP MST by calling drm_dp_mst_connector_late_register()/drm_dp_mst_connector_early_unregister(), so let's hook that up. Changes since v1: * Call intel_connector_register/unregister() from intel_dp_mst_connector_late_register/unregister() so we don't lose

Re: [PATCH 1/2] drm/panel: Add Starry KR070PE2T

Hi Pascal. Thanks for submitting. On Tue, Mar 10, 2020 at 11:27:23AM +0100, Pascal Roeleven wrote: > The KR070PE2T is a 7" panel with a resolution of 800x480. > > KR070PE2T is the marking present on the ribbon cable. As this panel is > probably available under different brands, this marking

Re: [PATCH] drm/i915/mst: Hookup DRM DP MST late_register/early_unregister callbacks

On Tue, 2020-03-10 at 20:42 +0200, Ville Syrjälä wrote: > On Tue, Mar 10, 2020 at 02:28:54PM -0400, Lyude Paul wrote: > > i915 can enable aux device nodes for DP MST by calling > > drm_dp_mst_connector_late_register()/drm_dp_mst_connector_early_unregister > > (), > > so let's hook that up. > >

Re: [PATCH] drm/i915/mst: Hookup DRM DP MST late_register/early_unregister callbacks

On Tue, Mar 10, 2020 at 02:28:54PM -0400, Lyude Paul wrote: > i915 can enable aux device nodes for DP MST by calling > drm_dp_mst_connector_late_register()/drm_dp_mst_connector_early_unregister(), > so let's hook that up. Oh, we didn't have that yet? I thought it got hooked up for everyone but I

Applied "spi: spi-fsl-dspi: fix DMA mapping" to the spi tree

The patch spi: spi-fsl-dspi: fix DMA mapping has been applied to the spi tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during

Re: [PATCH V3 1/4] backlight: qcom-wled: convert the wled bindings to .yaml format

On Mon, 9 Mar 2020 18:55:59 +0530, Kiran Gunda wrote: > Convert the qcom-wled bindings from .txt to .yaml format. > > Signed-off-by: Kiran Gunda > --- > .../bindings/leds/backlight/qcom-wled.txt | 154 - > .../bindings/leds/backlight/qcom-wled.yaml | 184 >

[PATCH] drm/i915/mst: Hookup DRM DP MST late_register/early_unregister callbacks

i915 can enable aux device nodes for DP MST by calling drm_dp_mst_connector_late_register()/drm_dp_mst_connector_early_unregister(), so let's hook that up. Cc: Ville Syrjälä Cc: Manasi Navare Cc: "Lee, Shawn C" Signed-off-by: Lyude Paul --- drivers/gpu/drm/i915/display/intel_dp_mst.c | 22

Re: [v2] dt-bindings: msm: disp: add yaml schemas for DPU and DSI bindings

Hi Krishna On Mon, Mar 09, 2020 at 03:52:46PM +0530, Krishna Manikandan wrote: > MSM Mobile Display Subsytem(MDSS) encapsulates sub-blocks > like DPU display controller, DSI etc. Add YAML schema > for the device tree bindings for the same. > > Signed-off-by: Krishna Manikandan Looks good ow -

Re: [PATCH v4 2/2] drm/panel: add support for rm69299 visionox panel driver

Hi Harigovindan Thanks for the v4. nice work! There is one tiny detail to fix. With this fixed: Reviewed-by: Sam Ravnborg Sam On Fri, Mar 06, 2020 at 04:06:28PM +0530, Harigovindan P wrote: > Add support for Visionox panel driver. > > Signed-off-by: Harigovindan P > --- > >

Re: [PATCH v4 1/2] dt-bindings: display: add visionox rm69299 panel variant

Hi Harigovindan Thanks for the follow-up. There are still a few things to improve. See below. Sam On Fri, Mar 06, 2020 at 04:06:27PM +0530, Harigovindan P wrote: > Add bindings for visionox rm69299 panel. > > Signed-off-by: Harigovindan P > --- > > Changes in v2: > - Removed

Re: [PATCH v3] drm/dp_mst: Rewrite and fix bandwidth limit checks

On 3/9/20 5:01 PM, Lyude Paul wrote: Sigh, this is mostly my fault for not giving commit cd82d82cbc04 ("drm/dp_mst: Add branch bandwidth validation to MST atomic check") enough scrutiny during review. The way we're checking bandwidth limitations here is mostly wrong: For starters,

Re: [PATCH] drm/panel-simple: Fix dotclock for Ortustech COM37H3M

Hi Nikolaus Thanks for the detailed explanation. Applied and pushed to drm-misc-next. Sam On Tue, Mar 10, 2020 at 08:43:19AM +0100, H. Nikolaus Schaller wrote: > The currently listed dotclock disagrees with the currently > listed vrefresh rate. Change the dotclock to match the

Re: [PATCH] drm: panel: Set connector type for OrtusTech COM43H4M85ULC panel

Hi Laurent. On Mon, Mar 09, 2020 at 09:01:27PM +0200, Laurent Pinchart wrote: > Hi Sam, > > On Mon, Mar 09, 2020 at 08:00:47PM +0100, Sam Ravnborg wrote: > > On Mon, Mar 09, 2020 at 08:42:10PM +0200, Laurent Pinchart wrote: > > > The OrtusTech COM43H4M85ULC is a DPI panel, set the connector type

Re: [PATCH] drm: panel: Set connector type for OrtusTech COM43H4M85ULC panel

Hi Ville. > > > > > > My lame and simple workflow > > > > > > dim update-branches > > > # save patch from mutt > > > cat mbox | dim apply > > Why don't you just pipe the thing into dim straight from mutt? > That's what I do. Followed by some amount of dim extract-tag > also piped in from mutt.

Re: [PATCH] spi: spi-fsl-dspi: fix DMA mapping

On Tue, Mar 10, 2020 at 03:12:45PM +0100, Michael Walle wrote: > Am 2020-03-10 14:02, schrieb Vladimir Oltean: > > I'm testing LS1028A with IOMMU_DEFAULT_PASSTHROUGH=y and I didn't have > > time to change my setup now. I've also sent a v3 to my patch series > > which is going to conflict with

[PATCH v1.1 16/21] drm: mxsfb: Add i.MX7 to the list of supported SoCs in Kconfig

Extend the Kconfig option description by listing the i.MX7 SoCs, as they are supported by the same driver. Replace the list of SoCs in the short description with just "(e)LCDIF LCD controller" to avoid expanding it further in the future as support for more SoCs is added. Signed-off-by: Laurent

Re: [PATCH 16/21] drm: mxsfb: Add i.MX7 to the list of supported SoCs in Kconfig

Hi Fabio, On Tue, Mar 10, 2020 at 01:28:35PM -0300, Fabio Estevam wrote: > On Mon, Mar 9, 2020 at 4:53 PM Laurent Pinchart wrote: > > > config DRM_MXSFB > > - tristate "i.MX23/i.MX28/i.MX6SX MXSFB LCD controller" > > + tristate "i.MX23/i.MX28/i.MX6SX/i.MX7 MXSFB LCD controller" > >

Re: [PATCH 16/21] drm: mxsfb: Add i.MX7 to the list of supported SoCs in Kconfig

Hi Laurent, On Mon, Mar 9, 2020 at 4:53 PM Laurent Pinchart wrote: > config DRM_MXSFB > - tristate "i.MX23/i.MX28/i.MX6SX MXSFB LCD controller" > + tristate "i.MX23/i.MX28/i.MX6SX/i.MX7 MXSFB LCD controller" Can't we just make it simpler and write: tristate "i.MX eLCDIF

Re: [PATCH v5 2/2] drm/edid: Add function to parse EDID descriptors for adaptive sync limits

On Mon, Mar 09, 2020 at 02:39:40PM -0700, Manasi Navare wrote: > Adaptive Sync is a VESA feature so add a DRM core helper to parse > the EDID's detailed descritors to obtain the adaptive sync monitor range. > Store this info as part fo drm_display_info so it can be used > across all drivers. >

Re: [PATCH v5 1/2] drm/edid: Name the detailed monitor range flags

On Mon, Mar 09, 2020 at 02:39:39PM -0700, Manasi Navare wrote: > This patch adds defines for the detailed monitor > range flags as per the EDID specification. > > v2: > * Rename the flags with DRM_EDID_ (Jani N) > > Suggested-by: Ville Syrjälä > Cc: Ville Syrjälä > Cc: Harry Wentland > Cc:

Re: [RFC][PATCH 5/5] drm/i915/display: Add Nearest-neighbor based integer scaling support

On Tue, Feb 25, 2020 at 12:35:45PM +0530, Pankaj Bharadiya wrote: > Integer scaling (IS) is a nearest-neighbor upscaling technique that > simply scales up the existing pixels by an integer > (i.e., whole number) multiplier.Nearest-neighbor (NN) interpolation > works by filling in the missing color

Re: [RFC][PATCH 4/5] drm/i915: Introduce scaling filter related registers and bit fields.

On Tue, Feb 25, 2020 at 12:35:44PM +0530, Pankaj Bharadiya wrote: > Introduce scaler registers and bit fields needed to configure the > scaling filter in prgrammed mode and configure scaling filter > coefficients. > > Signed-off-by: Pankaj Bharadiya > Signed-off-by: Ankit Nautiyal > --- >

Re: [RFC][PATCH 3/5] drm/i915: Enable scaling filter for plane and pipe

On Tue, Feb 25, 2020 at 12:35:43PM +0530, Pankaj Bharadiya wrote: > Attach scaling filter property for crtc and plane and program the > scaler control register for the selected filter type. > > This is preparatory patch to enable Nearest-neighbor integer scaling. > > Signed-off-by: Pankaj

Re: [RFC][PATCH 1/5] drm: Introduce scaling filter property

On Tue, Feb 25, 2020 at 12:35:41PM +0530, Pankaj Bharadiya wrote: > Introduce new scaling filter property to allow userspace to select > the driver's default scaling filter or Nearest-neighbor(NN) filter > for upscaling operations on crtc/plane. > > Drivers can set up this property for a plane by

Re: [PATCH V3 3/4] backlight: qcom-wled: Add support for WLED5 peripheral in PM8150L

On Mon, Mar 09, 2020 at 06:56:01PM +0530, Kiran Gunda wrote: > Add support for WLED5 peripheral that is present on PM8150L PMICs. > > PM8150L WLED supports the following: > - Two modulators and each sink can use any of the modulator > - Multiple CABC selection options > - Multiple

Re: [PATCH v2 06/17] drm/arm: make hdlcd_debugfs_init() return 0

On Tue, Mar 10, 2020 at 04:31:10PM +0300, Wambui Karuga wrote: > Since commit 987d65d01356 (drm: debugfs: make > drm_debugfs_create_files() never fail), drm_debugfs_create_files() never > fails and should return void. Therefore, remove its use as the > return value of hdlcd_debugfs_init() and have

Re: [PATCH v2 2/4] drm/dp_mst: Use full_pbn instead of available_pbn for bandwidth checks

On 3/6/20 6:46 PM, Lyude Paul wrote: DisplayPort specifications are fun. For a while, it's been really unclear to us what available_pbn actually does. There's a somewhat vague explanation in the DisplayPort spec (starting from 1.2) that partially explains it: The minimum payload bandwidth

Re: [PATCH V3 2/4] backlight: qcom-wled: Add callback functions

On Mon, Mar 09, 2020 at 06:56:00PM +0530, Kiran Gunda wrote: > Add cabc_config, sync_toggle, wled_ovp_fault_status and wled_ovp_delay > callback functions to prepare the driver for adding WLED5 support. > > Signed-off-by: Kiran Gunda Overall this code would a lot easier to review if > --- >

Re: [PATCH V3 1/4] backlight: qcom-wled: convert the wled bindings to .yaml format

On Mon, Mar 09, 2020 at 06:55:59PM +0530, Kiran Gunda wrote: > Convert the qcom-wled bindings from .txt to .yaml format. > > Signed-off-by: Kiran Gunda Acked-by: Daniel Thompson > --- > .../bindings/leds/backlight/qcom-wled.txt | 154 - >

Re: [PATCH v7 12/13] backlight: pwm_bl: Use 64-bit division macros for period and duty cycle

On Mon, Mar 09, 2020 at 12:35:15PM -0700, Guru Das Srinagesh wrote: > Because period and duty cycle are defined in the PWM framework structs > as ints with units of nanoseconds, the maximum time duration that can be > set is limited to ~2.147 seconds. Redefining them as u64 values will > enable

Re: [PATCH v2 00/17] drm: subsytem-wide debugfs functions refactor

On Tue, Mar 10, 2020 at 04:31:04PM +0300, Wambui Karuga wrote: > This series includes work on various debugfs functions both in drm/core > and across various drivers in the subsystem. > Since commit 987d65d01356 (drm: debugfs: make drm_debugfs_create_files() > never fail),

[PATCH v2 00/22] Move media documentation files

That's a second version of a patch series with moves the media documents to better places. The first version was actually a RFC. This one is more complete. Yet, my plan is to merge it only at the media trees only after the end of the next merge window. I'm preparing several patches on the top of

[PATCH 5.5 144/189] drm: kirin: Revert "Fix for hikey620 display offset problem"

From: John Stultz commit 1b79cfd99ff5127e6a143767b51694a527b3ea38 upstream. This reverts commit ff57c6513820efe945b61863cf4a51b79f18b592. With the commit ff57c6513820 ("drm: kirin: Fix for hikey620 display offset problem") we added support for handling LDI overflows by resetting the hardware.

  1   2   >