From: "Stanley Chang[昌育德]" <stanley_chang@realtek.com>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v6] usb: dwc3: core: add support for realtek SoCs custom's global register start address
Date: Sat, 6 May 2023 04:14:45 +0000 [thread overview]
Message-ID: <c2ddb17c182a42be9fc22afa85669695@realtek.com> (raw)
In-Reply-To: <20230506013842.7iu4hq35uyamt6np@synopsys.com>
Hi Thinh,
> > diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c index
> > 0beaab932e7d..278cd1c33841 100644
> > --- a/drivers/usb/dwc3/core.c
> > +++ b/drivers/usb/dwc3/core.c
> > @@ -1800,6 +1800,17 @@ static int dwc3_probe(struct platform_device
> *pdev)
> > dwc_res = *res;
> > dwc_res.start += DWC3_GLOBALS_REGS_START;
> >
> > + if (dev->of_node) {
> > + struct device_node *parent =
> > + of_get_parent(dev->of_node);
> > +
> > + if (of_device_is_compatible(parent, "realtek,rtd-dwc3"))
> > + {
>
> Is your platform already released or is it still under development? Just curious
> since the compatible string isn't fixed. Is it going to be changed in the future?
Yes, our platform is released.
In our driver (the parent of the dwc3 driver), we used the compatible name "Realtek,dwc3".
To support this patch, I will add an alternative name "Realtek,rtd-dwc3" to our driver.
Thanks,
Stanley
next prev parent reply other threads:[~2023-05-06 4:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 2:50 [PATCH v6] usb: dwc3: core: add support for realtek SoCs custom's global register start address Stanley Chang
2023-05-06 1:38 ` Thinh Nguyen
2023-05-06 4:14 ` Stanley Chang[昌育德] [this message]
2023-05-11 0:35 ` Thinh Nguyen
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=c2ddb17c182a42be9fc22afa85669695@realtek.com \
--to=stanley_chang@realtek.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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