From: Jordan Crouse <jcrouse@codeaurora.org>
To: Georgi Djakov <georgi.djakov@linaro.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Gross <agross@kernel.org>,
linux-arm-msm@vger.kernel.org
Subject: [PATCH v1 0/2] interconnect: Move qcom interconnect drivers to core_initcall
Date: Thu, 31 Oct 2019 12:28:50 -0600 [thread overview]
Message-ID: <1572546532-19248-1-git-send-email-jcrouse@codeaurora.org> (raw)
Currently all the qcom interconnect drivers initialize at the device_initcall
level when they are built-in which is a problem since nearly all the frameworks
and leaf drivers in the SoC depend on interconnect in some fashion. While those
frameworks and drivers should be properly PROBE_DEFER aware it is in our best
interest to try not to defer just because we can. Move all the drivers to
core_initcall when built to increase the chance that they will be available when
their dependent drivers need them.
I also tossed on a quick cleanup patch to remove unneeded module exit code from
the core file since it is always built in.
Regards,
Jordan
Jordan Crouse (2):
interconnect: Move interconnect drivers to core_initcall
interconnect: Remove unused module exit code from core
drivers/interconnect/core.c | 7 +------
drivers/interconnect/qcom/msm8974.c | 14 +++++++++++++-
drivers/interconnect/qcom/qcs404.c | 14 +++++++++++++-
drivers/interconnect/qcom/sdm845.c | 13 ++++++++++++-
4 files changed, 39 insertions(+), 9 deletions(-)
--
2.7.4
next reply other threads:[~2019-10-31 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 18:28 Jordan Crouse [this message]
2019-10-31 18:28 ` [PATCH v1 1/2] interconnect: Move interconnect drivers to core_initcall Jordan Crouse
2019-10-31 18:30 ` Bjorn Andersson
2019-10-31 18:28 ` [PATCH v1 2/2] interconnect: Remove unused module exit code from core Jordan Crouse
2019-10-31 18:32 ` Bjorn Andersson
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=1572546532-19248-1-git-send-email-jcrouse@codeaurora.org \
--to=jcrouse@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=georgi.djakov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.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).