From: Paul Cercueil <paul@crapouillou.net>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
linux-mips@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, list@opendingux.net,
Christophe Branchereau <cbranchereau@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/ingenic: Use the highest possible DMA burst size
Date: Sun, 03 Jul 2022 12:45:18 +0100 [thread overview]
Message-ID: <IN0GER.UCST485AI2YD1@crapouillou.net> (raw)
In-Reply-To: <YsE6mZanHLy9LpBd@ravnborg.org>
Hi Sam,
Le dim., juil. 3 2022 at 08:43:37 +0200, Sam Ravnborg
<sam@ravnborg.org> 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 would think that the framebuffer needs to be aligned with the burst
size, indeed. Here, our buffers are always page-aligned so that's not a
problem.
> Patch looks good and is a-b.
Thanks!
Cheers,
-Paul
>>
>> 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: <stable@vger.kernel.org>
>> Fixes: 90b86fcc47b4 ("DRM: Add KMS driver for the Ingenic JZ47xx
>> SoCs")
>> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
> Acked-by: Sam Ravnborg <sam@ravnborg.org>
next prev parent reply other threads:[~2022-07-03 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 23:07 [PATCH] drm/ingenic: Use the highest possible DMA burst size Paul Cercueil
2022-07-03 6:43 ` Sam Ravnborg
2022-07-03 11:45 ` Paul Cercueil [this message]
2022-07-04 10:11 ` Paul Cercueil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=IN0GER.UCST485AI2YD1@crapouillou.net \
--to=paul@crapouillou.net \
--cc=airlied@linux.ie \
--cc=cbranchereau@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=list@opendingux.net \
--cc=sam@ravnborg.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox