All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tony Lindgren <tony@atomide.com>, Darren Etheridge <detheridge@ti.com>
Cc: bcousson@baylibre.com, linux-omap@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH] arm/dts: am335x-evmsk enable display and lcd panel support
Date: Fri, 9 May 2014 14:29:02 +0300	[thread overview]
Message-ID: <536CBBFE.40508@ti.com> (raw)
In-Reply-To: <20140506161001.GH18474@atomide.com>

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

On 06/05/14 19:10, Tony Lindgren wrote:
> * Darren Etheridge <detheridge@ti.com> [140422 13:39]:
>> Add the necessary nodes to enable the LCD controller and the
>> LCD panel that is attached to the Texas Instruments AM335x
>> EVMSK platform.  Also setup the necessary pin mux within the
>> DT file to drive the LCD connector and add the correct
>> pinmux settings for the lcd pins to be configured to when
>> the SoC goes into sleep state for the minimum power
>> consumption.
>>
>> For the sleep mode LCD pin settings, MUX_MODE7 is chosen as
>> this corresponds to switching the pins into input GPIO's with
>> an internal pulldown.  Which has been determined to offer the
>> lowest power solution vs leaving the pins configured in LCD
>> mode.
> 
> Probably best that Tomi queues all the panel .dts changes into
> a separate immutable branch that I can merge too.

This is not for OMAP DSS, but for the LCDC used in beaglebone, so there
are no dependencies to any of my work.

 Tomi



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

  reply	other threads:[~2014-05-09 11:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22 20:37 [PATCH] arm/dts: am335x-evmsk enable display and lcd panel support Darren Etheridge
2014-05-06 16:10 ` Tony Lindgren
2014-05-09 11:29   ` Tomi Valkeinen [this message]
2014-05-09 14:47     ` Darren Etheridge
2014-05-09 16:27       ` Darren Etheridge

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=536CBBFE.40508@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=detheridge@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --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.