[lkml]   [2022]   [Jul]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] drm/ingenic: Use the highest possible DMA burst size
Hi Sam,

Le dim., juil. 3 2022 at 08:43:37 +0200, Sam Ravnborg
<> a écrit :
> Hi Paul,
> On Sun, Jul 03, 2022 at 12:07:27AM +0100, Paul Cercueil wrote:
>> Until now, when running at the maximum resolution of 1280x720 at
>> 32bpp
>> on the JZ4770 SoC the output was garbled, the X/Y position of the
>> top-left corner of the framebuffer warping to a random position with
>> the whole image being offset accordingly, every time a new frame was
>> being submitted.
>> This problem can be eliminated by using a bigger burst size for the
>> DMA.
> Are there any alignment constraints of the framebuffer that depends on
> the burst size? I am hit by this with some atmel IP - which is why I
> ask.

I verified this, and everything behaves correctly when the source
address is not aligned to the burst size. So I believe in our case the
DMA is smart enough to auto-select the best burst size, up to the
configured value.


> Patch looks good and is a-b.
>> Set in each soc_info structure the maximum burst size supported by
>> the
>> corresponding SoC, and use it in the driver.
>> Set the new value using regmap_update_bits() instead of
>> regmap_set_bits(), since we do want to override the old value of the
>> burst size. (Note that regmap_set_bits() wasn't really valid before
>> for
>> the same reason, but it never seemed to be a problem).
>> Cc: <>
>> Fixes: 90b86fcc47b4 ("DRM: Add KMS driver for the Ingenic JZ47xx
>> SoCs")
>> Signed-off-by: Paul Cercueil <>
> Acked-by: Sam Ravnborg <>

 \ /
  Last update: 2022-07-04 12:12    [W:0.047 / U:0.316 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site