Hi Mathieu,
On 19/06/2019 21:16, Mathieu Poirier wrote:
On Wed, 19 Jun 2019 at 12:39, Stephan Gerhold <stephan@xxxxxxxxxxx> wrote:
In this case I'm wondering how it works on the Dragonboard 410c.
There can be two problems:
1) CPUidle is enabled on your platform and as I pointed out before,
that won't work. There are patches circulating[1] to fix that problem
but it still needs a little bit of work.
2) As Suzuki pointed out the debug power domain may not be enabled by
default on your platform, something I would understand if it is a
production device. There is nothing I can do on that front.
[1]. https://www.spinics.net/lists/arm-kernel/msg735707.html
Does it enable these power domains in the firmware?
(Assuming it boots without this error...)
The debug power domain is enabled by default on the 410c and the board
boots without error.
If coresight is not working properly on all/most msm8916 devices,
shouldn't coresight be disabled by default in msm8916.dtsi?
It is in the defconfig for arm64, as such it shouldn't bother you.
At least until those power domains can be set up by the kernel.
If this is a device-specific issue, what would be an acceptable solution
for mainline?
Can I turn on these power domains from the kernel?
Yes, if you have the SoC's TRM.
Or is it fine to disable coresight for this device with the snippet above?
I'm not actually trying to use coresight, I just want the device to boot :)
And since I am considering submitting my device tree for inclusion in
mainline, I want to ask in advance how I should tackle this problem.
Simply don't enable coresight in the kernel config if the code isn't
mature enough to properly handle the relevant power domains using the
PM runtime API.
I don't think disabling the Coresight in kernel config will hide it.
Since the coresight components have the AMBA compatible, the AMBA bus
driver will definitely try to probe the PIDs via amba_device_try_add(),
as shown by the backtrace. I assume that is causing the problem.
Cheers
Suzuki
