linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@suse.de>
Cc: Andrew Victor <avictor.za@gmail.com>,
	linux-fbdev-devel@lists.sourceforge.net,
	Haavard Skinnemoen <hskinnemoen@atmel.com>
Subject: Re: [PATCH] atmel_lcdfb: Correct fifo size for some products
Date: Mon, 08 Jun 2009 17:36:20 +0200	[thread overview]
Message-ID: <4A2D2FF4.1010304@atmel.com> (raw)
In-Reply-To: <20090528003526.542d306e.akpm@linux-foundation.org>

Andrew Morton :
> On Fri, 15 May 2009 12:34:18 +0200 Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
> 
>> Remove wrong fifo size definition for some AT91 products.
>>
>> Due to a misunderstanding of some AT91 datasheets, a fifo size of 2048 (words)
>> has been introduced by mistake. In fact, all products (AT91/AT32) are sharing
>> the same fifo size of 512 words.
>>
> 
> Changelog fails to describe the impact of the bug, so people who are
> working out which kernel versions it should be ported into don't know
> what to do.
> 
> Furthermore, people who are hitting a bug in this driver in older
> kernel versions will have difficulty working out whether this patch
> might fix their bug.

Ok, you are right, I will try to add some information.

In fact, if you mis-configure the fifo watermark making it too high you
end without the capacity of issuing burst transfers on the internal AHB
bus. This will decrease overall system performance as the LCD will ask
for data as soon as the fifo will have one byte available (not efficient
single accesses).

>> Can we consider this fix for .30-final ?
> 
> Sure, but for what reason?
> 
> What about 2.6.29.x, 2.6.28.x, earlier?

Indeed, should be valuable to extend this correction to stable kernel
series. I added Greg to the loop for this purpose.

>> --- a/drivers/video/atmel_lcdfb.c
>> +++ b/drivers/video/atmel_lcdfb.c
>> @@ -29,14 +29,8 @@
>>  
>>  /* configurable parameters */
>>  #define ATMEL_LCDC_CVAL_DEFAULT		0xc8
>> -#define ATMEL_LCDC_DMA_BURST_LEN	8
>> -
>> -#if defined(CONFIG_ARCH_AT91SAM9263) || defined(CONFIG_ARCH_AT91CAP9) || \
>> -	defined(CONFIG_ARCH_AT91SAM9RL)
>> -#define ATMEL_LCDC_FIFO_SIZE		2048
>> -#else
>> -#define ATMEL_LCDC_FIFO_SIZE		512
>> -#endif
>> +#define ATMEL_LCDC_DMA_BURST_LEN	8	/* words */
>> +#define ATMEL_LCDC_FIFO_SIZE		512	/* words */
>>  
>>  #if defined(CONFIG_ARCH_AT91)
>>  #define	ATMEL_LCDFB_FBINFO_DEFAULT	(FBINFO_DEFAULT \

Thanks to have taken immediately this patch into account ; even before
my late explanation ;-)

Best regards,
-- 
Nicolas Ferre


------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects

  reply	other threads:[~2009-06-08 15:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-15 10:34 [PATCH] atmel_lcdfb: Correct fifo size for some products Nicolas Ferre
2009-05-19  8:02 ` Haavard Skinnemoen
2009-05-28  7:35 ` Andrew Morton
2009-06-08 15:36   ` Nicolas Ferre [this message]
2009-06-09  0:21     ` Greg KH

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=4A2D2FF4.1010304@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=akpm@linux-foundation.org \
    --cc=avictor.za@gmail.com \
    --cc=gregkh@suse.de \
    --cc=hskinnemoen@atmel.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).