From: Greg Ungerer <gerg@linux-m68k.org>
To: "Angelo Dureghello" <adureghello@baylibre.com>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Steven King" <sfking@fdwdc.com>, "Arnd Bergmann" <arnd@arndb.de>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>
Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH v3 03/11] m68k: mcf5441x: initialize DAC clocks by iio DAC driver name
Date: Sun, 31 May 2026 23:15:43 +1000 [thread overview]
Message-ID: <ecf346d5-a65f-4507-b277-40e75ae89442@linux-m68k.org> (raw)
In-Reply-To: <20260522-wip-stmark2-dac-v3-3-16be0ad35a67@baylibre.com>
Hi Angelo,
On 23/5/26 07:20, Angelo Dureghello wrote:
> From: Angelo Dureghello <adureghello@baylibre.com>
>
> Later in this patchset, the mcf54415 DAC driver is added.
> Considering some other different ColdFire cpu DACs exists, the DAC driver
> is named as "mcf54415_dac", related to the mcf5441x family SoCs with
> DACs (mcf54415/6/7/8).
>
> So updating DAC CLKDEDV_INIT with proper driver name.
>
> Signed-off-by: Angelo Dureghello <adureghello@baylibre.com>
> ---
> Changes in v2:
> - none
> Changes in v3
> - roll back clock names as they was originally
> ---
> arch/m68k/coldfire/m5441x.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/m68k/coldfire/m5441x.c b/arch/m68k/coldfire/m5441x.c
> index 5b5e09ecf487..b02ca2eb55a4 100644
> --- a/arch/m68k/coldfire/m5441x.c
> +++ b/arch/m68k/coldfire/m5441x.c
> @@ -106,8 +106,8 @@ static struct clk_lookup m5411x_clk_lookup[] = {
> CLKDEV_INIT("mcfpit.3", NULL, &__clk_0_35),
> CLKDEV_INIT("mcfeport.0", NULL, &__clk_0_36),
> CLKDEV_INIT("mcfadc.0", NULL, &__clk_0_37),
> - CLKDEV_INIT("mcfdac.0", NULL, &__clk_0_38),
> - CLKDEV_INIT("mcfdac.1", NULL, &__clk_0_39),
> + CLKDEV_INIT("mcf54415_dac.0", NULL, &__clk_0_38),
> + CLKDEV_INIT("mcf54415_dac.1", NULL, &__clk_0_39),
I thought after the last discussion on this that we would not change these
clock names?
Regards
Greg
> CLKDEV_INIT("mcfrtc.0", NULL, &__clk_0_42),
> CLKDEV_INIT("mcfsim.0", NULL, &__clk_0_43),
> CLKDEV_INIT("mcfusb-otg.0", NULL, &__clk_0_44),
>
next prev parent reply other threads:[~2026-05-31 13:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 21:20 [PATCH v3 00/11] add mcf54415 DAC driver Angelo Dureghello
2026-05-22 21:20 ` [PATCH v3 01/11] m68k: mcf5441x: fix clocks numbering Angelo Dureghello
2026-05-22 21:20 ` [PATCH v3 02/11] m68k: mcf5441x: add clock for DAC channel 1 Angelo Dureghello
2026-05-22 21:20 ` [PATCH v3 03/11] m68k: mcf5441x: initialize DAC clocks by iio DAC driver name Angelo Dureghello
2026-05-31 13:15 ` Greg Ungerer [this message]
2026-05-31 15:37 ` Angelo Dureghello
2026-05-22 21:20 ` [PATCH v3 04/11] m68k: defconfig: update stmark2 defconfig Angelo Dureghello
2026-05-22 21:20 ` [PATCH v3 05/11] m68k: add DAC modules base addresses Angelo Dureghello
2026-05-22 21:20 ` [PATCH v3 06/11] m68k: mcf5441x: add CCM registers Angelo Dureghello
2026-05-22 21:20 ` [PATCH v3 07/11] m68k: mcf5441x: add CCR MISCCR2 bitfields Angelo Dureghello
2026-05-22 21:20 ` [PATCH v3 08/11] m68k: stmark2: use ioport.h macros for resources Angelo Dureghello
2026-05-22 21:20 ` [PATCH v3 09/11] m68k: stmark2: add mcf5441x DAC platform devices Angelo Dureghello
2026-05-22 21:20 ` [PATCH v3 10/11] m68k: stmark2: enable DACs outputs Angelo Dureghello
2026-05-22 21:20 ` [PATCH v3 11/11] iio: dac: add mcf54415 DAC Angelo Dureghello
2026-05-26 13:30 ` Jonathan Cameron
2026-05-26 21:25 ` Angelo Dureghello
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=ecf346d5-a65f-4507-b277-40e75ae89442@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=adureghello@baylibre.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andy@kernel.org \
--cc=arnd@arndb.de \
--cc=dlechner@baylibre.com \
--cc=geert@linux-m68k.org \
--cc=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=nuno.sa@analog.com \
--cc=sfking@fdwdc.com \
/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