[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240816053528.GE2331@thinkpad>
Date: Fri, 16 Aug 2024 11:05:28 +0530
From: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
To: Bart Van Assche <bvanassche@....org>
Cc: Alim Akhtar <alim.akhtar@...sung.com>,
Avri Altman <avri.altman@....com>,
"James E.J. Bottomley" <James.Bottomley@...senPartnership.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, Kyoungrul Kim <k831.kim@...sung.com>,
Amit Pundir <amit.pundir@...aro.org>
Subject: Re: [PATCH v2 2/3] ufs: core: Add a quirk for handling broken LSDBS
field in controller capabilities register
On Thu, Aug 15, 2024 at 11:12:57AM -0700, Bart Van Assche wrote:
> On 8/14/24 10:16 PM, Manivannan Sadhasivam via B4 Relay wrote:
> > + /*
> > + * This quirk needs to be enabled if the host controller has the broken
> > + * Legacy Queue & Single Doorbell Support (LSDBS) field in Controller
> > + * Capabilities register.
> > + */
> > + UFSHCD_QUIRK_BROKEN_LSDBS_CAP = 1 << 25,
>
> The above comment is misleading because it suggests that the definition
> of this bit in the UFSHCI specification is broken, which is not the
> case.
Really? I don't see where the comment implies that the bit in the specification
is broken. It clearly says that the 'host controller has the broken bit'.
>How about this comment?
>
> /*
> * This quirk indicates that the controller reports the value 1
> * (not supported) in the Legacy Single DoorBell Support (LSDBS)
> * bit although it supports the legacy single doorbell mode.
But this comment is more elaborative. So I'll use it, thanks!
- Mani
--
மணிவண்ணன் சதாசிவம்
Powered by blists - more mailing lists