devicetree.vger.kernel.org archive mirror
 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: [PATCH v6 1/2] usb: dwc3: add Realtek DHC RTD SoC dwc3 glue layer driver
Date: Wed, 1 Nov 2023 06:27:16 +0000	[thread overview]
Message-ID: <bc33c01db5b048899dce5467e7efec74@realtek.com> (raw)
In-Reply-To: <202310301424.39UEOShlC2187546@rtits1.realtek.com.tw>

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);

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-01  6:27 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[昌育德] [this message]
2023-11-01  7:48     ` Christophe JAILLET
     [not found]     ` <202311011453.3A1ErwKI3829148@rtits1.realtek.com.tw>
2023-11-03 10:54       ` Stanley Chang[昌育德]
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=bc33c01db5b048899dce5467e7efec74@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 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).