All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: [PATCH] m68k/irq - use polled IRQ flag for MFP timer cascaded interrupts
Date: Mon, 23 Dec 2013 22:23:42 +1300	[thread overview]
Message-ID: <f61c2f6c42756c3bcd905f901767893a@gmail.com> (raw)
In-Reply-To: <CAMuHMdXwXi6jeKz0TJPm9iHBBC8vfXrJnG19+Vogq32zr79zmw@mail.gmail.com>

Geert,

forgot to reply to all last time ...

>>
>
> Missing SoB.

Sorry, please add:

Signed-off-By: Michael Schmitz <schmitz@debian.org>

>
>> ---
>>  arch/m68k/atari/ataints.c |    5 ++++-
>>  1 files changed, 4 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/m68k/atari/ataints.c b/arch/m68k/atari/ataints.c
>> index 90f7a48..3e73a63 100644
>> --- a/arch/m68k/atari/ataints.c
>> +++ b/arch/m68k/atari/ataints.c
>> @@ -330,9 +330,12 @@ void __init atari_init_IRQ(void)
>>         sound_ym.rd_data_reg_sel = 7;
>>         sound_ym.wd_data = 0xff;
>>
>> -       m68k_setup_irq_controller(&atari_mfptimer_chip, 
>> handle_polled_irq,
>> +       m68k_setup_irq_controller(&atari_mfptimer_chip, 
>> handle_simple_irq,
>>                                   IRQ_MFP_TIMER1, 8);
>>
>> +       irq_set_status_flags(IRQ_MFP_TIMER1, IRQ_IS_POLLED);
>> +       irq_set_status_flags(IRQ_MFP_TIMER2, IRQ_IS_POLLED);
>
> Why do you set this flag for timer 2, too? Timer D is timer1, right?
>
>

The  IRQ_MFP_TIMER1 and IRQ_MFP_TIMER2 interrupts are the multiplexed 
ones. These are the only ones currently used by EtherNEC and NetUSBee 
(if someone wants to use IRQ_MFP_TIMER3 for another piece of broken 
hardware, this one would need the same flag added).

IRQ_MFP_TIMD is the real hardware interrupt driving IRQ_MFP_TIMER1 and 
IRQ_MFP_TIMER2. It always returns IRQ_HANDLED so no flag required.

Cheers,

	Michael


>
>> +
>>         /* prepare timer D data for use as poll interrupt */
>>         /* set Timer D data Register - needs to be > 0 */
>>         st_mfp.tim_dt_d = 254;  /* < 100 Hz */
>
> Gr{oetje,eeting}s,
>
>                         Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- 
> geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a 
> hacker. But
> when I'm talking to journalists I just say "programmer" or something 
> like that.
>                                 -- Linus Torvalds
> --
> To unsubscribe from this list: send the line "unsubscribe linux-m68k" 
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-12-23  9:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1387611538-18305-1-git-send-email-schmitz@debian.org>
     [not found] ` <1387611538-18305-2-git-send-email-schmitz@debian.org>
2013-12-22 10:19   ` Fwd: [PATCH] m68k/irq - use polled IRQ flag for MFP timer cascaded interrupts Geert Uytterhoeven
2013-12-22 11:15     ` Andreas Schwab
2013-12-22 11:51       ` Geert Uytterhoeven
2013-12-23  9:16       ` Michael Schmitz
2013-12-23 11:30         ` Andreas Schwab
2013-12-23 23:36           ` Michael Schmitz
2013-12-22 11:53     ` Geert Uytterhoeven
2013-12-23  9:23       ` Michael Schmitz [this message]
2014-01-11  1:01 Michael Schmitz
2014-01-11 10:39 ` Geert Uytterhoeven

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=f61c2f6c42756c3bcd905f901767893a@gmail.com \
    --to=schmitzmic@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@lists.linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.