From: Bean Huo <beanhuo@iokpp.de>
To: Bart Van Assche <bvanassche@acm.org>,
avri.altman@wdc.com, alim.akhtar@samsung.com, jejb@linux.ibm.com,
martin.petersen@oracle.com, stanley.chu@mediatek.com,
mani@kernel.org, quic_cang@quicinc.com,
quic_asutoshd@quicinc.com, beanhuo@micron.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
mikebi@micron.com, lporzio@micron.com
Subject: Re: [PATCH v1 2/2] scsi: ufs: core: Add sysfs node for UFS RTC update
Date: Tue, 14 Nov 2023 19:46:27 +0100 [thread overview]
Message-ID: <e946d56d5f9fd8458043b579ab47e4d9f8e88b04.camel@iokpp.de> (raw)
In-Reply-To: <fb80565a-9b91-4125-ac50-f8469f27c3b8@acm.org>
Hi Bart,
On Thu, 2023-11-09 at 10:07 -0800, Bart Van Assche wrote:
> On 11/9/23 04:52, Bean Huo wrote:
> > This patch introduces a sysfs node named 'rtc_update_ms' within the
> > kernel, enabling users to
> > adjust the RTC periodic update frequency to suit the specific
> > requirements of the system and
> > UFS. Also, this patch allows the user to disable periodic update
> > RTC in the UFS idle time.
>
> Why is this behavior enabled by default instead of disabled by
> default?
No problem, I will disable it by default in the next version and let
customers choose on a case-by-case basis.
Kind regards,
Bean
next prev parent reply other threads:[~2023-11-14 18:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 12:52 [PATCH v1 0/2] Add UFS RTC support Bean Huo
2023-11-09 12:52 ` [PATCH v1 1/2] scsi: ufs: core: " Bean Huo
2023-11-09 14:05 ` Thomas Weißschuh
2023-11-14 18:27 ` Bean Huo
2023-11-14 18:53 ` Thomas Weißschuh
2023-11-09 15:09 ` Avri Altman
2023-11-14 18:42 ` Bean Huo
2023-11-09 18:06 ` Bart Van Assche
2023-11-09 12:52 ` [PATCH v1 2/2] scsi: ufs: core: Add sysfs node for UFS RTC update Bean Huo
2023-11-09 14:05 ` Thomas Weißschuh
2023-11-14 18:39 ` Bean Huo
2023-11-14 18:48 ` Thomas Weißschuh
2023-11-09 15:10 ` Avri Altman
2023-11-09 18:07 ` Bart Van Assche
2023-11-14 18:46 ` Bean Huo [this message]
2023-11-12 2:02 ` kernel test robot
2023-11-09 15:10 ` [PATCH v1 0/2] Add UFS RTC support Avri Altman
2023-11-09 18:07 ` 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=e946d56d5f9fd8458043b579ab47e4d9f8e88b04.camel@iokpp.de \
--to=beanhuo@iokpp.de \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--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=stanley.chu@mediatek.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®