sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Two r's and only two r's in the word interrupt

Browse Source
This commit is contained in:
Gregory Nutt 2015-04-23 14:04:43 -06:00
parent 770b7f9e3c
commit 49415e7cc8
20 changed files with 21 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
configs/arduino-due/include/board.h
View File

@ -191,7 +191,7 @@
/* Thus if LED L is statically on, NuttX has successfully booted and is,
* apparently, running normmally. If LED RX is glowing, then NuttX is
* handling interupts (and also signals and assertions). If TX is flashing
* handling interrupts (and also signals and assertions). If TX is flashing
* at approximately 2Hz, then a fatal error has been detected and the system
*/

2
configs/arduino-due/src/arduino-due.h
View File

@ -86,7 +86,7 @@
*
* Thus if LED L is statically on, NuttX has successfully booted and is,
* apparently, running normmally. If LED RX is glowing, then NuttX is
* handling interupts (and also signals and assertions). If TX is flashing
* handling interrupts (and also signals and assertions). If TX is flashing
* at approximately 2Hz, then a fatal error has been detected and the system
*/

2
configs/arduino-due/src/sam_autoleds.c
View File

@ -88,7 +88,7 @@
*
* Thus if LED L is statically on, NuttX has successfully booted and is,
* apparently, running normmally. If LED RX is glowing, then NuttX is
* handling interupts (and also signals and assertions). If TX is flashing
* handling interrupts (and also signals and assertions). If TX is flashing
* at approximately 2Hz, then a fatal error has been detected and the system
*/

2
configs/cloudctrl/README.txt
View File

@ -441,7 +441,7 @@ events as follows:
* If LED1, LED2, LED3 are statically on, then NuttX probably failed to boot
and these LEDs will give you some indication of where the failure was
** The normal state is LED1 ON and LED1 faintly glowing. This faint glow
is because of timer interupts that result in the LED being illuminated
is because of timer interrupts that result in the LED being illuminated
on a small proportion of the time.
*** LED2 may also flicker normally if signals are processed.
**** LED4 may not be available if RS-485 is also used. For RS-485, it will

2
configs/hymini-stm32v/README.txt
View File

@ -262,7 +262,7 @@ They are encoded as follows:
LED_IDLE STM32 is is sleep mode (Optional, not used)
* If Nuttx starts correctly, normal state is to have LED1 on and LED2 off.
** LED1 is turned off during interrrupt.
** LED1 is turned off during interrupt.
*** LED2 is turned on during signal handler.
RTC

2
configs/lincoln60/src/lpc17_buttons.c
View File

@ -69,7 +69,7 @@ static const uint16_t g_buttoncfg[BOARD_NUM_BUTTONS] =
LINCOLN60_BUT1
};
/* This array defines all of the interupt handlers current attached to
/* This array defines all of the interrupt handlers current attached to
* button events.
*/

2
configs/olimex-lpc1766stk/src/lpc17_buttons.c
View File

@ -70,7 +70,7 @@ static const uint16_t g_buttoncfg[BOARD_NUM_BUTTONS] =
LPC1766STK_UP, LPC1766STK_DOWN, LPC1766STK_LEFT, LPC1766STK_RIGHT
};
/* This array defines all of the interupt handlers current attached to
/* This array defines all of the interrupt handlers current attached to
* button events.
*/

2
configs/open1788/README.txt
View File

@ -36,7 +36,7 @@ LEDs
LED_HEAPALLOCATE ON OFF OFF OFF
LED_IRQSENABLED OFF ON OFF OFF
LED_STACKCREATED ON ON OFF OFF
LED_INIRQ LED3 glows, on while in interupt
LED_INIRQ LED3 glows, on while in interrupt
LED_SIGNAL LED3 glows, on while in signal handler
LED_ASSERTION LED3 glows, on while in assertion
LED_PANIC LED3 Flashes at 2Hz

2
configs/open1788/include/board.h
View File

@ -250,7 +250,7 @@
#define LED_HEAPALLOCATE 1 /* ON OFF OFF OFF */
#define LED_IRQSENABLED 2 /* OFF ON OFF OFF */
#define LED_STACKCREATED 3 /* ON ON OFF OFF */
#define LED_INIRQ 4 /* LED3 glows, on while in interupt */
#define LED_INIRQ 4 /* LED3 glows, on while in interrupt */
#define LED_SIGNAL 4 /* LED3 glows, on while in signal handler */
#define LED_ASSERTION 4 /* LED3 glows, on while in assertion */
#define LED_PANIC 4 /* LED3 Flashes at 2Hz */

2
configs/open1788/src/lpc17_autoleds.c
View File

@ -75,7 +75,7 @@
* LED_HEAPALLOCATE 1 ON OFF OFF OFF
* LED_IRQSENABLED 2 OFF ON OFF OFF
* LED_STACKCREATED 3 ON ON OFF OFF
* LED_INIRQ 4 LED3 glows, on while in interupt
* LED_INIRQ 4 LED3 glows, on while in interrupt
* LED_SIGNAL 4 LED3 glows, on while in signal handler
* LED_ASSERTION 4 LED3 glows, on while in assertion
* LED_PANIC 4 LED3 Flashes at 2Hz

2
configs/open1788/src/lpc17_buttons.c
View File

