[PATCH v6 0/4] GuC HWCONFIG with documentation

This is John/Rodrigo's 2 patches with some minor changes, and I added 2 patches. "drm/i915/uapi: Add query for hwconfig blob" was changed: * Rename DRM_I915_QUERY_HWCONFIG_TABLE to DRM_I915_QUERY_HWCONFIG_BLOB as requested by Joonas. * Reword commit message * I added Acked-by to this patc

[PATCH v6 1/4] drm/i915/guc: Add fetch of hwconfig table

From: John Harrison Implement support for fetching the hardware description table from the GuC. The call is made twice - once without a destination buffer to query the size and then a second time to fill in the buffer. The table is stored in the GT structure so that it can be fetched once at dri

[PATCH v6 4/4] drm/i915/guc: Verify hwconfig blob matches supported format

i915_drm.h now defines the format of the returned DRM_I915_QUERY_HWCONFIG_BLOB query item. Since i915 receives this from the black box GuC software, it should verify that the data matches that format before sending it to user-space. The verification makes a single simple pass through the blob cont

[PATCH v6 3/4] drm/i915/uapi: Add struct drm_i915_query_hwconfig_blob_item

Also, document DRM_I915_QUERY_HWCONFIG_BLOB with this struct. v3: * Add various changes suggested by Tvrtko v5: * Fix documenation formatting and verified with `make htmldocs` as suggested by Daniel Cc: Daniel Vetter Signed-off-by: Jordan Justen Acked-by: Jon Bloomfield Acked-by: Daniel

[PATCH v6 2/4] drm/i915/uapi: Add query for hwconfig blob

From: Rodrigo Vivi The DRM_I915_QUERY_HWCONFIG_BLOB query item returns a blob of data which it receives from the GuC software. This blob provides some useful data about the hardware for drivers. Although the blob is not fully documented at this time, the basic format is an array of u32 values. T

Re: [PATCH v6 1/4] drm/i915/guc: Add fetch of hwconfig table

] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch] url: https://github.com/0day-ci/linux/commits/Jordan-Justen/GuC-HWCONFIG-with-documentation/20220

[PATCH v6 0/5] drm/tiny: Add MIPI DBI compatible SPI driver

Hi, This patchset adds a driver that will work with most MIPI DBI compatible SPI panels out there. One change this time: Fix indentation in the DT binding. All patches are reviewed now so I will apply this after Rob's bot have looked at the binding. Thanks for reviewing! Noralf. Noralf Trønn

[PATCH v6 2/5] drm/modes: Remove trailing whitespace

Remove trailing whitespace from a comment. Acked-by: Sam Ravnborg Signed-off-by: Noralf Trønnes --- drivers/gpu/drm/drm_modes.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/drm_modes.c b/drivers/gpu/drm/drm_modes.c index 96b13e36293c..77a4c8dd0bb8 100644 -

[PATCH v6 3/5] drm/modes: Add of_get_drm_panel_display_mode()

Add a function to get a drm_display_mode from a panel-timing device tree subnode. Suggested-by: Sam Ravnborg Reviewed-by: Sam Ravnborg Signed-off-by: Noralf Trønnes --- drivers/gpu/drm/drm_modes.c | 49 + include/drm/drm_modes.h | 8 ++ 2 files chan

[PATCH v6 5/5] drm/tiny: Add MIPI DBI compatible SPI driver

Add a driver that will work with most MIPI DBI compatible SPI panels. This avoids adding a driver for every new MIPI DBI compatible controller that is to be used by Linux. The 'compatible' Device Tree property with a '.bin' suffix will be used to load a firmware file that contains the controller co

[PATCH v6 4/5] drm/mipi-dbi: Add driver_private member to struct mipi_dbi_dev

devm_drm_dev_alloc() can't allocate structures that embed a structure which then again embeds drm_device. Workaround this by adding a driver_private pointer to struct mipi_dbi_dev which the driver can use for its additional state. v3: - Add documentation Acked-by: Maxime Ripard Acked-by: Sam Rav

[PATCH v6 1/5] dt-bindings: display: add bindings for MIPI DBI compatible SPI panels

