[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0c42bec7-4358-a8d6-b1db-f52218a8e59a@codeaurora.org>
Date: Wed, 20 Oct 2021 17:33:18 +0530
From: Chandrasekhar L <clingutla@...eaurora.org>
To: Lukasz Luba <lukasz.luba@....com>
Cc: rafael.j.wysocki@...el.com, qperret@...gle.com,
daniel.lezcano@...aro.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH] PM: EM: do not allow pd creation prior to debugfs
initialization
Thanks Lukasz for comment.
For any reason (ex: HW dependency, etc), if init_call level of cpufreq/devfreq driver changed
prior to fs_init call, we would land there right?
One of such example is, 'drivers/cpufreq/qcom-cpufreq-hw.c' uses postcore_initcall().
Thanks,
Chandrasekhar L
On 10/19/2021 10:35 PM, Lukasz Luba wrote:
>
>
> On 10/19/21 4:28 PM, Lingutla Chandrasekhar wrote:
>> em_dev_register_perf_domain() can be called from any initcall level before
>
> The EM is registered by cpufreq drivers (or devfreq), which is later
> than fs_initcall, so the debugfs is setup. We even have added recently
> a dedicated callback into the cpufreq (register_em()) for that.
>
> Do you have such code which registers EM for CPUs (or some devfreq)
> earlier than this fs_initcall?
>
> I cannot find such code in mainline.
>
> Regards,
> Lukasz
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project.
Powered by blists - more mailing lists