public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] tegra: enable LCD on PAZ00
Date: Tue, 27 Nov 2012 12:53:08 -0700	[thread overview]
Message-ID: <50B51A24.90607@wwwdotorg.org> (raw)
In-Reply-To: <50B4FB7A.5030507@wwwdotorg.org>

On 11/27/2012 10:42 AM, Stephen Warren wrote:
> On 11/26/2012 05:07 PM, Tom Warren wrote:
>> TEGRA_DEVICE_SETTINGS patch is assigned to Marek and waiting on him to
>> pull 'em thru the USB tree.
> 
> It looks like the patch has been in u-boot-usb/master for about a week.
> 
> (we really need a linux-next for U-Boot to hide all the pull latency)
> 
> So, I'd propose that paz00.h can add the config options to enable LCD
> support right now, but that changes to TEGRA_DEVICE_SETTINGS should
> instead be implemented generically as a change to the logic in
> tegra-common-post.h (and hence support all boards not just paz00),
> either applied to u-boot-usb/master right now, or u-boot-tegra/master
> once the dependencies are enabled there.

It's been pointed out that Seaboard already uses this method to override
TEGRA_DEVICE_SETTINGS. Given that precedent, I withdraw any objection.
We'll just have to remember to fix this all up once the
TEGRA_DEVICE_SETTINGS patch makes its way from u-boot-usb to u-boot-tegra.

  reply	other threads:[~2012-11-27 19:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-25 21:26 [U-Boot] [PATCH 1/2] tegra: display: add board pinmux Marc Dietrich
2012-11-25 21:26 ` [U-Boot] [PATCH 2/2] tegra: enable LCD on PAZ00 Marc Dietrich
2012-11-26 19:00   ` Stephen Warren
2012-11-26 21:00     ` Marc Dietrich
2012-11-27  0:07       ` Tom Warren
2012-11-27 17:42         ` Stephen Warren
2012-11-27 19:53           ` Stephen Warren [this message]
2012-11-27 21:59             ` Marek Vasut
2012-11-26 16:55 ` [U-Boot] [PATCH 1/2] tegra: display: add board pinmux Tom Warren
2012-11-26 20:51   ` Marc Dietrich

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=50B51A24.90607@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=u-boot@lists.denx.de \
    /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