From: Greg Ungerer <gerg@polyxeno.com>
To: "Angelo Dureghello" <adureghello@baylibre.com>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Uwe Kleine-König" <ukleinek@kernel.org>
Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
linux-pwm@vger.kernel.org
Subject: Re: [PATCH 1/2] m68k: mcf5441x: add PWM defines
Date: Mon, 5 Oct 2026 23:03:10 +1000 [thread overview]
Message-ID: <d5e415dc-f5f2-4b23-a9f4-dfd2ba31f099@polyxeno.com> (raw)
In-Reply-To: <20261005-wip-bl-stmark2-pwm-v1-1-168b9dc653f2@baylibre.com>
Hi Angelo,
On 5/10/26 20:06, Angelo Dureghello wrote:
> From: Angelo Dureghello <adureghello@baylibre.com>
>
> Add PWM defines for the mcf5441x family.
>
> Signed-off-by: Angelo Dureghello <adureghello@baylibre.com>
Looks good to me, I will apply to the m68knommu git tree.
Thanks
Greg
> ---
> arch/m68k/include/asm/m5441xsim.h | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/m68k/include/asm/m5441xsim.h b/arch/m68k/include/asm/m5441xsim.h
> index ea01c7753b7b..aa925fac87f4 100644
> --- a/arch/m68k/include/asm/m5441xsim.h
> +++ b/arch/m68k/include/asm/m5441xsim.h
> @@ -375,4 +375,11 @@
> #define MCF_IRQ_BOFF1 (MCFINT1_VECBASE + MCFINT1_FLEXCAN1_BOFF)
> #define MCF_IRQ_ERR1 (MCFINT1_VECBASE + MCFINT1_FLEXCAN1_ERR)
>
> +/*
> + * PWM module
> + */
> +#define MCFPWM_BASE 0xec088000
> +#define MCFPWM_SIZE 0x150
> +#define MCFPWM_SUB_SIZE 0x50
> +
> #endif /* m5441xsim_h */
>
next prev parent reply other threads:[~2026-10-05 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 10:06 [PATCH 0/2] drivers: pwm: add mcf5441X mcPWM support Angelo Dureghello
2026-10-05 10:06 ` [PATCH 1/2] m68k: mcf5441x: add PWM defines Angelo Dureghello
2026-10-05 13:03 ` Greg Ungerer [this message]
2026-10-05 10:06 ` [PATCH 2/2] drivers: pwm: add mcf54415 mcPWM support 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=d5e415dc-f5f2-4b23-a9f4-dfd2ba31f099@polyxeno.com \
--to=gerg@polyxeno.com \
--cc=adureghello@baylibre.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-pwm@vger.kernel.org \
--cc=ukleinek@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
all inboxes | Powered by JetHome®