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, jejb@linux.ibm.com,
martin.petersen@oracle.com, beanhuo@micron.com,
cang@codeaurora.org, adrian.hunter@intel.com, sc.suh@samsung.com,
hy50.seo@samsung.com, sh425.lee@samsung.com,
bhoon95.kim@samsung.com
Cc: Kiwoong Kim <kwmad.kim@samsung.com>
Subject: [PATCH v2 0/3] scsi: ufs: introduce vendor isr
Date: Mon, 13 Sep 2021 16:55:52 +0900 [thread overview]
Message-ID: <cover.1631519695.git.kwmad.kim@samsung.com> (raw)
In-Reply-To: CGME20210913081148epcas2p21c23ca6a745f40083ee7d6e7da4d7c00@epcas2p2.samsung.com
This patch is to activate some interrupt sources
that aren't defined in UFSHCI specifications. Those
purpose could be error handling, workaround or whatever.
Kiwoong Kim (3):
scsi: ufs: introduce vendor isr
scsi: ufs: introduce force requeue
scsi: ufs: ufs-exynos: implement exynos isr
drivers/scsi/ufs/ufs-exynos.c | 84 ++++++++++++++++++++++++++++++++++++-------
drivers/scsi/ufs/ufshcd.c | 22 ++++++++++--
drivers/scsi/ufs/ufshcd.h | 2 ++
3 files changed, 93 insertions(+), 15 deletions(-)
--
2.7.4
next parent reply other threads:[~2021-09-13 8:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210913081148epcas2p21c23ca6a745f40083ee7d6e7da4d7c00@epcas2p2.samsung.com>
2021-09-13 7:55 ` Kiwoong Kim [this message]
2021-09-13 7:55 ` [PATCH v2 1/3] scsi: ufs: introduce vendor isr Kiwoong Kim
2021-09-14 3:30 ` Bart Van Assche
2021-09-14 5:13 ` Kiwoong Kim
2021-09-14 11:53 ` Avri Altman
2021-09-14 16:29 ` Bart Van Assche
2021-09-13 7:55 ` [PATCH v2 2/3] scsi: ufs: introduce force requeue Kiwoong Kim
2021-09-13 7:55 ` [PATCH v2 3/3] scsi: ufs: ufs-exynos: implement exynos isr Kiwoong Kim
2021-09-13 16:23 ` Bart Van Assche
2021-09-14 5:12 ` Kiwoong Kim
2021-09-17 19:59 ` Avri Altman
2021-09-13 16:09 ` [PATCH v2 0/3] scsi: ufs: introduce vendor isr Bart Van Assche
2021-09-13 17:26 ` Alim Akhtar
2021-09-14 3:23 ` Bart Van Assche
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.1631519695.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=bhoon95.kim@samsung.com \
--cc=cang@codeaurora.org \
--cc=hy50.seo@samsung.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sc.suh@samsung.com \
--cc=sh425.lee@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