From: Niklas Cassel <cassel@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Cryptearth <cryptearth@googlemail.com>,
Andrey Melnikov <temnota.am@gmail.com>,
linux-ide@vger.kernel.org, conikost@gentoo.org
Subject: Re: ASMedia ASM1166/ASM1064 port restrictions will break cards with port-multipliers
Date: Sun, 17 Mar 2024 10:36:11 +0100 [thread overview]
Message-ID: <Zfa5iylgKrtrKH8H@ryzen> (raw)
In-Reply-To: <2e471c2b-8432-4501-b093-4295529a4d38@redhat.com>
Hello Hans,
On Fri, Mar 15, 2024 at 04:01:07PM +0100, Hans de Goede wrote:
> >
> > If they only claimed that the HBA supported PMP, the Linux device
> > driver would try to enumerate the devices behind the PMP according
> > to the standard.
> >
> > See AHCI 1.3.1, section 9.2 Port Multiplier Enumeration.
> > Or
> > SATA-IO - Port Multiplier 1.0, 7.4.2 Device Enumeration.
> >
> > The PMP standard also describes how you read the device and vendor
> > ID of the PMP.
> >
> >
> > Right now, they AMedia? seem to have their own home-made PMP implementation.
>
> Ah, ok so I think you did see my reply? Checking if we can ignore
> the builtin PMP support and uses Linux PMP support instead is
> indeed an option.
Yes, I saw your reply.
I wouldn't call it "Linux PMP support", I would simply call it "PMP",
since how you enumerate a PMP is decribed in AHCI and SATA-IO specs.
The "builtin PMP support" is not PMP, since it doesn't follow the specs.
I would rather call it "non-standard vendor extension" or "pseudo-PMP".
> I think we should still merge the revert / dropping of the quirk
> while we figure this out though, because not finding people's disks
> anymore is a clear regression.
I was hoping that someone could try the patch I sent out on Thursday,
which sets the PMP supported bit in the CAP register, as that could
potentially solve both problems here.
I guess if no one has tested it by Monday or Tuesday, we will have
no choice but to revert.
Kind regards,
Niklas
next prev parent reply other threads:[~2024-03-17 9:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFDm6W19R3KHDO09c94Uwry9mdG+whAVy=u4Sdpt30A2MK1KPA@mail.gmail.com>
2024-03-13 6:36 ` ASMedia ASM1166/ASM1064 port restrictions will break cards with port-multipliers Andrey Melnikov
2024-03-13 17:37 ` Cryptearth
2024-03-13 21:21 ` Hans de Goede
2024-03-13 21:52 ` Re[2]: " Conrad Kostecki
2024-03-13 22:20 ` Hans de Goede
2024-03-16 14:01 ` Andrey Jr. Melnikov
2024-03-17 1:34 ` Cryptearth
2024-03-14 15:58 ` Niklas Cassel
2024-03-15 15:01 ` Hans de Goede
2024-03-16 11:33 ` Cryptearth
2024-03-16 11:45 ` Re[2]: " Conrad Kostecki
[not found] ` <CAFDm6W2nCj+qw=-7Sb9xcJTYZ8sitwUriR+Qdh9fo9+ET1Oo=g@mail.gmail.com>
2024-03-17 22:58 ` Fwd: " Cryptearth
2024-03-17 23:04 ` Christoph Hellwig
[not found] ` <CAFDm6W2X_2Nhn4ZeDd-=6Sra-evDW8Dx_CE0m5yggXpOXNTQ9g@mail.gmail.com>
2024-03-17 23:25 ` Christoph Hellwig
[not found] ` <CAFDm6W3pe+nv5CTcEq2FwGbKS4Cdu+7xdLa1Zy6iODampfwxsw@mail.gmail.com>
2024-03-17 23:48 ` Christoph Hellwig
2024-03-18 10:56 ` Niklas Cassel
2024-03-18 11:07 ` Hans de Goede
2024-03-18 11:31 ` Niklas Cassel
2024-03-18 11:53 ` Damien Le Moal
2024-03-18 14:21 ` Hans de Goede
2024-03-18 23:59 ` Damien Le Moal
2024-03-17 9:36 ` Niklas Cassel [this message]
2024-03-15 21:19 Ioannis Barkas
2024-03-17 9:46 ` Niklas Cassel
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=Zfa5iylgKrtrKH8H@ryzen \
--to=cassel@kernel.org \
--cc=conikost@gentoo.org \
--cc=cryptearth@googlemail.com \
--cc=hdegoede@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=temnota.am@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 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.