Hi Damien,
On Wed, 27 Oct 2021, Damien Le Moal wrote:
Add support to discover if an ATA device supports the Concurrent
Positioning Ranges data log (address 0x47), indicating that the device
is capable of seeking to multiple different locations in parallel using
multiple actuators serving different LBA ranges.
Also add support to translate the concurrent positioning ranges log
into its equivalent Concurrent Positioning Ranges VPD page B9h in
libata-scsi.c.
The format of the Concurrent Positioning Ranges Log is defined in ACS-5
r9.
Signed-off-by: Damien Le Moal <damien.lemoal@xxxxxxx>
Thanks for your patch, which is now commit fe22e1c2f705676a ("libata:
support concurrent positioning ranges log") upstream.
During resume from s2ram on Renesas Salvator-XS, I now see more scary
messages than before:
ata1: link resume succeeded after 1 retries
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
+ata1.00: qc timeout (cmd 0x2f)
+ata1.00: Read log page 0x00 failed, Emask 0x4
+ata1.00: ATA Identify Device Log not supported
+ata1.00: failed to set xfermode (err_mask=0x40)
ata1: link resume succeeded after 1 retries
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
+ata1.00: ATA Identify Device Log not supported
+ata1.00: ATA Identify Device Log not supported
ata1.00: configured for UDMA/133
I guess this is expected?
The hard drive (old Maxtor 6L160M0 that received a third life as a test
bed for Renesas SATA regression testing) seems to still work fine.
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
