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: <747ce0a9-a629-e3f9-c59c-388333d3d911@gmail.com>
Date:   Thu, 4 May 2023 11:27:34 +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:26 AM, Stanley Chang[昌育德] wrote:
[...]

>>> The Realtek RTD1xxx SoCs were designed, the global register address
>>> offset at 0x8100.
>>
>>   Can't parse that, perhaps "with" is missing?
>>
>>> The default address offset is constant at DWC3_GLOBALS_REGS_START
>>> (0xc100). Therefore, add a check if the compatible name of the parent
>>> is "realtek,rtd1xxx-dwc3", then global
>>
>>    Wildcards are not allowed in the "compatible" props...
> 
> I can't understand your meaning.
> Do you mean I can't use rtd1xxx ?

   You can't, indeed.

MBR, Sergey