[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20241118144117.88483-1-avri.altman@wdc.com>
Date: Mon, 18 Nov 2024 16:41:14 +0200
From: Avri Altman <avri.altman@....com>
To: "Martin K . Petersen" <martin.petersen@...cle.com>
Cc: linux-scsi@...r.kernel.org,
linux-kernel@...r.kernel.org,
Bart Van Assche <bvanassche@....org>,
Bean Huo <beanhuo@...ron.com>,
Avri Altman <avri.altman@....com>
Subject: [PATCH v4 0/3] Untie the host lock entanglement - part 2
Here is the 2nd part in the sequel, watering down the scsi host lock
usage in the ufs driver. This work is motivated by a comment made by
Bart [1], of the abuse of the scsi host lock in the ufs driver. Its
Precursor [2] removed the host lock around some of the host register
accesses.
This part replaces the scsi host lock by dedicated locks serializing
access to the clock gating and clock scaling members.
Changes compared to v3:
- Keep the host lock when checking ufshcd_state (Bean)
Changes compared to v2:
- Use clang-format to fix formating (Bart)
- Use guard() in ufshcd_clkgate_enable_store (Bart)
- Elaborate commit log (Bart)
Changes compared to v1:
- use the guard() & scoped_guard() macros (Bart)
- re-order struct ufs_clk_scaling and struct ufs_clk_gating (Bart)
[1] https://lore.kernel.org/linux-scsi/0b031b8f-c07c-42ef-af93-7336439d3c37@acm.org/
[2] https://lore.kernel.org/linux-scsi/20241024075033.562562-1-avri.altman@wdc.com/
Avri Altman (3):
scsi: ufs: core: Prepare to introduce a new clock_gating lock
scsi: ufs: core: Introduce a new clock_gating lock
scsi: ufs: core: Introduce a new clock_scaling lock
drivers/ufs/core/ufshcd.c | 255 +++++++++++++++++++-------------------
include/ufs/ufshcd.h | 24 ++--
2 files changed, 144 insertions(+), 135 deletions(-)
--
2.25.1
Powered by blists - more mailing lists