[v3,0/2] processing of asymmetric connected lanes

Message ID	cover.1728544727.git.hy50.seo@samsung.com
Headers	show Received: from mailout2.samsung.com (mailout2.samsung.com [203.254.224.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 953DF1E6DD5 for <linux-scsi@vger.kernel.org>; Thu, 10 Oct 2024 07:42:26 +0000 (UTC) From: SEO HOYOUNG <hy50.seo@samsung.com> To: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, alim.akhtar@samsung.com, avri.altman@wdc.com, jejb@linux.ibm.com, martin.petersen@oracle.com, beanhuo@micron.com, bvanassche@acm.org, kwangwon.min@samsung.com, kwmad.kim@samsung.com, sh425.lee@samsung.com, quic_nguyenb@quicinc.com, cpgs@samsung.com, h10.kim@samsung.com, grant.jung@samsung.com, junwoo80.lee@samsung.com, wkon.kim@samsung.com Cc: SEO HOYOUNG <hy50.seo@samsung.com> Subject: [PATCH v3 0/2] processing of asymmetric connected lanes Date: Thu, 10 Oct 2024 16:52:27 +0900 Message-Id: <cover.1728544727.git.hy50.seo@samsung.com> Precedence: bulk MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" CMS-TYPE: 102P DLP-Filter: Pass References: <CGME20241010074222epcas2p4278413120c00584d83f654dbde6c0f49@epcas2p4.samsung.com>
Series	processing of asymmetric connected lanes \| expand [v3,0/2] processing of asymmetric connected lanes [v3,1/2] scsi: ufs: core: check asymmetric connected lanes [v3,2/2] scsi: ufs: core: reflect function execution result in return

Message ID

cover.1728544727.git.hy50.seo@samsung.com

Headers

From: SEO HOYOUNG <hy50.seo@samsung.com>
To: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	alim.akhtar@samsung.com, avri.altman@wdc.com, jejb@linux.ibm.com,
	martin.petersen@oracle.com, beanhuo@micron.com, bvanassche@acm.org,
	kwangwon.min@samsung.com, kwmad.kim@samsung.com, sh425.lee@samsung.com,
	quic_nguyenb@quicinc.com, cpgs@samsung.com, h10.kim@samsung.com,
	grant.jung@samsung.com, junwoo80.lee@samsung.com, wkon.kim@samsung.com
Cc: SEO HOYOUNG <hy50.seo@samsung.com>
Subject: [PATCH v3 0/2] processing of asymmetric connected lanes
Date: Thu, 10 Oct 2024 16:52:27 +0900
Message-Id: <cover.1728544727.git.hy50.seo@samsung.com>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="utf-8"
CMS-TYPE: 102P
DLP-Filter: Pass
References: 
 <CGME20241010074222epcas2p4278413120c00584d83f654dbde6c0f49@epcas2p4.samsung.com>

Series

processing of asymmetric connected lanes | expand

Message

SEO HOYOUNG Oct. 10, 2024, 7:52 a.m. UTC

Performance problems may occur if there is a problem with the
asymmetric connected lane such as h/w failure.
Currently, only check connected lane for rx/tx is checked if it is not 0.
But it should also be checked if it is asymmetrically connected.
So if it is an asymmetric connected lane, an error occurs.

v1 -> v2: add error routine.
ufs initialization error occurs in case of asymmetic connected

v2 -> v3: split two patches

SEO HOYOUNG (2):
  scsi: ufs: core: check asymmetric connected lanes
  scsi: ufs: core: reflect function execution result in return

 drivers/ufs/core/ufshcd.c | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

Comments

Martin K. Petersen Nov. 5, 2024, 2:32 a.m. UTC | #1

On Thu, 10 Oct 2024 16:52:27 +0900, SEO HOYOUNG wrote:

> Performance problems may occur if there is a problem with the
> asymmetric connected lane such as h/w failure.
> Currently, only check connected lane for rx/tx is checked if it is not 0.
> But it should also be checked if it is asymmetrically connected.
> So if it is an asymmetric connected lane, an error occurs.
> 
> v1 -> v2: add error routine.
> ufs initialization error occurs in case of asymmetic connected
> 
> [...]

Applied to 6.13/scsi-queue, thanks!

[1/2] scsi: ufs: core: check asymmetric connected lanes
      https://git.kernel.org/mkp/scsi/c/10c58d7eea44