netdev - Re: [PATCH net 0/2] aqc111: Thermal throttling feature

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 for Android: free password hash cracker in your pocket

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

Date:   Wed, 12 Dec 2018 16:18:24 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     Igor.Russkikh@...antia.com
Cc:     linux-usb@...r.kernel.org, netdev@...r.kernel.org,
        Dmitry.Bezrukov@...antia.com
Subject: Re: [PATCH net 0/2] aqc111: Thermal throttling feature

From: Igor Russkikh <Igor.Russkikh@...antia.com>
Date: Wed, 12 Dec 2018 13:50:06 +0000

> This patches introduce the thermal throttling feature to prevent possible
> heat damage to the hardware.

I see what seems to be a bit of a conflict here, maybe you can explain
the situation better to me.

Andrew suggested that the firmware manage the thermal aspects of the
PHY since it manages all other aspects of the PHY too.

And then the feedback was that the firmware folks don't want to do
that right now.

But then it was also stated that the long term goal is to support
what Andrew asked for, firmware update in the driver and updated
firmwares submitted to linux-firmware.

If the firwmare will eventually have support for thermal management
added, then the code in this series is going to be not used and
just taking up space.

Please explain how all of this is going to fit together, and how we'll
not end up with having to keep this thermal code around forever.

Thanks.