Home
last modified time | relevance | path

Searched refs:mraa_init (Results 1 – 15 of 15) sorted by relevance

/hardware/bsp/intel/peripheral/libmraa/api/mraa/
Dcommon.h74 mraa_result_t mraa_init();
79 mraa_result_t mraa_init() __attribute__((constructor));
Dcommon.hpp58 return (Result) mraa_init(); in init()
/hardware/bsp/intel/peripheral/libmraa/examples/
Dgpio_read6.c33 mraa_init(); in main()
Dcycle-pwm3.c32 mraa_init(); in main()
Disr_pin6.c41 mraa_init(); in main()
Dspi_mcp4261.c32 mraa_init(); in main()
Dblink-io.c59 mraa_init(); in main()
Di2c_HMC5883L.c81 mraa_init(); in main()
/hardware/bsp/intel/peripheral/examples/mraa/gpio_output/
Dledflasher_mraa.cpp32 mraa_init(); in main()
DOutputGPIO.cpp107 mraa_init(); in main()
/hardware/bsp/intel/peripheral/libmraa/docs/
Dinternals.md45 initialised during mraa_init(). The pinmap file in
138 mraa_init() needs to be called in order to initialise the platform files or
140 mraa_init on library load. This means that it is not possible to stop this
142 mraa_init(). This feature is supported by most sane compilers and libcs but you
144 someone doing that. mraa_init() can be called multiple times if you feel like
147 In the SWIG modules mraa_init() is called during the %init stage of the module
148 loading. This is simply to avoid mraa_init() running 'too' early, though I've
/hardware/bsp/intel/peripheral/libmraa/src/java/
Dmraajava.i73 mraa_init(); in JNI_OnLoad()
/hardware/bsp/intel/peripheral/libmraa/src/python/
Dmraa.i153 mraa_init();
/hardware/bsp/intel/peripheral/libmraa/src/javascript/
Dmraajs.i138 mraa_init();
/hardware/bsp/intel/peripheral/libmraa/src/
Dmraa.c82 mraa_init() in mraa_init() function