lkml.org 
[lkml]   [2022]   [May]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v2] hwmon: (sun4i-lradc) Add driver for LRADC found on Allwinner A13/A20 SoC
Hi Guenter,

I'm sorry to disappoint you, but continuous mode for LRADC works only
for key presses (significant voltage change), it does not work for raw
data. Here's an excerpt from the manual that supports my discovery
(punctuation and grammar preserved):

> The LRADC have three mode, Normal Mode、Single Mode and Continue Mode.
> Normal mode is that the LRADC will
> report the result data of each convert all the time when the key is
> down. Single Mode is that the LRADC
> will only report the first convert result data when the key is down.
> Continue Mode is that the LRADC will
> report one of 8*(N+1) (N is program can set) sample convert result data
> when key is down.

In other words, all three modes require key down event (voltage change)
and IRQ is the only way to get continuous raw data updates from LRADC.
I've experimented quite a lot with this for past few days, there are no
changes to values in ADC data regs except in DATA IRQ mode.

Regarding variant structure. Vref is not the only difference between
different implementations of LRADC in different Allwinner SoCs. For
example, A83T has only one channel LRADC instead of two channels in
A10/A13/A20. Some other SoCs may have even more differences. I
introduced hwmon_chip_info structure into variant to encapsulate such
differences in one place. Patch version 3 will follow. Thank you.

---
Regards,
Ruslan.

Fabmicro, LLC.

On 2022-04-29 11:03, Guenter Roeck wrote:
> On 4/28/22 22:32, Guenter Roeck wrote:
>> On 4/28/22 17:28, Ruslan Zalata wrote:
>>> Thank you Guenter for your valuable time.
>>>
>>> I have added update_interval option (it's in ms units, right?) and
>>> fixed all other issues you pointed to. Will test it on real hardware
>>> and send third version of the patch for review.
>>>
>>> Regarding IRQ. Alternatively the driver would need to sit and poll
>>> conversion ready bit in a loop which might cause a much worse load on
>>> system, is not it ? Anyway, the real problem with this piece of
>>> hardware is that there's no "conversion ready bit" provided, the only
>>> way to know data ready status is to receive an interrupt.
>>>
>>
>> Not necessarily. The data does not have to be "current", after all,
>> if the hardware is able to continuously convert. If not, the question
>> is how long a conversion takes. If it doesn't take too long, it would
>> be better to initiate a conversion and then wait for the completion.
>>
>>> I think it still needs a semaphore/seqlock to synchronize conversions
>>> and reads. I.e. two consequent reads should not return same old
>>> value. Although it's not an issue in my case, but could be a problem
>>> for others.
>>>
>> Why ? That happens for almost all hwmon devices. They will all report
>> the most recent conversion value. Some of them can take seconds
>> to complete a new conversion, so the reported value is always "old"
>> for a given defition of old (ie any time smaller than a conversion
>> interval).
>>
>> Sigh. Looks like I'll have to dig up the documentation and read about
>> the ADC myself.
>>
>
> I did, for both A13 and A20. The ADC supports continuous mode. That
> means it can be configured accordingly, and reading the ADC value
> just returns the most recent conversion value. There is absolutely
> no need to keep reading the conversion values using interrupts.
>
> Also,
>
> +struct lradc_variant {
> + u32 bits;
> + u32 resolution;
> + u32 vref;
> +};
>
> is unnecessary because the values are the same for both supported
> chips.
> That means that defines can and should be used. Yes, I can see that
> A83T uses a different voltage, but even that doesn't need a structure -
> the voltage can be set in struct sun4i_lradc_data if/when needed,
> and the resolution and number of bits is still the same.
>
> Guenter

\
 
 \ /
  Last update: 2022-05-03 01:50    [W:0.136 / U:0.248 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site