linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 06/23] video: da8xx-fb: store clk rate even if !CPUFREQ
Date: Wed, 26 Jun 2013 09:39:24 +0000	[thread overview]
Message-ID: <51CAB6CC.1050707@ti.com> (raw)
In-Reply-To: <1372170171-9561-7-git-send-email-detheridge@ti.com>

[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]

On 25/06/13 17:22, Darren Etheridge wrote:
> From: Afzal Mohammed <afzal@ti.com>
> 
> store lcd clk rate always, i.e. irrespective of whether CPUFREQ is
> enabled or not. This can be used to get clk rate directly instead of
> enquiring with clock framework with clk handle every time.
> 
> Signed-off-by: Afzal Mohammed <afzal@ti.com>
> Signed-off-by: Darren Etheridge <detheridge@ti.com>
> ---
>  drivers/video/da8xx-fb.c |    4 +---
>  1 files changed, 1 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/video/da8xx-fb.c b/drivers/video/da8xx-fb.c
> index d060f14..f1d88ac 100644
> --- a/drivers/video/da8xx-fb.c
> +++ b/drivers/video/da8xx-fb.c
> @@ -174,8 +174,8 @@ struct da8xx_fb_par {
>  	unsigned int		which_dma_channel_done;
>  #ifdef CONFIG_CPU_FREQ
>  	struct notifier_block	freq_transition;
> -	unsigned int		lcd_fck_rate;
>  #endif
> +	unsigned int		lcd_fck_rate;

The naming related to this clock is quite confusing. There's
lcd_fck_rate, fb_clk and lcdc_clk, all of which refer to the same clock
as far as I understand.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

      reply	other threads:[~2013-06-26  9:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25 14:22 [PATCH 06/23] video: da8xx-fb: store clk rate even if !CPUFREQ Darren Etheridge
2013-06-26  9:39 ` Tomi Valkeinen [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=51CAB6CC.1050707@ti.com \
    --to=tomi.valkeinen@ti.com \
    --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 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).