Add binding for MIPI DBI compatible SPI panels. v6: - Fix indentation (Rob) v5: - Add sainsmart18 to compatible items (Rob) - Expand write-only description (Sam) v4: - There should only be two compatible (Maxime) - s/panel-dbi-spi/panel-mipi-dbi-spi/in compatible v3: - Move properties to Device

Re: [PATCH v6 1/4] drm/i915/guc: Add fetch of hwconfig table

] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch] url: https://github.com/0day-ci/linux/commits/Jordan-Justen/GuC-HWCONFIG-with-documentation/20220

Re: [PATCH v4 7/9] drm: vkms: Refactor the plane composer to accept new formats

Hi Pekka, On 2/25/22 05:38, Pekka Paalanen wrote: > On Thu, 24 Feb 2022 21:43:01 -0300 > Igor Torrente wrote: > >> Hi Pekka, >> >> On 2/10/22 06:37, Pekka Paalanen wrote: >>> On Fri, 21 Jan 2022 18:38:29 -0300 >>> Igor Torrente wrote: >>> Currently the blend function only accepts XRGB_

Re: [PATCH] drm/amdgpu: Fix realloc of ptr

On 2/26/22 2:21 PM, David Laight wrote: From: t...@redhat.com Sent: 26 February 2022 15:59 From: Tom Rix Clang static analysis reports this error amdgpu_debugfs.c:1690:9: warning: 1st function call argument is an uninitialized value tmp = krealloc_array(tmp, i + 1, ^~

RE: [PATCH 1/3] drm/edid: parse multiple CEA extension block

On Saturday, February 26, 2022 1:47 AM, Ville Syrjälä wrote: >On Thu, Feb 24, 2022 at 10:16:23PM +0800, Lee Shawn C wrote: >> Try to find and parse more CEA ext blocks if edid->extensions is >> greater than one. >> >> Cc: Jani Nikula >> Cc: Ville Syrjala >> Cc: Ankit Nautiyal >> Signed-off-b

RE: [PATCH 2/3] drm/edid: read HF-EEODB ext block

On Saturday, February 26, 2022 2:09 AM, Ville Syrjälä wrote: >On Thu, Feb 24, 2022 at 10:16:24PM +0800, Lee Shawn C wrote: >> Support to read HF_EEODB block that request by HDMI 2.1 specification. > >Please spell out what that thing is and why it exists. > >> >> Cc: Jani Nikula >> Cc: Ville Syrja

[PATCH v2] drm/amdgpu: Fix realloc of ptr

From: Tom Rix Clang static analysis reports this error amdgpu_debugfs.c:1690:9: warning: 1st function call argument is an uninitialized value tmp = krealloc_array(tmp, i + 1, ^~~ realloc uses tmp, so tmp can not be garbage. And the return needs to be checked.

Re: [PATCH 15/15] drm/i915/gt: Clear compress metadata for Xe_HP platforms

Matt, Thanks for the review. On 2022-02-18 at 17:47:22 -0800, Matt Roper wrote: > On Sat, Feb 19, 2022 at 12:17:52AM +0530, Ramalingam C wrote: > > From: Ayaz A Siddiqui > > > > Xe-HP and latest devices support Flat CCS which reserved a portion of > > the device memory to store compression meta

[CI 0/2] drm/mm: Add an iterator to optimally walk over holes suitable for an allocation

The first patch is a drm core patch that replaces the for loop in drm_mm_insert_node_in_range() with the iterator and would not cause any functional changes. The second patch is a i915 driver specific patch that also uses the iterator but solves a different problem. v2: - Added a new patch to this

[CI 1/2] drm/mm: Add an iterator to optimally walk over holes for an allocation (v4)

This iterator relies on drm_mm_first_hole() and drm_mm_next_hole() functions to identify suitable holes for an allocation of a given size by efficiently traversing the rbtree associated with the given allocator. It replaces the for loop in drm_mm_insert_node_in_range() and can also be used by drm

[CI 2/2] drm/i915/gem: Don't try to map and fence large scanout buffers (v9)

On platforms capable of allowing 8K (7680 x 4320) modes, pinning 2 or more framebuffers/scanout buffers results in only one that is mappable/ fenceable. Therefore, pageflipping between these 2 FBs where only one is mappable/fenceable creates latencies large enough to miss alternate vblanks thereby

Re: [PATCH v3 0/2] drm/dp: Fix out-of-bounds reads

On Fri, Feb 25, 2022 at 10:30:19AM +0100, Thierry Reding wrote: > On Thu, Feb 24, 2022 at 07:56:08PM -0800, Kees Cook wrote: > > Hi, > > > > I'm sending these again, as they still need fixing. They have been > > rebased due to the drm_dp_helper code being moved into a subdirectory. > > Yeah, I no

[PATCH] Kbuild: remove -std=gnu89 from compiler arguments

From: Arnd Bergmann During a patch discussion, Linus brought up the option of changing the C standard version from gnu89 to gnu99, which allows using variable declaration inside of a for() loop. While the C99, C11 and later standards introduce many other features, most of these are already availa

Re: [PATCH] Kbuild: remove -std=gnu89 from compiler arguments

On Sun, Feb 27, 2022 at 1:54 PM Arnd Bergmann wrote: > > Since the differences between gnu99, gnu11 and gnu17 are fairly minimal > and mainly impact warnings at the -Wpedantic level that the kernel > never enables, the easiest way is to just leave out the -std=gnu89 > argument entirely, and rely o

Re: [greybus-dev] [PATCH] Kbuild: remove -std=gnu89 from compiler arguments

On Sun, Feb 27, 2022 at 3:04 PM Alex Elder wrote: > > Glancing at the Greybus code, I don't believe there's any > reason it needs to shift a negative value. Such warnings > could be fixed by making certain variables unsigned, for > example. As mentioned in the original thread, making things unsi

[PATCH 1/9] dt-bindings: mxsfb: Add compatible for i.MX8MP

Add compatible string for i.MX8MP LCDIF variant. This is called LCDIFv3 and is completely different from the LCDIFv3 found in i.MX23 in that it has a completely scrambled register layout compared to all previous LCDIF variants. The new LCDIFv3 also supports 36bit address space. However, except for

[PATCH 3/9] drm: mxsfb: Simplify LCDIF IRQ handling

The call to drm_crtc_vblank_off(&lcdif->crtc); disables IRQ generation from the LCDIF block already and this is called in mxsfb_load() before request_irq(), so explicitly disabling IRQ using custom function like mxsfb_irq_disable() is not needed, remove it. The request_irq() call would return -ENOT

[PATCH 9/9] drm: mxsfb: Add support for i.MX8MP LCDIF variant

Add support for i.MX8MP LCDIF variant. This is called LCDIFv3 and is completely different from the LCDIFv3 found in i.MX23 in that it has a completely scrambled register layout compared to all previous LCDIF variants. The new LCDIFv3 also supports 36bit address space. However, except for the compl

[PATCH 6/9] drm: mxsfb: Factor out mxsfb_set_mode()

Pull mode registers programming from mxsfb_enable_controller() into dedicated function mxsfb_set_mode(). This is a clean up. No functional change. Signed-off-by: Marek Vasut Cc: Alexander Stein Cc: Laurent Pinchart Cc: Lucas Stach Cc: Peng Fan Cc: Robby Cai Cc: Sam Ravnborg Cc: Stefan Agner

[PATCH 8/9] drm: mxsfb: Factor out mxsfb_update_buffer()

Pull functionality responsible for programming framebuffer address into the controller into dedicated function mxsfb_update_buffer(). This is a clean up. No functional change. Signed-off-by: Marek Vasut Cc: Alexander Stein Cc: Laurent Pinchart Cc: Lucas Stach Cc: Peng Fan Cc: Robby Cai Cc: S

[PATCH 2/9] drm: mxsfb: Simplify LCDIF clock handling

The current clock handling in the LCDIF driver is a convoluted mess. Implement runtime PM ops which turn the clock ON and OFF and let the pm_runtime_get_sync()/pm_runtime_put_sync() calls in .atomic_enable and .atomic_disable callbacks turn the clock ON and OFF at the right time. This requires sli

[PATCH 4/9] drm: mxsfb: Wrap FIFO reset and comments into mxsfb_reset_block()

Wrap FIFO reset and comments into mxsfb_reset_block(), this is a clean up. No functional change. Signed-off-by: Marek Vasut Cc: Alexander Stein Cc: Laurent Pinchart Cc: Lucas Stach Cc: Peng Fan Cc: Robby Cai Cc: Sam Ravnborg Cc: Stefan Agner --- drivers/gpu/drm/mxsfb/mxsfb_kms.c | 36

[PATCH 7/9] drm: mxsfb: Reorder mxsfb_crtc_mode_set_nofb()

Reorder mxsfb_crtc_mode_set_nofb() such that all functions which perform register IO are called from one single location in this function. This is a clean up. No functional change. Signed-off-by: Marek Vasut Cc: Alexander Stein Cc: Laurent Pinchart Cc: Lucas Stach Cc: Peng Fan Cc: Robby Cai

[PATCH 5/9] drm: mxsfb: Move mxsfb_get_fb_paddr() away from register IO functions

Move mxsfb_get_fb_paddr() out of the way, away from register IO functions. This is a clean up. No functional change. Signed-off-by: Marek Vasut Cc: Alexander Stein Cc: Laurent Pinchart Cc: Lucas Stach Cc: Peng Fan Cc: Robby Cai Cc: Sam Ravnborg Cc: Stefan Agner --- drivers/gpu/drm/mxsfb/m

Re: [PATCH] drm/panel: simple: Fix Innolux G070Y2-L01 BPP settings

On 2/20/22 05:52, Laurent Pinchart wrote: Hi Marek, Thank you for the patch. On Sun, Feb 20, 2022 at 05:07:18AM +0100, Marek Vasut wrote: The Innolux G070Y2-L01 supports two modes of operation: 1) FRC=Low/NC ... MEDIA_BUS_FMT_RGB666_1X7X3_SPWG ... BPP=6 2) FRC=High . MEDIA_BUS_FMT_RGB888_1

