Add definition for UFS phy type.
Signed-off-by: Vivek Gautam
---
include/dt-bindings/phy/phy.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/dt-bindings/phy/phy.h b/include/dt-bindings/phy/phy.h
index 6c901930eb3e..d16e8755f6a9 100644
--- a/include/dt-bindings/phy/phy.h
+++ b/inclu
UFS phy has two modes for each High speed generation.
These modes are identified by two rates of operations -
Rate A, and Rate B.
Add these UFS phy modes to phy framework.
Signed-off-by: Vivek Gautam
---
include/linux/phy/phy.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/
Set the phy mode based on the UFS HS PA mode. This lets the
controller let phy know the mode in which the PHY Adapter is
running and set the phy rates accordingly.
Signed-off-by: Vivek Gautam
---
drivers/scsi/ufs/ufs-qcom.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/scsi/ufs/
Adding support to set desired UFS phy mode that can be set
from the host controller.
Signed-off-by: Vivek Gautam
---
drivers/phy/qualcomm/phy-qcom-ufs-i.h| 2 ++
drivers/phy/qualcomm/phy-qcom-ufs-qmp-14nm.c | 14 ++
drivers/phy/qualcomm/phy-qcom-ufs-qmp-20nm.c | 14 +
Refactor ufs_qcom_power_up_sequence() to get rid of ugly
exported phy APIs and use the phy_init() and phy_power_on()
to do the phy initialization.
Signed-off-by: Vivek Gautam
---
drivers/phy/qualcomm/phy-qcom-ufs-i.h| 2 --
drivers/phy/qualcomm/phy-qcom-ufs-qmp-14nm.c | 9 +--
driv
Refactoring the qcom-ufs phy and host controller code to move
further towards the generic phy usage. Right now the qcom-ufs exports
a bunch of APIs that are used by the host controller to initialize
the phy.
With this patch series, we populate the phy_init() which was a no-op
earlier. The host cont
ALUA is only relevant for disk-like devices, so we shouldn't
be printing out warning messages for other device types.
Signed-off-by: Hannes Reinecke
---
drivers/scsi/device_handler/scsi_dh_alua.c | 2 ++
drivers/scsi/scsi_dh.c | 5 +++--
drivers/scsi/scsi_sysfs.c
This patch improves readability. There are no functional changes.
Since this touches on a questionable ESP_INTR_DC conditional, add some
commentary to help others who may (as I did) find themselves chasing an
"Invalid Command" error after the device flags this condition.
This cleanup also elimina
If an LLD aborts a task set, it should complete the affected commands
with the appropriate result code. In a couple of cases esp_scsi doesn't
do so.
When the initiator receives an unhandled message, just respond by sending
a MESSAGE REJECT instead of ABORT TASK SET, and thus avoid the issue.
OTOH
After sending a message, always clear esp->msg_out_len. Otherwise,
eh_abort_handler may subsequently fail to send an ABORT TASK SET
message.
Tested-by: Stan Johnson
Signed-off-by: Finn Thain
---
drivers/scsi/esp_scsi.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/scsi/esp_scsi.
Avoid the following warning from "make C=1":
CHECK drivers/scsi/mac_esp.c
drivers/scsi/mac_esp.c:357:30: warning: incorrect type in initializer
(different address spaces)
drivers/scsi/mac_esp.c:357:30:expected unsigned char [usertype] *fifo
drivers/scsi/mac_esp.c:357:30:got void [node
When in MESSAGE IN phase, the ESP device does not automatically
acknowledge each byte that is transferred by PIO. The mac_esp driver
neglects to explicitly ack them, which causes a timeout during messages
larger than one byte (e.g. tag bytes during reconnect). Fix this with an
ESP_CMD_MOK command a
This series has been tested on m68k Macs (ESP236 equivalent).
Some more testing with different targets and devices (FAS236 etc)
might be nice. Being that the esp_scsi fixes are on error paths,
more review may actually be more valuable than more testing...
Finn Thain (5):
scsi/mac_esp: Avoid ty
We terminate the aac_get_name_resp on a byte that is outside the bounds of
the structure. Extend the return response by one byte to remove the
appearance of out of bounds reference.
Thank you Dan for reporting the issue.
Thank you Bart Van Assche for suggesting the
FIELD_SIZEOF macro.
Fixes: b83
ahc_platform_dump_card_state() does nothing. Remove it.
Signed-off-by: Michał Mirosław
---
drivers/scsi/aic7xxx/aic7xxx_core.c | 1 -
drivers/scsi/aic7xxx/aic7xxx_osm.c | 5 -
drivers/scsi/aic7xxx/aic7xxx_osm.h | 1 -
3 files changed, 7 deletions(-)
diff --git a/drivers/scsi/aic7xxx/aic7
Current code is not SMP-friendly and since now each printk() call
generates a separate line in the log, the output is mostly unreadable.
Make it better formatted.
Signed-off-by: Michał Mirosław
---
drivers/scsi/Kconfig | 3 +-
drivers/scsi/aic7xxx/Kconfig
This series aims to clean up printing of card state after a problem event.
Currently, the output is pretty much unreadable, as it is spread over a lot
of single-word lines.
This series compiles (on x86), but is not tested, yet.
v2: rebased after 516b7db593 ("scsi: aic7xxx: fix firmware build with
Regenerate firmware files to make cleaner base for following fix.
This removes some unused definitions and reorders some #defines, but
the code remains the same.
Signed-off-by: Michał Mirosław
---
drivers/scsi/aic7xxx/aic79xx_reg.h_shipped | 1267 --
drivers/scsi/aic7xx
There are Kbuild rules for that already.
Signed-off-by: Michał Mirosław
---
drivers/scsi/aic7xxx/Makefile | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/scsi/aic7xxx/Makefile b/drivers/scsi/aic7xxx/Makefile
index b03ba0df7a83..1a5509d40f8a 100644
--- a/drivers/scsi/aic7xxx/Makefi
We need to override Kbuild rules for copying shipped files, otherwise
aic7xxx_reg.h and aic7xxx_reg_print.c will be ovewritten by old versions.
Fixes: 516b7db593f3a541e2e98867575c3c697f41a247
Signed-off-by: Michał Mirosław
---
drivers/scsi/aic7xxx/Makefile | 6 --
1 file changed, 4 insertion
One of the two scsi-mq functions that requeue a request unprepares
a request before requeueing (scsi_io_completion()) but the other
function not (__scsi_queue_insert()). Make sure that a request is
unprepared before requeuing it.
Fixes: commit d285203cf647 ("scsi: add support for a blk-mq based I/
On Thu, Aug 03, 2017 at 12:34:51PM -0700, Nick Desaulniers wrote:
> > Why no one on the to: line?
>
> I usually cc everyone from get_maintainer.pl. Should I be using
> --to= then explicitly for named folks, and --cc= for lists?
That's usually a good idea, many email clients throw away stuff if th
> Why no one on the to: line?
I usually cc everyone from get_maintainer.pl. Should I be using
--to= then explicitly for named folks, and --cc= for lists?
> And do you want this in the stable kernel trees?
Looks like I can follow up on option #2 once this patch has
been reviewed+merged by maintai
On Thu, Aug 03, 2017 at 12:02:47PM -0700, Nick Desaulniers wrote:
> From: Robb Glasser
>
> sg_ioctl could be spammed by requests, leading to a double free in
> __free_pages. This protects the entry points of sg_ioctl where the
> memory could be corrupted by a double call to __free_pages if multip
From: Robb Glasser
sg_ioctl could be spammed by requests, leading to a double free in
__free_pages. This protects the entry points of sg_ioctl where the
memory could be corrupted by a double call to __free_pages if multiple
requests are happening concurrently.
Signed-off-by: Robb Glasser
Signed
Dear Linux folks,
Since the merge windows opened for Linux 4.13, I am unable to resume
from ACPI S3 suspend on a Lenovo X60t. The graphics comes back, but I am
unable to enter anything, and the system seems to be hung. Magic SysRq
keys still work though, but powering the system of doesn’t wor
On 08/01/2017 03:09 PM, Dan Carpenter wrote:
> Calling list_del() on the iterator pointer in list_for_each_entry() will
> cause an oops. We need to user the _safe() version for that.
>
> Fixes: c73d02f63c16 ("tcmu: Add fifo type waiter list support to avoid
> starvation")
> Signed-off-by: Dan Ca
On Thu, 2017-08-03 at 11:13 +0800, Ming Lei wrote:
> On Thu, Aug 03, 2017 at 01:35:29AM +, Bart Van Assche wrote:
> > On Wed, 2017-08-02 at 11:31 +0800, Ming Lei wrote:
> > > On Tue, Aug 01, 2017 at 03:11:42PM +, Bart Van Assche wrote:
> > > > On Tue, 2017-08-01 at 18:50 +0800, Ming Lei wro
James Smart writes:
> From: Dick Kennedy
>
> Null pointer dereference in lpfc_sli4_fof_intr_handler
>
> The driver does not set up cq->assoc_qp for sli4_hba->oas_cq
>
> Initialize cq->assoc_qp before accessing it
>
> Signed-off-by: Dick Kennedy
> Signed-off-by: James Smart
> ---
> drivers/scs
On Thu, Aug 3, 2017 at 12:10 PM, Hannes Reinecke wrote:
> On 07/14/2017 03:22 PM, Suganath Prabu S wrote:
>> After Controller reset, Scan and add nvme device back to the topology.
>>
>> Signed-off-by: Chaitra P B
>> Signed-off-by: Suganath Prabu S
>> ---
>> drivers/scsi/mpt3sas/mpt3sas_scsih.c
On Thu, Aug 3, 2017 at 11:57 AM, Hannes Reinecke wrote:
> On 07/14/2017 03:22 PM, Suganath Prabu S wrote:
>> 1) Added support for probing pcie device and adding NVMe drives to
>> SML and driver's internal list pcie_device_list.
>>
>> 2) Added support for determing NVMe as boot device.
>>
>> 3) Add
On Thu, Aug 3, 2017 at 12:09 PM, Hannes Reinecke wrote:
> On 07/14/2017 03:22 PM, Suganath Prabu S wrote:
>> Sets nvme device queue depth, name and displays device capabilities
>>
>> Signed-off-by: Chaitra P B
>> Signed-off-by: Suganath Prabu S
>> ---
>> drivers/scsi/mpt3sas/mpt3sas_base.h |
On Thu, Aug 3, 2017 at 1:25 PM, Johannes Thumshirn wrote:
> On Thu, Aug 03, 2017 at 08:24:59AM +0200, Hannes Reinecke wrote:
>> > + U32
>> > + IOCLogInfo; /*0x10 */
>> > + U16
>> > + ErrorResponseCount; /*0x14 */
>> > + U16
>> > +
On Thu, Aug 03, 2017 at 08:24:59AM +0200, Hannes Reinecke wrote:
> > + U32
> > + IOCLogInfo; /*0x10 */
> > + U16
> > + ErrorResponseCount; /*0x14 */
> > + U16
> > + Reserved4; /*0x16 */
> > +} MPI26_NVME_ENCAPS
34 matches
Mail list logo
