New API directives to enable/disable interrupt vectors

[Joel Sherrill]

On Thu, Jun 17, 2021 at 12:40 AM Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> On 16/06/2021 20:36, Gedare Bloom wrote:
> > Looks like the existing irq-extension.h uses 'vector', so
> > rtems_interrupt_disable_vector() is a possibility, or else
> > rtems_interrupt_controller_disable_vector() is more wordy but if we
> > want to treat 'interrupt controller' as its own category of API
> > separate from 'interrupt'.
>
> Yes, mixing "vector" into the name a good idea.  What about
> rtems_interrupt_vector_enable() and rtems_interrupt_vector_disable()?
>

I like this. Interrupt vector refers to the source not the hardware being
manipulated.

>
> I am not that fond of using "interrupt controller" since I don't want to
> change the existing API and it would result in very long directive names.
>

I know they are usually called interrupt controllers but you are right,
it is longer and implies a technology.

--joel

>
> --
> embedded brains GmbH
> Herr Sebastian HUBER
> Dornierstr. 4
> 82178 Puchheim
> Germany
> email: sebastian.huber at embedded-brains.de
> phone: +49-89-18 94 741 - 16
> fax:   +49-89-18 94 741 - 08
>
> Registergericht: Amtsgericht München
> Registernummer: HRB 157899
> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
> Unsere Datenschutzerklärung finden Sie hier:
> https://embedded-brains.de/datenschutzerklaerung/
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20210617/e6f5f46e/attachment-0001.html>