From: Akinobu Mita <akinobu.mita@gmail.com> To: linux-block@vger.kernel.org, linux-leds@vger.kernel.org, linux-nvme@lists.infradead.org, linux-scsi@vger.kernel.org Cc: Akinobu Mita <akinobu.mita@gmail.com>, Frank Steiner <fsteiner-mail1@bio.ifi.lmu.de>, Jacek Anaszewski <jacek.anaszewski@gmail.com>, Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>, Jens Axboe <axboe@kernel.dk>, "James E.J. Bottomley" <jejb@linux.ibm.com>, "Martin K. Petersen" <martin.petersen@oracle.com>, GOTO Masanori <gotom@debian.or.jp>, YOKOTA Hiroshi <yokota@netlab.is.tsukuba.ac.jp>, Hannes Reinecke <hare@suse.com> Subject: [PATCH v4 0/5] introduce LED block device activity trigger Date: Fri, 16 Aug 2019 01:59:54 +0900 [thread overview] Message-ID: <1565888399-21550-1-git-send-email-akinobu.mita@gmail.com> (raw) This work is inspired by the report on linux-nvme mailing list. disk-activity trigger not working for nvme disk: http://lists.infradead.org/pipermail/linux-nvme/2019-July/025253.html This LED block device activity trigger works with any block devices. * v4 - Squash patch 'add interface to stop and restart polling disk stats' into the ledtrig-blk introduction patch - Rename 'led' to 'led_trig' in struct ledtrig_blk * v3 - Avoid the name collision with LED_OFF and LED_ON - Add ABI documentation - Add more detail to Kconfig help text * v2 - Remove "move declaration of led_stop_software_blink() to linux/leds.h" patch - Move the trigger implementation to drivers/leds/trigger - s/blk_ledtrig/ledtrig_blk/ - Add CONFIG_LEDS_TRIGGER_BLOCK - Fix wrong bitops usages - Add interface to stop and restart polling disk stats - Stop polling disk stats for scsi disk during runtime suspend Akinobu Mita (5): block: umem: rename LED_* macros to MEMCTRL_LED_* scsi: mvsas: rename LED_* enums to SGPIO_LED_* scsi: nsp32: rename LED_* macros to EXT_PORT_LED_* block: introduce LED block device activity trigger scsi: sd: stop polling disk stats by ledtrig-blk during runtime suspend .../ABI/testing/sysfs-class-led-trigger-blk | 37 +++ block/genhd.c | 2 + drivers/block/umem.c | 20 +- drivers/block/umem.h | 20 +- drivers/leds/trigger/Kconfig | 9 + drivers/leds/trigger/Makefile | 1 + drivers/leds/trigger/ledtrig-blk.c | 259 +++++++++++++++++++++ drivers/scsi/mvsas/mv_94xx.c | 2 +- drivers/scsi/mvsas/mv_94xx.h | 24 +- drivers/scsi/nsp32.c | 7 +- drivers/scsi/nsp32.h | 4 +- drivers/scsi/sd.c | 40 ++-- include/linux/genhd.h | 3 + include/linux/leds.h | 38 +++ 14 files changed, 411 insertions(+), 55 deletions(-) create mode 100644 Documentation/ABI/testing/sysfs-class-led-trigger-blk create mode 100644 drivers/leds/trigger/ledtrig-blk.c Cc: Frank Steiner <fsteiner-mail1@bio.ifi.lmu.de> Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com> Cc: Pavel Machek <pavel@ucw.cz> Cc: Dan Murphy <dmurphy@ti.com> Cc: Jens Axboe <axboe@kernel.dk> Cc: "James E.J. Bottomley" <jejb@linux.ibm.com> Cc: "Martin K. Petersen" <martin.petersen@oracle.com> Cc: GOTO Masanori <gotom@debian.or.jp> Cc: YOKOTA Hiroshi <yokota@netlab.is.tsukuba.ac.jp> Cc: Hannes Reinecke <hare@suse.com> -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: akinobu.mita@gmail.com (Akinobu Mita) Subject: [PATCH v4 0/5] introduce LED block device activity trigger Date: Fri, 16 Aug 2019 01:59:54 +0900 [thread overview] Message-ID: <1565888399-21550-1-git-send-email-akinobu.mita@gmail.com> (raw) This work is inspired by the report on linux-nvme mailing list. disk-activity trigger not working for nvme disk: http://lists.infradead.org/pipermail/linux-nvme/2019-July/025253.html This LED block device activity trigger works with any block devices. * v4 - Squash patch 'add interface to stop and restart polling disk stats' into the ledtrig-blk introduction patch - Rename 'led' to 'led_trig' in struct ledtrig_blk * v3 - Avoid the name collision with LED_OFF and LED_ON - Add ABI documentation - Add more detail to Kconfig help text * v2 - Remove "move declaration of led_stop_software_blink() to linux/leds.h" patch - Move the trigger implementation to drivers/leds/trigger - s/blk_ledtrig/ledtrig_blk/ - Add CONFIG_LEDS_TRIGGER_BLOCK - Fix wrong bitops usages - Add interface to stop and restart polling disk stats - Stop polling disk stats for scsi disk during runtime suspend Akinobu Mita (5): block: umem: rename LED_* macros to MEMCTRL_LED_* scsi: mvsas: rename LED_* enums to SGPIO_LED_* scsi: nsp32: rename LED_* macros to EXT_PORT_LED_* block: introduce LED block device activity trigger scsi: sd: stop polling disk stats by ledtrig-blk during runtime suspend .../ABI/testing/sysfs-class-led-trigger-blk | 37 +++ block/genhd.c | 2 + drivers/block/umem.c | 20 +- drivers/block/umem.h | 20 +- drivers/leds/trigger/Kconfig | 9 + drivers/leds/trigger/Makefile | 1 + drivers/leds/trigger/ledtrig-blk.c | 259 +++++++++++++++++++++ drivers/scsi/mvsas/mv_94xx.c | 2 +- drivers/scsi/mvsas/mv_94xx.h | 24 +- drivers/scsi/nsp32.c | 7 +- drivers/scsi/nsp32.h | 4 +- drivers/scsi/sd.c | 40 ++-- include/linux/genhd.h | 3 + include/linux/leds.h | 38 +++ 14 files changed, 411 insertions(+), 55 deletions(-) create mode 100644 Documentation/ABI/testing/sysfs-class-led-trigger-blk create mode 100644 drivers/leds/trigger/ledtrig-blk.c Cc: Frank Steiner <fsteiner-mail1 at bio.ifi.lmu.de> Cc: Jacek Anaszewski <jacek.anaszewski at gmail.com> Cc: Pavel Machek <pavel at ucw.cz> Cc: Dan Murphy <dmurphy at ti.com> Cc: Jens Axboe <axboe at kernel.dk> Cc: "James E.J. Bottomley" <jejb at linux.ibm.com> Cc: "Martin K. Petersen" <martin.petersen at oracle.com> Cc: GOTO Masanori <gotom at debian.or.jp> Cc: YOKOTA Hiroshi <yokota at netlab.is.tsukuba.ac.jp> Cc: Hannes Reinecke <hare at suse.com> -- 2.7.4
next reply other threads:[~2019-08-15 17:00 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-08-15 16:59 Akinobu Mita [this message] 2019-08-15 16:59 ` [PATCH v4 0/5] introduce LED block device activity trigger Akinobu Mita 2019-08-15 16:59 ` [PATCH v4 1/5] block: umem: rename LED_* macros to MEMCTRL_LED_* Akinobu Mita 2019-08-15 16:59 ` Akinobu Mita 2019-08-15 16:59 ` [PATCH v4 2/5] scsi: mvsas: rename LED_* enums to SGPIO_LED_* Akinobu Mita 2019-08-15 16:59 ` Akinobu Mita 2019-08-15 16:59 ` [PATCH v4 3/5] scsi: nsp32: rename LED_* macros to EXT_PORT_LED_* Akinobu Mita 2019-08-15 16:59 ` Akinobu Mita 2019-08-15 16:59 ` [PATCH v4 4/5] block: introduce LED block device activity trigger Akinobu Mita 2019-08-15 16:59 ` Akinobu Mita 2019-08-17 14:55 ` Pavel Machek 2019-08-17 14:55 ` Pavel Machek 2019-08-17 20:07 ` Jacek Anaszewski 2019-08-17 20:07 ` Jacek Anaszewski 2019-08-19 14:38 ` Pavel Machek 2019-08-19 18:22 ` Jacek Anaszewski 2019-08-19 18:37 ` Jacek Anaszewski 2019-08-23 16:00 ` Akinobu Mita 2019-08-24 15:53 ` Jacek Anaszewski 2019-08-27 14:03 ` Akinobu Mita 2019-08-27 21:23 ` Jacek Anaszewski 2019-08-28 14:56 ` Akinobu Mita 2019-08-15 16:59 ` [PATCH v4 5/5] scsi: sd: stop polling disk stats by ledtrig-blk during runtime suspend Akinobu Mita 2019-08-15 16:59 ` Akinobu Mita 2019-08-16 19:52 ` Jacek Anaszewski 2019-08-16 19:52 ` Jacek Anaszewski
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=1565888399-21550-1-git-send-email-akinobu.mita@gmail.com \ --to=akinobu.mita@gmail.com \ --cc=axboe@kernel.dk \ --cc=dmurphy@ti.com \ --cc=fsteiner-mail1@bio.ifi.lmu.de \ --cc=gotom@debian.or.jp \ --cc=hare@suse.com \ --cc=jacek.anaszewski@gmail.com \ --cc=jejb@linux.ibm.com \ --cc=linux-block@vger.kernel.org \ --cc=linux-leds@vger.kernel.org \ --cc=linux-nvme@lists.infradead.org \ --cc=linux-scsi@vger.kernel.org \ --cc=martin.petersen@oracle.com \ --cc=pavel@ucw.cz \ --cc=yokota@netlab.is.tsukuba.ac.jp \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.