[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <471c24af-ad63-3986-6265-1cf62ce45cb0@baylibre.com>
Date: Wed, 29 May 2019 16:17:52 +0200
From: Neil Armstrong <narmstrong@...libre.com>
To: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
Cc: khilman@...libre.com, linux-amlogic@...ts.infradead.org,
Christian Hewitt <christianshewitt@...il.com>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 03/10] arm64: dts: meson-gxbb-wetek: enable SARADC
On 27/05/2019 20:15, Martin Blumenstingl wrote:
> On Mon, May 27, 2019 at 3:22 PM Neil Armstrong <narmstrong@...libre.com> wrote:
>>
>> From: Christian Hewitt <christianshewitt@...il.com>
>>
>> Enable SARADC on Wetek Boards.
> as far I as remember there's a story behind this (and it would be nice
> to have it documented here):
> some of the SCPI firmware revisions don't enable the SAR ADC clock
> when reading the SoCs temperature.
> if the SAR ADC is disabled in Linux then the common clock framework
> will disable the SAR ADC clock.
> now, when the SCPI firmware uses the SAR ADC to read the SoC
> temperature we only get garbage.
>
> enabling the SAR ADC in Linux "fixes" this issue
Yes seems to be this issue solved here
>
>> Signed-off-by: Christian Hewitt <christianshewitt@...il.com>
>> Signed-off-by: Neil Armstrong <narmstrong@...libre.com>
> with that:
> Reviewed-by: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
>
Powered by blists - more mailing lists