Re: [PATCH V2] drm/imx: parallel-display: Remove bus flags check in imx_pd_bridge_atomic_check()

On 2/21/22 13:31, Boris Brezillon wrote: On Mon, 21 Feb 2022 12:56:43 +0100 Max Krummenacher wrote: Am Montag, den 21.02.2022, 09:29 +0100 schrieb Boris Brezillon: Hello Christoph, On Sat, 19 Feb 2022 09:28:44 + Christoph Niedermaier wrote: From: Max Krummenacher [mailto:max.oss...

Re: [PATCH V2] drm/imx: parallel-display: Remove bus flags check in imx_pd_bridge_atomic_check()

On 2/28/22 02:04, Marek Vasut wrote: On 2/21/22 13:31, Boris Brezillon wrote: On Mon, 21 Feb 2022 12:56:43 +0100 Max Krummenacher wrote: Am Montag, den 21.02.2022, 09:29 +0100 schrieb Boris Brezillon: Hello Christoph, On Sat, 19 Feb 2022 09:28:44 + Christoph Niedermaier wrote: From: M

[PATCH] docs: fix 'make htmldocs' error in vgaarbiter.rst

Fix following 'make htmldocs' error: Error: Cannot open file ./drivers/gpu/vga/vgaarb.c Error: Cannot open file ./drivers/gpu/vga/vgaarb.c WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -sphinx-version 2.4.4 -export ./drivers/gpu/vga/vgaarb.c' failed with return code 2 Fixes: d6e189

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

Hi all, Today's linux-next merge of the drm tree got a conflict in: drivers/gpu/drm/amd/amdgpu/amdgpu_display.c between commit: e2b993302f40 ("drm/amdgpu: bypass tiling flag check in virtual display case (v2)") from Linus' tree and commit: 2af104290da5 ("drm: introduce fb_modifiers_not

Re: linux-next: manual merge of the drm-tegra tree with the drm tree

Hi all, On Wed, 23 Feb 2022 16:30:07 + broo...@kernel.org wrote: > > Today's linux-next merge of the drm-tegra tree got conflicts in: > > drivers/gpu/drm/tegra/dpaux.c > drivers/gpu/drm/tegra/Kconfig > > between commit: > > adb9d5a2cc77e ("drm/dp: Move DisplayPort helpers into separat

Re: linux-next: build failure after merge of the drm tree

Hi all, On Fri, 25 Feb 2022 16:42:31 + broo...@kernel.org wrote: > > After merging the drm tree, today's linux-next build (x86 allmodconfig) > failed like this: > > /tmp/next/build/drivers/gpu/drm/bridge/ite-it6505.c: In function > 'receive_timing_debugfs_show': > /tmp/next/build/drivers/gpu

Re: [PATCH 9/9] drm: mxsfb: Add support for i.MX8MP LCDIF variant

Hi Marek, I love your patch! Perhaps something to improve: [auto build test WARNING on drm-intel/for-linux-next] [also build test WARNING on drm-exynos/exynos-drm-next next-20220225] [cannot apply to drm/drm-next drm-tip/drm-tip tegra-drm/drm/tegra/for-next v5.17-rc6] [If your patch is applied t

Re: [PATCH 1/9] dt-bindings: mxsfb: Add compatible for i.MX8MP

Hi Marek, On Mon, 2022-02-28 at 01:45 +0100, Marek Vasut wrote: > Add compatible string for i.MX8MP LCDIF variant. This is called LCDIFv3 > and is completely different from the LCDIFv3 found in i.MX23 in that it In i.MX23 reference manual, there is no LCDIFv3 found, but only LCDIF. > has a compl

Re: [PATCH 1/9] dt-bindings: mxsfb: Add compatible for i.MX8MP

Hi Marek, Thank you for the patch. On Mon, Feb 28, 2022 at 01:45:57AM +0100, Marek Vasut wrote: > Add compatible string for i.MX8MP LCDIF variant. This is called LCDIFv3 > and is completely different from the LCDIFv3 found in i.MX23 in that it > has a completely scrambled register layout compared

Re: linux-next: build failure after merge of the drm tree

On Sat, Feb 26, 2022 at 12:43 AM wrote: > > Hi all, > > After merging the drm tree, today's linux-next build (x86 allmodconfig) > failed like this: > > lib/strncpy_from_user.o: warning: objtool: strncpy_from_user()+0x10b: call to > do_strncpy_from_user() with UACCESS enabled > lib/strnlen_user.o:

Re: linux-next: build failure after merge of the drm tree

On Mon, 28 Feb 2022 at 16:44, Hsin-Yi Wang wrote: > > On Sat, Feb 26, 2022 at 12:43 AM wrote: > > > > Hi all, > > > > After merging the drm tree, today's linux-next build (x86 allmodconfig) > > failed like this: > > > > lib/strncpy_from_user.o: warning: objtool: strncpy_from_user()+0x10b: call >

Re: [GIT PULL] drm/tegra: Changes for v5.18-rc1

Hi Thierry, dim: d65e338027e7 ("gpu: host1x: Fix an error handling path in 'host1x_probe()'"): SHA1 in fixes line not found: dim: e3166698a8a0 ("drm/tegra: Implement buffer object cache") not the same as 1f39b1dfa53c84b56d7ad37fed44afda7004959d Author: Thierry Reding Date: Fri Feb 7 16:5

Re: [pull] amdgpu, amdkfd drm-next-5.18

On Sat, 26 Feb 2022 at 04:35, Alex Deucher wrote: > > Hi Dave, Daniel, > > New stuff for 5.18. > > The following changes since commit b63c54d978236dd6014cf2ffba96d626e97c915c: > > drm/amdkfd: Use proper enum in pm_unmap_queues_v9() (2022-02-17 15:59:06 > -0500) > > are available in the Git repo

Re: [PATCH 1/9] dt-bindings: mxsfb: Add compatible for i.MX8MP

On 2/28/22 07:37, Liu Ying wrote: Hi Marek, Hi, On Mon, 2022-02-28 at 01:45 +0100, Marek Vasut wrote: Add compatible string for i.MX8MP LCDIF variant. This is called LCDIFv3 and is completely different from the LCDIFv3 found in i.MX23 in that it In i.MX23 reference manual, there is no LCDI