public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
Cc: <lee@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
	<conor+dt@kernel.org>, <alexandre.torgue@foss.st.com>,
	<wbg@kernel.org>, <ukleinek@kernel.org>,
	<catalin.marinas@arm.com>, <will@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>,
	<linux-pwm@vger.kernel.org>, <olivier.moysan@foss.st.com>
Subject: Re: [PATCH v2 3/9] iio: trigger: stm32-timer: add support for stm32mp25
Date: Fri, 20 Dec 2024 19:23:17 +0000	[thread overview]
Message-ID: <20241220192317.1266a34e@jic23-huawei> (raw)
In-Reply-To: <20241220095927.1122782-4-fabrice.gasnier@foss.st.com>

On Fri, 20 Dec 2024 10:59:21 +0100
Fabrice Gasnier <fabrice.gasnier@foss.st.com> wrote:

> Add support for STM32MP25 SoC. Use newly introduced compatible to handle
> this new HW variant. Add TIM20 trigger definitions that can be used by
> the stm32 analog-to-digital converter. Use compatible data to identify
> it.
> As the counter framework is now superseding the deprecated IIO counter
> interface (IIO_COUNT), don't support it. Only register IIO trigger
> devices for ADC usage. So, make the valids_table a cfg option.
> 
> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Signed-off-by: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
I'm not seeing any compile time dependencies, so I've picked this one up.
Applied to the togreg branch of iio.git and pushed out initially as testing
to let 0-day see if I missed anything.

Thanks,

Jonathan


  reply	other threads:[~2024-12-20 19:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20  9:59 [PATCH v2 0/9] Add STM32MP25 timers support: MFD, PWM, IIO and counter drivers Fabrice Gasnier
2024-12-20  9:59 ` [PATCH v2 1/9] dt-bindings: mfd: stm32-timers: add support for stm32mp25 Fabrice Gasnier
2024-12-20  9:59 ` [PATCH v2 2/9] " Fabrice Gasnier
2024-12-20  9:59 ` [PATCH v2 3/9] iio: trigger: stm32-timer: " Fabrice Gasnier
2024-12-20 19:23   ` Jonathan Cameron [this message]
2024-12-20  9:59 ` [PATCH v2 4/9] counter: stm32-timer-cnt: " Fabrice Gasnier
2024-12-20  9:59 ` [PATCH v2 5/9] pwm: stm32: " Fabrice Gasnier
2024-12-20  9:59 ` [PATCH v2 6/9] arm64: defconfig: enable STM32 timers drivers Fabrice Gasnier
2024-12-20  9:59 ` [PATCH v2 7/9] arm64: dts: st: add timer nodes on stm32mp251 Fabrice Gasnier
2024-12-20  9:59 ` [PATCH v2 8/9] arm64: dts: st: add timer pins for stm32mp257f-ev1 Fabrice Gasnier
2024-12-20  9:59 ` [PATCH v2 9/9] arm64: dts: st: add timer nodes on stm32mp257f-ev1 Fabrice Gasnier

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=20241220192317.1266a34e@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=fabrice.gasnier@foss.st.com \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=olivier.moysan@foss.st.com \
    --cc=robh@kernel.org \
    --cc=ukleinek@kernel.org \
    --cc=wbg@kernel.org \
    --cc=will@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