From: Bean Huo <beanhuo@iokpp.de>
To: "Thomas Weißschuh" <thomas@t-8ch.de>
Cc: avri.altman@wdc.com, bvanassche@acm.org, 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,
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:39:55 +0100 [thread overview]
Message-ID: <5e4f204e1ab2bb5f146b81e9809231f3a17c162f.camel@iokpp.de> (raw)
In-Reply-To: <f1fe8b99-bf57-4243-90bb-665c3bb4e0e4@t-8ch.de>
Hi Thomas,
On Thu, 2023-11-09 at 15:05 +0100, Thomas Weißschuh wrote:
> > + schedule_delayed_work(&hba->ufs_rtc_delayed_work,
> > + msecs_to_jiffies(hb
> > a->dev_info.rtc_update_period));
>
> What about the other work that has already been scheduled?
I don't quite understand your concern here, I need to schedule the
work when needed because of resume_period_update.
Work may have been scheduled, but that's okay, there will be one more
RTC update as expected.
Kind regards,
Bean
next prev parent reply other threads:[~2023-11-14 18:40 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 [this message]
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
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=5e4f204e1ab2bb5f146b81e9809231f3a17c162f.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 \
--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®