From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
<robdclark@gmail.com>, <sean@poorly.run>,
<dmitry.baryshkov@linaro.org>, <airlied@gmail.com>,
<daniel@ffwll.ch>, <lyude@redhat.com>
Cc: <javierm@redhat.com>, <tzimmermann@suse.de>,
<quic_khsieh@quicinc.com>, <quic_bjorande@quicinc.com>,
<johan+linaro@kernel.org>, <linux-arm-msm@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
<freedreno@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/msm/dp: unregister audio driver during unbind
Date: Fri, 21 Apr 2023 11:41:59 -0700 [thread overview]
Message-ID: <7579b02e-5b4d-72b7-4cef-e18f9fc86d7d@quicinc.com> (raw)
In-Reply-To: <20230421145657.12186-1-srinivas.kandagatla@linaro.org>
On 4/21/2023 7:56 AM, Srinivas Kandagatla wrote:
> while binding the code always registers a audio driver, however there
> is no corresponding unregistration done in unbind. This leads to multiple
> redundant audio platform devices if dp_display_bind and dp_display_unbind
> happens multiple times during startup. On X13s platform this resulted in
> 6 to 9 audio codec device instead of just 3 codec devices for 3 dp ports.
>
> Fix this by unregistering codecs on unbind.
>
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> ---
Fixes: d13e36d7d222 ("drm/msm/dp: add audio support for Display Port on
MSM")
Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
(pls ignore the line break in the fixes tag, its a mail editor issue, I
will apply the tag properly while applying to -fixes)
next prev parent reply other threads:[~2023-04-21 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 14:56 [PATCH] drm/msm/dp: unregister audio driver during unbind Srinivas Kandagatla
2023-04-21 18:41 ` Abhinav Kumar [this message]
2023-04-28 19:52 ` Abhinav Kumar
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=7579b02e-5b4d-72b7-4cef-e18f9fc86d7d@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=johan+linaro@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=quic_bjorande@quicinc.com \
--cc=quic_khsieh@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=srinivas.kandagatla@linaro.org \
--cc=tzimmermann@suse.de \
/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