From: hdegoede@redhat.com (Hans de Goede)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] Problem with Allwinner H3 clocks
Date: Wed, 27 Jan 2016 19:16:42 +0100 [thread overview]
Message-ID: <56A9098A.5010107@redhat.com> (raw)
In-Reply-To: <20160127175512.87caf31b5e21a1fec91507f2@free.fr>
Hi,
On 27-01-16 17:55, Jean-Francois Moine wrote:
> On Wed, 27 Jan 2016 15:36:21 +0100
> Jens Kuske <jenskuske@gmail.com> wrote:
>
>> That sounds strange, 4.5-rc1 is working perfectly fine for me too.
>>
>> I doubt the patch you linked is responsible for making it work, it only
>> removes the hardcoded output-names. If your DT isn't messed up this
>> isn't relevant at all since pll8, the initial reason for this patch, is
>> only a dummy clock for now. Are you sure you are using a clean v4.5-rc1
>> without any own modifications?
>
> 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.
Regards,
Hans
next prev parent reply other threads:[~2016-01-27 18: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 [this message]
2016-01-27 19:02 ` Jean-Francois Moine
2016-01-28 8:15 ` Hans de Goede
2016-01-28 13:16 ` Jens Kuske
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=56A9098A.5010107@redhat.com \
--to=hdegoede@redhat.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;
as well as URLs for NNTP newsgroup(s).