From: htejun@gmail.com (Tejun Heo)
To: linux-arm-kernel@lists.infradead.org
Subject: Cannot detect SATA disks w/ CONFIG_SATA_PMP w/o actually using SATA multiplier
Date: Tue, 30 Nov 2010 20:49:29 +0100 [thread overview]
Message-ID: <4CF55549.4080000@gmail.com> (raw)
In-Reply-To: <AANLkTi=0gBcfrAyJNb0+=obH2QDsqhGM5a9xxwHAoh88@mail.gmail.com>
Hello,
On 11/30/2010 06:46 PM, Lin Mac wrote:
> Could be, but disabling it is the last option. And it's anoying to
> have 2 different modules for different uses.
>
> I'd prefer some clues/checkpoint if possible.
One thing which could be possible is that the controller stashes the
result code for the PMP aware SRST according to the PMP number instead
of the usual place, so the driver can't see it. In that case, the
driver can be modified to check both places I suppose but if the
hardware can be fixed, that would be great.
> I supposed the behavior of detecting and resetting disks (without
> using port multiplier) should be the same for both with and without
> CONFIG_SATA_PMP. All I know about port multiplier is when it is used
> (not much too), but is there any register configuration or behavior is
> required for multiplier to work properly and take effect even when no
> multiplier is used?
Yeah, the only difference is the PMP port number when issuing SRST.
Non-PMP devices ignore it and respond the same way while PMP
recognizes it and responds with PMP signature instead of the signature
of the first device. As written above, I think it's quite likely that
the controller is handling the response D2H Reg FIS incorrectly when a
non-PMP device responds to PMP SRST.
Good luck.
--
tejun
next prev parent reply other threads:[~2010-11-30 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 4:02 Cannot detect SATA disks w/ CONFIG_SATA_PMP w/o actually using SATA multiplier Lin Mac
2010-11-30 14:08 ` Tejun Heo
2010-11-30 17:46 ` Lin Mac
2010-11-30 19:49 ` Tejun Heo [this message]
2010-12-01 5:53 ` Lin Mac
2010-12-01 9:45 ` Tejun Heo
2010-12-02 10:23 ` Lin Mac
2010-12-02 10:31 ` Tejun Heo
2010-12-04 17:07 ` Lin Mac
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=4CF55549.4080000@gmail.com \
--to=htejun@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).