From: Mark yao <mark.yao@rock-chips.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
John Keeping <john@keeping.me.uk>
Cc: Douglas Anderson <dianders@chromium.org>,
Heiko Stuebner <heiko@sntech.de>, David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-rockchip@lists.infradead.org,
Daniel Kurtz <djkurtz@chromium.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] drm/rockchip: dw_hdmi: Call drm_encoder_cleanup() in error path
Date: Mon, 07 Mar 2016 16:37:03 +0800 [thread overview]
Message-ID: <56DD3DAF.8090700@rock-chips.com> (raw)
In-Reply-To: <20160305123942.GE19428@n2100.arm.linux.org.uk>
On 2016年03月05日 20:39, Russell King - ARM Linux wrote:
> On Sat, Mar 05, 2016 at 12:11:16PM +0000, John Keeping wrote:
>> On Fri, Mar 04, 2016 at 03:22:01PM -0800, Douglas Anderson wrote:
>>> The drm_encoder_cleanup() was missing both from the error path of
>>> dw_hdmi_rockchip_bind(). This caused a crash when slub_debug was
>>> enabled and we ended up deferring probe of HDMI at boot.
>>>
>>> This call isn't needed from unbind() because if dw_hdmi_bind() returns
>>> no error then it takes over the job of freeing the encoder (in
>>> dw_hdmi_unbind).
>>>
>>> Signed-off-by: Douglas Anderson <dianders@chromium.org>
>>> ---
>> Does dw_hdmi-imx need a similar change? I wonder if it would be cleaner
>> to push this into dw_hdmi_bind() if it affects all of the platforms..
> I don't think moving it there would make sense - keep the initialisation
> and cleanup together in the same file so that it's contained together.
>
I don't like this patch too, initialisation and cleanup not in the same
file looks bad,
How about:
drivers/gpu/drm/bridge/dw-hdmi.c
void dw_hdmi_unbind(struct device *dev, struct device *master, void *data)
hdmi_writeb(hdmi, ~0, HDMI_IH_MUTE_PHY_STAT0);
hdmi->connector.funcs->destroy(&hdmi->connector);
- hdmi->encoder->funcs->destroy(hdmi->encoder);
drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c
static int dw_hdmi_rockchip_bind(struct device *dev, struct device *master,
- return dw_hdmi_bind(dev, master, data, encoder, iores, irq,
plat_data);
+ ret = dw_hdmi_bind(dev, master, data, encoder, iores, irq,
plat_data);
+ if (ret)
+ drm_encoder_cleanup(encoder);
+
+ return ret;
}
static void dw_hdmi_rockchip_unbind(struct device *dev, struct device
*master,
void *data)
{
+ drm_encoder_cleanup(...);
return dw_hdmi_unbind(dev, master, data);
}
Thanks.
--
Mark Yao
next prev parent reply other threads:[~2016-03-07 8:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 23:22 [PATCH 1/2] drm/rockchip: dw_hdmi: Call drm_encoder_cleanup() in error path Douglas Anderson
2016-03-04 23:22 ` [PATCH 2/2] drm/rockchip: vop: Fix vop crtc cleanup Douglas Anderson
2016-03-05 12:11 ` [PATCH 1/2] drm/rockchip: dw_hdmi: Call drm_encoder_cleanup() in error path John Keeping
2016-03-05 12:39 ` Russell King - ARM Linux
2016-03-07 8:37 ` Mark yao [this message]
2016-03-07 17:36 ` Doug Anderson
2016-03-07 17:57 ` Heiko Stübner
2016-03-07 18:49 ` Doug Anderson
2016-03-07 18:56 ` Heiko Stübner
2016-03-07 19:26 ` Russell King - ARM Linux
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=56DD3DAF.8090700@rock-chips.com \
--to=mark.yao@rock-chips.com \
--cc=airlied@linux.ie \
--cc=dianders@chromium.org \
--cc=djkurtz@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=john@keeping.me.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
/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