All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avri Altman <Avri.Altman@wdc.com>
To: Bart Van Assche <bvanassche@acm.org>,
	"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: RE: [PATCH 1/4] scsi: ufs: Reduce the clock scaling latency
Date: Fri, 29 Apr 2022 05:44:28 +0000	[thread overview]
Message-ID: <DM6PR04MB6575B1EF6F41CA69BB816EA7FCFC9@DM6PR04MB6575.namprd04.prod.outlook.com> (raw)
In-Reply-To: <f3c2d9a1-f36e-1da3-4568-67214ed43886@acm.org>

> On 4/28/22 00:09, Avri Altman wrote:
> > Maybe we should create some linkage to DOORBELL_CLR_TOUT_US?
> 
> Hi Avri,
> 
> Do you perhaps want me to change
> 
>         io_schedule_timeout(msecs_to_jiffies(20));
> 
> into something like the following?
> 
>         io_schedule_timeout(msecs_to_jiffies(min(20, remaining_time)));
> 
> Documenting that wait_timeout_us may be exceeded by 20 ms seems like
> the
> easier solution to me :-)
I meant some fraction of DOORBELL_CLR_TOUT_US but that's fine - 
It is going away anyway.

Thanks,
Avri

> 
> Thanks,
> 
> Bart.

  reply	other threads:[~2022-04-29  5:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 23:38 [PATCH 0/4] Prepare for upstreaming Pixel 6 UFS support Bart Van Assche
2022-04-27 23:38 ` [PATCH 1/4] scsi: ufs: Reduce the clock scaling latency Bart Van Assche
2022-04-28  7:09   ` Avri Altman
2022-04-28 20:13     ` Bart Van Assche
2022-04-29  5:44       ` Avri Altman [this message]
2022-04-27 23:38 ` [PATCH 2/4] scsi: ufs: Move a clock scaling check Bart Van Assche
2022-04-28  7:38   ` Avri Altman
2022-04-28 20:15     ` Bart Van Assche
2022-04-27 23:38 ` [PATCH 3/4] scsi: ufs: Pass the clock scaling timeout as an argument Bart Van Assche
2022-04-28  7:16   ` Avri Altman
2022-04-27 23:38 ` [PATCH 4/4] scsi: ufs: Add suspend/resume SCSI command processing support 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=DM6PR04MB6575B1EF6F41CA69BB816EA7FCFC9@DM6PR04MB6575.namprd04.prod.outlook.com \
    --to=avri.altman@wdc.com \
    --cc=adrian.hunter@intel.com \
    --cc=bvanassche@acm.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.