On 01/11, Can Guo wrote:
> On 2021-01-11 16:15, Avri Altman wrote:
> > >
> > > Sorry, typo corrected.
> > >
> > > Hi Jaegeuk,
> > >
> > > I think the problem is that func ufshcd_read_desc_param() is not
> > > expecting
> > > one access unsupported descriptors on RPMB LU.
> > Correct.
> > This is
On 2021-01-11 16:15, Avri Altman wrote:
Sorry, typo corrected.
Hi Jaegeuk,
I think the problem is that func ufshcd_read_desc_param() is not
expecting
one access unsupported descriptors on RPMB LU.
Correct.
This is about wb introducing a new constraint: wb buffer is only
allowed in lu 0..7.
An
>
> Sorry, typo corrected.
>
> Hi Jaegeuk,
>
> I think the problem is that func ufshcd_read_desc_param() is not
> expecting
> one access unsupported descriptors on RPMB LU.
Correct.
This is about wb introducing a new constraint: wb buffer is only allowed in lu
0..7.
And this is why, IMHO, the f
Sorry, typo corrected.
Hi Jaegeuk,
I think the problem is that func ufshcd_read_desc_param() is not
expecting
one access unsupported descriptors on RPMB LU.
If we can get the right buf_len from func
ufshcd_map_desc_id_to_length(),
the issue won't happen. -
https://lore.kernel.org/patchwork/
Hi Jaegeuk,
I think the problem is that func ufshcd_read_desc_param() is not
expecting
one access unsupported descriptors on all W-LUs, not just RPMB LU.
If we can get the right buf_len from func
ufshcd_map_desc_id_to_length(),
the issue won't happen. -
https://lore.kernel.org/patchwork/patc
5 matches
Mail list logo