/****************************************************************************** * Filename: gpio_doc.h * * Copyright (c) 2022 Texas Instruments Incorporated * * 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 gpio_api //! @{ //! \section sec_gpio Introduction //! //! The GPIO module allows software to control the pins of the device directly. //! //! The System CPU can access the GPIO module to read the value of any DIO of the device and if the IOC //! module has been configured such that one or more DIOs are GPIO controlled (software controlled) the //! System CPU can write these DIOs through the GPIO module. //! //! The IOC module can also be configured to generate events on edge detection and these events can be //! read and cleared in the GPIO module by the System CPU. //! //! \section sec_gpio_api API //! //! The API functions can be grouped like this: //! //! Set and get direction of DIO (output enable): //! - \ref GPIOSetOutputEnableDio() //! - \ref GPIOSetOutputEnableMultiDio() //! - \ref GPIOGetOutputEnableDio() //! - \ref GPIOGetOutputEnableMultiDio() //! //! Write DIO (requires IOC to be configured for GPIO usage): //! - \ref GPIOWriteDio() //! - \ref GPIOWriteMultiDio() //! //! Set, clear, or toggle DIO (requires IOC to be configured for GPIO usage): //! - \ref GPIOSetDio() //! - \ref GPIOSetMultiDio() //! - \ref GPIOClearDio() //! - \ref GPIOClearMultiDio() //! - \ref GPIOToggleDio() //! - \ref GPIOToggleMultiDio() //! //! Read DIO (even if IOC is NOT configured for GPIO usage; however, the DIO must be configured for input enable in //! IOC): //! - \ref GPIOReadDio() //! - \ref GPIOReadMultiDio() //! //! Read or clear events (even if IOC is NOT configured for GPIO usage; however, the DIO must be configured for input //! enable in IOC): //! - \ref GPIOGetEventDio() //! - \ref GPIOGetEventMultiDio() //! - \ref GPIOClearEventDio() //! - \ref GPIOClearEventMultiDio() //! //! @}