All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: "Daniel Glöckner" <dg@emlix.com>
Cc: linux-fbdev-devel@lists.sourceforge.net,
	Ben Nizette <bn@niasdigital.com>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: atmel_lcdfb: max pixclock check
Date: Tue, 12 May 2009 14:30:03 +0200	[thread overview]
Message-ID: <4A096BCB.3030403@atmel.com> (raw)
In-Reply-To: <49F1C0E4.9050906@emlix.com>

Daniel Glöckner :
> Hi,
> in the current Atmel LCD framebuffer driver there is the following check in the
> fb_check_var callback:
> 
> if ((PICOS2KHZ(var->pixclock) * var->bits_per_pixel / 8) > clk_value_khz) {
> 	dev_err(dev, "%lu KHz pixel clock is too fast\n",
> 		PICOS2KHZ(var->pixclock));
> 	return -EINVAL;
> }
> 
> I can't find any constraint like this in the data sheets and application note.
> What I can find is a minimum for clk_value_khz/PICOS2KHZ(var->pixclock)
> depending on the display type, scan mode, and interface width.

Indeed, I have just acked a patch from Ben Nizette removing this constrain.
http://lkml.org/lkml/2009/5/12/189

> Is the quoted if-statement correct or should it be changed to a minimum clock
> divider check?

We can imagine such a check depending on display type. Patches welcome ;-)

> And while we're at it, is it correct to return -EINVAL here instead of changing
> var->pixclock to the closest supported value?

I do not know... Maybe someone on linux-fb-devel can answer ?

Bye,
-- 
Nicolas Ferre

           reply	other threads:[~2009-05-12 12:30 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <49F1C0E4.9050906@emlix.com>]

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=4A096BCB.3030403@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=bn@niasdigital.com \
    --cc=dg@emlix.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@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 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.