From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH net 0/2] aqc111: Thermal throttling feature
Date: Wed, 12 Dec 2018 21:38:46 +0100
Message-ID: <20181212203846.GD14328@lunn.ch>
References: <cover.1544622414.git.igor.russkikh@aquantia.com>
 <eeb5ad8f-267f-a74b-5ff6-4851bbd2a99d@aquantia.com>
 <b932bbed-be20-02f4-9407-f7d767a66d91@gmail.com>
 <ce7d3cb2-9cd4-5901-b1bd-9401f6895100@aquantia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Florian Fainelli <f.fainelli@gmail.com>,
        "davem@davemloft.net" <davem@davemloft.net>,
        "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
        Dmitry Bezrukov <Dmitry.Bezrukov@aquantia.com>
To: Igor Russkikh <Igor.Russkikh@aquantia.com>
Return-path: <netdev-owner@vger.kernel.org>
Received: from vps0.lunn.ch ([185.16.172.187]:45016 "EHLO vps0.lunn.ch"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1726297AbeLLUiv (ORCPT <rfc822;netdev@vger.kernel.org>);
        Wed, 12 Dec 2018 15:38:51 -0500
Content-Disposition: inline
In-Reply-To: <ce7d3cb2-9cd4-5901-b1bd-9401f6895100@aquantia.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

> A whole separate concern is how much userspace should be involved here.
> It could be a very device specific (and therefore driver specific) logic
> on how to do device's thermal control.

Hi Igor

Well, if you fully expose the PHY to Linux using a PHY driver, it
would not be device specific at all. The PHY layer knows how to ask
the PHY to drop to lower speeds. The Marvell PHYs with their
temperature sensors could also use this core code.

You are running into trouble because you want to both to hide the PHY
from Linux, but also have Linux control the PHY to avoid it melting.
This is why i actually think you should be doing this in firmware.

     Andrew