mbox series

[net,0/2] aqc111: Thermal throttling feature

Message ID cover.1544622414.git.igor.russkikh@aquantia.com (mailing list archive)
Headers show
Series aqc111: Thermal throttling feature | expand

Message

Igor Russkikh Dec. 12, 2018, 1:50 p.m. UTC
This patches introduce the thermal throttling feature to prevent possible
heat damage to the hardware.

Dmitry Bezrukov (2):
  net: usb: aqc111: Add read_mdio operation
  net: usb: aqc111: Support for thermal throttling feature

 drivers/net/usb/aqc111.c | 83 ++++++++++++++++++++++++++++++++++++++++
 drivers/net/usb/aqc111.h | 19 +++++++++
 2 files changed, 102 insertions(+)

Comments

David Miller Dec. 13, 2018, 12:18 a.m. UTC | #1
From: Igor Russkikh <Igor.Russkikh@aquantia.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.