From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>, robdclark@gmail.com
Cc: sean@poorly.run, airlied@linux.ie, daniel@ffwll.ch,
maxime@cerno.tech, linux-arm-msm@vger.kernel.org,
dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org,
linux-kernel@vger.kernel.org, kernel@collabora.com,
konrad.dybcio@somainline.org, marijn.suijten@somainline.org,
jami.kettunen@somainline.org
Subject: Re: [PATCH] drm/msm: Initialize MDSS irq domain at probe time
Date: Fri, 26 Nov 2021 10:26:15 +0100 [thread overview]
Message-ID: <2b37dfd3-c3be-2640-56d0-25c9971c4f50@collabora.com> (raw)
In-Reply-To: <32cdade5-1487-9182-e939-4d93f8a27ad6@linaro.org>
Il 26/11/21 01:06, Dmitry Baryshkov ha scritto:
> On 25/11/2021 18:09, AngeloGioacchino Del Regno wrote:
>> Since commit 8f59ee9a570c ("drm/msm/dsi: Adjust probe order"), the
>> DSI host gets initialized earlier, but this caused unability to probe
>> the entire stack of components because they all depend on interrupts
>> coming from the main `mdss` node (mdp5, or dpu1).
>>
>> To fix this issue, also anticipate probing mdp5 or dpu1 by initializing
>> them at msm_pdev_probe() time: this will make sure that we add the
>> required interrupt controller mapping before dsi and/or other components
>> try to initialize, finally satisfying the dependency.
>>
>> While at it, also change the allocation of msm_drm_private to use the
>> devm variant of kzalloc().
>>
>> Fixes: 8f59ee9a570c ("drm/msm/dsi: Adjust probe order")
>> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
>
> Another issue (or a pack of issues):
> Now the msm_drm_init() is unbalanced with msm_drm_uninit(). Bits of code (putting
> the drm dev, removing the IRQ domain, etc) have to be called now from the
> msm_pdev_remove() function rather than from the unbind path.
>
> The following changes fix the observed issues here, however additional care should
> be taken.
>
Hello Dmitry,
thanks for the thorough review (and solutions!).
Are you going to push your changes on top, or should I send a V2?
Cheers,
- Angelo
next prev parent reply other threads:[~2021-11-26 9:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 15:09 [PATCH] drm/msm: Initialize MDSS irq domain at probe time AngeloGioacchino Del Regno
2021-11-25 15:23 ` Dmitry Baryshkov
2021-11-25 22:39 ` Dmitry Baryshkov
2021-11-26 0:06 ` Dmitry Baryshkov
2021-11-26 9:26 ` AngeloGioacchino Del Regno [this message]
2021-11-26 21:12 ` Dmitry Baryshkov
2021-11-26 16:08 ` AngeloGioacchino Del Regno
2021-11-29 2:20 ` Dmitry Baryshkov
2021-11-29 14:14 ` AngeloGioacchino Del Regno
2021-11-29 14:53 ` Dmitry Baryshkov
2021-11-29 14:56 ` AngeloGioacchino Del Regno
-- strict thread matches above, loose matches on Subject: below --
2021-12-01 10:52 [PATCH v3 2/2] " AngeloGioacchino Del Regno
2021-12-01 20:20 ` [PATCH] " Dmitry Baryshkov
2021-12-03 10:43 ` AngeloGioacchino Del Regno
2021-12-03 13:14 ` Dmitry Baryshkov
2021-12-03 13:17 ` AngeloGioacchino Del Regno
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=2b37dfd3-c3be-2640-56d0-25c9971c4f50@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jami.kettunen@somainline.org \
--cc=kernel@collabora.com \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=maxime@cerno.tech \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
/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