Re: [PATCH 1/7] scsi: ufs: amend the ocs handling with fatal error

2013-08-13 Thread Subhash Jadavani
On 8/13/2013 5:20 PM, Seungwon Jeon wrote: On Mon, August 12, 2013, Subhash Jadavani wrote: On 7/30/2013 6:32 PM, Seungwon Jeon wrote: On Mon, July 29, 2013, Sujit Reddy Thumma wrote: On 7/29/2013 11:47 AM, Subhash Jadavani wrote: On 7/26/2013 7:15 PM, Seungwon Jeon wrote: Fatal error in OCS

RE: [PATCH 1/7] scsi: ufs: amend the ocs handling with fatal error

2013-08-13 Thread Seungwon Jeon
On Mon, August 12, 2013, Subhash Jadavani wrote: > On 7/30/2013 6:32 PM, Seungwon Jeon wrote: > > On Mon, July 29, 2013, Sujit Reddy Thumma wrote: > >> On 7/29/2013 11:47 AM, Subhash Jadavani wrote: > >>> On 7/26/2013 7:15 PM, Seungwon Jeon wrote: > Fatal error in OCS(overall command status) f

Re: [PATCH 1/7] scsi: ufs: amend the ocs handling with fatal error

2013-08-12 Thread Subhash Jadavani
On 7/30/2013 6:32 PM, Seungwon Jeon wrote: On Mon, July 29, 2013, Sujit Reddy Thumma wrote: On 7/29/2013 11:47 AM, Subhash Jadavani wrote: On 7/26/2013 7:15 PM, Seungwon Jeon wrote: Fatal error in OCS(overall command status) field indicates error conditions which is not covered by UFSHCI. It m

RE: [PATCH 1/7] scsi: ufs: amend the ocs handling with fatal error

2013-07-30 Thread Seungwon Jeon
On Mon, July 29, 2013, Sujit Reddy Thumma wrote: > On 7/29/2013 11:47 AM, Subhash Jadavani wrote: > > On 7/26/2013 7:15 PM, Seungwon Jeon wrote: > >> Fatal error in OCS(overall command status) field indicates > >> error conditions which is not covered by UFSHCI. > >> It means that host cannot defin

Re: [PATCH 1/7] scsi: ufs: amend the ocs handling with fatal error

2013-07-29 Thread Santosh Y
On Fri, Jul 26, 2013 at 7:15 PM, Seungwon Jeon wrote: > Fatal error in OCS(overall command status) field indicates > error conditions which is not covered by UFSHCI. > It means that host cannot define the result of command status > and therefore host may need to check transfer response UPIU's > re

Re: [PATCH 1/7] scsi: ufs: amend the ocs handling with fatal error

2013-07-29 Thread Sujit Reddy Thumma
On 7/29/2013 11:47 AM, Subhash Jadavani wrote: On 7/26/2013 7:15 PM, Seungwon Jeon wrote: Fatal error in OCS(overall command status) field indicates error conditions which is not covered by UFSHCI. It means that host cannot define the result of command status and therefore host may need to check

Re: [PATCH 1/7] scsi: ufs: amend the ocs handling with fatal error

2013-07-29 Thread Subhash Jadavani
On 7/29/2013 3:35 PM, Seungwon Jeon wrote: On Mon, July 29, 2013, Subhash Jadavani wrote: On 7/26/2013 7:15 PM, Seungwon Jeon wrote: Fatal error in OCS(overall command status) field indicates error conditions which is not covered by UFSHCI. It means that host cannot define the result of command

RE: [PATCH 1/7] scsi: ufs: amend the ocs handling with fatal error

2013-07-29 Thread Seungwon Jeon
On Mon, July 29, 2013, Subhash Jadavani wrote: > On 7/26/2013 7:15 PM, Seungwon Jeon wrote: > > Fatal error in OCS(overall command status) field indicates > > error conditions which is not covered by UFSHCI. > > It means that host cannot define the result of command status > > and therefore host ma

Re: [PATCH 1/7] scsi: ufs: amend the ocs handling with fatal error

2013-07-28 Thread Subhash Jadavani
On 7/26/2013 7:15 PM, Seungwon Jeon wrote: Fatal error in OCS(overall command status) field indicates error conditions which is not covered by UFSHCI. It means that host cannot define the result of command status and therefore host may need to check transfer response UPIU's response and status fi

[PATCH 1/7] scsi: ufs: amend the ocs handling with fatal error

2013-07-26 Thread Seungwon Jeon
Fatal error in OCS(overall command status) field indicates error conditions which is not covered by UFSHCI. It means that host cannot define the result of command status and therefore host may need to check transfer response UPIU's response and status field. It was actually found that 'CHECK CONDIT