All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Thomas Weber <thomas@tomweber.eu>
Cc: tony@atomide.com, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	stable@vger.kernel.org.#v3.5.v3.6
Subject: Re: [PATCH] ARM: OMAP3: Devkit8000: Fix dvi output
Date: Mon, 19 Nov 2012 07:52:09 +0200	[thread overview]
Message-ID: <50A9C909.1030006@ti.com> (raw)
In-Reply-To: <1353256083-19983-1-git-send-email-thomas@tomweber.eu>

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

On 2012-11-18 18:28, Thomas Weber wrote:
> Add i2c bus number for DVI output.
> The driver uses this to detect if a panel is connected and to read EDID.
> 
> Signed-off-by: Thomas Weber <thomas@tomweber.eu>
> Cc: stable@vger.kernel.org #v3.5 v3.6
> ---
>  arch/arm/mach-omap2/board-devkit8000.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm/mach-omap2/board-devkit8000.c b/arch/arm/mach-omap2/board-devkit8000.c
> index 1fd161e..73d3d8e 100644
> --- a/arch/arm/mach-omap2/board-devkit8000.c
> +++ b/arch/arm/mach-omap2/board-devkit8000.c
> @@ -138,6 +138,7 @@ static struct omap_dss_device devkit8000_lcd_device = {
>  };
>  
>  static struct tfp410_platform_data dvi_panel = {
> +	.i2c_bus_num		= 1,
>  	.power_down_gpio	= -1,
>  };

That change is already included in the "[PATCH] OMAP: board-files: fix
i2c_bus for tfp410" path I sent on Friday.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 897 bytes --]

       reply	other threads:[~2012-11-19  5:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1353256083-19983-1-git-send-email-thomas@tomweber.eu>
2012-11-19  5:52 ` Tomi Valkeinen [this message]
2012-11-19  6:10   ` [PATCH] ARM: OMAP3: Devkit8000: Fix dvi output Thomas Weber
2012-11-19  6:10     ` Thomas Weber

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=50A9C909.1030006@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=stable@vger.kernel.org.#v3.5.v3.6 \
    --cc=thomas@tomweber.eu \
    --cc=tony@atomide.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 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.