All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] drivers/video: fsl-diu-fb: don't initialize the THRESHOLDS registers
Date: Sun, 13 May 2012 21:00:39 +0000	[thread overview]
Message-ID: <4FB020F7.504@gmx.de> (raw)
In-Reply-To: <1336687048-16519-1-git-send-email-timur@freescale.com>

On 05/10/2012 09:57 PM, Timur Tabi wrote:
> The THRESHOLDS register configures thresholds for two interrupts, but
> these interrupts are not used in the DIU driver.  An early version of the
> driver may have used the "lines before vsync" interrupt, which requires
> the LS_BF_VS of THRESHOLDS to be initialized.
> 
> Unfortunately, the initialization of this register does not do a
> read-modify-write to set only LS_BF_VS.  On the MPC8610, the value
> written is correct.  On other chips, like the P1022, the value overwrites
> some reserved bits.  This results in a performance drop on the P1022.
> 
> Since the default value is acceptable as-is on all SOCs, we should just
> avoid touching this register.
> 
> Signed-off-by: Timur Tabi <timur@freescale.com>

Applied.


Thanks,

Florian Tobias Schandinat

> ---
>  drivers/video/fsl-diu-fb.c |    1 -
>  1 files changed, 0 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/video/fsl-diu-fb.c b/drivers/video/fsl-diu-fb.c
> index 6af3f16..458c006 100644
> --- a/drivers/video/fsl-diu-fb.c
> +++ b/drivers/video/fsl-diu-fb.c
> @@ -834,7 +834,6 @@ static void update_lcdc(struct fb_info *info)
>  	diu_ops.set_pixel_clock(var->pixclock);
>  
>  	out_be32(&hw->syn_pol, 0);	/* SYNC SIGNALS POLARITY */
> -	out_be32(&hw->thresholds, 0x00037800); /* The Thresholds */
>  	out_be32(&hw->int_status, 0);	/* INTERRUPT STATUS */
>  	out_be32(&hw->plut, 0x01F5F666);
>  


      reply	other threads:[~2012-05-13 21:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 21:57 [PATCH] drivers/video: fsl-diu-fb: don't initialize the THRESHOLDS registers Timur Tabi
2012-05-13 21:00 ` Florian Tobias Schandinat [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=4FB020F7.504@gmx.de \
    --to=florianschandinat@gmx.de \
    --cc=linux-fbdev@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.