public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "K, Mythri P" <mythripk@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v2 2/8] OMAP4 : DSS2 : HDMI: HDMI specific display controller and dss change.
Date: Thu, 3 Mar 2011 08:40:32 +0200	[thread overview]
Message-ID: <1299134432.2615.12.camel@deskari> (raw)
In-Reply-To: <AANLkTikzAD-B9LcK30v8J6MeMPHZ2FDRYcp5VFPR47TY@mail.gmail.com>

Hi,

On Wed, 2011-03-02 at 23:29 -0600, K, Mythri P wrote:
> Hi Tomi,
> I just rechecked the TRM.
> The TRM description of the bit is VENC_HDMI_switch , Wouldnt it be
> appropriate to have the same
> name for the enum and the variables as suggested by you.

Please don't top-post when posting to mailing lists.

Yes, it's a good rule of thumb to have similar naming with the TRM.
However, we shouldn't follow TRM blindly, and also TRM can be changed.

In this case we already have a bunch of functions to configure the clock
muxes, like
void dss_select_dispc_clk_source(enum dss_clk_source clk_src)

Also, a function name like dss_select_hdmi_venc doesn't really tell
anything about what it does. Even if you know the architecture of DSS
HW, you can't deduce what the function does.

And usually when you are pondering about the clocking configuration, you
look at the DSS clock tree figure (fig 10-4), or the DSS clock sources
table 10-3. And in this case I believe the naming in those figures and
tables are much better than the name of the bit we are setting.

 Tomi



  reply	other threads:[~2011-03-03  6:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-01 14:16 [PATCH v2 0/8] OMAP4 : DSS2 : HDMI support Mythri P K
2011-03-01 14:16 ` [PATCH v2 1/8] OMAP4 : DSS2 : Add display type HDMI to DSS2 Mythri P K
2011-03-01 14:16 ` [PATCH v2 2/8] OMAP4 : DSS2 : HDMI: HDMI specific display controller and dss change Mythri P K
2011-03-01 17:01   ` Tomi Valkeinen
2011-03-03  4:27     ` K, Mythri P
2011-03-03  5:29       ` K, Mythri P
2011-03-03  6:40         ` Tomi Valkeinen [this message]
2011-03-01 14:16 ` [PATCH v2 3/8] OMAP4 : DSS2 : HDMI: HDMI driver header file addition Mythri P K
2011-03-01 17:23   ` Tomi Valkeinen
2011-03-01 14:16 ` [PATCH v2 4/8] OMAP4 : DSS2 : HDMI: HDMI driver addition in the DSS drivers interface Mythri P K
2011-03-01 17:37   ` Tomi Valkeinen
2011-03-03  4:35     ` K, Mythri P
2011-03-01 14:16 ` [PATCH v2 5/8] OMAP4 : DSS2 : HDMI: HDMI panel driver addition in the DSS Mythri P K
2011-03-01 17:11   ` Tomi Valkeinen
2011-03-03  4:28     ` K, Mythri P
2011-03-01 14:16 ` [PATCH v2 6/8] OMAP4 : DSS : HDMI: Call to HDMI module init to register driver Mythri P K
2011-03-01 14:16 ` [PATCH v2 7/8] OMAP4 : HDMI : Add HDMI structure in the board file for OMAP4 SDP Mythri P K
2011-03-01 14:16 ` [PATCH v2 8/8] OMAP4 : HDMI : Add HDMI structure in the board file for OMAP4 PANDA Mythri P K

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=1299134432.2615.12.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mythripk@ti.com \
    /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