Hi Damien, On Tue, Mar 26, 2024 at 11:07 AM Damien Le Moal <dlemoal@xxxxxxxxxx> wrote: > On 3/26/24 18:53, Geert Uytterhoeven wrote: > > On Thu, Mar 7, 2024 at 10:55 PM Igor Pylypiv <ipylypiv@xxxxxxxxxx> wrote: > >> Libata sysfs attributes cannot be used for libsas managed SATA devices > >> because the ata_port location is different for libsas. > >> > >> Defined sysfs attributes (visible for SATA devices only): > >> - /sys/block/sda/device/ncq_prio_enable > >> - /sys/block/sda/device/ncq_prio_supported > >> > >> The newly defined attributes will pass the correct ata_port to libata > >> helper functions. > >> > >> Reviewed-by: John Garry <john.g.garry@xxxxxxxxxx> > >> Reviewed-by: Damien Le Moal <dlemoal@xxxxxxxxxx> > >> Reviewed-by: Jason Yan <yanaijie@xxxxxxxxxx> > >> Signed-off-by: Igor Pylypiv <ipylypiv@xxxxxxxxxx> > > > > Thanks for your patch, which is now commit b4d3ddd2df7531e3 ("scsi: > > libsas: Define NCQ Priority sysfs attributes for SATA devices") > > in scsi-mkp/for-next > > > >> --- a/drivers/scsi/libsas/sas_ata.c > >> +++ b/drivers/scsi/libsas/sas_ata.c > > > >> + > >> +DEVICE_ATTR(ncq_prio_supported, S_IRUGO, sas_ncq_prio_supported_show, NULL); > >> + > > > > [...] > > > >> + > >> +DEVICE_ATTR(ncq_prio_enable, S_IRUGO | S_IWUSR, > >> + sas_ncq_prio_enable_show, sas_ncq_prio_enable_store); > >> + > > > > When both CONFIG_SCSI_SAS_ATA and CONFIG_SATA_HOST are enabled: > > I have both enabled in my config and I do not see any issue. What is special > with these on ARM ? Modular or built-in? I have them built-in, and it fails on arm64 (with renesas_defconfig, which is not upstream). It also fails with shmobile_defconfig on arm32, after manually adding CONFIG_SCSI_SAS_LIBSAS=y and CONFIG_SCSI_SAS_ATA=y. 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