From: Bart Van Assche <bvanassche@acm.org>
To: SEO HOYOUNG <hy50.seo@samsung.com>,
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,
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
Subject: Re: [PATCH v3 1/2] scsi: ufs: core: check asymmetric connected lanes
Date: Tue, 15 Oct 2024 11:16:39 -0700 [thread overview]
Message-ID: <52ed0795-c493-414c-b22b-86c90b8d89c8@acm.org> (raw)
In-Reply-To: <e82b4b65b5f6501a687c624dd06e5c362e160f32.1728544727.git.hy50.seo@samsung.com>
On 10/10/24 12:52 AM, 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.
>
> Signed-off-by: SEO HOYOUNG <hy50.seo@samsung.com>
> ---
> drivers/ufs/core/ufshcd.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/ufs/core/ufshcd.c b/drivers/ufs/core/ufshcd.c
> index 24a32e2fd75e..387eec6f19ef 100644
> --- a/drivers/ufs/core/ufshcd.c
> +++ b/drivers/ufs/core/ufshcd.c
> @@ -4540,6 +4540,14 @@ static int ufshcd_get_max_pwr_mode(struct ufs_hba *hba)
> return -EINVAL;
> }
>
> + if (pwr_info->lane_rx != pwr_info->lane_tx) {
> + dev_err(hba->dev, "%s: asymmetric connected lanes. rx=%d, tx=%d\n",
> + __func__,
> + pwr_info->lane_rx,
> + pwr_info->lane_tx);
> + return -EINVAL;
> + }
> +
> /*
> * First, get the maximum gears of HS speed.
> * If a zero value, it means there is no HSGEAR capability.
It seems to me that symmetry of the number of lanes is required by the
UFS standard? From the UFS standard: "An equal number of downstream and
upstream lanes shall be provided in each link." Hence:
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2024-10-15 18:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241010074222epcas2p4278413120c00584d83f654dbde6c0f49@epcas2p4.samsung.com>
2024-10-10 7:52 ` [PATCH v3 0/2] processing of " SEO HOYOUNG
[not found] ` <CGME20241010074229epcas2p31ecc33731a96be7958cdd93908a1ce86@epcas2p3.samsung.com>
2024-10-10 7:52 ` [PATCH v3 1/2] scsi: ufs: core: check " SEO HOYOUNG
2024-10-15 18:16 ` Bart Van Assche [this message]
2024-10-25 18:37 ` Martin K. Petersen
[not found] ` <CGME20241010074231epcas2p2d15a81d68b68d757039a56e8dd9cca3c@epcas2p2.samsung.com>
2024-10-10 7:52 ` [PATCH v3 2/2] scsi: ufs: core: reflect function execution result in return SEO HOYOUNG
2024-10-15 18:13 ` Bart Van Assche
2024-11-05 2:32 ` [PATCH v3 0/2] processing of asymmetric connected lanes Martin K. Petersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52ed0795-c493-414c-b22b-86c90b8d89c8@acm.org \
--to=bvanassche@acm.org \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=cpgs@samsung.com \
--cc=grant.jung@samsung.com \
--cc=h10.kim@samsung.com \
--cc=hy50.seo@samsung.com \
--cc=jejb@linux.ibm.com \
--cc=junwoo80.lee@samsung.com \
--cc=kwangwon.min@samsung.com \
--cc=kwmad.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=quic_nguyenb@quicinc.com \
--cc=sh425.lee@samsung.com \
--cc=wkon.kim@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®