All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stanley Chang[昌育德]" <stanley_chang@realtek.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: "Thinh.Nguyen@synopsys.com" <Thinh.Nguyen@synopsys.com>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"krzysztof.kozlowski+dt@linaro.org"
	<krzysztof.kozlowski+dt@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>
Subject: RE: RE: [PATCH v6 1/2] usb: dwc3: add Realtek DHC RTD SoC dwc3 glue layer driver
Date: Fri, 3 Nov 2023 10:54:26 +0000	[thread overview]
Message-ID: <da4c75ba87c3476694361ee3bc333401@realtek.com> (raw)
In-Reply-To: <202311011453.3A1ErwKI3829148@rtits1.realtek.com.tw>

Hi Christophe,

> Le 01/11/2023 à 07:27, Stanley Chang[昌育德] a écrit :
> > Hi CJ,
> >
> > I think these functions are not needed in remove function.
> >
> > In dwc3_rtk_probe_dwc3_core,
> > I have used
> > dwc3_node = of_get_compatible_child(node, "snps,dwc3"); and dwc3_pdev
> > = of_find_device_by_node(dwc3_node);
> >
> > So, I call these put functions.
> > platform_device_put(dwc3_pdev);
> > of_node_put(dwc3_node);
> 
> Yes, but you call it only in the error handling path of the function.
> 
> I wonder if they should also be called in the remove function in order to
> decrement the ref-counted reference.
> 
> 
> Same in __get_dwc3_maximum_speed(), the reference taken by:
>     dwc3_np = of_get_compatible_child(np, "snps,dwc3"); is never released.
> 
> 
> See the comment at [1] to see what I mean.
> 
> 
> [1]: https://elixir.bootlin.com/linux/v6.6/source/drivers/of/base.c#L681

You are right!
For dwc3_pdev, dwc3_np or dwc3_node, I should add of_node_put to release them when the function exits. 
https://elixir.bootlin.com/linux/v6.5.10/source/drivers/usb/dwc3/dwc3-meson-g12a.c#L567

I will add a patch to fix this.

For example,
diff --git a/drivers/usb/dwc3/dwc3-rtk.c b/drivers/usb/dwc3/dwc3-rtk.c
index 590028e8fdcb..9d6f2a8bd6ce 100644
--- a/drivers/usb/dwc3/dwc3-rtk.c
+++ b/drivers/usb/dwc3/dwc3-rtk.c
@@ -187,6 +187,7 @@ static enum usb_device_speed __get_dwc3_maximum_speed(struct device_node *np)

        ret = match_string(speed_names, ARRAY_SIZE(speed_names), maximum_speed);

+       of_node_put(dwc3_np);
        return (ret < 0) ? USB_SPEED_UNKNOWN : ret;
 }

@@ -339,6 +340,8 @@ static int dwc3_rtk_probe_dwc3_core(struct dwc3_rtk *rtk)

        switch_usb2_role(rtk, rtk->cur_role);

+       platform_device_put(dwc3_pdev);
+       of_node_put(dwc3_node);
        return 0;

 err_pdev_put:


Thanks,
Stanley

> CJ
> >
> > Thanks,
> > Stanley
> >
> >> Hi,
> >>
> >> Is something like
> >>          platform_device_put(dwc3_pdev);
> >>          of_node_put(dwc3_node);
> >> needed in the remove function?
> >>
> >> (as done in the error handling path of dwc3_rtk_probe_dwc3_core())
> >>
> >> Or should it be added at the end of dwc3_rtk_probe_dwc3_core() if the
> >> reference are nor needed anymore when we leave the function?
> >>
> >> CJ
> >>
> >>> +     of_platform_depopulate(rtk->dev); }
> >>> +
> >>
> >> ...
> >


  parent reply	other threads:[~2023-11-03 10:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-26  3:10 [PATCH v6 1/2] usb: dwc3: add Realtek DHC RTD SoC dwc3 glue layer driver Stanley Chang
2023-08-26  3:10 ` [PATCH v6 2/2] dt-bindings: usb: dwc3: Add Realtek DHC RTD SoC DWC3 USB Stanley Chang
2023-10-30  8:05 ` [PATCH v6 1/2] usb: dwc3: add Realtek DHC RTD SoC dwc3 glue layer driver Christophe JAILLET
     [not found] ` <202310301424.39UEOShlC2187546@rtits1.realtek.com.tw>
2023-11-01  6:27   ` Stanley Chang[昌育德]
2023-11-01  7:48     ` Christophe JAILLET
     [not found]     ` <202311011453.3A1ErwKI3829148@rtits1.realtek.com.tw>
2023-11-03 10:54       ` Stanley Chang[昌育德] [this message]
2023-11-04  8:35         ` Christophe JAILLET

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=da4c75ba87c3476694361ee3bc333401@realtek.com \
    --to=stanley_chang@realtek.com \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=robh+dt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.