From: Mark Lord <liml@rtr.ca>
To: Frans Pop <elendil@planet.nl>
Cc: Saeed Bishara <saeed@marvell.com>,
linux-ide@vger.kernel.org, linux-arm@vger.kernel.org,
jeff@garzik.org, grundler@google.com, buytenh@marvell.com,
nico@marvell.com, tbm@cyrius.com
Subject: Re: [PATCH] sata_mv: enable active LED blink mode for SoC
Date: Mon, 08 Sep 2008 14:47:32 -0400 [thread overview]
Message-ID: <48C57344.4060901@rtr.ca> (raw)
In-Reply-To: <200809081625.31131.elendil@planet.nl>
Frans Pop wrote:
> On Monday 08 September 2008, Frans Pop wrote:
>> On Monday 08 September 2008, Mark Lord wrote:
>>> Frans Pop wrote:
>>>> So, IMO it is an improvement, but it is definitely not a fix for
>>>> the regression.
>>> With a new copy of hdparm, use "hdparm -Q1 /dev/sd?"
>>> Does that fix your "regression" ?
>> $ sudo hdparm -Q1 /dev/sda
>>
>> /dev/sda:
>> setting queue_depth to 1
>> queue_depth = 1
>>
>> Yes, that does result in the original behavior of the led.
>> (Using version 8.9 of hdparm.)
>
> But that's not new information: we'd already determined some time ago that
> disabling NCQ "fixed" the problem, both if it is done at runtime and when
> it is disabled in the driver:
> http://www.spinics.net/lists/linux-ide/msg25642.html
> http://www.spinics.net/lists/linux-ide/msg25645.html
..
Still, that's proof that there is NO REGRESSION here,
so please stop using that term.
Older kernels had a working LED without NCQ,
and so do newer ones. No regression.
In the meanwhile, it appears that Saeed is working to determine
for sure that this is a hardware limitation, as it appears to be.
Cheers
prev parent reply other threads:[~2008-09-08 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-07 11:19 [PATCH] sata_mv: enable active LED blink mode for SoC Saeed Bishara
2008-09-07 11:31 ` saeed bishara
2008-09-08 0:32 ` Frans Pop
2008-09-08 13:40 ` Mark Lord
2008-09-08 14:16 ` Frans Pop
2008-09-08 14:25 ` Frans Pop
2008-09-08 15:18 ` Simon Farnsworth
2008-09-08 15:37 ` Saeed Bishara
2008-09-08 18:44 ` Mark Lord
2008-09-08 18:47 ` Mark Lord [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=48C57344.4060901@rtr.ca \
--to=liml@rtr.ca \
--cc=buytenh@marvell.com \
--cc=elendil@planet.nl \
--cc=grundler@google.com \
--cc=jeff@garzik.org \
--cc=linux-arm@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=nico@marvell.com \
--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).