From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM64: dts: meson-gxbb-odroidc2: Disable SCPI DVFS
Date: Fri, 6 Jan 2017 11:54:48 +0000 [thread overview]
Message-ID: <83fd9b61-dbff-68e0-82e5-8e01058d04a9@arm.com> (raw)
In-Reply-To: <9f508097-f605-ebd8-20af-c3e798c6fdcc@poczta.onet.pl>
Hi Micha?,
On 05/01/17 19:04, Micha? Zegan wrote:
> Hello.
>
> The patch causes cpufreq module (scpi-cpufreq) not to detect cpufreq, so
> it actually works, but...
> Loading the module causes few errors because of not found frequencies or
> something, then it is all okay. However after loading scpi-cpufreq you
> cannot actually power the cpu off and on. You will power it off
> successfully, but when trying to power it on, the cpufreq driver will
> error out,
Yes I had noticed this in past, this needs to be fixed. I had a patch
and seems like it slipped through the cracks. I will fins and post it.
> and then after it happens, the cpu that was trying to go
> online will be offline again, and that is a little... unfortunate. The
IIUC, you mean the cpufreq drive spits error on every hotplug event ?
If so yes, otherwise I think I didn't understand you concern above.
> question is, and I cannot really test that: will the module actually
> autoload after this change?
>
It should work, I had tested this in past.
--
Regards,
Sudeep
next prev parent reply other threads:[~2017-01-06 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 15:02 [PATCH] ARM64: dts: meson-gxbb-odroidc2: Disable SCPI DVFS Neil Armstrong
2017-01-05 19:04 ` Michał Zegan
2017-01-06 8:04 ` Neil Armstrong
2017-01-06 11:54 ` Sudeep Holla [this message]
2017-01-06 13:12 ` Michał Zegan
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=83fd9b61-dbff-68e0-82e5-8e01058d04a9@arm.com \
--to=sudeep.holla@arm.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