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

On Mon, Jun 08, 2009 at 05:36:20PM +0200, Nicolas Ferre wrote:
> 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.

For stable stuff, please send any requested patches, with the git commit
id of the patch in Linus's tree, to stable@kernel.org, otherwise I might
miss it :)

Also, you can add:
	Cc: stable <stable@kernel.org>
to the signed-off-by area of the patch, and when it is taken into
Linus's tree, the stable team will automatically get notified of it and
include it in the next stable releases without any other work needed to
be done by you.

hope this helps,

greg k-h

------------------------------------------------------------------------------
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-09  1:10 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
2009-06-09  0:21     ` Greg KH [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=20090609002121.GA22622@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=avictor.za@gmail.com \
    --cc=hskinnemoen@atmel.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=nicolas.ferre@atmel.com \
    /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).