linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Bob Stewart <bob@evoria.net>
Cc: echo6 <echo6_uk@yahoo.com>, linux-ide@vger.kernel.org
Subject: Re: sata_inic162x  LED enable request
Date: Mon, 08 Sep 2008 14:12:36 +0200	[thread overview]
Message-ID: <48C516B4.80900@kernel.org> (raw)
In-Reply-To: <495283.8352.qm@web904.biz.mail.mud.yahoo.com>

Bob Stewart wrote:
> --- Tejun Heo <tj@kernel.org> wrote:
>> Hmm... according to the datasheet, this is SWLED.
>>
>>   SOFTWARE CONTROL LED ENABLE: When set, software has full control of
>>   LED activity. When clear, the LED’s are controlled by hardware.
>>
>> And then there are two more bits, LED0 and LED1 which seem to be the
>> actual control knob for LEDs.  From the description it looks like the
>> bit should stay off so tha the controller hardware can drive LEDs.  I
>> presume this doesn't work as described?
> 
> Uh oh.  It sounds like we may not be looking at the same book.  The one
> I have is "INIC-1620TA2/1622TA2/1623TA2", Version 1.4, October, 2005.
> In this book, the bit is "03  rw  0  (LEDEN)  LED ENABLE: When set, the 
> LED will flash when the device is busy."  With your driver as-is, both LEDs
> turn on during the boot process and then stay on completely.  

Hmm... I have two - INIC-1622 V1.0 Septermber, 2003 and the one you
have.  Till now, I haven't found any noticeable difference.
Apparently, the meaning of the bit has changed.

> Which book are you using and are all these bits in the Global
> Control register, which we call HOST_CTL?  Did I get an old book?

Yes, that's GCTRL.  Can you please do the '+' -> '|' change and resend
the patch?

Thanks.

-- 
tejun

  reply	other threads:[~2008-09-08 12:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21 16:58 sata_inic162x echo6
2008-08-21 16:52 ` sata_inic162x Alan Cox
2008-08-21 18:00   ` sata_inic162x echo6
2008-08-30 10:29 ` sata_inic162x Tejun Heo
2008-09-04  0:35   ` sata_inic162x LED enable request Bob Stewart
2008-09-04  7:27     ` echo6
2008-09-04 15:54       ` Bob Stewart
2008-09-04 18:14         ` echo6
2008-09-04  8:13     ` Tejun Heo
2008-09-04 15:52       ` Bob Stewart
2008-09-08 12:12         ` Tejun Heo [this message]
2008-09-08 15:13           ` Bob Stewart
2008-09-08 19:09             ` Tejun Heo
2008-09-08 20:24               ` Bob Stewart
2008-09-09  7:53                 ` Tejun Heo
2008-09-09 19:41                   ` Bob Stewart
2008-09-11  9:50                     ` [PATCH #upstream-fixes] sata_inic162x: enable LED blinking Tejun Heo
2008-09-13 20:43                       ` Jeff Garzik

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=48C516B4.80900@kernel.org \
    --to=tj@kernel.org \
    --cc=bob@evoria.net \
    --cc=echo6_uk@yahoo.com \
    --cc=linux-ide@vger.kernel.org \
    /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).