public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Minkyu Kang <mk7.kang@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/2 v3] No need for parade bridge on peach-pi
Date: Mon, 22 Dec 2014 21:22:01 +0900	[thread overview]
Message-ID: <54980CE9.7010108@samsung.com> (raw)
In-Reply-To: <1417799542-1366-1-git-send-email-sjoerd.simons@collabora.co.uk>

On 06/12/14 02:12, Sjoerd Simons wrote:
> With current u-boot-samsung HEAD on a peach-pi the following error is printed:
>   exynos_lcd_power_on: ps8625_init() failed
> 
> Which is not surprising given that chip does not exist on these boards.
> 
> Changes since v2:
>   * Move the parade_init function to its own header file
> Changes since v1:
>   * Only change the DTS for peach-pi not the default config. Further
>     configuration changes will be done seperately
>   * Use the approach as suggested by Ajay Kumar to fix compilation without
>     parade support
> 
> Sjoerd Simons (2):
>   Exynos5800: The Peach-Pi board does not have a Parade video bridge
>   exynos5420: fix compilation without parade video
> 
>  arch/arm/dts/exynos5800-peach-pi.dts      |  5 -----
>  arch/arm/include/asm/arch-exynos/system.h |  3 ---
>  board/samsung/smdk5420/smdk5420.c         |  1 +
>  include/parade.h                          | 18 ++++++++++++++++++
>  4 files changed, 19 insertions(+), 8 deletions(-)
>  create mode 100644 include/parade.h
> 

applied to u-boot-samsung.

Thanks,
Minkyu Kang.

      parent reply	other threads:[~2014-12-22 12:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-05 17:12 [U-Boot] [PATCH 0/2 v3] No need for parade bridge on peach-pi Sjoerd Simons
2014-12-05 17:12 ` [U-Boot] [PATCH 1/2 v3] Exynos5800: The Peach-Pi board does not have a Parade video bridge Sjoerd Simons
2014-12-05 17:12 ` [U-Boot] [PATCH 2/2 v3] exynos5420: fix compilation without parade video Sjoerd Simons
2014-12-22 12:22 ` Minkyu Kang [this message]

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=54980CE9.7010108@samsung.com \
    --to=mk7.kang@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox