From: Allen Martin <amartin@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tegra: fdt: add back missing host1x node
Date: Fri, 25 Jan 2013 16:51:09 -0800 [thread overview]
Message-ID: <20130126005108.GA29859@badger> (raw)
In-Reply-To: <1359139608-29659-1-git-send-email-amartin@nvidia.com>
On Fri, Jan 25, 2013 at 10:46:47AM -0800, Allen Martin wrote:
> Add back host1x node to seaboard dts file. This got dropped during
> the tegra fdt sort.
>
> Signed-off-by: Allen Martin <amartin@nvidia.com>
> ---
Hi Albert, would it be possible for you to apply this directly to your
u-boot-arm repository? It fixes a regression introduced by my
previous patch:
b7723f3 tegra: fdt: sort dts files
So I wanted to make sure it gets applied before that previous patch
makes it to u-boot/master, and Tom's not ready to do another tegra
pull request yet.
-Allen
> board/nvidia/dts/tegra20-seaboard.dts | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/board/nvidia/dts/tegra20-seaboard.dts b/board/nvidia/dts/tegra20-seaboard.dts
> index 9cb9b5b..527a296 100644
> --- a/board/nvidia/dts/tegra20-seaboard.dts
> +++ b/board/nvidia/dts/tegra20-seaboard.dts
> @@ -27,6 +27,17 @@
> reg = < 0x00000000 0x40000000 >;
> };
>
> + host1x {
> + status = "okay";
> + dc at 54200000 {
> + status = "okay";
> + rgb {
> + status = "okay";
> + nvidia,panel = <&lcd_panel>;
> + };
> + };
> + };
> +
> /* This is not used in U-Boot, but is expected to be in kernel .dts */
> i2c at 7000d000 {
> clock-frequency = <100000>;
> --
> 1.7.10.4
>
--
nvpublic
next prev parent reply other threads:[~2013-01-26 0:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 18:46 [U-Boot] [PATCH] tegra: fdt: add back missing host1x node Allen Martin
2013-01-26 0:51 ` Allen Martin [this message]
2013-01-26 10:57 ` Albert ARIBAUD
2013-01-28 16:35 ` Tom Warren
2013-01-28 18:14 ` Albert ARIBAUD
2013-01-28 22:51 ` Allen Martin
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=20130126005108.GA29859@badger \
--to=amartin@nvidia.com \
--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 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.