From: Dan Williams <dan.j.williams@intel.com>
To: JBottomley@parallels.com
Cc: linux-scsi@vger.kernel.org, jacek.danecki@intel.com
Subject: [PATCH 0/3] basic sgpio write support
Date: Thu, 01 Sep 2011 21:18:15 -0700 [thread overview]
Message-ID: <20110902041637.27608.29757.stgit@localhost6.localdomain6> (raw)
Just enough infrastructure to get raw-bitstream writes operational. With a
common decode implementation in libsas. SAS-2 support is deferred as SFF-8485
remains at v0.7 [1]. Read support and the "non-raw" tx registers are deferred
until the general approach is accepted.
For future patches it might be useful to register a 'sgpio' interface in sysfs
for all local phys to accept IBPI commands like "identify" or "fail". Although,
the driver has no way of verifying if phy0 is routed to sgpio-device0.
Until then this interface just uses the sas_host bsg device as shown in patch1.
--
Dan
[1]: http://marc.info/?l=linux-scsi&m=130693695829154&w=2
---
Dan Williams (3):
libsas: sgpio write support
isci: fix sgpio register definitions
isci: initial sgpio write support
drivers/scsi/isci/host.c | 69 ++++++++++++++++++++
drivers/scsi/isci/host.h | 15 ++++
drivers/scsi/isci/init.c | 3 +
drivers/scsi/isci/registers.h | 122 +-----------------------------------
drivers/scsi/libsas/sas_host_smp.c | 103 ++++++++++++++++++++++++++++++
include/scsi/libsas.h | 11 +++
include/scsi/sas.h | 8 ++
7 files changed, 211 insertions(+), 120 deletions(-)
next reply other threads:[~2011-09-02 4:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 4:18 Dan Williams [this message]
2011-09-02 4:18 ` [PATCH 1/3] libsas: sgpio write support Dan Williams
2011-09-02 4:18 ` [PATCH 2/3] isci: fix sgpio register definitions Dan Williams
2011-09-02 4:18 ` [PATCH 3/3] isci: initial sgpio write support Dan Williams
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=20110902041637.27608.29757.stgit@localhost6.localdomain6 \
--to=dan.j.williams@intel.com \
--cc=JBottomley@parallels.com \
--cc=jacek.danecki@intel.com \
--cc=linux-scsi@vger.kernel.org \
/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 NNTP newsgroup(s).