From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Rob Clark <robdclark@gmail.com>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
Marijn Suijten <marijn.suijten@somainline.org>,
Kuogee Hsieh <quic_khsieh@quicinc.com>,
Johan Hovold <johan+linaro@kernel.org>,
Bjorn Andersson <quic_bjorande@quicinc.com>
Cc: freedreno@lists.freedesktop.org, Sean Paul <sean@poorly.run>,
Douglas Anderson <dianders@chromium.org>,
dri-devel@lists.freedesktop.org,
Vinod Polimera <quic_vpolimer@quicinc.com>,
linux-arm-msm@vger.kernel.org, Stephen Boyd <swboyd@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/msm/dp: Drop aux devices together with DP controller
Date: Thu, 15 Jun 2023 14:31:23 +0300 [thread overview]
Message-ID: <168682860385.384026.4498168865636345708.b4-ty@linaro.org> (raw)
In-Reply-To: <20230612220106.1884039-1-quic_bjorande@quicinc.com>
On Mon, 12 Jun 2023 15:01:06 -0700, Bjorn Andersson wrote:
> Using devres to depopulate the aux bus made sure that upon a probe
> deferral the EDP panel device would be destroyed and recreated upon next
> attempt.
>
> But the struct device which the devres is tied to is the DPUs
> (drm_dev->dev), which may be happen after the DP controller is torn
> down.
>
> [...]
Applied, thanks!
[1/1] drm/msm/dp: Drop aux devices together with DP controller
https://gitlab.freedesktop.org/lumag/msm/-/commit/a7bfb2ad2184
Best regards,
--
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
next prev parent reply other threads:[~2023-06-15 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 22:01 [PATCH] drm/msm/dp: Drop aux devices together with DP controller Bjorn Andersson
2023-06-12 22:40 ` Dmitry Baryshkov
2023-06-13 19:33 ` Doug Anderson
2023-06-13 20:51 ` Abhinav Kumar
2023-06-15 11:31 ` Dmitry Baryshkov [this message]
2023-06-19 12:40 ` Johan Hovold
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=168682860385.384026.4498168865636345708.b4-ty@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=johan+linaro@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_bjorande@quicinc.com \
--cc=quic_khsieh@quicinc.com \
--cc=quic_vpolimer@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).