2013-01-12 22:44:42 +00:00
|
|
|
/*
|
|
|
|
* Copyright (c) 2012, Texas Instruments Incorporated - http://www.ti.com/
|
|
|
|
* All rights reserved.
|
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
* are met:
|
|
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer.
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
|
|
* documentation and/or other materials provided with the distribution.
|
|
|
|
*
|
|
|
|
* 3. Neither the name of the copyright holder nor the names of its
|
|
|
|
* contributors may be used to endorse or promote products derived
|
|
|
|
* from this software without specific prior written permission.
|
|
|
|
*
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
|
|
|
|
* ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
|
|
|
|
* LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
|
|
|
|
* FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
|
|
|
|
* COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
|
|
|
|
* INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
|
|
|
|
* (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
|
|
|
|
* SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
|
|
|
|
* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
|
|
|
|
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
|
|
|
|
* OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
*/
|
|
|
|
/**
|
|
|
|
* \addtogroup cc2538-gpio
|
|
|
|
* @{
|
|
|
|
*
|
|
|
|
* \file
|
|
|
|
* Implementation of the cc2538 GPIO controller
|
|
|
|
*/
|
|
|
|
#include "contiki.h"
|
|
|
|
#include "sys/energest.h"
|
|
|
|
#include "dev/leds.h"
|
|
|
|
#include "dev/gpio.h"
|
|
|
|
#include "dev/nvic.h"
|
|
|
|
#include "reg.h"
|
|
|
|
#include "lpm.h"
|
|
|
|
|
|
|
|
#include <string.h>
|
|
|
|
|
|
|
|
/**
|
|
|
|
* \brief Pointer to a function to be called when a GPIO interrupt is detected.
|
|
|
|
* Callbacks for Port A, Pins[0:7] are stored in positions [0:7] of this
|
|
|
|
* buffer, Port B callbacks in [8:15] and so on
|
|
|
|
*/
|
|
|
|
static gpio_callback_t gpio_callbacks[32];
|
|
|
|
/*---------------------------------------------------------------------------*/
|
|
|
|
void
|
|
|
|
gpio_register_callback(gpio_callback_t f, uint8_t port, uint8_t pin)
|
|
|
|
{
|
|
|
|
gpio_callbacks[(port << 3) + pin] = f;
|
|
|
|
}
|
|
|
|
/*---------------------------------------------------------------------------*/
|
|
|
|
/** \brief Run through all registered GPIO callbacks and invoke those
|
|
|
|
* associated with the \a port and the pins specified by \a mask
|
|
|
|
* \param mask Search callbacks associated with pins specified by this mask
|
|
|
|
* \param port Search callbacks associated with this port. Here, port is
|
|
|
|
* specified as a number between 0 and 3. Port A: 0, Port B: 1 etc */
|
|
|
|
void
|
|
|
|
notify(uint8_t mask, uint8_t port)
|
|
|
|
{
|
|
|
|
uint8_t i;
|
|
|
|
gpio_callback_t *f = &gpio_callbacks[port << 3];
|
|
|
|
|
|
|
|
for(i = 0; i < 8; i++) {
|
|
|
|
if(mask & (1 << i)) {
|
|
|
|
if((*f) != NULL) {
|
|
|
|
(*f)(port, i);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
f++;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
/*---------------------------------------------------------------------------*/
|
|
|
|
/** \brief Interrupt service routine for Port A */
|
|
|
|
void
|
|
|
|
gpio_port_a_isr()
|
|
|
|
{
|
|
|
|
lpm_exit();
|
|
|
|
|
2013-12-03 18:16:24 +00:00
|
|
|
ENERGEST_ON(ENERGEST_TYPE_IRQ);
|
|
|
|
|
Use additive offsets
OR-ing an offset to a base address instead of adding it is dangerous
because it can only work if the base address is aligned enough for the
offset.
Moreover, if the base address or the offset has a value unknown at
compile time, then the assembly instructions dedicated to 'base +
offset' addressing on most CPUs can't be emitted by the compiler because
this would require the alignment of the base address against the offset
to be known in order to optimize 'base | offset' into 'base + offset'.
In that case, the compiler has to emit more instructions in order to
compute 'base | offset' on most CPUs, e.g. on ARM, which means larger
binary size and slower execution.
Hence, replace all occurrences of 'base | offset' with 'base + offset'.
This must become a coding rule.
Here are the results for the cc2538-demo example:
- Compilation of uart_init():
* before:
REG(regs->base | UART_CC) = 0;
200b78: f446 637c orr.w r3, r6, #4032 ; 0xfc0
200b7c: f043 0308 orr.w r3, r3, #8
200b80: 2200 movs r2, #0
200b82: 601a str r2, [r3, #0]
* now:
REG(regs->base + UART_CC) = 0;
200b7a: 2300 movs r3, #0
200b7c: f8c4 3fc8 str.w r3, [r4, #4040] ; 0xfc8
- Size of the .text section:
* before: 0x4c7c
* now: 0x4c28
* saved: 84 bytes
Signed-off-by: Benoît Thébaudeau <benoit.thebaudeau.dev@gmail.com>
2015-03-28 16:16:17 +00:00
|
|
|
notify(REG(GPIO_A_BASE + GPIO_MIS), GPIO_A_NUM);
|
2013-01-12 22:44:42 +00:00
|
|
|
|
2013-11-15 18:57:44 +00:00
|
|
|
GPIO_CLEAR_INTERRUPT(GPIO_A_BASE, 0xFF);
|
2013-11-26 21:20:05 +00:00
|
|
|
GPIO_CLEAR_POWER_UP_INTERRUPT(GPIO_A_NUM, 0xFF);
|
2013-01-12 22:44:42 +00:00
|
|
|
|
|
|
|
ENERGEST_OFF(ENERGEST_TYPE_IRQ);
|
|
|
|
}
|
|
|
|
/*---------------------------------------------------------------------------*/
|
|
|
|
/** \brief Interrupt service routine for Port B */
|
|
|
|
void
|
|
|
|
gpio_port_b_isr()
|
|
|
|
{
|
|
|
|
lpm_exit();
|
|
|
|
|
2013-12-03 18:16:24 +00:00
|
|
|
ENERGEST_ON(ENERGEST_TYPE_IRQ);
|
|
|
|
|
Use additive offsets
OR-ing an offset to a base address instead of adding it is dangerous
because it can only work if the base address is aligned enough for the
offset.
Moreover, if the base address or the offset has a value unknown at
compile time, then the assembly instructions dedicated to 'base +
offset' addressing on most CPUs can't be emitted by the compiler because
this would require the alignment of the base address against the offset
to be known in order to optimize 'base | offset' into 'base + offset'.
In that case, the compiler has to emit more instructions in order to
compute 'base | offset' on most CPUs, e.g. on ARM, which means larger
binary size and slower execution.
Hence, replace all occurrences of 'base | offset' with 'base + offset'.
This must become a coding rule.
Here are the results for the cc2538-demo example:
- Compilation of uart_init():
* before:
REG(regs->base | UART_CC) = 0;
200b78: f446 637c orr.w r3, r6, #4032 ; 0xfc0
200b7c: f043 0308 orr.w r3, r3, #8
200b80: 2200 movs r2, #0
200b82: 601a str r2, [r3, #0]
* now:
REG(regs->base + UART_CC) = 0;
200b7a: 2300 movs r3, #0
200b7c: f8c4 3fc8 str.w r3, [r4, #4040] ; 0xfc8
- Size of the .text section:
* before: 0x4c7c
* now: 0x4c28
* saved: 84 bytes
Signed-off-by: Benoît Thébaudeau <benoit.thebaudeau.dev@gmail.com>
2015-03-28 16:16:17 +00:00
|
|
|
notify(REG(GPIO_B_BASE + GPIO_MIS), GPIO_B_NUM);
|
2013-01-12 22:44:42 +00:00
|
|
|
|
2013-11-15 18:57:44 +00:00
|
|
|
GPIO_CLEAR_INTERRUPT(GPIO_B_BASE, 0xFF);
|
2013-11-26 21:20:05 +00:00
|
|
|
GPIO_CLEAR_POWER_UP_INTERRUPT(GPIO_B_NUM, 0xFF);
|
2013-01-12 22:44:42 +00:00
|
|
|
|
|
|
|
ENERGEST_OFF(ENERGEST_TYPE_IRQ);
|
|
|
|
}
|
|
|
|
/*---------------------------------------------------------------------------*/
|
|
|
|
/** \brief Interrupt service routine for Port C */
|
|
|
|
void
|
|
|
|
gpio_port_c_isr()
|
|
|
|
{
|
|
|
|
lpm_exit();
|
|
|
|
|
2013-12-03 18:16:24 +00:00
|
|
|
ENERGEST_ON(ENERGEST_TYPE_IRQ);
|
|
|
|
|
Use additive offsets
OR-ing an offset to a base address instead of adding it is dangerous
because it can only work if the base address is aligned enough for the
offset.
Moreover, if the base address or the offset has a value unknown at
compile time, then the assembly instructions dedicated to 'base +
offset' addressing on most CPUs can't be emitted by the compiler because
this would require the alignment of the base address against the offset
to be known in order to optimize 'base | offset' into 'base + offset'.
In that case, the compiler has to emit more instructions in order to
compute 'base | offset' on most CPUs, e.g. on ARM, which means larger
binary size and slower execution.
Hence, replace all occurrences of 'base | offset' with 'base + offset'.
This must become a coding rule.
Here are the results for the cc2538-demo example:
- Compilation of uart_init():
* before:
REG(regs->base | UART_CC) = 0;
200b78: f446 637c orr.w r3, r6, #4032 ; 0xfc0
200b7c: f043 0308 orr.w r3, r3, #8
200b80: 2200 movs r2, #0
200b82: 601a str r2, [r3, #0]
* now:
REG(regs->base + UART_CC) = 0;
200b7a: 2300 movs r3, #0
200b7c: f8c4 3fc8 str.w r3, [r4, #4040] ; 0xfc8
- Size of the .text section:
* before: 0x4c7c
* now: 0x4c28
* saved: 84 bytes
Signed-off-by: Benoît Thébaudeau <benoit.thebaudeau.dev@gmail.com>
2015-03-28 16:16:17 +00:00
|
|
|
notify(REG(GPIO_C_BASE + GPIO_MIS), GPIO_C_NUM);
|
2013-01-12 22:44:42 +00:00
|
|
|
|
2013-11-15 18:57:44 +00:00
|
|
|
GPIO_CLEAR_INTERRUPT(GPIO_C_BASE, 0xFF);
|
2013-11-26 21:20:05 +00:00
|
|
|
GPIO_CLEAR_POWER_UP_INTERRUPT(GPIO_C_NUM, 0xFF);
|
2013-01-12 22:44:42 +00:00
|
|
|
|
|
|
|
ENERGEST_OFF(ENERGEST_TYPE_IRQ);
|
|
|
|
}
|
|
|
|
/*---------------------------------------------------------------------------*/
|
|
|
|
/** \brief Interrupt service routine for Port D */
|
|
|
|
void
|
|
|
|
gpio_port_d_isr()
|
|
|
|
{
|
|
|
|
lpm_exit();
|
|
|
|
|
2013-12-03 18:16:24 +00:00
|
|
|
ENERGEST_ON(ENERGEST_TYPE_IRQ);
|
|
|
|
|
Use additive offsets
OR-ing an offset to a base address instead of adding it is dangerous
because it can only work if the base address is aligned enough for the
offset.
Moreover, if the base address or the offset has a value unknown at
compile time, then the assembly instructions dedicated to 'base +
offset' addressing on most CPUs can't be emitted by the compiler because
this would require the alignment of the base address against the offset
to be known in order to optimize 'base | offset' into 'base + offset'.
In that case, the compiler has to emit more instructions in order to
compute 'base | offset' on most CPUs, e.g. on ARM, which means larger
binary size and slower execution.
Hence, replace all occurrences of 'base | offset' with 'base + offset'.
This must become a coding rule.
Here are the results for the cc2538-demo example:
- Compilation of uart_init():
* before:
REG(regs->base | UART_CC) = 0;
200b78: f446 637c orr.w r3, r6, #4032 ; 0xfc0
200b7c: f043 0308 orr.w r3, r3, #8
200b80: 2200 movs r2, #0
200b82: 601a str r2, [r3, #0]
* now:
REG(regs->base + UART_CC) = 0;
200b7a: 2300 movs r3, #0
200b7c: f8c4 3fc8 str.w r3, [r4, #4040] ; 0xfc8
- Size of the .text section:
* before: 0x4c7c
* now: 0x4c28
* saved: 84 bytes
Signed-off-by: Benoît Thébaudeau <benoit.thebaudeau.dev@gmail.com>
2015-03-28 16:16:17 +00:00
|
|
|
notify(REG(GPIO_D_BASE + GPIO_MIS), GPIO_D_NUM);
|
2013-01-12 22:44:42 +00:00
|
|
|
|
2013-11-15 18:57:44 +00:00
|
|
|
GPIO_CLEAR_INTERRUPT(GPIO_D_BASE, 0xFF);
|
2013-11-26 21:20:05 +00:00
|
|
|
GPIO_CLEAR_POWER_UP_INTERRUPT(GPIO_D_NUM, 0xFF);
|
2013-01-12 22:44:42 +00:00
|
|
|
|
|
|
|
ENERGEST_OFF(ENERGEST_TYPE_IRQ);
|
|
|
|
}
|
|
|
|
/*---------------------------------------------------------------------------*/
|
|
|
|
void
|
|
|
|
gpio_init()
|
|
|
|
{
|
|
|
|
memset(gpio_callbacks, 0, sizeof(gpio_callbacks));
|
|
|
|
}
|
|
|
|
/** @} */
|