From: Tejun Heo <tj@kernel.org>
To: Xiangliang Yu <yxlraid@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] AHCI: disabled FBS prior to issuing software reset
Date: Sat, 28 Sep 2013 07:49:50 -0400 [thread overview]
Message-ID: <20130928114950.GA2620@htj.dyndns.org> (raw)
In-Reply-To: <1380366816-16221-1-git-send-email-yxlraid@gmail.com>
Hello,
On Sat, Sep 28, 2013 at 07:13:36PM +0800, Xiangliang Yu wrote:
> If device is attached to port multiplier, the detection process
> look like this:
> ahci_hardreset(link, class, deadline)
> if (class == ATA_DEV_PMP) {
> sata_pmp_attach(dev) /* will enable FBS */
> sata_pmp_init_links(ap, nr_ports);
> ata_for_each_link(link, ap, EDGE) {
> sata_std_hardreset(link, class, deadline);
> if (link_is_online)
> ahci_softreset(link, class, deadline);
> }
> }
> But, according to chapter 9.3.9 in AHCI spec: Prior to issuing software reset,
> software shall clear PxCMD.ST to '0' and then clear PxFBS.EN to '0'.
How was this tested? Do you observe any behavior difference? At this
point, we are not using SRST on PMP ports anyway, so I can't see how
this would make any difference.
Thanks.
--
tejun
next prev parent reply other threads:[~2013-09-28 11:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-28 11:13 [PATCH 1/1] AHCI: disabled FBS prior to issuing software reset Xiangliang Yu
2013-09-28 11:49 ` Tejun Heo [this message]
2013-09-28 13:04 ` xiangliang yu
2013-09-28 13:10 ` Tejun Heo
2013-10-12 6:56 ` xiangliang yu
2013-10-13 19:57 ` Tejun Heo
2013-10-14 1:48 ` xiangliang yu
2013-10-15 3:40 ` xiangliang yu
2013-10-15 12:50 ` Tejun Heo
2013-09-28 15:23 ` Sergei Shtylyov
[not found] <CAP0P+NUQSByVNquY-zP3S-6GKhSvQXgq_4dDCTd2R8FM=YC_Gg@mail.gmail.com>
2013-10-27 11:57 ` Tejun Heo
2013-10-28 1:48 ` xiangliang yu
2013-11-14 0:26 ` xiangliang yu
2013-11-14 5:25 ` Tejun Heo
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=20130928114950.GA2620@htj.dyndns.org \
--to=tj@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yxlraid@gmail.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).