scsi: hisi_sas: dt-bindings: add an property of signal attenuationFor some new boards with hip07 chipset we are required to set PHY configregisters differently. The hw property which determines ho
scsi: hisi_sas: dt-bindings: add an property of signal attenuationFor some new boards with hip07 chipset we are required to set PHY configregisters differently. The hw property which determines how to set theseregisters is in the PHY signal attenuation readings.This patch add an devicetree property, "hisilicon,signal-attenuation", whichis used to describe the signal attenuation of an board.Cc: Rob Herring <robh+dt@kernel.org>Cc: Mark Rutland <mark.rutland@arm.com>Signed-off-by: Xiaofei Tan <tanxiaofei@huawei.com>Signed-off-by: John Garry <john.garry@huawei.com>Reviewed-by: Rob Herring <robh@kernel.org>Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
show more ...
scsi: hisi_sas: devicetree: bindings: add LED feature for v2 hwAdd directly attached disk LED feature for v2 hw.Signed-off-by: Xiaofei Tan <tanxiaofei@huawei.com>Signed-off-by: John Garry <john.
scsi: hisi_sas: devicetree: bindings: add LED feature for v2 hwAdd directly attached disk LED feature for v2 hw.Signed-off-by: Xiaofei Tan <tanxiaofei@huawei.com>Signed-off-by: John Garry <john.garry@huawei.com>Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
dt-bindings: Remove "status" from examplesPretty much any node can have a status property, so it doesn't need tobe in examples.Converted with the following command and removed examples with SoC
dt-bindings: Remove "status" from examplesPretty much any node can have a status property, so it doesn't need tobe in examples.Converted with the following command and removed examples with SoC andboard specific splits:git grep -l -E 'status.*=.*' Documentation/devicetree/ | xargs sed -i -E '/\sstatus.*=.*"(disabled|ok|okay)/d'Acked-by: Mark Rutland <mark.rutland@arm.com>Signed-off-by: Rob Herring <robh@kernel.org>
scsi: devicetree: bindings: hisi_sas: add hip07 supportAdd support for hip07 chipset to hisi_sas controller.Chipset hip07 has v2 hw.Signed-off-by: John Garry <john.garry@huawei.com>Signed-off-
scsi: devicetree: bindings: hisi_sas: add hip07 supportAdd support for hip07 chipset to hisi_sas controller.Chipset hip07 has v2 hw.Signed-off-by: John Garry <john.garry@huawei.com>Signed-off-by: Xiang Chen <chenxiang66@hisilicon.com>Acked-by: Rob Herring <robh@kernel.org>Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
devicetree: bindings: hisi_sas: add v2 HW bindingsAdd the dt bindings for HiSi SAS controller v2 HW.The main difference in the controller from dt perspective isinterrupts. The v2 controller does
devicetree: bindings: hisi_sas: add v2 HW bindingsAdd the dt bindings for HiSi SAS controller v2 HW.The main difference in the controller from dt perspective isinterrupts. The v2 controller does not have dedicated fatal andbroadcast interrupts - they are multiplexed on the channel interrupt.Each SAS v2 controller can issue upto 64 commands (or connectionrequests) on the system bus without waiting for a response - this isknow as am-max-transmissions. In hip06, sas controller #1 has alimitation that it has to limit am-max-transmissions to 32 - thislimitation is due to chip system bus design. It is not anticipated thatany future chip incorporating v2 controller will have such a limitation.Signed-off-by: John Garry <john.garry@huawei.com>Reviewed-by: Hannes Reinecke <hare@suse.de>Acked-by: Rob Herring <robh@kernel.org>Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
devicetree: bindings: scsi: HiSi SASAdd devicetree bindings for HiSilicon SAS driver.Signed-off-by: John Garry <john.garry@huawei.com>Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>Acked-
devicetree: bindings: scsi: HiSi SASAdd devicetree bindings for HiSilicon SAS driver.Signed-off-by: John Garry <john.garry@huawei.com>Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>Acked-by: Rob Herring <robh@kernel.org>Reviewed-by: Arnd Bergmann <arnd@arndb.de>Reviewed-by: Hannes Reinecke <hare@suse.de>Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>