[RESEND PATCHv2 1/2] drm: Add SDP Error Detection Configuration Register

DP2.0 E11 defines a new register to facilitate SDP error detection by a 128B/132B capable DPRX device. v2: Update the macro name to reflect the DP spec(Harry) Signed-off-by: Arun R Murthy Reviewed-by: Harry Wentland --- include/drm/display/drm_dp.h | 3 +++ 1 file changed, 3 insertions(+)

[PATCHv3 0/2] DP2.0 SDP CRC16 for 128/132b link layer

*** BLURB HERE *** Arun R Murthy (2): drm: Add SDP Error Detection Configuration Register i915/display/dp: SDP CRC16 for 128b132b link layer .../gpu/drm/i915/display/intel_dp_link_training.c| 12 include/drm/display/drm_dp.h | 3 +++ 2 files

Re: [PATCH] drm/edid: fix info leak when failing to get panel id

On Thu, 02 Mar 2023, Johan Hovold wrote: > Make sure to clear the transfer buffer before fetching the EDID to > avoid leaking slab data to the logs on errors that leave the buffer > unchanged. > > Fixes: 69c7717c20cc ("drm/edid: Dump the EDID when drm_edid_get_panel_id() > has an error") > Cc:

[PATCH 0/2] drm/nouveau: avoid usage of list iterator after loop

This patch set includes two instances where the list iterator variable 'pstate' is implicitly assumed to be valid after the iterator loop. While in pratice that is most likely the case (if 'pstatei'/'args->v0.state' is <= the elements in clk->states), we should explicitly only allow 'pstate' to

Re: [PATCH] drm/mediatek: dsi: fix error codes in mtk_dsi_host_transfer()

Dear Dan, Thank you for your patch. On lun., févr. 27, 2023 at 13:08, Dan Carpenter wrote: > There is a type bug because the return statement: > > return ret < 0 ? ret : recv_cnt; > > will not return negatives on 64bit systems. The problem is that the > function returns ssize_t types,

[PATCH 1/2] drm/nouveau/device: avoid usage of list iterator after loop

If potentially no valid element is found, 'pstate' would contain an invalid pointer past the iterator loop. To ensure 'pstate' is always valid, we only set it if the correct element was found. That allows adding a BUG_ON in case the code works incorrectly, exposing currently undetectable potential

Re: [PATCH] dt-bindings: Fix SPI and I2C bus node names in examples

On Tue, 28 Feb 2023 at 14:54, Rob Herring wrote: > > SPI and I2C bus node names are expected to be "spi" or "i2c", > respectively, with nothing else, a unit-address, or a '-N' index. A > pattern of 'spi0' or 'i2c0' or similar has crept in. Fix all these > cases. Mostly scripted with the following

[PATCH 2/2] drm/nouveau/clk: avoid usage of list iterator after loop

If potentially no valid element is found, 'pstate' would contain an invalid pointer past the iterator loop. To ensure 'pstate' is always valid, we only set it if the correct element was found. That allows adding a BUG_ON in case the code works incorrectly, exposing currently undetectable potential

Re: [PATCH] drm/vram-helper: turn on PRIME import/export

Hi Am 01.03.23 um 23:29 schrieb Simon Ser: We don't populate gem_prime_import_sg_table so only DMA-BUFs exported from our own device can be imported. Still, this is useful to user-space. VRAM helpers don't really offer much flexibility or control in where to place a BO. What happens if the

<    1   2