From: Bart Van Assche <bvanassche@acm.org>
To: webgeek1234@gmail.com, Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: ufs: core: Disable timestamp for Kioxia THGJFJT0E25BAIP
Date: Mon, 6 Apr 2026 09:03:56 -0700 [thread overview]
Message-ID: <17af030c-feea-4ad0-b297-74a5df209e6c@acm.org> (raw)
In-Reply-To: <20260403-thgjfjt0e25baip-no-timestamp-v1-1-1ddb34225133@gmail.com>
On 4/3/26 11:41 AM, Aaron Kling via B4 Relay wrote:
> Kioxia has another product that does not support the qTimestamp
> attribute.
>
> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> ---
> drivers/ufs/core/ufshcd.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/ufs/core/ufshcd.c b/drivers/ufs/core/ufshcd.c
> index 5c3518f1f97c7f85854b66bf87c86d00b539fba6..4805e40ed4d78cd4b0c07cda0df6bb0f7e172cb1 100644
> --- a/drivers/ufs/core/ufshcd.c
> +++ b/drivers/ufs/core/ufshcd.c
> @@ -315,6 +315,9 @@ static const struct ufs_dev_quirk ufs_fixups[] = {
> { .wmanufacturerid = UFS_VENDOR_TOSHIBA,
> .model = "THGLF2G9D8KBADG",
> .quirk = UFS_DEVICE_QUIRK_PA_TACTIVATE },
> + { .wmanufacturerid = UFS_VENDOR_TOSHIBA,
> + .model = "THGJFJT0E25BAIP",
> + .quirk = UFS_DEVICE_QUIRK_NO_TIMESTAMP_SUPPORT },
> { .wmanufacturerid = UFS_VENDOR_TOSHIBA,
> .model = "THGJFJT1E45BATP",
> .quirk = UFS_DEVICE_QUIRK_NO_TIMESTAMP_SUPPORT },
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2026-04-06 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 18:41 Aaron Kling via B4 Relay
2026-04-06 16:03 ` Bart Van Assche [this message]
2026-04-09 2:28 ` Martin K. Petersen
2026-04-14 2:19 ` 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=17af030c-feea-4ad0-b297-74a5df209e6c@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=webgeek1234@gmail.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®