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 2/2] scsi: ufs: core: reflect function execution result in return
Date: Tue, 15 Oct 2024 11:13:43 -0700 [thread overview]
Message-ID: <420692d5-d968-4e47-9eaf-14d574b62593@acm.org> (raw)
In-Reply-To: <300052382d9d03bf087d71201bd159805b8fd041.1728544727.git.hy50.seo@samsung.com>
On 10/10/24 12:52 AM, SEO HOYOUNG wrote:
> If an error is returned in the power mode function, it is returned and
> modified to cause failure in the UFS linkup.
> If it is an asymmetric connected lane, the UFS init can fail because it is
> an incorrect situation.
Why is this an incorrect situation? If ufshcd_get_max_pwr_mode() fails,
won't communication succeed with a lower power mode than maximum power?
Thanks,
Bart.
next prev parent reply other threads:[~2024-10-15 18:14 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 asymmetric connected lanes 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
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 [this message]
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=420692d5-d968-4e47-9eaf-14d574b62593@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®