From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: <hjc@rock-chips.com>, <heiko@sntech.de>,
<andy.yan@rock-chips.com>, <maarten.lankhorst@linux.intel.com>,
<mripard@kernel.org>, <tzimmermann@suse.de>, <airlied@gmail.com>,
<daniel@ffwll.ch>, <dri-devel@lists.freedesktop.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-rockchip@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <krzk@kernel.org>,
<jic23@kernel.org>
Subject: Re: [PATCH -next 1/5] drm/rockchip: Use for_each_child_of_node_scoped()
Date: Tue, 27 Aug 2024 10:49:00 +0100 [thread overview]
Message-ID: <20240827104900.00004060@Huawei.com> (raw)
In-Reply-To: <5d6debd0-1a02-f631-649e-26fb69e164e2@huawei.com>
On Tue, 27 Aug 2024 09:40:07 +0800
Jinjie Ruan <ruanjinjie@huawei.com> wrote:
> On 2024/8/23 19:32, Jonathan Cameron wrote:
> > On Fri, 23 Aug 2024 17:20:49 +0800
> > Jinjie Ruan <ruanjinjie@huawei.com> wrote:
> >
> >> Avoids the need for manual cleanup of_node_put() in early exits
> >> from the loop.
> >>
> >> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
> >
> > There is more to do here, and looking at the code, I'm far from
> > sure it isn't releasing references it never had.
> >
> >> ---
> >> drivers/gpu/drm/rockchip/rockchip_lvds.c | 8 +++-----
> >> 1 file changed, 3 insertions(+), 5 deletions(-)
> >>
> >> diff --git a/drivers/gpu/drm/rockchip/rockchip_lvds.c b/drivers/gpu/drm/rockchip/rockchip_lvds.c
> >> index 9a01aa450741..f5b3f18794dd 100644
> >> --- a/drivers/gpu/drm/rockchip/rockchip_lvds.c
> >> +++ b/drivers/gpu/drm/rockchip/rockchip_lvds.c
> >> @@ -548,7 +548,7 @@ static int rockchip_lvds_bind(struct device *dev, struct device *master,
> >> struct drm_encoder *encoder;
> >> struct drm_connector *connector;
> >> struct device_node *remote = NULL;
> >> - struct device_node *port, *endpoint;
> >
> > Odd extra space before *port in original. Clean that up whilst here.
> >
> >
> >> + struct device_node *port;
> >
> > Use __free(device_node) for *port as well.
>
> Yes,that is right.
>
> >
> > So where the current asignment is.
> > struct device_node *port = of_graph_get_port_by_id(dev->of_node, 1);
> >
> >> int ret = 0, child_count = 0;
> >> const char *name;
> >> u32 endpoint_id = 0;
> >> @@ -560,15 +560,13 @@ static int rockchip_lvds_bind(struct device *dev, struct device *master,
> >> "can't found port point, please init lvds panel port!\n");
> >> return -EINVAL;
> >> }
> >> - for_each_child_of_node(port, endpoint) {
> >> + for_each_child_of_node_scoped(port, endpoint) {
> >> child_count++;
> >> of_property_read_u32(endpoint, "reg", &endpoint_id);
> >> ret = drm_of_find_panel_or_bridge(dev->of_node, 1, endpoint_id,
> >> &lvds->panel, &lvds->bridge);
> >> - if (!ret) {
> >> - of_node_put(endpoint);
> >> + if (!ret)
> >> break;
> >
> > This then can simply be
> > return dev_err_probe(dev, ret,
> > "failed to find pannel and bridge node\n");
> >> - }
>
> It seems to me there's no easy way return here, as it will try
> drm_of_find_panel_or_bridge() for each child node, only "child_count =
> 0" or all child node drm_of_find_panel_or_bridge() fails it will error
> and return.
Ah. Good point. That is an odd code structure that I read wrong but it indeed
carries on and ignores the error if for an earlier loop
the drm_of_find_pannel_or_bridge() failed and a later one succeeds.
If you want to make it more 'standard I'd do
if (ret)
continue;
and have the code code path of the early break 'inline'
e.g.
for_each_child_of_node(port, endpoint) {
child_count++;
of_property_read_u32(endpoint, "reg", &endpoint_id);
ret = drm_of_find_panel_or_bridge(dev->of_node, 1, endpoint_id,
&lvds->panel, &lvds->bridge);
if (ret)
continue;
of_node_put(endpoint);
break;
}
I'd also be tempted to pull the child_count before this with
if (of_get_child_count() == 0) {
DRM_DEV_ERROR(dev, "...");
return -EINVAL;
Then can simply check ret at the end of the loop rather than needing
the else if as we can't get there with child_count non zero.
Can also drop the increment of child_count in the loop. So overall that
becomes something like
if (of_get_child_count(endpoint) == 0) {
DRM_DEV_ERROR(dev, "...");
return -EINVAL;
}
for_each_child_of_node_scoped(port, endpoint) {
of_property_read_u32(endpoint, "reg", &endpoint_id);
ret = drm_of_find_panel_or_bridge(dev->of_node, 1, endpoint_id,
&lvds->panel, &lvds->bridge);
/* A later child node may succeed */
if (ret)
continue;
break;
}
if (ret)
return dev_err_probe();
>
> >
> > Various other paths become direct returns as well.
> >
> >> }
> >
> > The later code with remote looks suspect as not obvious who got the reference that
> > is being put but assuming that is correct, it's another possible place for __free based
> > cleanup.
>
> Yes, the remote looks suspect.
>
> >
> >
> >> if (!child_count) {
> >> DRM_DEV_ERROR(dev, "lvds port does not have any children\n");
> >
next prev parent reply other threads:[~2024-08-27 9:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 9:20 [PATCH -next 0/5] drm: Use for_each_child_of_node_scoped() Jinjie Ruan
2024-08-23 9:20 ` [PATCH -next 1/5] drm/rockchip: " Jinjie Ruan
2024-08-23 9:45 ` Heiko Stübner
2024-08-23 11:32 ` Jonathan Cameron
2024-08-26 9:04 ` Jinjie Ruan
2024-08-27 1:40 ` Jinjie Ruan
2024-08-27 9:49 ` Jonathan Cameron [this message]
2024-08-23 9:20 ` [PATCH -next 2/5] drm/mediatek: Fix missing of_node_put() for mtk_drm_get_all_drm_priv() Jinjie Ruan
2024-08-23 10:46 ` Christophe JAILLET
2024-08-25 5:16 ` Marion & Christophe JAILLET
2024-08-27 1:42 ` Jinjie Ruan
2024-08-23 9:20 ` [PATCH -next 3/5] drm: of: Use for_each_child_of_node_scoped() Jinjie Ruan
2024-08-23 9:20 ` [PATCH -next 4/5] drm/nouveau: " Jinjie Ruan
2024-08-23 9:20 ` [PATCH -next 5/5] gpu: host1x: Use for_each_available_child_of_node_scoped() Jinjie Ruan
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=20240827104900.00004060@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=airlied@gmail.com \
--cc=andy.yan@rock-chips.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=jic23@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ruanjinjie@huawei.com \
--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;
as well as URLs for NNTP newsgroup(s).