From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] RFC: exynos: Disable the display controller when starting Linux
Date: Thu, 3 Oct 2013 10:55:58 +0200 [thread overview]
Message-ID: <20131003105558.41900743@lilith> (raw)
In-Reply-To: <1380791060-2578-2-git-send-email-ajaykumar.rs@samsung.com>
Hi Ajay,
On Thu, 03 Oct 2013 14:34:20 +0530, Ajay Kumar
<ajaykumar.rs@samsung.com> wrote:
> If the exynos display controller is still active when Linux starts,
> then it will result in a kernel panic while FIMD sysmmu driver is
> getting probed.
> Calling exynos_fimd_lcd_disable() before jumping into kernel
> disables the display controller by switching off the windows,
> hence resolving the kernel panic which arises from sysmmu driver.
>
> Create an Exynos specific definition for the weak function
> arch_cleanup_before_linux(), and then place the call to
> exynos_fimd_lcd_disable() inside the overrided definition of
> arch_cleanup_before_linux().
>
> Signed-off-by: Ajay Kumar <ajaykumar.rs@samsung.com>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
Why should the fix to this situation be making U-Boot disable the
display controller rather than making Linux able to cope with an
already active display controller?
Besides, fixing Linux would allow seamless booting displays, without an
ugly off-on glitch.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-10-03 8:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 9:04 [U-Boot] [PATCH 1/2] RFC: arm: add call to cleanup things before jumping into kernel Ajay Kumar
2013-10-03 8:58 ` Albert ARIBAUD
2013-10-03 9:19 ` Ajay kumar
2013-10-03 15:44 ` Albert ARIBAUD
2013-10-04 5:56 ` Ajay kumar
2013-10-03 14:23 ` Simon Glass
2013-10-03 9:04 ` [U-Boot] [PATCH 2/2] RFC: exynos: Disable the display controller when starting Linux Ajay Kumar
2013-10-03 8:55 ` Albert ARIBAUD [this message]
2013-10-03 9:24 ` Ajay kumar
2013-10-03 14:21 ` Simon Glass
2013-10-04 5:52 ` Ajay kumar
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=20131003105558.41900743@lilith \
--to=albert.u.boot@aribaud.net \
--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