[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1581945168.26304.4.camel@mtksdccf07>
Date: Mon, 17 Feb 2020 21:12:48 +0800
From: Stanley Chu <stanley.chu@...iatek.com>
To: Can Guo <cang@...eaurora.org>
CC: <linux-scsi@...r.kernel.org>, <martin.petersen@...cle.com>,
<avri.altman@....com>, <alim.akhtar@...sung.com>,
<jejb@...ux.ibm.com>, <beanhuo@...ron.com>,
<asutoshd@...eaurora.org>, <matthias.bgg@...il.com>,
<bvanassche@....org>, <linux-mediatek@...ts.infradead.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <kuohong.wang@...iatek.com>,
<peter.wang@...iatek.com>, <chun-hung.wu@...iatek.com>,
<andy.teng@...iatek.com>
Subject: Re: [PATCH v1 1/2] scsi: ufs: add required delay after gating
reference clock
Hi Can,
> > } else if (!on && clki->enabled) {
> > clk_disable_unprepare(clki->clk);
> > + wait_us = hba->dev_info.clk_gating_wait_us;
> > + if (ref_clk && wait_us)
> > + usleep_range(wait_us, wait_us + 10);
>
> Hi Stanley,
>
> If wait_us is 1us, it would be inappropriate to use usleep_range() here.
> You have checks of the delay in patch #2, but why it is not needed here?
>
> Thanks,
> Can Guo.
You are right. I could make that delay checking as common function so it
can be used here as well to cover all possible values.
Thanks for suggestion.
Stanley
Powered by blists - more mailing lists