Hello Chloe, On Tue, Mar 19, 2024 at 05:13:22PM +0800, Szuying Chen wrote: > Signed-off-by: Szuying Chen <Chloe_Chen@xxxxxxxxxxxxxx> > --- > > 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. Thank you for your reply! If you have any idea on how those users with a ASM1064 card that does not have any PMPs on the PCIe cards, e.g. Delock 90073, can avoid the extra 2-3 minutes delay during boot, we are open to suggestions. I guess you could send a new firmware to Delock that sets the PI register (Ports Implemented) register to 0xf. However, from what I've understood from how you have decided to implement PMP support on your HBAs, I assume that setting the PI register to 0xf would also stop Delock 90073 from working with an externally connected port multiplier, so that it probably not a good approach after all. Kind regards, Niklas
