From: John Garry <john.garry@huawei.com>
To: <jejb@linux.vnet.ibm.com>, <martin.petersen@oracle.com>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>
Cc: <linux-scsi@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linuxarm@huawei.com>, <linux-kernel@vger.kernel.org>,
John Garry <john.garry@huawei.com>
Subject: [PATCH 0/8] hisi_sas: support x6000 board and some misc changes
Date: Tue, 20 Feb 2018 03:13:23 +0800 [thread overview]
Message-ID: <1519067611-206638-1-git-send-email-john.garry@huawei.com> (raw)
This patchset primarily adds support for the Huawei x6000 board,
which includes hip07 chipset. Unfortunately, due to some board
layout differences with our development board, we need to set
a PHY-related register differently for optimal signal quality. As
such, a signal attenuation property is added to describe the
differences in the boards and allow the PHY register to be set
appropriately.
In addition to this above feature, some misc changes are added for:
- PHY linkrate sysfs interface
- linkrate set function
- internal abort timer timeout increase
Xiang Chen (2):
scsi: hisi_sas: remove unused variable hisi_sas_devices.running_req
scsi: hisi_sas: Code cleanup and minor bug fixes
Xiaofei Tan (6):
dt-bindings: scsi: hisi_sas: add an property of signal attenuation
scsi: hisi_sas: support the property of signal attenuation for v2 hw
scsi: hisi_sas: fix the issue of link rate inconsistency
scsi: hisi_sas: fix the issue of setting linkrate register
scsi: hisi_sas: increase timer expire of internal abort task
scsi: hisi_sas: fix return value of hisi_sas_task_prep()
.../devicetree/bindings/scsi/hisilicon-sas.txt | 7 +++
drivers/scsi/hisi_sas/hisi_sas.h | 1 -
drivers/scsi/hisi_sas/hisi_sas_main.c | 34 +++++-------
drivers/scsi/hisi_sas/hisi_sas_v1_hw.c | 13 +++--
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 62 +++++++++++++++++-----
drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 34 +++++-------
6 files changed, 88 insertions(+), 63 deletions(-)
--
1.9.1
next reply other threads:[~2018-02-19 18:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 19:13 John Garry [this message]
2018-02-19 19:13 ` [PATCH 1/8] dt-bindings: scsi: hisi_sas: add an property of signal attenuation John Garry
2018-02-23 1:49 ` Martin K. Petersen
2018-03-01 21:40 ` Rob Herring
2018-03-02 9:36 ` John Garry
2018-02-19 19:13 ` [PATCH 2/8] scsi: hisi_sas: support the property of signal attenuation for v2 hw John Garry
2018-02-19 19:13 ` [PATCH 3/8] scsi: hisi_sas: fix the issue of link rate inconsistency John Garry
2018-02-19 19:13 ` [PATCH 4/8] scsi: hisi_sas: fix the issue of setting linkrate register John Garry
2018-02-19 19:13 ` [PATCH 5/8] scsi: hisi_sas: increase timer expire of internal abort task John Garry
2018-02-19 19:13 ` [PATCH 6/8] scsi: hisi_sas: remove unused variable hisi_sas_devices.running_req John Garry
2018-02-19 19:13 ` [PATCH 7/8] scsi: hisi_sas: fix return value of hisi_sas_task_prep() John Garry
2018-02-19 19:13 ` [PATCH 8/8] scsi: hisi_sas: Code cleanup and minor bug fixes 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=1519067611-206638-1-git-send-email-john.garry@huawei.com \
--to=john.garry@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=martin.petersen@oracle.com \
--cc=robh+dt@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).