mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] irq: Export symbol no_action()
Date: Tue, 4 Mar 2014 19:56:22 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.02.1403041951090.18573@ionos.tec.linutronix.de> (raw)
In-Reply-To: <1393955639.661016045@f378.i.mail.ru>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1710 bytes --]

On Tue, 4 Mar 2014, Alexander Shiyan wrote:
> +сс Arnd Bergmann
> 
> Вторник,  4 марта 2014, 16:46 +01:00 от Thomas Gleixner <tglx@linutronix.de>:
> > On Tue, 4 Mar 2014, Alexander Shiyan wrote:
> > 
> > > Вторник,  4 марта 2014, 12:05 +01:00 от Thomas Gleixner <tglx@linutronix.de>:
> > > > On Sat, 1 Mar 2014, Alexander Shiyan wrote:
> > > > 
> > > > > This will allow to use dummy IRQ handler no_action() from
> > > > > drivers compiled as module. For example, dummy handler is could
> > > > > be used for drivers that use ARM FIQ interrupts.
> > > > 
> > > > And why exactly requires a driver which uses ARM FIQ interrupts the
> > > > no_action implementation?
> > >
> >  
> > > FIQ Interrupt handler is not used in this function. In FIQ case this
> > > is just a dummy declaration. Real handler is assigned by using the
> > > set_fiq_handler().
> > 
> > Why do you need a dummy declaration at all?
> > 
> > set_fiq_handler() is completely detached from the generic interrupt
> > subsystem.
> 
> Some limitations of hardware, such as bit interleaving for normal and
> FIQ interrupts for mask/status registers, led to the implement single
> driver for interrupt handling.
> As a result, all interrupts can be described equally, and single mechanism
> is used for the request/free and enable/disable.
> Correct me if I'm wrong. Driver that implements it, resent several times
> and expect comments within 3 months [1], you are the only one person,
> Thomas, specified as maintainer for this subsystem.
> I repeat, if I'm wrong in the implementation, let's fix this.
> 
> [1]: http://marc.info/?l=linux-arm-kernel&m=139132855024699

Lemme find this and review it.

Thanks,

	tglx

      reply	other threads:[~2014-03-04 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-01  6:45 Alexander Shiyan
2014-03-04 11:05 ` Thomas Gleixner
2014-03-04 11:15   ` Alexander Shiyan
2014-03-04 15:46     ` Thomas Gleixner
2014-03-04 17:53       ` Alexander Shiyan
2014-03-04 18:56         ` Thomas Gleixner [this message]

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=alpine.DEB.2.02.1403041951090.18573@ionos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shc_work@mail.ru \
    /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®