Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kurt Kanzenbach <kurt@linutronix.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Vinicius Costa Gomes <vinicius.gomes@intel.com>,
	intel-wired-lan@lists.osuosl.org,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Eric Dumazet <edumazet@google.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v2] igc: Add support for LEDs on i225/i226
Date: Thu, 01 Feb 2024 14:52:41 +0100	[thread overview]
Message-ID: <87wmro70ly.fsf@kurt.kurt.home> (raw)
In-Reply-To: <3629e504-4c22-4222-b218-32c9945ff77e@lunn.ch>

[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]

On Thu Feb 01 2024, Andrew Lunn wrote:
> On Thu, Feb 01, 2024 at 01:59:46PM +0100, Kurt Kanzenbach wrote:
>> Add support for LEDs on i225/i226. The LEDs can be controlled via sysfs
>> from user space using the netdev trigger. The LEDs are named as
>> igc-<bus><device>-<led> to be easily identified.
>> 
>> Offloading link speed is supported. Other modes are simulated in software
>> by using on/off. Tested on Intel i225.
>> 
>> Signed-off-by: Kurt Kanzenbach <kurt@linutronix.de>
>> ---
>> 
>> Changes since v1:
>> 
>>  * Add brightness_set() to allow software control (Andrew)
>>  * Remove offloading of activity, because the software control is more flexible
>
> Please could you expand on that. Activity is quite expensive in
> software, since it needs to get the statistics every 50ms and then
> control the LED. So if activity can be offloaded, it should
> be. Sometimes the hardware can only offload a subset of activity
> indications, which is fine. It should implement those it can, and
> leave the rest to software.

Activity can be offloaded to HW only with Tx and Rx combined. Individual
Rx or Tx activity is not supported. But sure, when a user selects Rx and
Tx it can be offloaded, if it's too expensive doing it in software.

Thanks,
Kurt

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

      reply	other threads:[~2024-02-01 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01 12:59 [Intel-wired-lan] [PATCH iwl-next v2] igc: Add support for LEDs on i225/i226 Kurt Kanzenbach
2024-02-01 13:39 ` Andrew Lunn
2024-02-01 13:52   ` Kurt Kanzenbach [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wmro70ly.fsf@kurt.kurt.home \
    --to=kurt@linutronix.de \
    --cc=andrew@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=bigeasy@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vinicius.gomes@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox