From: jic23@kernel.org (Jonathan Cameron)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 5/5] iio: adc: meson-saradc: program the channel muxes during initialization
Date: Sun, 19 Nov 2017 15:57:01 +0000 [thread overview]
Message-ID: <20171119155701.551b4cd1@archlinux> (raw)
In-Reply-To: <20171031200147.14660-6-martin.blumenstingl@googlemail.com>
On Tue, 31 Oct 2017 21:01:47 +0100
Martin Blumenstingl <martin.blumenstingl@googlemail.com> wrote:
> On some Meson8 devices the channel muxes are not programmed. This
> results in garbage values when trying to read channels that are not set
> up.
> Fix this by initializing the channel 0 and 1 muxes in
> MESON_SAR_ADC_CHAN_10_SW as well as the muxes for all other channels in
> MESON_SAR_ADC_AUX_SW based on what the vendor driver does (which is
> simply a 1:1 mapping of channel number and channel mux).
> This only showed up on Meson8 devices, because for GXBB and newer BL30
> is taking care of initializing the channel muxes.
>
> This additionally fixes a typo in the
> MESON_SAR_ADC_AUX_SW_MUX_SEL_CHAN_MASK macro because the old definition
> assumed that the register fields were 2 bit wide, while they are
> actually 3 bit wide.
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
I'll go with your opinion on this. We can always request that it is
added to stable after it has gone in during the next merge window.
Let me know if I seem to have forgotten this once the fixes have
come back round the loop to my togreg branch.
Thanks,
Jonathan
> ---
> drivers/iio/adc/meson_saradc.c | 32 +++++++++++++++++++++++++++++---
> 1 file changed, 29 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iio/adc/meson_saradc.c b/drivers/iio/adc/meson_saradc.c
> index fa3c1378c2c9..48fb1b642a5e 100644
> --- a/drivers/iio/adc/meson_saradc.c
> +++ b/drivers/iio/adc/meson_saradc.c
> @@ -96,8 +96,8 @@
> #define MESON_SAR_ADC_FIFO_RD_SAMPLE_VALUE_MASK GENMASK(11, 0)
>
> #define MESON_SAR_ADC_AUX_SW 0x1c
> - #define MESON_SAR_ADC_AUX_SW_MUX_SEL_CHAN_MASK(_chan) \
> - (GENMASK(10, 8) << (((_chan) - 2) * 2))
> + #define MESON_SAR_ADC_AUX_SW_MUX_SEL_CHAN_SHIFT(_chan) \
> + (8 + (((_chan) - 2) * 3))
> #define MESON_SAR_ADC_AUX_SW_VREF_P_MUX BIT(6)
> #define MESON_SAR_ADC_AUX_SW_VREF_N_MUX BIT(5)
> #define MESON_SAR_ADC_AUX_SW_MODE_SEL BIT(4)
> @@ -623,7 +623,7 @@ static int meson_sar_adc_clk_init(struct iio_dev *indio_dev,
> static int meson_sar_adc_init(struct iio_dev *indio_dev)
> {
> struct meson_sar_adc_priv *priv = iio_priv(indio_dev);
> - int regval, ret;
> + int regval, i, ret;
>
> /*
> * make sure we start at CH7 input since the other muxes are only used
> @@ -678,6 +678,32 @@ static int meson_sar_adc_init(struct iio_dev *indio_dev)
> FIELD_PREP(MESON_SAR_ADC_DELAY_INPUT_DLY_SEL_MASK,
> 1));
>
> + /*
> + * set up the input channel muxes in MESON_SAR_ADC_CHAN_10_SW
> + * (0 = SAR_ADC_CH0, 1 = SAR_ADC_CH1)
> + */
> + regval = FIELD_PREP(MESON_SAR_ADC_CHAN_10_SW_CHAN0_MUX_SEL_MASK, 0);
> + regmap_update_bits(priv->regmap, MESON_SAR_ADC_CHAN_10_SW,
> + MESON_SAR_ADC_CHAN_10_SW_CHAN0_MUX_SEL_MASK,
> + regval);
> + regval = FIELD_PREP(MESON_SAR_ADC_CHAN_10_SW_CHAN1_MUX_SEL_MASK, 1);
> + regmap_update_bits(priv->regmap, MESON_SAR_ADC_CHAN_10_SW,
> + MESON_SAR_ADC_CHAN_10_SW_CHAN1_MUX_SEL_MASK,
> + regval);
> +
> + /*
> + * set up the input channel muxes in MESON_SAR_ADC_AUX_SW
> + * (2 = SAR_ADC_CH2, 3 = SAR_ADC_CH3, ...) and enable
> + * MESON_SAR_ADC_AUX_SW_YP_DRIVE_SW and
> + * MESON_SAR_ADC_AUX_SW_XP_DRIVE_SW like the vendor driver.
> + */
> + regval = 0;
> + for (i = 2; i <= 7; i++)
> + regval |= i << MESON_SAR_ADC_AUX_SW_MUX_SEL_CHAN_SHIFT(i);
> + regval |= MESON_SAR_ADC_AUX_SW_YP_DRIVE_SW;
> + regval |= MESON_SAR_ADC_AUX_SW_XP_DRIVE_SW;
> + regmap_write(priv->regmap, MESON_SAR_ADC_AUX_SW, regval);
> +
> ret = clk_set_parent(priv->adc_sel_clk, priv->clkin);
> if (ret) {
> dev_err(indio_dev->dev.parent,
next prev parent reply other threads:[~2017-11-19 15:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 20:01 [PATCH 0/5] meson_saradc fixes and minor improvements Martin Blumenstingl
2017-10-31 20:01 ` [PATCH 1/5] iio: adc: meson-saradc: fix the bit_idx of the adc_en clock Martin Blumenstingl
2017-11-19 15:43 ` Jonathan Cameron
2017-10-31 20:01 ` [PATCH 2/5] iio: adc: meson-saradc: initialize the bandgap correctly on older SoCs Martin Blumenstingl
2017-11-19 15:44 ` Jonathan Cameron
2017-10-31 20:01 ` [PATCH 3/5] iio: adc: meson-saradc: Meson8 and Meson8b do not have REG11 and REG13 Martin Blumenstingl
2017-11-19 15:46 ` Jonathan Cameron
2017-10-31 20:01 ` [PATCH 4/5] iio: adc: meson-saradc: fix the clock frequency on Meson8 and Meson8b Martin Blumenstingl
2017-11-19 15:55 ` Jonathan Cameron
2017-12-10 19:47 ` Jonathan Cameron
2017-10-31 20:01 ` [PATCH 5/5] iio: adc: meson-saradc: program the channel muxes during initialization Martin Blumenstingl
2017-11-19 15:57 ` Jonathan Cameron [this message]
2017-12-10 19:49 ` Jonathan Cameron
2017-11-02 15:05 ` [PATCH 0/5] meson_saradc fixes and minor improvements Jonathan Cameron
2017-11-27 23:47 ` Kevin Hilman
2017-12-02 11:30 ` Jonathan Cameron
2017-12-10 17:48 ` Martin Blumenstingl
2017-12-10 19:50 ` Jonathan Cameron
2017-12-10 22:27 ` Martin Blumenstingl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171119155701.551b4cd1@archlinux \
--to=jic23@kernel.org \
--cc=linus-amlogic@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).