public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 10/11] arm64: dts: renesas: initial Eagle board device tree
Date: Fri, 15 Sep 2017 21:53:02 +0300	[thread overview]
Message-ID: <323063a2-1256-fa25-b91c-4c726ab277a2@cogentembedded.com> (raw)
In-Reply-To: <CAMuHMdU+DYBCu1bKLh_VjuSR-cSfjwPQuAxTsaU2JW-3d-5QUw@mail.gmail.com>

On 09/15/2017 09:44 PM, Geert Uytterhoeven wrote:

>>>> Add the initial device  tree for  the R8A77970 SoC based Eagle board.
>>>> The board has 1 debug serial port (SCIF0); include support for it,
>>>> so that the serial console can work.
>>>>
>>>> Based on the original (and large) patch by Vladimir Barinov
>>>> <vladimir.barinov@cogentembedded.com>.
>>>>
>>>> Signed-off-by: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
>>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>>>>
>>> [...]
>>>>
>>>> Index: renesas/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts
>>>> ===================================================================
>>>> --- /dev/null
>>>> +++ renesas/arch/arm64/boot/dts/renesas/r8a77970-eagle.dts
>>>> @@ -0,0 +1,45 @@
>>>
>>> [...]
>>>>
>>>> +&extal_clk {
>>>> +    clock-frequency = <16666666>;
>>>> +};
>>>> +
>>>> +&extalr_clk {
>>>> +    clock-frequency = <32768>;
>>>> +};
>>>> +
>>>
>>>      Forgot to specify SCIF_CLK -- it's populated.
>>
>>     Unfortunately, the kernel hangs after ttySC0 is registered if I specify
>> this frequency...
> 
> Is the crystal populated?

    It should be, with 14.7456MHz chrystal. But it's connected to SCIF_CLK_B 
pin -- perhaps that's the problem...

> When doing initial bringup of the remote Eagle I have access to, the SCIF
> registers didn't indicate SCIF_CLK was being used from U-Boot, while it
> is used on R-Car Gen2 boards that have it populated.

    Perhaps PFC is just not configured properly?

> 
> Gr{oetje,eeting}s,
> 
>                          Geert

MBR, Sergei

  reply	other threads:[~2017-09-15 18:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-12 20:37 [PATCH 10/11] arm64: dts: renesas: initial Eagle board device tree Sergei Shtylyov
2017-09-12 21:19 ` Sergei Shtylyov
2017-09-15 17:28   ` Sergei Shtylyov
2017-09-15 18:44     ` Geert Uytterhoeven
2017-09-15 18:53       ` Sergei Shtylyov [this message]
2017-09-15 19:00         ` Geert Uytterhoeven

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=323063a2-1256-fa25-b91c-4c726ab277a2@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=linux-arm-kernel@lists.infradead.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