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,
	Ricardo Salveti de Araujo <ricardo.salveti@linaro.org>
Subject: Re: [PATCH 2/2] OMAPDSS: HDMI: Disable DDC internal pull up
Date: Mon, 19 Dec 2011 10:31:15 +0200	[thread overview]
Message-ID: <1324283475.1903.28.camel@deskari> (raw)
In-Reply-To: <CAP5A+B-+SXzGOvY_51v32iHEC7vO0OMbfVMGR+TK3FGH3DkJpA@mail.gmail.com>

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

On Mon, 2011-12-19 at 13:56 +0530, K, Mythri P wrote:
> >> +     /*
> >> +      * CONTROL_I2C_1: HDMI_DDC_SDA_PULLUPRESX (bit 28) and
> >> +      * HDMI_DDC_SCL_PULLUPRESX (bit 24) are set to disable
> >> +      * internal pull up resistor - This is a change needed in
> >> +      * OMAP4460SDP/Blaze and OMAP4430 ES2.3 SDP/Blaze Boards as
> the
> >> +      * external pull up are present. This is needed to avoid
> >> +      * EDID read failure.
> >> +      */
> >
> Well CONTROL_I2C_1: HDMI_DDC_SDA_PULLUPRESX (bit 28) and
> HDMI_DDC_SCL_PULLUPRESX (bit 24) are marked as reserved bits in TRM
> and hence dont feature there so wanted to add to make clear as to what
> these bits mean, I can remove. 

It is fine to have the comments (and even good, if they are indeed not
mentioned in the TRM). My point was that the comments are in the wrong
place. You are not writing the bits in the board file, where the
comments are. You are writing the bits in display.c, which is where the
comments should be.

So in the board file you should have comment about the pull up without
the exact bit details, like I gave the example:

> "OMAP4460SDP/Blaze and OMAP4430 ES2.3 SDP/Blaze boards and later have
> external pull up on the HDMI I2C lines."

And in the display.c you can give details about the bits, if required.

 Tomi


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2011-12-19  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13  5:56 [PATCH 1/2] OMAPDSS: HDMI: Move duplicate code from boardfile mythripk
2011-12-13  5:56 ` [PATCH 2/2] OMAPDSS: HDMI: Disable DDC internal pull up mythripk
2011-12-13  8:48   ` Tomi Valkeinen
2011-12-19  8:26     ` K, Mythri P
2011-12-19  8:31       ` 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=1324283475.1903.28.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mythripk@ti.com \
    --cc=ricardo.salveti@linaro.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