[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <14a5925b-df2b-3f84-ed99-b4157c0a1b21@acm.org>
Date: Thu, 27 Oct 2022 14:09:50 -0700
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, quic_richardp@...cinc.com,
linux-arm-msm@...r.kernel.org,
Alim Akhtar <alim.akhtar@...sung.com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 03/17] ufs: core: Introduce Multi-circular queue
capability
On 10/20/22 11:03, Asutosh Das wrote:
> +
> + /*
> + * This capability allows the host controller driver to turn on/off
> + * MCQ mode. MCQ mode may be used to increase performance.
> + */
> + UFSHCD_CAP_MCQ_EN = 1 << 12,
> };
I prefer that the above flag would only be introduced after a need
appears to disable MCQ, e.g. discovery of a host controller that is too
broken to enable MCQ.
Since UFSHCI 4.0 controllers must support UFSHCI 3.0, shouldn't users
have a way to disable MCQ, e.g. via a kernel module parameter?
Thanks,
Bart.
Powered by blists - more mailing lists