From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5E7B81C2311; Wed, 2 Oct 2024 23:34:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=156.67.10.101 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1727912076; cv=none; b=Sb/3vKAJwCopiC/M/3fTeW8PF4SMdXJWN7tFY5Gt8jv8JTyXx0MbXC19OcDiJgzvCVe4RHJ2wSr211rekHFZSTSXdexHUx00E8Uj746GlMhyer7vKhPsIoKF8Kvq7cnll039gOvQS54GsmPbhxVBHcLeCGKsQZZTjtTVN0jmMbY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1727912076; c=relaxed/simple; bh=IR/2THjQ7N/lo1dYF3JRqfaQKnfbHKUU+bWBQEimd/Y=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=YWeDwv9ZNZyI8vV25bTWIxybEFYpGdAyztPJzq9sPHzzhH3mRpCsVYPiGCkNiSKtyhK1eshZWqb6DRoLcxrUD2UvPALm8F87M3ThMJo+uRxR34h0teDYa5HtbIyJqE5Ey0xxXOJKwGGJgTBbyEG6vS8Ex6SqqsBXwBCzqwMh03w= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch; spf=pass smtp.mailfrom=lunn.ch; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b=UPMSjtoL; arc=none smtp.client-ip=156.67.10.101 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lunn.ch Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b="UPMSjtoL" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=z/adl2pW0RCDm1r3rANHkuDq37x7Og47YTxSRMtrFnI=; b=UPMSjtoL/xUVUt8lXK1HxkKdry s6VgLmy+by7Qq01QD6TRQExajDup/DIXwxQSl9EDe2j0syl1NT17RBSEzNpnN8AMOE6TQtm5Maqff 9hYIgm0sLa7kGysUzSWxzu+cUdse70mtEnHv4MbUEf8yuM8nHOBCMHCV6AUCx+WEFe4s=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1sw8rR-008u9W-I1; Thu, 03 Oct 2024 01:34:25 +0200 Date: Thu, 3 Oct 2024 01:34:25 +0200 From: Andrew Lunn To: Kory Maincent Cc: Oleksij Rempel , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Jonathan Corbet , Donald Hunter , Thomas Petazzoni , linux-kernel@vger.kernel.org, netdev@vger.kernel.org, linux-doc@vger.kernel.org, Kyle Swenson , Dent Project , kernel@pengutronix.de Subject: Re: [PATCH net-next 05/12] net: pse-pd: Add support for getting and setting port priority Message-ID: References: <20241002-feature_poe_port_prio-v1-0-787054f74ed5@bootlin.com> <20241002-feature_poe_port_prio-v1-5-787054f74ed5@bootlin.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20241002-feature_poe_port_prio-v1-5-787054f74ed5@bootlin.com> On Wed, Oct 02, 2024 at 06:28:01PM +0200, Kory Maincent wrote: > From: Kory Maincent (Dent Project) > > This patch introduces the ability to configure the PSE PI port priority. > Port priority is utilized by PSE controllers to determine which ports to > turn off first in scenarios such as power budget exceedance. > > The pis_prio_max value is used to define the maximum priority level > supported by the controller. Both the current priority and the maximum > priority are exposed to the user through the pse_ethtool_get_status call. > > Signed-off-by: Kory Maincent Reviewed-by: Andrew Lunn Andrew