mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Stanley Chang[昌育德]" <stanley_chang@realtek.com>
To: Sergei Shtylyov <sergei.shtylyov@gmail.com>,
	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 v5] usb: dwc3: core: add support for realtek SoCs custom's global register start address
Date: Fri, 5 May 2023 02:17:30 +0000	[thread overview]
Message-ID: <0d1ed3a748cf4cec96d5ed890939e207@realtek.com> (raw)
In-Reply-To: <ed78530f-55b2-9152-976c-d13cf19407ad@gmail.com>

> >>> I can't understand your meaning.
> >>> Do you mean I can't use rtd1xxx ?
> >>
> >>    You can't, indeed.
> >>
> > The namr rtd1xxx is represent the name of SoCs, for rtd129x, rtd139x,
> rtd16xx, ... etc.
> >
> > Must I use a real chip name, example rtd129x?
> 
>    Yes but iff x is not also a wildcard. rtd1290 would fit iff that SoC actually
> exists.
> 
> > Or can I use "rtd" only to represent all Socs?
> 
>    If you have a fallback value of the "compatible" prop, you can use it...

I will use the name "rtd" to instead the "rtd1xxx".

Thanks,
Stanley

      reply	other threads:[~2023-05-05  2:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04  3:44 Stanley Chang
2023-05-04  7:50 ` Sergei Shtylyov
2023-05-04  8:26   ` Stanley Chang[昌育德]
2023-05-04  8:27     ` Sergei Shtylyov
2023-05-04  8:36       ` Stanley Chang[昌育德]
2023-05-04 15:45         ` Sergei Shtylyov
2023-05-05  2:17           ` Stanley Chang[昌育德] [this message]

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=0d1ed3a748cf4cec96d5ed890939e207@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 \
    --cc=sergei.shtylyov@gmail.com \
    /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
all inboxes | Powered by JetHome®