All of lore.kernel.org
 help / color / mirror / Atom feed
From: jenskuske@gmail.com (Jens Kuske)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] Problem with Allwinner H3 clocks
Date: Thu, 28 Jan 2016 14:16:26 +0100	[thread overview]
Message-ID: <56AA14AA.4070502@gmail.com> (raw)
In-Reply-To: <56A9CE3D.4020906@redhat.com>

On 28/01/16 09:15, Hans de Goede wrote:
> Hi,
> 
> On 27-01-16 20:02, Jean-Francois Moine wrote:
>> On Wed, 27 Jan 2016 19:16:42 +0100
>> Hans de Goede <hdegoede@redhat.com> wrote:
>>
>>>> To be sure, I generated a pure 4.5-rc1 kernel. Same result: no UART.
>>>> Maybe... one more information: I am using Allwinner's u-boot.
>>>
>>> Could be that that is the culprit, why are you not using upstream u-boot?
>>> upstream u-boot has H3 and orangepi-pc support now.
>>
>> Yes, but using the upstream u-boot may hide the clock problem.
> 
> I agree that that could be the case. Would be interesting to figure out
> what exactly is needed to get the upstream kernel to work properly
> with allwinner's u-boot.

Hi,

after figuring out how to boot a devicetree kernel with allwinner's
u-boot I only had to add the mandatory
	
	clock-frequency = <24000000>;
	arm,cpu-registers-not-fw-configured;

to the timer node and v4.5-rc1 booted successfully. They are
intentionally left out in the official dt, because documentation says
one should prefer to fix the firmware -> mainline u-boot
No problems with clocks or uart here.

Jens

  reply	other threads:[~2016-01-28 13:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27  7:46 Problem with Allwinner H3 clocks Jean-Francois Moine
2016-01-27  8:18 ` [linux-sunxi] " Chen-Yu Tsai
2016-01-27  9:37   ` Jean-Francois Moine
2016-01-27 14:36     ` Jens Kuske
2016-01-27 16:55       ` Jean-Francois Moine
2016-01-27 18:16         ` Hans de Goede
2016-01-27 19:02           ` Jean-Francois Moine
2016-01-28  8:15             ` Hans de Goede
2016-01-28 13:16               ` Jens Kuske [this message]
2016-01-28 16:59                 ` Jean-Francois Moine
2016-01-28 19:29                   ` Maxime Ripard
2016-01-29  6:25                     ` Hans de Goede
2016-01-29  7:59                       ` Chen-Yu Tsai
2016-02-01  6:37                       ` Maxime Ripard
2016-02-01 14:26                         ` Hans de Goede
2016-02-01 14:37                           ` Chen-Yu Tsai
2016-02-01 14:45                             ` Maxime Ripard
2016-02-01 14:47                           ` Maxime Ripard
2016-01-29  7:27                     ` Jean-Francois Moine
2016-01-28 15:51               ` Jean-Francois Moine
2016-01-28 17:31               ` Maxime Ripard

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=56AA14AA.4070502@gmail.com \
    --to=jenskuske@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.