From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: mythripk@ti.com
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH v4 0/2] OMAPDSS: HDMI: Boardfile cleanup
Date: Tue, 03 Jan 2012 11:39:43 +0200 [thread overview]
Message-ID: <1325583583.1973.11.camel@deskari> (raw)
In-Reply-To: <1325493158-25740-1-git-send-email-mythripk@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
On Mon, 2012-01-02 at 14:02 +0530, mythripk@ti.com wrote:
> From: Mythri P K <mythripk@ti.com>
>
> Clean up of boardfiles to have the functions common to differnt boards in a
> common display file, Also in some OMAP4 boards external pull-up's are enabled
> thus enabling internal pull up should be a parameter from the boardfile.
>
> changes since v3 : Comment improvement to move some portion from boardfile to
> display.
> changes since v2 : Make the flag as enum.
> changes since v1 : Make omap hdmi_init generic to handle different parameters
> and pass the pull up as a flag instead of int.
>
> Mythri P K (2):
> OMAPDSS: HDMI: Move duplicate code from boardfile
> OMAPDSS: HDMI: Disable DDC internal pull up
>
> arch/arm/mach-omap2/board-4430sdp.c | 23 ++++++------------
> arch/arm/mach-omap2/board-omap4panda.c | 25 +++++++-------------
> arch/arm/mach-omap2/display.c | 39 ++++++++++++++++++++++++++++++++
> include/video/omapdss.h | 6 +++++
> 4 files changed, 62 insertions(+), 31 deletions(-)
These look fine, I'll apply to DSS tree.
Btw, do you know what is the reason to use an external pull-up on the
newer boards? Is the internal pull-up somehow insufficient?
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-01-03 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 8:32 [PATCH v4 0/2] OMAPDSS: HDMI: Boardfile cleanup mythripk
2012-01-02 8:32 ` [PATCH v4 1/2] OMAPDSS: HDMI: Move duplicate code from boardfile mythripk
2012-01-02 8:32 ` [PATCH v4 2/2] OMAPDSS: HDMI: Disable DDC internal pull up mythripk
2012-01-03 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=1325583583.1973.11.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