From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753223AbdK1Vym (ORCPT ); Tue, 28 Nov 2017 16:54:42 -0500 Received: from mail-wm0-f67.google.com ([74.125.82.67]:34561 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751673AbdK1Vyk (ORCPT ); Tue, 28 Nov 2017 16:54:40 -0500 X-Google-Smtp-Source: AGs4zMZoxr4nFbewa67XWXKvZClC+cjkDeANycpGZUvb0ijgIAZef8u5liVwpUFmeFDtIYpuBbj5pw== From: Ben Whitten To: rpurdie@rpsys.net, jacek.anaszewski@gmail.com, pavel@ucw.cz Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, Ben Whitten Subject: [PATCH] Introduce a NETDEV LED trigger Date: Tue, 28 Nov 2017 21:54:17 +0000 Message-Id: <1511906058-30649-1-git-send-email-ben.whitten@gmail.com> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org It's quite useful to be able to trigger LEDs based on network activity, similar mechanisms exist in routers and gateway devices. I am looking to mainline a patch that has existed out of tree for some time in OpenWRT/LEDE. The patch has been updated and restructured and most of the issues raised in the initial submission have been addressed [1]. I am also including the netdev mailing list as it was suggested previously that if there is no activity the interval will still run and is wasteful [1] https://lkml.org/lkml/2010/11/14/116 Ben Whitten (1): leds: trigger: Introduce a NETDEV trigger .../ABI/testing/sysfs-class-led-trigger-netdev | 45 +++ drivers/leds/trigger/Kconfig | 7 + drivers/leds/trigger/Makefile | 1 + drivers/leds/trigger/ledtrig-netdev.c | 428 +++++++++++++++++++++ 4 files changed, 481 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-class-led-trigger-netdev create mode 100644 drivers/leds/trigger/ledtrig-netdev.c -- 2.7.4