public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Mayuresh Janorkar <mayur@ti.com>
Cc: linux-omap@vger.kernel.org, Mythri P K <mythripk@ti.com>
Subject: Re: [PATCH 6/7] OMAP4: DSS: Adding a picodlp in OMAP4430 SDP board file
Date: Tue, 19 Apr 2011 14:54:25 +0300	[thread overview]
Message-ID: <1303214065.32281.47.camel@deskari> (raw)
In-Reply-To: <1303107350-22747-7-git-send-email-mayur@ti.com>

On Mon, 2011-04-18 at 11:45 +0530, Mayuresh Janorkar wrote:
> An on-board panel named picodlp projector is available for OMAP4430 SDP.
> 
> Entry for this panel is being added in dss_devices in the board file.
> It also needs 4 GPIO pins and are defined and used in board file.
> picodlp also needs an i2c client over i2c controller-2 at address 0x1b.
> 
> Signed-off-by: Mayuresh Janorkar <mayur@ti.com>
> Signed-off-by: Mythri P K <mythripk@ti.com>
> ---
>  arch/arm/mach-omap2/board-4430sdp.c |   40 +++++++++++++++++++++++++++++++++++
>  1 files changed, 40 insertions(+), 0 deletions(-)
> diff --git a/arch/arm/mach-omap2/board-4430sdp.c b/arch/arm/mach-omap2/board-4430sdp.c
> index 1503f0b..6827612
> --- a/arch/arm/mach-omap2/board-4430sdp.c
> +++ b/arch/arm/mach-omap2/board-4430sdp.c
> @@ -38,6 +38,7 @@
>  #include <plat/omap4-keypad.h>
>  #include <plat/display.h>
>  #include <plat/nokia-dsi-panel.h>
> +#include <plat/panel-picodlp.h>
>  
>  #include "mux.h"
>  #include "hsmmc.h"
> @@ -585,6 +586,7 @@ static struct i2c_board_info __initdata sdp4430_i2c_boardinfo[] = {
>  		.platform_data = &sdp4430_twldata,
>  	},
>  };
> +

Unneeded change.

>  static struct i2c_board_info __initdata sdp4430_i2c_3_boardinfo[] = {
>  	{
>  		I2C_BOARD_INFO("tmp105", 0x48),
> @@ -598,6 +600,7 @@ static struct i2c_board_info __initdata sdp4430_i2c_4_boardinfo[] = {
>  		I2C_BOARD_INFO("hmc5843", 0x1e),
>  	},
>  };
> +

Unneeded change.

 Tomi



  reply	other threads:[~2011-04-19 11:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-18  6:15 [PATCH 0/7] picodlp projector driver Mayuresh Janorkar
2011-04-18  6:15 ` [PATCH 1/7] OMAP: DSS: Adding a header file for picodlp panel data Mayuresh Janorkar
2011-04-18  6:15 ` [PATCH 2/7] OMAP: DSS: Adding a picodlp panel header file Mayuresh Janorkar
2011-04-18  6:15 ` [PATCH 3/7] OMAP: DSS: Adding a picodlp panel driver Mayuresh Janorkar
2011-04-19 11:09   ` Tomi Valkeinen
2011-04-21 11:06     ` Janorkar, Mayuresh
2011-04-26 10:42       ` Tomi Valkeinen
2011-04-18  6:15 ` [PATCH 4/7] OMAP: DSS: Add i2c client driver for picodlp Mayuresh Janorkar
2011-04-19 11:26   ` Tomi Valkeinen
2011-04-19 11:42   ` Tomi Valkeinen
2011-04-21 11:08     ` Janorkar, Mayuresh
2011-04-18  6:15 ` [PATCH 5/7] OMAP: DSS: Adding initialization routine to picodlp panel Mayuresh Janorkar
2011-04-19 11:52   ` Tomi Valkeinen
2011-04-21 11:17     ` Janorkar, Mayuresh
2011-04-26 10:47       ` Tomi Valkeinen
2011-04-18  6:15 ` [PATCH 6/7] OMAP4: DSS: Adding a picodlp in OMAP4430 SDP board file Mayuresh Janorkar
2011-04-19 11:54   ` Tomi Valkeinen [this message]
2011-04-21 11:18     ` Janorkar, Mayuresh
2011-04-18  6:15 ` [PATCH 7/7] OMAP4: DSS: Adding picodlp panel entry in Kconfig and Makefile Mayuresh Janorkar

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