On 2020-10-27 03:48, Jaegeuk Kim wrote:
On 10/26, Can Guo wrote:
On 2020-10-26 14:13, Jaegeuk Kim wrote:
> On 10/26, Can Guo wrote:
> > On 2020-10-24 23:06, Jaegeuk Kim wrote:
> > > From: Jaegeuk Kim
> > >
> > > When giving a stress test which enables/disables clkgating, we hit
> > > device
>
On 10/26, Can Guo wrote:
> On 2020-10-26 14:13, Jaegeuk Kim wrote:
> > On 10/26, Can Guo wrote:
> > > On 2020-10-24 23:06, Jaegeuk Kim wrote:
> > > > From: Jaegeuk Kim
> > > >
> > > > When giving a stress test which enables/disables clkgating, we hit
> > > > device
> > > > timeout sometimes. This
On 2020-10-26 14:13, Jaegeuk Kim wrote:
On 10/26, Can Guo wrote:
On 2020-10-24 23:06, Jaegeuk Kim wrote:
> From: Jaegeuk Kim
>
> When giving a stress test which enables/disables clkgating, we hit
> device
> timeout sometimes. This patch avoids subtle racy condition to address
> it.
>
> If we
On 10/26, Can Guo wrote:
> On 2020-10-24 23:06, Jaegeuk Kim wrote:
> > From: Jaegeuk Kim
> >
> > When giving a stress test which enables/disables clkgating, we hit
> > device
> > timeout sometimes. This patch avoids subtle racy condition to address
> > it.
> >
> > If we use __ufshcd_release(),
On 2020-10-24 23:06, Jaegeuk Kim wrote:
From: Jaegeuk Kim
When giving a stress test which enables/disables clkgating, we hit
device
timeout sometimes. This patch avoids subtle racy condition to address
it.
If we use __ufshcd_release(), I've seen that gate_work can be called in
parallel
From: Jaegeuk Kim
When giving a stress test which enables/disables clkgating, we hit device
timeout sometimes. This patch avoids subtle racy condition to address it.
If we use __ufshcd_release(), I've seen that gate_work can be called in parallel
with ungate_work, which results in UFS timeout
6 matches
Mail list logo
