From: John Garry <john.garry@huawei.com>
To: <James.Bottomley@HansenPartnership.com>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<arnd@arndb.de>, <linuxarm@huawei.com>, <zhangfei.gao@linaro.org>,
<linux-scsi@vger.kernel.org>, <xuwei5@hisilicon.com>,
<john.garry2@mail.dcu.ie>, <hare@suse.de>
Subject: Re: [PATCH 00/25] HiSilicon SAS driver
Date: Mon, 19 Oct 2015 09:47:41 +0100 [thread overview]
Message-ID: <5624AE2D.9070200@huawei.com> (raw)
In-Reply-To: <1444663237-238302-1-git-send-email-john.garry@huawei.com>
Hi James,
Could we please get a review for our driver? We have got some good input
on changes we need to make, and we will produce another patchset in the
coming days. However it would good to get a subsystem maintainer
review/acknowledgement to progress our upstreaming.
Thanks in advance,
John
On 12/10/2015 16:20, John Garry wrote:
> This is the driver patchset for the HiSilicon SAS driver. The driver
> is a platform driver.
>
> The driver will support multiple revisions of HW. Currently only "v1"
> HW is supported.
>
> The driver uses libsas framework within the SCSI framework.
>
> The v1 HW supports SSP and SMP, but not STP/SATA.
>
>
> John Garry (25):
> [SCSI] sas: centralise ssp frame information units
> devicetree: bindings: scsi: HiSi SAS
> scsi: hisi_sas: add initial bare driver
> scsi: hisi_sas: add scsi host registration
> scsi: hisi_sas: allocate memories and create pools
> scsi: hisi_sas: add slot init code
> scsi: hisi_sas: add ioremap for device HW
> scsi: hisi_sas: add cq structure initialization
> scsi: hisi_sas: add phy SAS ADDR initialization
> scsi: hisi_sas: add misc HBA initialization
> scsi: hisi_sas: add v1 hardware register definitions
> scsi: hisi_sas: add v1 HW initialisation code
> scsi: hisi_sas: add path from phyup irq to SAS framework
> scsi: hisi_sas: add ssp command function
> scsi: hisi_sas: add cq interrupt handler
> scsi: hisi_sas: add dev_found and port_formed
> scsi: hisi_sas: add abnormal irq handler
> scsi: hisi_sas: add dev_gone and port_deformed
> scsi: hisi_sas: add bcast interrupt handler
> scsi: hisi_sas: add smp protocol support
> scsi: hisi_sas: add scan finished and start
> scsi: hisi_sas: add tmf methods
> scsi: hisi_sas: add control phy handler
> scsi: hisi_sas: add fatal irq handler
> MAINTAINERS: add maintainer for HiSi SAS driver
>
> .../devicetree/bindings/scsi/hisilicon-sas.txt | 63 +
> MAINTAINERS | 7 +
> drivers/scsi/Kconfig | 1 +
> drivers/scsi/Makefile | 1 +
> drivers/scsi/aic94xx/aic94xx_sas.h | 49 +-
> drivers/scsi/hisi_sas/Kconfig | 5 +
> drivers/scsi/hisi_sas/Makefile | 2 +
> drivers/scsi/hisi_sas/hisi_sas.h | 406 +++++
> drivers/scsi/hisi_sas/hisi_sas_init.c | 489 ++++++
> drivers/scsi/hisi_sas/hisi_sas_main.c | 1115 ++++++++++++
> drivers/scsi/hisi_sas/hisi_sas_v1_hw.c | 1850 ++++++++++++++++++++
> include/scsi/sas.h | 74 +
> 12 files changed, 4019 insertions(+), 43 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/scsi/hisilicon-sas.txt
> create mode 100644 drivers/scsi/hisi_sas/Kconfig
> create mode 100644 drivers/scsi/hisi_sas/Makefile
> create mode 100644 drivers/scsi/hisi_sas/hisi_sas.h
> create mode 100644 drivers/scsi/hisi_sas/hisi_sas_init.c
> create mode 100644 drivers/scsi/hisi_sas/hisi_sas_main.c
> create mode 100644 drivers/scsi/hisi_sas/hisi_sas_v1_hw.c
>
next prev parent reply other threads:[~2015-10-19 8:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1444663237-238302-1-git-send-email-john.garry@huawei.com>
[not found] ` <1444663237-238302-6-git-send-email-john.garry@huawei.com>
2015-10-12 15:15 ` [PATCH 05/25] scsi: hisi_sas: allocate memories and create pools Arnd Bergmann
2015-10-13 9:42 ` zhangfei
[not found] ` <1444663237-238302-5-git-send-email-john.garry@huawei.com>
2015-10-12 15:21 ` [PATCH 04/25] scsi: hisi_sas: add scsi host registration Arnd Bergmann
2015-10-13 9:16 ` John Garry
2015-10-13 12:18 ` Arnd Bergmann
[not found] ` <1444663237-238302-8-git-send-email-john.garry@huawei.com>
2015-10-12 15:21 ` [PATCH 07/25] scsi: hisi_sas: add ioremap for device HW Arnd Bergmann
2015-10-13 9:47 ` zhangfei
2015-10-13 12:20 ` Arnd Bergmann
2015-10-13 15:09 ` zhangfei
[not found] ` <1444663237-238302-13-git-send-email-john.garry@huawei.com>
2015-10-12 18:46 ` [PATCH 12/25] scsi: hisi_sas: add v1 HW initialisation code Arnd Bergmann
2015-10-13 12:44 ` John Garry
2015-10-13 12:47 ` Arnd Bergmann
[not found] ` <1444663237-238302-14-git-send-email-john.garry@huawei.com>
2015-10-16 12:55 ` [PATCH 13/25] scsi: hisi_sas: add path from phyup irq to SAS framework Arnd Bergmann
2015-10-16 13:29 ` John Garry
2015-10-16 13:36 ` Arnd Bergmann
2015-10-19 14:11 ` John Garry
2015-10-19 14:26 ` Arnd Bergmann
2015-10-19 14:55 ` John Garry
2015-10-20 8:40 ` Arnd Bergmann
2015-10-20 9:09 ` John Garry
2015-10-19 8:47 ` John Garry [this message]
2015-10-19 8:55 ` [PATCH 00/25] HiSilicon SAS driver Hannes Reinecke
2015-10-19 10:40 ` John Garry
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=5624AE2D.9070200@huawei.com \
--to=john.garry@huawei.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=hare@suse.de \
--cc=john.garry2@mail.dcu.ie \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=xuwei5@hisilicon.com \
--cc=zhangfei.gao@linaro.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).