From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "Taneja, Archit" <archit@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] OMAP2PLUS: DSS2: Clock Source Changes
Date: Tue, 8 Mar 2011 18:24:07 +0200 [thread overview]
Message-ID: <1299601447.2131.16.camel@deskari> (raw)
In-Reply-To: <1299585035-26931-1-git-send-email-archit@ti.com>
On Tue, 2011-03-08 at 05:50 -0600, Taneja, Archit wrote:
> There are clocks on OMAP4 within DSS2 which can have multiple clock sources.
> This cleans up the existing way of selecting/getting the clock sources and add
> some of the new clock sources for OMAP4.
>
> Applies over:
> http://gitorious.org/linux-omap-dss2/linux/commits/master
>
> Archit Taneja (2):
> OMAP2PLUS: DSS2: Cleanup clock source related code
> OMAP4: DSS2: Clock source changes for OMAP4
The set looks good. I'll apply it tomorrow morning after some testing.
But something for future patches:
The naming of the functions could be made clearer. We have logic clock
for the LCD outputs but also for DISPC. So for example dispc_lclk_rate()
could be dispc_lcd_lclk_rate(), to make sure it's not called when the
caller needs to know the lclk of dispc. And it looks too similar to
dispc_fclk_rate() which returns clock for dispc core, easily giving the
impression that these two are linked.
And similarly dispc_pclk_rate() could be dispc_lcd_pclk_rate(), to make
clear that it's not for example venc pixel clock.
Perhaps there are also other functions whose name could be more specific
now that we have separate clocks for dispc core and the lcd paths.
Tomi
prev parent reply other threads:[~2011-03-08 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 11:50 [PATCH v2 0/2] OMAP2PLUS: DSS2: Clock Source Changes Archit Taneja
2011-03-08 11:50 ` [PATCH v2 1/2] OMAP2PLUS: DSS2: Cleanup clock source related code Archit Taneja
2011-03-08 11:50 ` [PATCH v2 2/2] OMAP4: DSS2: Clock source changes for OMAP4 Archit Taneja
2011-03-08 16:24 ` 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=1299601447.2131.16.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=archit@ti.com \
--cc=linux-omap@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.