V5:
as per comment, patch 05/14 in V4, was divided into 2 patches in V5
V4:
fixed DOS EOL symbols in 2 new files
V3:
Due to comments in V2
Removed change 02/17 of V2
Removed change 03/17 of V2
Removed change 17/17 of V2
V2:
This series should be pushed on top of 15 patches series:
"Big fixes, r
Currently when we try to put the link in off/disabled state during
suspend, it seems link is not being kept in low power mode.
This patch fixes the issue by putting the link in hibern8 first
(so device also puts the link in low power mode) and then stop the
host controller.
Signed-off-by: Subhash
Some UFS devices (and may be host) have issues if LCC is
enabled. So we are setting PA_Local_TX_LCC_Enable to 0
before link startup which will make sure that both host
and device TX LCC are disabled once link startup is
completed.
This change also:
- enables the device ref clock before changing to
We put the UFS device in sleep state & UFS link in hibern8 state during
runtime suspaned. After this we put all the UFS rails in low power
modes immediately but it seems some devices may still draw more than
sleep current from UFS rails (especially from VCCQ rail) atleast for
500us.
To avoid this s
Optimal values of local UniPro parameters like PA_Hibern8Time &
PA_TActivate can help reduce the hibern8 exit latency. If both host and
device supports UniPro ver1.6 or later, these parameters will be
automatically tuned during link startup itself. But if either host or
device doesn't support UniPr
UFS driver's error handler forcefully tries to clear all the pending
requests. For each pending request in the queue, it waits 1 sec for it
to get cleared. If we have multiple requests in the queue then it's
possible that we might end up waiting for those many seconds before
resetting the host. But
Some vendor's UFS device sends back to back NACs for the DL data frames
causing the host controller to raise the DFES error status. Sometimes
such UFS devices send back to back NAC without waiting for new
retransmitted DL frame from the host and in such cases it might be
possible the Host UniPro go
Query commands have 100ms timeout and it may timeout if they are
issued in parallel to ongoing read/write SCSI commands, this change
adds the retry (max: 10) in case command timeouts.
Signed-off-by: Subhash Jadavani
Signed-off-by: Yaniv Gardi
---
drivers/scsi/ufs/ufshcd.c | 55
We are seeing that some devices are raising the urgent bkops exception
events even when BKOPS status doesn't indicate performace impacted or
critical. Handle these device by determining their urgent bkops status
at runtime.
Signed-off-by: Subhash Jadavani
Signed-off-by: Yaniv Gardi
---
drivers
Currently we use the host quirks mechanism in order to
handle both device and host controller quirks.
In order to support various of UFS devices we should separate
handling the device quirks from the host controller's.
Reviewed-by: Gilad Broner
Signed-off-by: Raviv Shvili
Signed-off-by: Yaniv Ga
This change adds support to read device descriptor and string descriptor
from a UFS device
Reviewed-by: Gilad Broner
Signed-off-by: Raviv Shvili
Signed-off-by: Yaniv Gardi
---
drivers/scsi/ufs/ufs.h| 1 +
drivers/scsi/ufs/ufshcd.c | 88 ++-
dri
Sometimes due to hw issues it takes some time to the
host controller register to update. In order to verify the register
has updated, a polling is done until its value is set.
In addition the functions ufshcd_hba_stop() and
ufshcd_wait_for_register() was updated with an additional input
parameter,
Some UFS devices don't require VCCQ rail for device operations hence
this change adds support to recognize such devices and remove vote for
the unused VCCQ rail.
Signed-off-by: Subhash Jadavani
Signed-off-by: Yaniv Gardi
---
drivers/scsi/ufs/ufs.h| 1 +
drivers/scsi/ufs/ufshcd.c | 60
A race condition exists between request requeueing and scsi layer
error handling:
When UFS driver queuecommand returns a busy status for a request,
it will be requeued and its tag will be freed and set to -1.
At the same time it is possible that the request will timeout and
scsi layer will start er
When control reaches to Linux UFS driver during UFS boot mode, UFS host
controller interrupt status/enable registers may have left over
settings.
In order to avoid any spurious interrupts due to these left overs,
it's important to clear these interrupt status/enable registers before
enabling UFS in
>> Currently we use the host quirks mechanism in order to
>> handle both device and host controller quirks.
>> In order to support various of UFS devices we should separate
>> handling the device quirks from the host controller's.
>>
>> Reviewed-by: Gilad Broner
>> Signed-off-by: Raviv Shvili
>>
Different platform may have different number of lanes
for the UFS link.
Add parameter to device tree specifying how many lanes
should be configured for the UFS link.
Signed-off-by: Gilad Broner
Signed-off-by: Yaniv Gardi
---
.../devicetree/bindings/ufs/ufshcd-pltfrm.txt | 3 ++
drivers/s
Hi,
to solve the long standing problems when reading the end of TAO CD
data tracks, i propose to perform a test READ(10) of the last 2 blocks
on any data CD, before believing in the readable size as deduced from
the reply of READ CAPACITY.
Please instruct me if i have to re-submit this issue some
I was still hoping we'd get your slicing patches in ASAP at least.
But there are couple more topics here, so I think it would
still be useful in that case.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo
On 02/29/2016 12:13 AM, Christoph Hellwig wrote:
> I was still hoping we'd get your slicing patches in ASAP at least.
> But there are couple more topics here, so I think it would
> still be useful in that case.
>
Actually I have been pondering an alternative approach.
In most cases submit_bio() /
>On Wed 24-02-16 01:53:24, Damien Le Moal wrote:
>>
>> >On Tue 23-02-16 05:31:13, Damien Le Moal wrote:
>> >>
>> >> >On 02/22/16 18:56, Damien Le Moal wrote:
>> >> >> 2) Write back of dirty pages to SMR block devices:
>> >> >>
>> >> >> Dirty pages of a block device inode are currently processed
https://bugzilla.kernel.org/show_bug.cgi?id=112241
--- Comment #1 from Anthony ---
Created attachment 206351
--> https://bugzilla.kernel.org/attachment.cgi?id=206351&action=edit
Screenshot with call trace for kernel 4.5.0
--
You are receiving this mail because:
You are watching the assignee o
https://bugzilla.kernel.org/show_bug.cgi?id=112241
Anthony changed:
What|Removed |Added
Kernel Version|4.3.3 |4.5.0
--- Comment #2 from Anthony ---
With ke
On 02/29/2016 10:02 AM, Damien Le Moal wrote:
>
>> On Wed 24-02-16 01:53:24, Damien Le Moal wrote:
>>>
On Tue 23-02-16 05:31:13, Damien Le Moal wrote:
>
>> On 02/22/16 18:56, Damien Le Moal wrote:
>>> 2) Write back of dirty pages to SMR block devices:
>>>
>>> Dirty pages o
>On 02/29/2016 10:02 AM, Damien Le Moal wrote:
>>
>>> On Wed 24-02-16 01:53:24, Damien Le Moal wrote:
> On Tue 23-02-16 05:31:13, Damien Le Moal wrote:
>>
>>> On 02/22/16 18:56, Damien Le Moal wrote:
2) Write back of dirty pages to SMR block devices:
Di
25 matches
Mail list logo
