[PATCH 04/41] rtems: Add rtems_interrupt_cause_on()

Sebastian Huber sebastian.huber at embedded-brains.de
Wed Jul 21 17:50:02 UTC 2021


On 21/07/2021 19:43, Gedare Bloom wrote:
> Before we bake this into the API forever, I want to ask if "cause" is
> the right word to use here? Often, "interrupt cause" is thought of as
> a noun to mean what caused the interrupt, while the verb is usually
> "raise" or post, trigger, etc. Because "cause" is both a noun and a
> verb that mean something in this context, it may be better to use a
> different verb. English is pretty much terrible.
> 
> I don't have a major problem with sticking to "cause" but thought I'd
> bring this up.

I just used the existing (not implemented) directive. We can also use 
rtems_interrupt_raise() (similar to the signal raise()). In this case we 
should remove rtems_interrupt_cause().

-- 
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/


More information about the devel mailing list