mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Bean Huo <beanhuo@iokpp.de>,
	avri.altman@wdc.com, alim.akhtar@samsung.com, jejb@linux.ibm.com,
	martin.petersen@oracle.com, mani@kernel.org,
	quic_cang@quicinc.com, quic_asutoshd@quicinc.com,
	beanhuo@micron.com, thomas@t-8ch.de
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	mikebi@micron.com, lporzio@micron.com
Subject: Re: [PATCH v2 2/3] scsi: ufs: core: Add UFS RTC support
Date: Wed, 22 Nov 2023 09:51:27 -0800	[thread overview]
Message-ID: <fbc51bf1-3c4f-4575-a148-65fcfee1a8fe@acm.org> (raw)
In-Reply-To: <20231122172512.103748-3-beanhuo@iokpp.de>

On 11/22/23 09:25, Bean Huo wrote:
> Given that the RTC has been a standard feature since UFS Spec 2.0, and qTimestamp was introduced
> in UFS Spec 4.0, the majority of UFS devices currently on the market rely on RTC. Therefore, it
> is advisable to continue supporting RTC in the Linux kernel. This ensures compatibility with the
> prevailing UFS device implementations and facilitates seamless integration with existing hardware.
> By maintaining support for RTC, we ensure broad compatibility and avoid potential issues arising
> from deviations in device specifications across different UFS versions.

Patch descriptions should be 75 characters wide. See also
Documentation/process/submitting-patches.rst.

Thanks,

Bart.


  reply	other threads:[~2023-11-22 17:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 17:25 [PATCH v2 0/3] " Bean Huo
2023-11-22 17:25 ` [PATCH v2 1/3] scsi: ufs: core: Add ufshcd_is_ufs_dev_busy() Bean Huo
2023-11-22 17:43   ` Bart Van Assche
2023-11-22 17:25 ` [PATCH v2 2/3] scsi: ufs: core: Add UFS RTC support Bean Huo
2023-11-22 17:51   ` Bart Van Assche [this message]
2023-11-22 17:25 ` [PATCH v2 3/3] scsi: ufs: core: Add sysfs node for UFS RTC update Bean Huo

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=fbc51bf1-3c4f-4575-a148-65fcfee1a8fe@acm.org \
    --to=bvanassche@acm.org \
    --cc=alim.akhtar@samsung.com \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@iokpp.de \
    --cc=beanhuo@micron.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lporzio@micron.com \
    --cc=mani@kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mikebi@micron.com \
    --cc=quic_asutoshd@quicinc.com \
    --cc=quic_cang@quicinc.com \
    --cc=thomas@t-8ch.de \
    /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®