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 3/5] arm: tegra30: video: integrate display driver for t30
Date: Thu, 20 Aug 2015 14:10:35 -0600	[thread overview]
Message-ID: <55D6343B.2040602@wwwdotorg.org> (raw)
In-Reply-To: <1440070152-27094-4-git-send-email-marcel.ziswiler@toradex.com>

On 08/20/2015 05:29 AM, Marcel Ziswiler wrote:
> On popular request make the display driver from T20 work on T30 as
> well. Turned out to be quite straight forward. However a few notes
> about some things encountered during porting: Of course the T30 device
> tree was completely missing host1x as well as PWM support but it turns
> out this can simply be copied from T20 supplementing some tegra30-
> compatible nodes here and there while comparing it with the Linux
> device tree includes.

Hopefully the process was to copy the Linux Tegra30 DT verbatim? That's 
far more likely to yield a correct DT than copying the Tegra20 DT to 
Tegra30 and then patching it until it works. If this DT doesn't exactly 
match the Linux kernel, this needs to be fixed.

> diff --git a/arch/arm/mach-tegra/tegra30/Makefile b/arch/arm/mach-tegra/tegra30/Makefile

> -obj-$(CONFIG_SPL_BUILD) += cpu.o
> +ifdef CONFIG_SPL_BUILD
> +obj-y	+= cpu.o


I don't think there's any need to edit the cpu.o line. While you can 
move it into the ifdef like that, I don't see a need.

> diff --git a/arch/arm/mach-tegra/tegra30/display.c b/arch/arm/mach-tegra/tegra30/display.c

I didn't review this file in detail; I'll leave that to Thierry since he 
knows the display HW.

However, one question: Is this file a complete cut/paste of 
tegra20/display.c, or does it just replace some parts of it? Hopefully 
this patch doesn't simply duplicate the whole driver?

  reply	other threads:[~2015-08-20 20:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 11:29 [U-Boot] [PATCH 0/5] arm: tegra: apalis/colibri_t30: video: add display driver Marcel Ziswiler
2015-08-20 11:29 ` [U-Boot] [PATCH 1/5] arm: tegra20: video: rename display header ifdef gating Marcel Ziswiler
2015-08-23 21:22   ` Simon Glass
2015-08-20 11:29 ` [U-Boot] [PATCH 2/5] arm: tegra20: video: ifdef gate hard-coded ugly Tegra20 pin muxing Marcel Ziswiler
2015-08-20 20:05   ` Stephen Warren
2015-08-20 11:29 ` [U-Boot] [PATCH 3/5] arm: tegra30: video: integrate display driver for t30 Marcel Ziswiler
2015-08-20 20:10   ` Stephen Warren [this message]
2015-08-20 11:29 ` [U-Boot] [PATCH 4/5] colibri_t30: enable display driver Marcel Ziswiler
2015-08-23 21:22   ` Simon Glass
2015-08-20 11:29 ` [U-Boot] [PATCH 5/5] apalis_t30: " Marcel Ziswiler
2015-08-23 21:23   ` Simon Glass
  -- strict thread matches above, loose matches on Subject: below --
2015-08-20 23:46 [U-Boot] [PATCH 3/5] arm: tegra30: video: integrate display driver for t30 Marcel Ziswiler
2015-08-21  9:27 ` Thierry Reding
2015-08-22  0:37   ` Simon Glass
2015-08-24 10:12     ` Thierry Reding
2015-08-24 16:58       ` Simon Glass
2015-08-25 11:02         ` Thierry Reding
2015-08-25 16:03           ` Simon Glass
2015-08-26  7:29             ` Thierry Reding
2015-08-26 13:32               ` Simon Glass
2015-08-24 22:03 Marcel Ziswiler
2015-08-26  7:39 ` Thierry Reding
2015-08-26 13:32   ` Simon Glass
2015-08-24 22:13 Marcel Ziswiler

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=55D6343B.2040602@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