linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] video: mxsfb: Fix framebuffer corruption on mx6sx
Date: Fri, 26 Aug 2016 15:28:54 +0000	[thread overview]
Message-ID: <b8587113-0750-fa66-c067-a2496f038359@denx.de> (raw)
In-Reply-To: <20160826143045.7386-1-marex@denx.de>

On 08/26/2016 04:38 PM, Lucas Stach wrote:
> Am Freitag, den 26.08.2016, 16:30 +0200 schrieb Marek Vasut:
>> Allocate the framebuffer memory as coherent, otherwise the framebuffer
>> will suffer from artifacts when displaying scrolling text or video.
>> This can be replicated on i.MX6SX (armv7), which has more complex memory
>> architecture compared to the i.MX23/28 (armv5).
>>
>> Signed-off-by: Marek Vasut <marex@denx.de>
>> Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
>> Cc: Fabio Estevam <fabio.estevam@nxp.com>
>> Cc: Lucas Stach <l.stach@pengutronix.de>
>> Cc: Shawn Guo <shawnguo@kernel.org>
>> ---
>>  drivers/video/fbdev/mxsfb.c | 10 ++++++----
>>  1 file changed, 6 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/video/fbdev/mxsfb.c b/drivers/video/fbdev/mxsfb.c
>> index 4e6608c..bd1a310 100644
>> --- a/drivers/video/fbdev/mxsfb.c
>> +++ b/drivers/video/fbdev/mxsfb.c
>> @@ -800,6 +800,7 @@ static int mxsfb_init_fbinfo(struct mxsfb_info *host,
>>  			struct fb_videomode *vmode)
>>  {
>>  	int ret;
>> +	struct device *dev = &host->pdev->dev;
>>  	struct fb_info *fb_info = &host->fb_info;
>>  	struct fb_var_screeninfo *var = &fb_info->var;
>>  	dma_addr_t fb_phys;
>> @@ -825,12 +826,11 @@ static int mxsfb_init_fbinfo(struct mxsfb_info *host,
>>  
>>  	/* Memory allocation for framebuffer */
>>  	fb_size = SZ_2M;
>> -	fb_virt = alloc_pages_exact(fb_size, GFP_DMA);
>> +	fb_virt = dma_alloc_coherent(dev, PAGE_ALIGN(fb_size), &fb_phys,
>> +				     GFP_KERNEL);
> 
> You probably want writecombined memory here instead of coherent. Using
> coherent memory for framebuffers sucks performance wise.

Ah, true. That'd be dma_{alloc,free}_wc() , right ?

-- 
Best regards,
Marek Vasut

      parent reply	other threads:[~2016-08-26 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26 14:30 [PATCH] video: mxsfb: Fix framebuffer corruption on mx6sx Marek Vasut
2016-08-26 14:38 ` Lucas Stach
2016-08-26 15:28 ` Marek Vasut [this message]

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=b8587113-0750-fa66-c067-a2496f038359@denx.de \
    --to=marex@denx.de \
    --cc=linux-fbdev@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;
as well as URLs for NNTP newsgroup(s).