[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAFBinCCzx2e92S-cQp2CVup4hr6Ge12uCJ3Qh0+sqNVFRWkv7A@mail.gmail.com>
Date: Sun, 25 Jun 2023 22:37:00 +0200
From: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
To: George Stark <gnstark@...rdevices.ru>
Cc: jic23@...nel.org, lars@...afoo.de, neil.armstrong@...aro.org,
khilman@...libre.com, jbrunet@...libre.com,
andriy.shevchenko@...ux.intel.com, nuno.sa@...log.com,
linux-iio@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-amlogic@...ts.infradead.org,
kernel@...rdevices.ru
Subject: Re: [PATCH v2 6/6] meson saradc: support reading from channel7 mux inputs
Hi George,
On Fri, Jun 23, 2023 at 6:38 PM George Stark <gnstark@...rdevices.ru> wrote:
[...]
> So I think to return to double definition of meson_sar_adc_iio_channels and keep the driver backwards compatible.
Ack!
> I've just realized another moment with channels defined after MESON_SAR_ADC_TEMP_CHAN in channel array.
Good catch
> In dts by default channels are referenced by channel array index not even by channel number.
> So channel e.g MUX_0_VSS will have the same number (due to enum patch) but different index on meson8 and gxbb.
> As alternative we can implement fwnode_xlate method in meson adc driver and use channel numbers in dts (probably not in the current patchset)
That is actually an interesting third approach. But as you said: let's
start simple and add the tables back for now.
Best regards,
Martin
Powered by blists - more mailing lists