From: Lyude Paul <lyude@redhat.com>
To: linux-tegra@vger.kernel.org, dri-devel@lists.freedesktop.org
Cc: "Thierry Reding" <treding@nvidia.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Subject: [PATCH 0/2] drm/tegra: Fix device/module refs for DP
Date: Fri, 23 Apr 2021 14:21:44 -0400 [thread overview]
Message-ID: <20210423182146.185633-1-lyude@redhat.com> (raw)
This patch series fixes a regression that was introduced by one of the
changes I made to when Tegra registers its AUX adapters, along with
fixing some reference leaks that I found along the way.
!!!NOTE!!!
There's one thing I'm not entirely sure about, which is the use of
module references (e.g. try_module_get()) here. If I'm understanding how
this code worked previously: since the get_device call in tegra_sor_probe()
was previously the i2c adapter for the AUX channel - which itself is
initialized in drm_dp_aux_register() - then I -think- that the module
owner for the DDC adapter would likely have been drm_kms_helper. With
these changes, if I'm understanding things correctly we're now just
grabbing a module reference for ourselves - something which might not be
the best idea?
If anyone could confirm if I need to fix this or not that'd be
appreciated, along with reviews of course :P
Lyude Paul (2):
drm/tegra: Get ref for DP AUX channel, not its ddc adapter
drm/tegra: Fix DP AUX channel reference leaks
drivers/gpu/drm/tegra/sor.c | 25 ++++++++++++++++++-------
1 file changed, 18 insertions(+), 7 deletions(-)
--
2.30.2
next reply other threads:[~2021-04-23 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 18:21 Lyude Paul [this message]
2021-04-23 18:21 ` [PATCH 1/2] drm/tegra: Get ref for DP AUX channel, not its ddc adapter Lyude Paul
2021-04-26 7:42 ` Thierry Reding
2021-04-27 22:44 ` Lyude Paul
2021-05-14 22:13 ` [PATCH v2] " Lyude Paul
2021-04-23 18:21 ` [PATCH 2/2] drm/tegra: Fix DP AUX channel reference leaks Lyude Paul
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=20210423182146.185633-1-lyude@redhat.com \
--to=lyude@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-tegra@vger.kernel.org \
--cc=treding@nvidia.com \
--cc=ville.syrjala@linux.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