From: John Garry <john.g.garry@oracle.com>
To: Niklas Cassel <cassel@kernel.org>
Cc: Igor Pylypiv <ipylypiv@google.com>,
Damien Le Moal <dlemoal@kernel.org>,
Jason Yan <yanaijie@huawei.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Jack Wang <jinpu.wang@cloud.ionos.com>,
Hannes Reinecke <hare@suse.de>,
Xiang Chen <chenxiang66@hisilicon.com>,
Artur Paszkiewicz <artur.paszkiewicz@intel.com>,
Bart Van Assche <bvanassche@acm.org>,
TJ Adams <tadamsjr@google.com>,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 5/7] scsi: hisi_sas: Add libsas SATA sysfs attributes group
Date: Thu, 7 Mar 2024 11:17:08 +0000 [thread overview]
Message-ID: <c1f8280b-3f8d-48ff-b5f3-40c3840f98e8@oracle.com> (raw)
In-Reply-To: <ZemQBLMcJP617WDC@ryzen>
> John, now I'm curious, do you know why hisi_sas_v1_hw.c is implemented
> as a libsas driver (instead of a regular SCSI driver), if it doesn't
> support SATA?
Using libsas is not really dependent on whether the HW supports SATA/STP
or not. It's a protocol layer thing. Considering the SAS protocol stack,
HW for drivers using libsas have implemented only the lower protocol
layers, and SW, i.e. libsas, is required to manage upper layers, like
Port layer and above.
BTW, IIRC, v1 hw did support SATA, but not STP, i.e. directly attached
SATA only, but the SATA support was even more broken than v2 hw (which
is quite broken), so never bothered supporting in SW.
>
> Was perhaps v2_hw and v3_hw implemented as a libsas driver first
> (since they support SATA), and v1_hw support was added later,
> so that it could reuse much of the parts of the existing driver?
v1 driver support came first.
Thanks,
John
next prev parent reply other threads:[~2024-03-07 11:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 1:22 [PATCH v7 0/7] NCQ Priority sysfs sttributes for libsas Igor Pylypiv
2024-03-06 1:22 ` [PATCH v7 1/7] ata: libata-sata: Factor out NCQ Priority configuration helpers Igor Pylypiv
2024-03-06 10:54 ` Niklas Cassel
2024-03-06 1:22 ` [PATCH v7 2/7] scsi: libsas: Define NCQ Priority sysfs attributes for SATA devices Igor Pylypiv
2024-03-06 10:54 ` Niklas Cassel
2024-03-06 19:28 ` Igor Pylypiv
2024-03-07 9:51 ` Niklas Cassel
2024-03-07 21:41 ` Igor Pylypiv
2024-03-06 1:22 ` [PATCH v7 3/7] scsi: pm80xx: Add libsas SATA sysfs attributes group Igor Pylypiv
2024-03-06 10:55 ` Niklas Cassel
2024-03-06 1:22 ` [PATCH v7 4/7] scsi: mvsas: " Igor Pylypiv
2024-03-06 10:55 ` Niklas Cassel
2024-03-06 21:13 ` Igor Pylypiv
2024-03-07 9:52 ` Niklas Cassel
2024-03-07 20:35 ` Igor Pylypiv
2024-03-06 1:22 ` [PATCH v7 5/7] scsi: hisi_sas: " Igor Pylypiv
2024-03-06 10:55 ` Niklas Cassel
2024-03-06 20:56 ` Igor Pylypiv
2024-03-07 8:55 ` John Garry
2024-03-07 9:59 ` Niklas Cassel
2024-03-07 11:17 ` John Garry [this message]
2024-03-06 1:22 ` [PATCH v7 6/7] scsi: aic94xx: " Igor Pylypiv
2024-03-06 10:55 ` Niklas Cassel
2024-03-06 21:17 ` Igor Pylypiv
2024-03-06 1:22 ` [PATCH v7 7/7] scsi: isci: " Igor Pylypiv
2024-03-06 10:55 ` Niklas Cassel
2024-03-06 10:54 ` [PATCH v7 0/7] NCQ Priority sysfs sttributes for libsas Niklas Cassel
2024-03-06 21:33 ` Igor Pylypiv
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=c1f8280b-3f8d-48ff-b5f3-40c3840f98e8@oracle.com \
--to=john.g.garry@oracle.com \
--cc=artur.paszkiewicz@intel.com \
--cc=bvanassche@acm.org \
--cc=cassel@kernel.org \
--cc=chenxiang66@hisilicon.com \
--cc=dlemoal@kernel.org \
--cc=hare@suse.de \
--cc=ipylypiv@google.com \
--cc=jejb@linux.ibm.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=tadamsjr@google.com \
--cc=yanaijie@huawei.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
all inboxes | Powered by JetHome®