All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Mark Lord <liml@rtr.ca>
Cc: Jeff Garzik <jgarzik@pobox.com>, Alan Cox <alan@redhat.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Port-Multiplier hotplug support: ATA_FLAG_AN
Date: Wed, 14 May 2008 12:10:34 +0900	[thread overview]
Message-ID: <482A582A.7090108@gmail.com> (raw)
In-Reply-To: <482A1B41.50507@rtr.ca>

Mark Lord wrote:
> Tejun,
> 
> Apparently the newer (GenIIe) sata_mv chips *can* support asynchronous
> notification without problems.  Some/all of the older ones cannot (errata).
> 
> So, I've done the one-liner change in sata_mv, to add ATA_FLAG_AN to
> the 7042 and 6042 chips, and it all seems to work rather nicely.
> 
> Am I missing something?  Is there any other local code to sata_mv
> that should be provided before setting ATA_FLAG_AN ?
> 
> Like I said, it works, but I just want to check whether any other
> pieces are expected to be present?

You need to call sata_async_notification() from interrupt handler after 
AN FIS is received.  sata_async_notification() is responsible for 
discerning between ATAPI and PMP ANs using SNotification and schedule 
appropriate actions.  If SNotification is not available && PMP is 
attached, it just calls ata_port_schedule_eh().  That's probably why it 
just worked by setting ATA_FLAG_AN.

Thanks.

-- 
tejun

  parent reply	other threads:[~2008-05-14  3:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13 22:50 Port-Multiplier hotplug support: ATA_FLAG_AN Mark Lord
2008-05-13 23:25 ` Jeff Garzik
2008-05-14  2:50   ` Mark Lord
2008-05-14  3:10 ` Tejun Heo [this message]
2008-05-14 12:46   ` Mark Lord

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=482A582A.7090108@gmail.com \
    --to=htejun@gmail.com \
    --cc=alan@redhat.com \
    --cc=jgarzik@pobox.com \
    --cc=liml@rtr.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.