[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <02fdf311-5683-9932-f881-fc72e0ad8115@acm.org>
Date: Fri, 25 Nov 2022 17:20:36 -0800
From: Bart Van Assche <bvanassche@....org>
To: Asutosh Das <quic_asutoshd@...cinc.com>, quic_cang@...cinc.com,
martin.petersen@...cle.com, linux-scsi@...r.kernel.org
Cc: quic_nguyenb@...cinc.com, quic_xiaosenh@...cinc.com,
stanley.chu@...iatek.com, eddie.huang@...iatek.com,
daejun7.park@...sung.com, avri.altman@....com, mani@...nel.org,
beanhuo@...ron.com, linux-arm-msm@...r.kernel.org,
Alim Akhtar <alim.akhtar@...sung.com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
Jinyoung Choi <j-young.choi@...sung.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Kiwoong Kim <kwmad.kim@...sung.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5 08/16] ufs: core: mcq: Allocate memory for mcq mode
On 11/22/22 20:10, Asutosh Das wrote:
> To read the bqueuedepth, the device descriptor is fetched
> in Single Doorbell Mode. This allocated memory may not be
> enough for MCQ mode because the number of tags supported
> in MCQ mode may be larger than in SDB mode.
> Hence, release the memory allocated in SDB mode and allocate
> memory for MCQ mode operation.
> Define the ufs hardware queue and Completion Queue Entry.
Reviewed-by: Bart Van Assche <bvanassche@....org>
Powered by blists - more mailing lists