From: Szuying Chen <chensiying21@gmail.com>
To: cassel@kernel.org, dlemoal@kernel.org, linux-ide@vger.kernel.org,
Jesse1_Chang@asmedia.com.tw, Richard_Hsu@asmedia.com.tw,
Chloe_Chen@asmedia.com.tw, conikost@gentoo.org,
cryptearth@googlemail.com, temnota.am@gmail.com,
hdegoede@redhat.com, jnyb.de@gmail.com
Subject: Re: ASMedia PMP inquiry
Date: Tue, 19 Mar 2024 17:41:44 +0800 [thread overview]
Message-ID: <20240319094144.11946-1-Chloe_Chen@asmedia.com.tw> (raw)
Signed-off-by: Szuying Chen <Chloe_Chen@asmedia.com.tw>
---
On 3/18/24 19:32, Niklas Cassel wrote:
> A user plugging in an external PMP (so not a PMP embedded on the PCIe card).
> We need to be able to read the PMP device and vendor ID, in order to apply
> the correct PMP quirks, see sata_pmp_quirks(). So trying to hide which PMP
> that is connected is bad, not only because it violates the specs, but also
> because it stops us from providing the proper quirks for the connected PMP.
>
> Could you please tell us how we can communicate with the PMPs directly?
> (Regardless if they are external PMPs or PMPs embedded on the PCIe card.)
>
Hello Niklas,
Unfortunately, our design does not provide interface to communicate with
the PMPs directly.
When ASM1064 plugging in an external PMP, we will hide the PMP and map to
the virtual port to run.
Thanks.
Chloe
>
> Kind regards,
> Niklas
next reply other threads:[~2024-03-19 9:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 9:41 Szuying Chen [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-19 9:28 ASMedia PMP inquiry Szuying Chen
2024-03-19 9:13 Szuying Chen
2024-03-19 10:14 ` Andrey Jr. Melnikov
2024-03-19 10:22 ` Niklas Cassel
2024-03-20 19:35 ` Cryptearth
2024-03-21 23:23 ` Re[2]: " Conrad Kostecki
2024-03-22 0:00 ` Damien Le Moal
2024-04-02 18:31 ` Re[2]: " Conrad Kostecki
2024-04-02 23:21 ` Damien Le Moal
2024-04-04 9:51 ` Damien Le Moal
2024-03-18 11:32 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=20240319094144.11946-1-Chloe_Chen@asmedia.com.tw \
--to=chensiying21@gmail.com \
--cc=Chloe_Chen@asmedia.com.tw \
--cc=Jesse1_Chang@asmedia.com.tw \
--cc=Richard_Hsu@asmedia.com.tw \
--cc=cassel@kernel.org \
--cc=conikost@gentoo.org \
--cc=cryptearth@googlemail.com \
--cc=dlemoal@kernel.org \
--cc=hdegoede@redhat.com \
--cc=jnyb.de@gmail.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).