public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Olivier Moysan <olivier.moysan@foss.st.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	Jonathan Cameron <jic23@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Frank Rowand <frowand.list@gmail.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, <devicetree@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-iio@vger.kernel.org>
Subject: Re: [RFC PATCH 0/7] iio: add iio backend device type
Date: Sun, 2 Jul 2023 19:00:02 +0800	[thread overview]
Message-ID: <20230702190002.00002681@Huawei.com> (raw)
In-Reply-To: <20230623140944.2613002-1-olivier.moysan@foss.st.com>

On Fri, 23 Jun 2023 16:09:36 +0200
Olivier Moysan <olivier.moysan@foss.st.com> wrote:

> This RFC re-opens an old discussion regarding channel scaling
> management in STM32 DFSDM driver [1]
> 
> The DFSDM is a peripheral provided by the STM32MP1x SoC family.
> One objective is also to prepare the introduction of its successor in
> the STM32MP12x SoC family: the MDF (Multi-function Digital Filter).
> The MDF driver will have the same requirements as the DFSDM regarding
> channel scaling management. So, the solution proposed here will apply
> also for the future MDF driver.
For next version, please make sure all patches go at least to linux-iio@vger.kernel.org



      parent reply	other threads:[~2023-07-02 11:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23 14:09 [RFC PATCH 0/7] iio: add iio backend device type Olivier Moysan
2023-06-23 14:09 ` [RFC PATCH 1/7] iio: introduce iio backend device Olivier Moysan
2023-06-23 14:09 ` [RFC PATCH 2/7] of: property: add device link support for io-backends Olivier Moysan
2023-06-23 14:09 ` [RFC PATCH 3/7] iio: adc: stm32-dfsdm: manage dfsdm as a channel provider Olivier Moysan
2023-06-23 14:09 ` [RFC PATCH 4/7] iio: adc: stm32-dfsdm: adopt generic channel bindings Olivier Moysan
2023-06-23 14:09 ` [RFC PATCH 5/7] iio: adc: sd_adc_modulator: change to iio backend device Olivier Moysan
2023-06-23 14:09 ` [RFC PATCH 6/7] iio: adc: stm32-dfsdm: add scaling support to dfsdm Olivier Moysan
2023-06-23 14:09 ` [RFC PATCH 7/7] ARM: dts: stm32: add dfsdm iio suppport Olivier Moysan
2023-07-02 10:56 ` [RFC PATCH 0/7] iio: add iio backend device type Jonathan Cameron
2023-07-02 11:07   ` Jonathan Cameron
2023-07-02 11:00 ` Jonathan Cameron [this message]

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=20230702190002.00002681@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=jic23@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=olivier.moysan@foss.st.com \
    --cc=robh+dt@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