linux-kernel - Re: [PATCH v5] usb: dwc3: core: add support for realtek SoCs custom's global register start address

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ed78530f-55b2-9152-976c-d13cf19407ad@gmail.com>
Date:   Thu, 4 May 2023 18:45:42 +0300
From:   Sergei Shtylyov <sergei.shtylyov@...il.com>
To:     Stanley Chang[昌育德] 
        <stanley_chang@...ltek.com>,
        Thinh Nguyen <Thinh.Nguyen@...opsys.com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5] usb: dwc3: core: add support for realtek SoCs custom's
 global register start address

On 5/4/23 11:36 AM, Stanley Chang[昌育德] wrote:

>>> 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...

MBR, Sergey