[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a10a5816-bfba-9bc5-e90c-39d91ad9f2cb@nvidia.com>
Date: Fri, 23 Jun 2023 10:21:29 +0530
From: Sameer Pujar <spujar@...dia.com>
To: Mark Brown <broonie@...nel.org>
Cc: robh+dt@...nel.org, krzk+dt@...nel.org, thierry.reding@...il.com,
lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com,
jonathanh@...dia.com, mkumard@...dia.com, sheetal@...dia.com,
alsa-devel@...a-project.org, devicetree@...r.kernel.org,
linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH 7/8] arm64: tegra: Update AHUB clock parent and rate on
Tegra234
On 22-06-2023 17:43, Mark Brown wrote:
> On Thu, Jun 22, 2023 at 05:04:15PM +0530, Sameer Pujar wrote:
>> From: Sheetal <sheetal@...dia.com>
>>
>> I2S data sanity tests fail beyond a bit clock frequency of 6.144MHz.
>> This happens because the AHUB clock rate is too low and it shows
>> 9.83MHz on boot.
>>
>> The maximum rate of PLLA_OUT0 is 49.152MHz and is used to serve I/O
>> clocks. It is recommended that AHUB clock operates higher than this.
>> Thus fix this by using PLLP_OUT0 as parent clock for AHUB instead of
>> PLLA_OUT0 and fix the rate to 81.6MHz.
>>
>> Fixes: dc94a94daa39 ("arm64: tegra: Add audio devices on Tegra234")
>> Cc: stable@...r.kernel.org
>> Signed-off-by: Sheetal <sheetal@...dia.com>
> Fixes should come before cleanups in a patch series to ensure that they
> can be applied and sent as fixes without dependencies on non-fixes.
I sorted the series based on the subsystem. Will make sure to put
'fixes' patch always first. Thanks.
Powered by blists - more mailing lists