From: Angelo Dureghello <adureghello@baylibre.com>
To: "Greg Ungerer" <gerg@linux-m68k.org>,
"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: Greg Ungerer <gerg@uclinux.org>,
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,
Angelo Dureghello <adureghello@baylibre.com>
Subject: [PATCH v4 08/11] m68k: stmark2: use ioport.h macros for resources
Date: Sun, 31 May 2026 17:26:01 +0200 [thread overview]
Message-ID: <20260531-wip-stmark2-dac-v4-8-7e65ab4215dd@baylibre.com> (raw)
In-Reply-To: <20260531-wip-stmark2-dac-v4-0-7e65ab4215dd@baylibre.com>
From: Angelo Dureghello <adureghello@baylibre.com>
Change resource declaration using DEFINE_RES_*() macros.
DEFINE_DMA_RES() is for a single dma channel, not a range, so used twice.
Also, some drivers assume IRQ resources are from index 1, so just to stay
uniform, moved IRQ resource at index 1.
Signed-off-by: Angelo Dureghello <adureghello@baylibre.com>
---
Changes in v2:
- none
Changes in v3:
- moved this patch (cleanup) before adding new resources
- moved IRQ resource to index pos 1
---
arch/m68k/coldfire/stmark2.c | 19 ++++---------------
1 file changed, 4 insertions(+), 15 deletions(-)
diff --git a/arch/m68k/coldfire/stmark2.c b/arch/m68k/coldfire/stmark2.c
index 9263b77bd09a..536252ccb87e 100644
--- a/arch/m68k/coldfire/stmark2.c
+++ b/arch/m68k/coldfire/stmark2.c
@@ -62,21 +62,10 @@ static struct fsl_dspi_platform_data dspi_spi0_info = {
};
static struct resource dspi_spi0_resource[] = {
- [0] = {
- .start = MCFDSPI_BASE0,
- .end = MCFDSPI_BASE0 + 0xFF,
- .flags = IORESOURCE_MEM,
- },
- [1] = {
- .start = 12,
- .end = 13,
- .flags = IORESOURCE_DMA,
- },
- [2] = {
- .start = MCF_IRQ_DSPI0,
- .end = MCF_IRQ_DSPI0,
- .flags = IORESOURCE_IRQ,
- },
+ DEFINE_RES_MEM(MCFDSPI_BASE0, 0x100),
+ DEFINE_RES_IRQ(MCF_IRQ_DSPI0),
+ DEFINE_RES_DMA(12),
+ DEFINE_RES_DMA(13),
};
static u64 stmark2_dspi_mask = DMA_BIT_MASK(32);
--
2.54.0
next prev parent reply other threads:[~2026-05-31 15:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 15:25 [PATCH v4 00/11] add mcf54415 DAC driver Angelo Dureghello
2026-05-31 15:25 ` [PATCH v4 01/11] m68k: mcf5441x: fix clocks numbering Angelo Dureghello
2026-05-31 15:25 ` [PATCH v4 02/11] m68k: mcf5441x: add clock for DAC channel 1 Angelo Dureghello
2026-05-31 15:25 ` [PATCH v4 03/11] m68k: mcf5441x: initialize DAC clocks by iio DAC driver name Angelo Dureghello
2026-05-31 15:25 ` [PATCH v4 04/11] m68k: defconfig: update stmark2 defconfig Angelo Dureghello
2026-05-31 15:51 ` Jonathan Cameron
2026-06-02 9:24 ` Andy Shevchenko
2026-06-02 9:40 ` Andy Shevchenko
2026-05-31 15:25 ` [PATCH v4 05/11] m68k: add DAC modules base addresses Angelo Dureghello
2026-05-31 15:25 ` [PATCH v4 06/11] m68k: mcf5441x: add CCM registers Angelo Dureghello
2026-05-31 15:26 ` [PATCH v4 07/11] m68k: mcf5441x: add CCR MISCCR2 bitfields Angelo Dureghello
2026-05-31 15:26 ` Angelo Dureghello [this message]
2026-05-31 15:26 ` [PATCH v4 09/11] m68k: stmark2: add mcf5441x DAC platform devices Angelo Dureghello
2026-06-02 9:27 ` Andy Shevchenko
2026-05-31 15:26 ` [PATCH v4 10/11] m68k: stmark2: enable DACs outputs Angelo Dureghello
2026-05-31 15:26 ` [PATCH v4 11/11] iio: dac: add mcf54415 DAC Angelo Dureghello
2026-05-31 16:37 ` Jonathan Cameron
2026-06-02 9:39 ` Andy Shevchenko
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=20260531-wip-stmark2-dac-v4-8-7e65ab4215dd@baylibre.com \
--to=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=gerg@linux-m68k.org \
--cc=gerg@uclinux.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