From: ssuloev@orpaltech.com (Sergey Suloev)
To: linux-arm-kernel@lists.infradead.org
Subject: SUN6I a31 OPP table clock issue
Date: Mon, 9 Apr 2018 13:35:42 +0300 [thread overview]
Message-ID: <8b797d9c-b2fb-e49b-daa2-e4e15753f3fa@orpaltech.com> (raw)
In-Reply-To: <20180409085356.goemvdy3ecyqoghp@flea>
On 04/09/2018 11:53 AM, Maxime Ripard wrote:
> On Sat, Apr 07, 2018 at 10:53:10PM +0300, Sergey Suloev wrote:
>> I was able to catch oops coming from OPP table on BananaPi M2.
>>
>> https://pastebin.com/ZRaXTtEx
>>
>> Let me know if need more detail.
> Of course we do.
>
> Which kernel version was this for? With which configuration? What
> makes you say it's related to the OPP table, is it a regression or
> something you just noticed?
Ok, first of all, I am having the problem using linus tree, 4.16 as it
is, with no extra patches.
My config file is here [1].
The problem is easily avoided by just commenting all freqs out of the
OPP table except for 1008 MHz, i.e. things work well when there is no
freq switch at all.
It makes me think that there might be an issue in A31 clocks driver as
it is the only important component used by cpufreq-dt.
As of cpufreq-dt driver it seems ok because works fine on other boards.
>
> Maxime
>
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
[1] https://pastebin.com/eZxbra2f
next prev parent reply other threads:[~2018-04-09 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-07 19:53 SUN6I a31 OPP table clock issue Sergey Suloev
2018-04-09 8:53 ` Maxime Ripard
2018-04-09 10:35 ` Sergey Suloev [this message]
2018-04-09 11:28 ` Maxime Ripard
2018-04-09 11:49 ` Sergey Suloev
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=8b797d9c-b2fb-e49b-daa2-e4e15753f3fa@orpaltech.com \
--to=ssuloev@orpaltech.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).