From: Frans Pop <elendil@planet.nl>
To: Mark Lord <liml@rtr.ca>
Cc: linux-arm@vger.kernel.org, linux-ide@vger.kernel.org,
Saeed Bishara <saeed@marvell.com>, Nicolas Pitre <nico@cam.org>,
Lennert Buytenhek <buytenh@wantstofly.org>,
Martin Michlmayr <tbm@cyrius.com>
Subject: Re: [RFC][PATCH] sata-mv: add module parameter msq_blink_led to enable quirk for SOC
Date: Tue, 10 Mar 2009 18:09:43 +0100 [thread overview]
Message-ID: <200903101809.45770.elendil@planet.nl> (raw)
In-Reply-To: <49B6820C.1010206@rtr.ca>
On Tuesday 10 March 2009, Mark Lord wrote:
> Frans Pop wrote:
> > For some Marvell chips the HDD led does not blink when there is disk
> > I/O if NCQ is enabled. Only enable the quirk that works around this
> > (by enabling blink mode for the led) if parameter msq_blink_led is
> > set as it is not clear whether this is a general erratum or related
> > to the type of hard disk connected to the controller.
>
> ...
> +/* msq_blink_led only has effect for SOC */
> +module_param(msq_blink_led, int, 0444);
> +MODULE_PARM_DESC(msq_blink_led,
> + "Use blink mode quirk for HDD led when MSQ is enabled (0=off,
> 1=on)"); ...
>
> Well, I don't understand the parameter name (msq??),
Brainfart: contamination from msi and phonetically ncq and msq are
somewhat similar :-/
Will fix for next version.
> and I'm not sure if we need a parameter or not.
I don't either. But given the uncertainty surrounding this it seemed like
as useful feature. I'll leave it as a separate patch so it can either be
omitted or more easily reverted later.
> Saeed said the original patch should apply "for all devices besides
> to the SOC", which I think means all GenIIe chip variants.
>
> So if you want to rework the first patch so that the blink fix
> works for all GEN_IIE chips, then I'll test it here with a few
> different drives from different vendors and see how the LEDs behave.
> I also have boards from several different vendors to try it on.
Cool. Will do. I'm going to assume I can use the same code to actually
enable the blink mode.
For the testing at least the parameter will be useful.
> I'd also like to investigate whether the same fix is necessary
> for GEN_II chips as well as GEN_IIE. Perhaps Saeed might provide
> further information there, but we shouldn't hold our breaths waiting.
OK. I'll implement it as an op so it can be extended as needed.
Thanks,
FJP
next prev parent reply other threads:[~2009-03-10 17:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 9:24 [regression] sata_mv: harddisk activity led no longer responsive on QNAP TS-109 Frans Pop
2008-08-26 10:25 ` Frans Pop
2009-01-24 14:57 ` Mark Lord
2009-02-24 8:33 ` [RFC][PATCH] " Frans Pop
2009-02-24 9:33 ` saeed bishara
2009-03-01 7:59 ` Martin Michlmayr
2009-03-01 12:44 ` Frans Pop
2009-03-10 11:36 ` [RFC][PATCH] sata-mv: add module parameter msq_blink_led to enable quirk for SOC Frans Pop
2009-03-10 15:06 ` Mark Lord
2009-03-10 16:28 ` Martin Michlmayr
2009-03-10 16:40 ` Mark Lord
2009-03-10 16:47 ` Frans Pop
2009-03-10 17:09 ` Frans Pop [this message]
2008-08-26 14:03 ` [regression] sata_mv: harddisk activity led no longer responsive on QNAP TS-109 Mark Lord
2008-08-27 14:56 ` Martin Michlmayr
2008-08-27 17:06 ` saeed bishara
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=200903101809.45770.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=buytenh@wantstofly.org \
--cc=liml@rtr.ca \
--cc=linux-arm@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=nico@cam.org \
--cc=saeed@marvell.com \
--cc=tbm@cyrius.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).