From: Lukasz Majewski <l.majewski@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] interrupt handling
Date: Mon, 24 Jun 2013 14:23:56 +0200 [thread overview]
Message-ID: <20130624142356.448f15ee@amdc308.digital.local> (raw)
In-Reply-To: <51C58631.60803@denx.de>
Hi Stefan,
> Hi Albert,
>
> On 22.06.2013 11:58, Albert ARIBAUD wrote:
> > From time to time there is discussion about the need for proper
> > interrupt support in U-Boot.
> >
> > Right now, the only thing left in the source code which remotely
> > looks like interrupt support is a few code sections compiled
> > conditionally under CONFIG_USE_IRQ, and it does not constitute a
> > good approach to interrupt support, if only for the following
> > reasons:
> >
> > - CONFIG_USE_IRQ is very general and imprecise as far as overall
> > meaning goes. It does not say "allow drivers to use IRQs", or
> > "IRQs are provided by supporting this specific interrupt
> > controller", or "this driver requires IRQs to work". It does not
> > help us either that the option was never documented...
> >
> > - CONFIG_USE_IRQ is, OTOH, very specific as far as interrupt types
> > go. IRQ is an acronym known in ARM for a specific type of
> > interrupt, but ARM also knows FIQ. IRQ may have a different meaning
> > for another architecture, and each platform has its own
> > classification and attributes for interrupts.
> >
> > - no API is defined for registering interrupt controller or
> > interrupt client drivers.
> >
> > But the worst part is, CONFIG_USE_IRQ is never *ever* defined. :)
> >
> > So I am tempted to start this RFC with a first question: do we
> > *need* interrupts in the first place, and if we do, do we need an
> > organized interrupts subsystem or do we keep an ad hoc approach?
>
> I know that interrupts are currently used on PowerPC for the PPC4xx
> ethernet driver (emac). This could be reworked to of cause, but I just
> wanted to point this out.
>
> I have no idea if interrupts are used on any ARM platform though.
For me it looks, like a fundamental decision to support interrupts on
ARM. Do we need them - it's an open question. Does anyone have good use
case for it?
On the other hand I remember that Marek was struggling to introduce new
driver model. It was also a fundamental change and as fair as I know we
don't have it yet finished.
Anyway it is a good discussion topic :-)
>
> Thanks,
> Stefan
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
--
Best regards,
Lukasz Majewski
Samsung R&D Institute Poland (SRPOL) | Linux Platform Group
next prev parent reply other threads:[~2013-06-24 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-22 9:58 [U-Boot] [RFC] interrupt handling Albert ARIBAUD
2013-06-22 11:10 ` Stefan Roese
2013-06-24 12:23 ` Lukasz Majewski [this message]
2013-06-24 9:46 ` [U-Boot] [RFC] ARM interrupt handling - was: " Wolfgang Denk
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=20130624142356.448f15ee@amdc308.digital.local \
--to=l.majewski@samsung.com \
--cc=u-boot@lists.denx.de \
/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