From: Aditya Prayoga <aditya@kobol.io>
To: linux-ide@vger.kernel.org, linux-leds@vger.kernel.org
Cc: Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Jens Axboe <axboe@kernel.dk>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Daniel Golle <daniel@makrotopia.org>,
Aditya Prayoga <aditya@kobol.io>
Subject: [PATCH 0/2] Add support per ATA port ledtrigger on armada 38x
Date: Wed, 19 Sep 2018 11:45:28 +0800 [thread overview]
Message-ID: <1537328730-9156-1-git-send-email-aditya@kobol.io> (raw)
Hi everyone,
This series adds support LED trigger for each ATA port indicating disk activity
in Armada 38x. I pick up the work done by Daniel Golle which can be found at [1]
Helios4 which is based on Armada 388, has four LEDs designed to indicate disk
activity on each SATA ports. As the final switch (CONFIG_ATA_LEDS) to enable
the codepath by default is no, it should not affect the rest of Armada 38x
based boards.
[1] https://patchwork.ozlabs.org/patch/420733/
---
Notes
checkpatch.pl complains about "WARNING: please write a paragraph that
describes the config symbol fully" but I think the description is clear
enough to ignore the warning.
Some performance number tested on Western Digital Red 2TB WD20EFRX
using fio randrw
* CONFIG_ATA_LEDS disabled and selected trigger is none
read : iops=326
write : iops=109
* CONFIG_ATA_LEDS disabled and selected trigger is disk-activity
read : iops=325
write : iops=108
* CONFIG_ATA_LEDS enabled and selected trigger is ata1
read : iops=325
write : iops=108
---
Aditya Prayoga (1):
ARM: mvebu: Enable ARCH_WANT_LIBATA_LEDS in Armada 38x
Daniel Golle (1):
libata: add ledtrig support
arch/arm/mach-mvebu/Kconfig | 1 +
drivers/ata/Kconfig | 16 +++++++++++++
drivers/ata/libata-core.c | 56 +++++++++++++++++++++++++++++++++++++++++++++
include/linux/libata.h | 7 ++++++
4 files changed, 80 insertions(+)
--
2.7.4
next reply other threads:[~2018-09-19 3:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 3:45 Aditya Prayoga [this message]
2018-09-19 3:45 ` [PATCH 1/2] libata: add ledtrig support Aditya Prayoga
2018-09-19 13:01 ` Andrew Lunn
2018-09-20 9:53 ` Aditya Prayoga
2018-09-19 18:36 ` kbuild test robot
2018-09-19 21:49 ` kbuild test robot
2018-09-19 21:49 ` [PATCH] libata: fix semicolon.cocci warnings kbuild test robot
2018-09-20 7:23 ` [PATCH 1/2] libata: add ledtrig support Pavel Machek
2018-09-20 8:24 ` Daniel Golle
2018-09-20 22:04 ` Pavel Machek
2018-09-21 6:31 ` Daniel Golle
2018-09-19 3:45 ` [PATCH 2/2] ARM: mvebu: Enable ARCH_WANT_LIBATA_LEDS in Armada 38x Aditya Prayoga
2018-09-20 7:26 ` Pavel Machek
2018-09-26 6:05 ` Aditya Prayoga
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=1537328730-9156-1-git-send-email-aditya@kobol.io \
--to=aditya@kobol.io \
--cc=andrew@lunn.ch \
--cc=axboe@kernel.dk \
--cc=daniel@makrotopia.org \
--cc=gregory.clement@bootlin.com \
--cc=jacek.anaszewski@gmail.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=pavel@ucw.cz \
--cc=sebastian.hesselbarth@gmail.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;
as well as URLs for NNTP newsgroup(s).