[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <165889172881.804.1367014483116861516.b4-ty@oracle.com>
Date: Tue, 26 Jul 2022 23:15:56 -0400
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: Adrian Hunter <adrian.hunter@...el.com>,
Daniil Lunev <dlunev@...omium.org>,
Bart Van Assche <bvanassche@....org>
Cc: "Martin K . Petersen" <martin.petersen@...cle.com>,
Bean Huo <beanhuo@...ron.com>,
Alim Akhtar <alim.akhtar@...sung.com>,
Avri Altman <avri.altman@....com>,
Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
Randy Dunlap <rdunlap@...radead.org>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>
Subject: Re: [PATCH] scsi: ufs: ufshcd: Read device property for ref clock
On Fri, 15 Jul 2022 21:03:53 +1000, Daniil Lunev wrote:
> UFS storage devices require bRefClkFreq attribute to be set to operate
> correctly at high speed mode. The necessary value is determined by what the
> SoC / board supports. The standard doesn't specify a method to query the
> value, so the information needs to be fed in separately.
>
> DT information feeds into setting up the clock framework, so platforms
> using DT can get the UFS reference clock frequency from the clock
> framework. A special node "ref_clk" from the clock array for the UFS
> controller node is used as the source for the information.
>
> [...]
Applied to 5.20/scsi-queue, thanks!
[1/1] scsi: ufs: ufshcd: Read device property for ref clock
https://git.kernel.org/mkp/scsi/c/ca452621b829
--
Martin K. Petersen Oracle Linux Engineering
Powered by blists - more mailing lists