From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Ioana Risteiu <Ioana.Risteiu@analog.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Ramona Nechita" <ramona.nechita@analog.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/4] iio: adc: adi-axi-adc: add axi_adc_num_lanes_set
Date: Wed, 20 Aug 2025 17:14:58 +0300 [thread overview]
Message-ID: <aKXYYm0yXfujRb_n@smile.fi.intel.com> (raw)
In-Reply-To: <20250820120247.3012-2-Ioana.Risteiu@analog.com>
On Wed, Aug 20, 2025 at 03:02:42PM +0300, Ioana Risteiu wrote:
> Add axi_adc_num_lanes_set in the adi_axi_adc_ops structure to support
axi_adc_num_lanes_set()
or I think even better to rephrase
"Assign num_lanes_set in the adi_axi_adc_ops to axi_adc_num_lanes_set()..."
> setting number of lanes used by AXI ADC. This operation is included in
> the generic structure because the number of lanes is a configurable
> parameter of the generic AXI ADC IP core, not specific to a device.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-08-20 14:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 12:02 [PATCH v4 0/4] Add IIO backend support for AD7779 Ioana Risteiu
2025-08-20 12:02 ` [PATCH v4 1/4] iio: adc: adi-axi-adc: add axi_adc_num_lanes_set Ioana Risteiu
2025-08-20 14:14 ` Andy Shevchenko [this message]
2025-08-20 12:02 ` [PATCH v4 2/4] dt-bindings: iio: adc: add IIO backend support Ioana Risteiu
2025-08-20 12:02 ` [PATCH v4 3/4] iio: adc: extract setup function without backend Ioana Risteiu
2025-08-20 14:13 ` Andy Shevchenko
2025-08-20 12:02 ` [PATCH v4 4/4] iio: adc: update ad7779 to use IIO backend Ioana Risteiu
2025-08-20 14:18 ` Andy Shevchenko
2025-08-25 10:15 ` 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=aKXYYm0yXfujRb_n@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=Ioana.Risteiu@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=ramona.nechita@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.