From: Andrew Morton <akpm@linux-foundation.org>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net, hskinnemoen@atmel.com,
adaplas@gmail.com, linux@maxim.org.za
Subject: Re: [PATCH] atmel_lcdfb: FIFO underflow management
Date: Mon, 19 May 2008 16:00:06 -0700 [thread overview]
Message-ID: <20080519160006.12a30e71.akpm@linux-foundation.org> (raw)
In-Reply-To: <482D7F44.7040404@atmel.com>
On Fri, 16 May 2008 14:34:12 +0200
Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
> Manage atmel_lcdfb FIFO underflow
>
> Resetting the LCD and DMA allows to fix screen shifting after a
> FIFO underflow. It follows reset sequence from errata
> "LCD Screen Shifting After a Reset".
>
This looks like 2.6.26-worthy bugfix to me? But as commonly happens,
that isn't terribly clear.
> + if (status & ATMEL_LCDC_UFLWI) {
> + dev_warn(info->device, "FIFO underflow %#x\n", status);
> + /* reset DMA and FIFO to avoid screen shifting */
> + schedule_work(&sinfo->task);
> + }
> + lcdc_writel(sinfo, ATMEL_LCDC_ICR, status);
> return IRQ_HANDLED;
> }
Shouldn't there be a cancel_work_sync() in atmel_lcdfb_exit()?
> + /* Initialize bottom half workqueue */
Well. "bottom half" is an ancient term for softirqs, not for the
new-fangled process-context callbacks.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: linux-fbdev-devel@lists.sourceforge.net, adaplas@gmail.com,
hskinnemoen@atmel.com, linux@maxim.org.za,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] atmel_lcdfb: FIFO underflow management
Date: Mon, 19 May 2008 16:00:06 -0700 [thread overview]
Message-ID: <20080519160006.12a30e71.akpm@linux-foundation.org> (raw)
In-Reply-To: <482D7F44.7040404@atmel.com>
On Fri, 16 May 2008 14:34:12 +0200
Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
> Manage atmel_lcdfb FIFO underflow
>
> Resetting the LCD and DMA allows to fix screen shifting after a
> FIFO underflow. It follows reset sequence from errata
> "LCD Screen Shifting After a Reset".
>
This looks like 2.6.26-worthy bugfix to me? But as commonly happens,
that isn't terribly clear.
> + if (status & ATMEL_LCDC_UFLWI) {
> + dev_warn(info->device, "FIFO underflow %#x\n", status);
> + /* reset DMA and FIFO to avoid screen shifting */
> + schedule_work(&sinfo->task);
> + }
> + lcdc_writel(sinfo, ATMEL_LCDC_ICR, status);
> return IRQ_HANDLED;
> }
Shouldn't there be a cancel_work_sync() in atmel_lcdfb_exit()?
> + /* Initialize bottom half workqueue */
Well. "bottom half" is an ancient term for softirqs, not for the
new-fangled process-context callbacks.
next prev parent reply other threads:[~2008-05-19 23:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 12:34 [PATCH] atmel_lcdfb: FIFO underflow management Nicolas Ferre
2008-05-19 23:00 ` Andrew Morton [this message]
2008-05-19 23:00 ` Andrew Morton
2008-05-20 13:54 ` [PATCH] atmel_lcdfb: FIFO underflow management rework Nicolas Ferre
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=20080519160006.12a30e71.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adaplas@gmail.com \
--cc=hskinnemoen@atmel.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.