@ -89,7 +89,7 @@ static const lpc17_pinset_t g_buttoncfg[BOARD_NUM_BUTTONS] =
GPIO_JOY_B, GPIO_JOY_C, GPIO_JOY_D, GPIO_JOY_CTR
};
/* This array defines all of the interupt handlers current attached to
/* This array defines all of the interrupt handlers current attached to
* button events.
*/

2
configs/open1788/src/open1788.h
View File

@ -103,7 +103,7 @@
#define GPIO_JOY_D (GPIO_INTBOTH | GPIO_PULLUP | GPIO_PORT2 | GPIO_PIN19)
#define GPIO_JOY_CTR (GPIO_INTBOTH | GPIO_PULLUP | GPIO_PORT0 | GPIO_PIN14)
/* IRQ numbers for the buttons that do support interrrupts */
/* IRQ numbers for the buttons that do support interrupts */
#define GPIO_USER2_IRQ LPC17_IRQ_P2p22
#define GPIO_USER3_IRQ LPC17_IRQ_P0p10

2
configs/pic32mx7mmb/src/pic32_touchscreen.c
View File

@ -312,7 +312,7 @@ static void tc_adc_sample(int pin)
putreg32(ADC_CON3_ADCS(6) | ADC_CON3_SAMC(0), PIC32MX_ADC_CON3);
/* No interrrupts, no scan, internal voltage reference */
/* No interrupts, no scan, internal voltage reference */
putreg32(ADC_CON2_VCFG_AVDDAVSS, PIC32MX_ADC_CON2);

2
configs/sam3u-ek/README.txt
View File

@ -262,7 +262,7 @@ LEDs
* If LED1 and LED2 are statically on, then NuttX probably failed to boot
and these LEDs will give you some indication of where the failure was
** The normal state is LED0=OFF, LED2=ON and LED1 faintly glowing. This faint
glow is because of timer interupts that result in the LED being illuminated
glow is because of timer interrupts that result in the LED being illuminated
on a small proportion of the time.
*** LED2 may also flicker normally if signals are processed.

2
configs/shenzhou/README.txt
View File

@ -458,7 +458,7 @@ events as follows:
* If LED1, LED2, LED3 are statically on, then NuttX probably failed to boot
and these LEDs will give you some indication of where the failure was
** The normal state is LED1 ON and LED1 faintly glowing. This faint glow
is because of timer interupts that result in the LED being illuminated
is because of timer interrupts that result in the LED being illuminated
on a small proportion of the time.
*** LED2 may also flicker normally if signals are processed.
**** LED4 may not be available if RS-485 is also used. For RS-485, it will

2
configs/spark/README.txt
View File

@ -499,7 +499,7 @@ Buttons and LEDs
* If LED2, LED3, LED4 are statically on, then NuttX probably failed to boot
and these LEDs will give you some indication of where the failure was
** The normal state is LED4 ON and LED2 faintly glowing. This faint glow
is because of timer interupts that result in the LED being illuminated
is because of timer interrupts that result in the LED being illuminated
on a small proportion of the time.
*** LED3 may also flicker normally if signals are processed.

4
configs/stm3210e-eval/README.txt
View File

@ -340,7 +340,7 @@ events as follows:
* If LED1, LED2, LED3 are statically on, then NuttX probably failed to boot
and these LEDs will give you some indication of where the failure was
** The normal state is LED3 ON and LED1 faintly glowing. This faint glow
is because of timer interupts that result in the LED being illuminated
is because of timer interrupts that result in the LED being illuminated
on a small proportion of the time.
*** LED2 may also flicker normally if signals are processed.
@ -1048,7 +1048,7 @@ Where <subdir> is one of the following:
CONFIG_PM_BUTTONS=y
CONFIG_PM_BUTTONS enables button support for PM testing. Buttons can
drive EXTI interrupts and EXTI interrrupts can be used to wakeup for
drive EXTI interrupts and EXTI interrupts can be used to wakeup for
certain reduced power modes (STOP mode). The use of the buttons here
is for PM testing purposes only; buttons would normally be part the
application code and CONFIG_PM_BUTTONS would not be defined.

2
configs/stm3220g-eval/README.txt
View File

@ -323,7 +323,7 @@ events as follows:
* If LED1, LED2, LED3 are statically on, then NuttX probably failed to boot
and these LEDs will give you some indication of where the failure was
** The normal state is LED3 ON and LED1 faintly glowing. This faint glow
is because of timer interupts that result in the LED being illuminated
is because of timer interrupts that result in the LED being illuminated
on a small proportion of the time.
*** LED2 may also flicker normally if signals are processed.

2
configs/twr-k60n512/README.txt
View File

@ -281,7 +281,7 @@ as follows:
* If LED1, LED2, LED3 are statically on, then NuttX probably failed to boot
and these LEDs will give you some indication of where the failure was
** The normal state is LED3 ON and LED1 faintly glowing. This faint glow
is because of timer interupts that result in the LED being illuminated
is because of timer interrupts that result in the LED being illuminated
on a small proportion of the time.
*** LED2 may also flicker normally if signals are processed.

2
configs/twr-k60n512/src/k60_buttons.c
View File

@ -162,7 +162,7 @@ xcpt_t board_button_irq(int id, xcpt_t irqhandler)
oldhandler = knetis_pinirqattach(pinset, irqhandler);
/* Then make sure that interupts are enabled on the pin */
/* Then make sure that interrupts are enabled on the pin */
kinetis_pindmaenable(pinset);
return oldhandler;