linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Khiem Nguyen <khiem.nguyen.xt@rvc.renesas.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: shmobile: defconfig: enable HDMI output for RCar
Date: Wed, 14 Oct 2015 14:11:24 +0000	[thread overview]
Message-ID: <561E628C.1090803@rvc.renesas.com> (raw)
In-Reply-To: <1407974835-11064-1-git-send-email-khilman@linaro.org>

On 10/14/2015 8:32 PM, Geert Uytterhoeven wrote:
> On Wed, Oct 14, 2015 at 3:18 PM, Khiem Nguyen
> <khiem.nguyen.xt@rvc.renesas.com> wrote:
>>>> AFAIK, in some recent versions of Gen2 BSP, all the devices (including
>>>> all devices enabled by u-boot for its processing, like Ethernet, TMU,
>>>> serial) will be turned off right before jumping to kernel start address.
>>>
>>> Would it make sense to keep the serial port enabled in order to support
>>> early
>>> printk ?
>>>
>>
>> I don't think early printk is supported in Gen2 BSP, which is base on LTSI
>> 3.10.
>> Geert has introduced early printk support for Gen2 in Nov 2014.
>>
>> Maybe, we need to consider this point for Gen3.
>
> INTC-RT, MFIS, INTC-SYS, IRQC, and SCIF0 are left enabled, according
> to the U-Boot sources.

Yes, you are right. Above devices were left enabled.
Especially, some interrupt controller devices need to keep ON to ensure 
system operation
while transferring to kernel boot.


> Gr{oetje,eeting}s,
>
>                          Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
>                                  -- Linus Torvalds
>




  parent reply	other threads:[~2015-10-14 14:11 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14  0:07 [PATCH] ARM: shmobile: defconfig: enable initrd and atag dtb compat Kevin Hilman
2014-08-14  5:25 ` Simon Horman
2014-08-17  0:37   ` Simon Horman
2014-08-14 23:03 ` [PATCH] ARM: shmobile: defconfig: enable ARM_ATAG_DTB_COMPAT_CMDLINE_EXTEND Simon Horman
2014-08-17  0:38   ` Simon Horman
2015-10-10 19:14 ` [PATCH] ARM: shmobile: defconfig: enable HDMI output for RCar Wolfram Sang
2015-10-12  0:19 ` Simon Horman
2015-10-12  6:38 ` Wolfram Sang
2015-10-13  1:03 ` Simon Horman
2015-10-14  1:09 ` Laurent Pinchart
2015-10-14  5:52 ` Wolfram Sang
2015-10-14  7:07 ` Geert Uytterhoeven
2015-10-14  7:44 ` Magnus Damm
2015-10-14  7:54 ` Geert Uytterhoeven
2015-10-14  8:09 ` Magnus Damm
2015-10-14  8:22 ` Geert Uytterhoeven
2015-10-14  8:25 ` Wolfram Sang
2015-10-14  8:36 ` Magnus Damm
2015-10-14 11:41 ` Laurent Pinchart
2015-10-14 12:11 ` Khiem Nguyen
2015-10-14 12:55 ` Laurent Pinchart
2015-10-14 13:18 ` Khiem Nguyen
2015-10-14 13:32 ` Geert Uytterhoeven
2015-10-14 14:11 ` Khiem Nguyen [this message]
2015-11-30 13:35 ` [PATCH] ARM: shmobile: defconfig: Enable CONFIG_PRINTK_TIME Geert Uytterhoeven
2015-12-01  6:44   ` Simon Horman
2015-12-09  9:28     ` Geert Uytterhoeven
2015-12-10  7:04       ` Simon Horman

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=561E628C.1090803@rvc.renesas.com \
    --to=khiem.nguyen.xt@rvc.renesas.com \
    --cc=linux-sh@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).