From: Kiwoong Kim <kwmad.kim@samsung.com>
To: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
alim.akhtar@samsung.com, avri.altman@wdc.com, bvanassche@acm.org,
jejb@linux.ibm.com, martin.petersen@oracle.com,
beanhuo@micron.com, adrian.hunter@intel.com, h10.kim@samsung.com,
hy50.seo@samsung.com, sh425.lee@samsung.com,
kwangwon.min@samsung.com, junwoo80.lee@samsung.com,
wkon.kim@samsung.com
Cc: Kiwoong Kim <kwmad.kim@samsung.com>
Subject: [PATCH v1 0/2] scsi: ufs: introduce a callback to override OCS value
Date: Wed, 21 Aug 2024 15:44:34 +0900 [thread overview]
Message-ID: <cover.1724222619.git.kwmad.kim@samsung.com> (raw)
In-Reply-To: CGME20240821064152epcas2p2552e92767564272fb7e172fecd7ade3e@epcas2p2.samsung.com
UFSHCI defines OCS values but doesn't specify what exact
conditions raise them. So I think it needs another callback
to replace the original OCS value with the value that works
the way you want.
Kiwoong Kim (2):
scsi: ufs: core: introduce override_cqe_ocs
scsi: ufs: ufs-exynos: implement override_cqe_ocs
drivers/ufs/core/ufshcd-priv.h | 9 +++++++++
drivers/ufs/core/ufshcd.c | 4 +++-
drivers/ufs/host/ufs-exynos.c | 9 +++++++++
include/ufs/ufshcd.h | 1 +
4 files changed, 22 insertions(+), 1 deletion(-)
--
2.7.4
next parent reply other threads:[~2024-08-21 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240821064152epcas2p2552e92767564272fb7e172fecd7ade3e@epcas2p2.samsung.com>
2024-08-21 6:44 ` Kiwoong Kim [this message]
2024-08-21 6:44 ` [PATCH v1 1/2] scsi: ufs: core: introduce override_cqe_ocs Kiwoong Kim
2024-08-22 10:38 ` kernel test robot
2024-08-21 6:44 ` [PATCH v1 2/2] scsi: ufs: ufs-exynos: implement override_cqe_ocs Kiwoong Kim
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=cover.1724222619.git.kwmad.kim@samsung.com \
--to=kwmad.kim@samsung.com \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--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=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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