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 v2 0/2] scsi: ufs: introduce a callback to override OCS value
Date: Thu, 22 Aug 2024 20:15:33 +0900 [thread overview]
Message-ID: <cover.1724325280.git.kwmad.kim@samsung.com> (raw)
In-Reply-To: CGME20240822111247epcas2p2d3051255f42af05fd049b7247c395da4@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.
v1 -> v2: fix build error for arguments
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 | 11 +++++++----
drivers/ufs/host/ufs-exynos.c | 8 ++++++++
include/ufs/ufshcd.h | 1 +
4 files changed, 25 insertions(+), 4 deletions(-)
--
2.7.4
next parent reply other threads:[~2024-08-22 11:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240822111247epcas2p2d3051255f42af05fd049b7247c395da4@epcas2p2.samsung.com>
2024-08-22 11:15 ` Kiwoong Kim [this message]
2024-08-22 11:15 ` [PATCH v2 1/2] scsi: ufs: core: introduce override_cqe_ocs Kiwoong Kim
2024-08-26 13:08 ` kernel test robot
2024-08-22 11:15 ` [PATCH v2 2/2] scsi: ufs: ufs-exynos: implement override_cqe_ocs Kiwoong Kim
2024-08-22 14:54 ` [PATCH v2 0/2] scsi: ufs: introduce a callback to override OCS value Bean Huo
2024-08-22 16:23 ` Bart Van Assche
2024-08-27 5:59 ` Kiwoong Kim
2024-08-22 15:42 ` Bean Huo
2024-08-22 16:26 ` Bart Van Assche
2024-09-02 0:27 ` Kiwoong Kim
2024-08-27 5:51 ` 김기웅
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.1724325280.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.