From: Michael Schmitz <schmitzmic@gmail.com>
To: Eero Tamminen <oak@helsinkinet.fi>,
linux-m68k <linux-m68k@lists.linux-m68k.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH 1/2] m68k: Drop Atari EtherNAT support when it's not configured in
Date: Tue, 24 Sep 2024 13:03:05 +1200 [thread overview]
Message-ID: <4540348c-84f6-4993-97b5-f007771be444@gmail.com> (raw)
In-Reply-To: <20240922214821.16818-1-oak@helsinkinet.fi>
Eero,
thanks for your patch!
On 23/09/24 09:48, Eero Tamminen wrote:
> Not having it configured, but crash backtraces going through its IRQ
> handling code, is confusing (found while debugging issues in Atari
I don't see how backtraces could go through the EtherNAT interrupt code
- the interrupt only gets enabled if the hardware has been detected.
Maybe you meant you see the generic IRQ handling code called for the
EtherNAT's interrupt controller?
> emulation).
>
> Signed-off-by: Eero Tamminen <oak@helsinkinet.fi>
> ---
> arch/m68k/atari/ataints.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/arch/m68k/atari/ataints.c b/arch/m68k/atari/ataints.c
> index 0465444ce..fa189eeb7 100644
> --- a/arch/m68k/atari/ataints.c
> +++ b/arch/m68k/atari/ataints.c
> @@ -179,6 +179,7 @@ static struct irq_chip atari_mfptimer_chip = {
> };
>
>
> +#ifdef CONFIG_ATARI_ETHERNAT
I believe we now use
#if IS_ENABLED(CONFIG_ATARI_ETHERNAT)
but that's perhaps a matter of taste (CONFIG_ATARI_ETHERNAT can't take
the value 'm').
OK by me if it helps with your debugging ...
Cheers,
Michael
> /*
> * EtherNAT CPLD interrupt handling
> * CPLD interrupt register is at phys. 0x80000023
> @@ -251,6 +252,7 @@ static struct irq_chip atari_ethernat_chip = {
> .irq_enable = atari_ethernat_enable,
> .irq_disable = atari_ethernat_disable,
> };
> +#endif
>
> /*
> * void atari_init_IRQ (void)
> @@ -343,12 +345,13 @@ void __init atari_init_IRQ(void)
> stmfp_base.name, &stmfp_base))
> pr_err("Couldn't register %s interrupt\n", stmfp_base.name);
>
> +#ifdef CONFIG_ATARI_ETHERNAT
> /*
> * EtherNAT ethernet / USB interrupt handlers
> */
> -
> m68k_setup_irq_controller(&atari_ethernat_chip, handle_simple_irq,
> 139, 2);
> +#endif
> }
>
>
next prev parent reply other threads:[~2024-09-24 1:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-22 21:48 [PATCH 1/2] m68k: Drop Atari EtherNAT support when it's not configured in Eero Tamminen
2024-09-22 21:48 ` [PATCH 2/2] m68k: Set reasonable PSG port-A default value Eero Tamminen
2024-09-22 21:58 ` [PATCH 1/2] m68k: Drop Atari EtherNAT support when it's not configured in John Paul Adrian Glaubitz
2024-09-23 8:39 ` Eero Tamminen
2024-09-23 9:04 ` John Paul Adrian Glaubitz
2024-09-24 1:03 ` Michael Schmitz [this message]
2024-09-24 20:58 ` Eero Tamminen
2024-09-24 21:09 ` Andreas Schwab
2024-09-24 23:11 ` Eero Tamminen
2024-09-25 17:13 ` Andreas Schwab
2024-09-26 15:41 ` Eero Tamminen
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=4540348c-84f6-4993-97b5-f007771be444@gmail.com \
--to=schmitzmic@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=oak@helsinkinet.fi \
/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