public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: <robh@kernel.org>, <conor+dt@kernel.org>,
	<linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-pwm@vger.kernel.org>,
	Nuno Sa <nuno.sa@analog.com>
Subject: Re: [PATCH v12 6/9] iio: adc: adi-axi-adc: set data format
Date: Sat, 8 Feb 2025 16:22:09 +0000	[thread overview]
Message-ID: <20250208162209.2d43bae3@jic23-huawei> (raw)
In-Reply-To: <20250207140918.7814-7-antoniu.miclaus@analog.com>

On Fri, 7 Feb 2025 16:09:15 +0200
Antoniu Miclaus <antoniu.miclaus@analog.com> wrote:

> Add support for selecting the data format within the AXI ADC ip.
> 
> Add separate complatible string for the custom AD485X IP and implement
> the necessary changes.
> 
> Reviewed-by: Nuno Sa <nuno.sa@analog.com>
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
> ---
> changes in v12:
>  - add separate compatible for ad485x AXI IP core.
>  drivers/iio/adc/adi-axi-adc.c | 99 +++++++++++++++++++++++++++++++----
>  1 file changed, 90 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/iio/adc/adi-axi-adc.c b/drivers/iio/adc/adi-axi-adc.c
> index d2e1dc63775c..272d82c6e887 100644
> --- a/drivers/iio/adc/adi-axi-adc.c
> +++ b/drivers/iio/adc/adi-axi-adc.c
> @@ -45,6 +45,12 @@
>  #define ADI_AXI_ADC_REG_CTRL			0x0044
>  #define    ADI_AXI_ADC_CTRL_DDR_EDGESEL_MASK	BIT(1)
>  
> +#define ADI_AXI_ADC_REG_CNTRL_3			0x004c
> +#define   AD485X_CNTRL_3_PACKET_FORMAT_MSK	GENMASK(1, 0)
Sorry I missed this until now, but normal IIO thing is no wild cards
in naming (been bitten too often!)

So I'd like to see these named after a specific part.




  parent reply	other threads:[~2025-02-08 16:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07 14:09 [PATCH v12 0/9] Add support for AD485x DAS Family Antoniu Miclaus
2025-02-07 14:09 ` [PATCH v12 1/9] iio: backend: add API for interface get Antoniu Miclaus
2025-02-07 14:09 ` [PATCH v12 2/9] iio: backend: add support for data size set Antoniu Miclaus
2025-02-07 14:09 ` [PATCH v12 3/9] iio: backend: add API for oversampling Antoniu Miclaus
2025-02-07 14:09 ` [PATCH v12 4/9] iio: adc: adi-axi-adc: add interface type Antoniu Miclaus
2025-02-07 14:09 ` [PATCH v12 5/9] dt-bindings: iio: adc: add ad485x axi variant Antoniu Miclaus
2025-02-08 16:20   ` Jonathan Cameron
2025-02-11  8:16     ` Krzysztof Kozlowski
2025-02-11 19:53       ` Jonathan Cameron
2025-02-07 14:09 ` [PATCH v12 6/9] iio: adc: adi-axi-adc: set data format Antoniu Miclaus
2025-02-07 20:51   ` David Lechner
2025-02-08 16:22   ` Jonathan Cameron [this message]
2025-02-11 19:55     ` Jonathan Cameron
2025-02-07 14:09 ` [PATCH v12 7/9] iio: adc: adi-axi-adc: add oversampling Antoniu Miclaus
2025-02-08 16:23   ` Jonathan Cameron
2025-02-07 14:09 ` [PATCH v12 8/9] dt-bindings: iio: adc: add ad4851 Antoniu Miclaus
2025-02-07 14:09 ` [PATCH v12 9/9] iio: adc: ad4851: add ad485x driver Antoniu Miclaus
2025-02-07 20:51   ` David Lechner
2025-02-08 16:28   ` Jonathan Cameron

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=20250208162209.2d43bae3@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=antoniu.miclaus@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=robh@kernel.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