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, junwoo80.lee@samsung.com,
wkon.kim@samsung.com
Subject: Re: [PATCH v2] scsi: ufs: core: check asymmetric connected lanes
Date: Tue, 8 Oct 2024 10:42:25 -0700 [thread overview]
Message-ID: <66d8938c-3bf8-49c3-b42a-e2c32f1d1338@acm.org> (raw)
In-Reply-To: <20241008063842.82769-1-hy50.seo@samsung.com>
On 10/7/24 11:38 PM, SEO HOYOUNG wrote:
> diff --git a/drivers/ufs/core/ufshcd.c b/drivers/ufs/core/ufshcd.c
> index 24a32e2fd75e..1381eb7d506a 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.
> @@ -8579,7 +8587,8 @@ static int ufshcd_device_params_init(struct ufs_hba *hba)
> hba->dev_info.f_power_on_wp_en = flag;
>
> /* Probe maximum power mode co-supported by both UFS host and device */
> - if (ufshcd_get_max_pwr_mode(hba))
> + ret = ufshcd_get_max_pwr_mode(hba);
> + if (ret)
> dev_err(hba->dev,
> "%s: Failed getting max supported power mode\n",
> __func__);
I see two independent changes in the above patch. Should this patch
perhaps be split into two patches?
Thanks,
Bart.
prev parent reply other threads:[~2024-10-08 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241008062836epcas2p2caa5c41cf8fe4d1bfe5d923633ea2618@epcas2p2.samsung.com>
2024-10-08 6:38 ` SEO HOYOUNG
2024-10-08 17:42 ` Bart Van Assche [this message]
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=66d8938c-3bf8-49c3-b42a-e2c32f1d1338@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=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®