From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
Abhinav Kumar <quic_abhinavk@quicinc.com>
Cc: David Airlie <airlied@linux.ie>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Stephen Boyd <swboyd@chromium.org>,
freedreno@lists.freedesktop.org
Subject: [PATCH 0/3] drm/msm/hdmi: move resource allocation to probe function
Date: Thu, 16 Jun 2022 10:59:44 +0300 [thread overview]
Message-ID: <20220616075947.347888-1-dmitry.baryshkov@linaro.org> (raw)
As pointed several times in the discussions, start moving resource
allocation from component bind to the probe function. This simplifies
boot process, as the component will not be registered until all
resources (clocks, regulators, IRQ, etc.) are not registered.
Dmitry Baryshkov (3):
drm/msm/hdmi: use devres helper for runtime PM management
drm/msm/hdmi: drop constant resource names from platform config
drm/msm/hdmi: move resource allocation to probe function
drivers/gpu/drm/msm/hdmi/hdmi.c | 298 ++++++++++++++------------------
drivers/gpu/drm/msm/hdmi/hdmi.h | 3 -
2 files changed, 134 insertions(+), 167 deletions(-)
--
2.35.1
next reply other threads:[~2022-06-16 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 7:59 Dmitry Baryshkov [this message]
2022-06-16 7:59 ` [PATCH 1/3] drm/msm/hdmi: use devres helper for runtime PM management Dmitry Baryshkov
2022-08-23 17:39 ` Abhinav Kumar
2022-06-16 7:59 ` [PATCH 2/3] drm/msm/hdmi: drop constant resource names from platform config Dmitry Baryshkov
2022-08-23 17:40 ` Abhinav Kumar
2022-06-16 7:59 ` [PATCH 3/3] drm/msm/hdmi: move resource allocation to probe function Dmitry Baryshkov
2022-08-23 23:58 ` Abhinav Kumar
2022-08-26 8:57 ` Dmitry Baryshkov
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=20220616075947.347888-1-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=airlied@linux.ie \
--cc=bjorn.andersson@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=swboyd@chromium.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).