linux-kernel - Re: [PATCH] atmel_lcdfb: FIFO underflow management

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080519160006.12a30e71.akpm@linux-foundation.org>
Date:	Mon, 19 May 2008 16:00:06 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Nicolas Ferre <nicolas.ferre@...el.com>
Cc:	linux-fbdev-devel@...ts.sourceforge.net, adaplas@...il.com,
	hskinnemoen@...el.com, linux@...im.org.za,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] atmel_lcdfb: FIFO underflow management

On Fri, 16 May 2008 14:34:12 +0200
Nicolas Ferre <nicolas.ferre@...el.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/