netdev - RE: [PATCH net-next 05/10] lan78xx: Disable USB3 link power state transitions

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] [day] [month] [year] [list]

Message-ID: <02dc01d79900$20a60580$61f21080$@pebblebay.com>
Date:   Tue, 24 Aug 2021 16:52:45 +0100
From:   "John Efstathiades" <john.efstathiades@...blebay.com>
To:     "'Jakub Kicinski'" <kuba@...nel.org>
Cc:     <linux-usb@...r.kernel.org>, <UNGLinuxDriver@...rochip.com>,
        <woojung.huh@...rochip.com>, <davem@...emloft.net>,
        <netdev@...r.kernel.org>
Subject: RE: [PATCH net-next 05/10] lan78xx: Disable USB3 link power state transitions



> > I like the sound of the device match list but I don't know what you
> mean.
> > Is there a driver or other reference you could point me at that provides
> > additional info?
> 
> Depends on what the discriminator is. If problems happen with
> a particular ASIC revisions driver needs to read the revision
> out and make a match. If it's product by product you can use
> struct usb_device_id :: driver_info to attach metadata per
> device ID. If it's related to the platform things like DMI
> matching are sometimes used. I have very limited experience
> with Android / embedded ARM so not sure what would work there.

Thanks. Based on that I will remove this change from the patch set and
discuss again with the driver maintainer.