From: Chandrasekhar L <clingutla@codeaurora.org>
To: Lukasz Luba <lukasz.luba@arm.com>
Cc: rafael.j.wysocki@intel.com, qperret@google.com,
daniel.lezcano@linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] PM: EM: do not allow pd creation prior to debugfs initialization
Date: Wed, 20 Oct 2021 17:33:18 +0530 [thread overview]
Message-ID: <0c42bec7-4358-a8d6-b1db-f52218a8e59a@codeaurora.org> (raw)
In-Reply-To: <e01188a0-1dc7-db57-309f-f49390216875@arm.com>
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.
next prev parent reply other threads:[~2021-10-20 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 15:28 [PATCH] PM: EM: do not allow pd creation prior to debugfs initialization Lingutla Chandrasekhar
2021-10-19 17:05 ` Lukasz Luba
2021-10-20 12:03 ` Chandrasekhar L [this message]
2021-10-20 12:54 ` Lukasz Luba
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=0c42bec7-4358-a8d6-b1db-f52218a8e59a@codeaurora.org \
--to=clingutla@codeaurora.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=qperret@google.com \
--cc=rafael.j.wysocki@intel.com \
/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