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>
Subject: Re: [PATCH,v2][1/2] sata-mv: enable HDD led blinking when NCQ is active for GenIIe
Date: Thu, 12 Mar 2009 12:40:51 +0100 [thread overview]
Message-ID: <200903121240.55194.elendil@planet.nl> (raw)
In-Reply-To: <49B7C782.9070004@rtr.ca>
On Wednesday 11 March 2009, Mark Lord wrote:
> Frans Pop wrote:
> > On Wednesday 11 March 2009, Mark Lord wrote:
> >> I'm afraid I just don't understand the purpose of "inherits" above.
> >> This field appears to never be referenced anywhere.
> >
> > What it does (I've been assuming) is include any ops defined in the
> > struct that is being referred to. So mv6xxx_iie_ops gets all the ops
> > defined for mv6xxx_ops plus mv_iie_enable_led_blink.
>
> Except it is not a C-language feature, but rather a simple/clever
> implementation for those specific data structures, as can be seen
> in libata-core.c :: ata_finalize_port_ops().
>
> So, skip that.
Oops. So I implemented part of what's needed, but not all. Well, that just
proves my level of C knowledge. Should have just copied the set of ops
instead of trying to do it clean :-/
> So enough: we'll just do this the original way, for SOC only.
> All of the SOC chips that I know about appear to have the correct bits
> in the same places, so perhaps that's what Saeed's cryptic commment was
> about.
OK. Fine by me. It can always be extended if the need for that is proven.
> Can you test this there and confirm that it still works for you?
> Please try switching NCQ on/off etc.. just to make sure.
The LED behavior is correct with NCQ enabled: slow blink.
But if I disable NCQ blink mode is not turned off, the led continues the
slow blinking. So it looks as if just calling mv_soc_led_blink_disable in
mv_edma_cfg is not sufficient.
> After I hear back, I'll submit this for #upstream.
Thanks Mark.
next prev parent reply other threads:[~2009-03-12 11:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 7:13 [PATCH,v2][0/2] sata_mv: harddisk activity led no longer responsive on QNAP TS-109 Frans Pop
2009-03-11 7:15 ` [PATCH,v2][1/2] sata-mv: enable HDD led blinking when NCQ is active for GenIIe Frans Pop
2009-03-11 12:47 ` Mark Lord
2009-03-11 13:08 ` Frans Pop
2009-03-11 14:15 ` Mark Lord
2009-03-12 11:40 ` Frans Pop [this message]
2009-03-12 14:14 ` Mark Lord
2009-03-12 14:15 ` Mark Lord
2009-03-12 14:26 ` Mark Lord
2009-03-13 8:07 ` Frans Pop
2009-03-13 13:04 ` Mark Lord
2009-03-13 18:19 ` Frans Pop
2009-03-13 19:09 ` Mark Lord
2009-03-14 11:57 ` Frans Pop
2009-03-14 14:53 ` Mark Lord
2009-03-15 10:18 ` Frans Pop
2009-03-12 14:27 ` Frans Pop
2009-03-12 14:31 ` Mark Lord
2009-03-11 7:17 ` [PATCH,v2][2/2] sata-mv: add module parameter msq_blink_led to enable quirk " Frans Pop
2009-03-11 12:33 ` [PATCH,v2][0/2] sata_mv: harddisk activity led no longer responsive on QNAP TS-109 Mark Lord
2009-03-11 12:58 ` Mark Lord
2009-03-11 13:01 ` Frans Pop
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=200903121240.55194.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 \
/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).