nuttx/arch/arm/src/kinetis
2015-05-27 13:32:39 -06:00
..
chip.h
Kconfig Basic support for the Kinetis K20 architecture. Taken from PX4. This is the work of Jakob Odersky. 2015-05-26 15:03:35 -06:00
kinetis_adc.h
kinetis_aips.h
kinetis_allocateheap.c Make some file section headers more consistent with standard 2015-04-08 08:04:12 -06:00
kinetis_axbs.h
kinetis_clockconfig.c Make some file section headers more consistent with standard 2015-04-08 08:04:12 -06:00
kinetis_clrpend.c Make some file section headers more consistent with standard 2015-04-08 08:04:12 -06:00
kinetis_cmp.h
kinetis_cmt.h
kinetis_config.h A10: Add A10 configuration header file 2013-12-13 12:53:33 -06:00
kinetis_crc.h
kinetis_dac.h
kinetis_dma.h
kinetis_dmamux.h
kinetis_dspi.h
kinetis_enet.c All Ethernet drivers (again): Missed one place where arp_out() is called and neighber_out() needs to be called 2015-01-21 11:36:33 -06:00
kinetis_enet.h More trailing whilespace removal 2014-04-13 16:22:22 -06:00
kinetis_ewm.h
kinetis_flexbus.h
kinetis_flexcan.h
kinetis_fmc.h
kinetis_ftfl.h
kinetis_ftm.h Basic support for the Kinetis K20 architecture. Taken from PX4. This is the work of Jakob Odersky. 2015-05-26 15:03:35 -06:00
kinetis_gpio.h
kinetis_i2c.h
kinetis_i2s.h
kinetis_idle.c arch/: board function prototypes are now in include/nuttx/board.h. Remove from architecture header file; Add inclusion of nuttx/board.h to all files referencing board functions 2015-02-27 17:19:38 -06:00
kinetis_internal.h Make some file section headers more consistent with standard 2015-04-08 08:04:12 -06:00
kinetis_irq.c Make some file section headers more consistent with standard 2015-04-08 08:04:12 -06:00
kinetis_k20pinmux.h K20: Some preliminary pin definitions 2015-05-26 17:02:47 -06:00
kinetis_k40pinmux.h
kinetis_k60pinmux.h More trailing whilespace removal 2014-04-13 16:22:22 -06:00
kinetis_llwu.h
kinetis_lowputc.c Make some file section headers more consistent with standard 2015-04-08 08:04:12 -06:00
kinetis_lptmr.h
kinetis_mcg.h
kinetis_mcm.h
kinetis_memorymap.h Basic support for the Kinetis K20 architecture. Taken from PX4. This is the work of Jakob Odersky. 2015-05-26 15:03:35 -06:00
kinetis_mmcau.h
kinetis_mpu.h
kinetis_mpuinit.c Make some file section headers more consistent with standard 2015-04-08 08:04:12 -06:00
kinetis_mpuinit.h Rename CONFIG_NUTTX_KERNEL to CONFIG_BUILD_PROTECTED; Partially integrate new CONFIG_BUILD_KERNEL 2014-08-29 14:47:22 -06:00
kinetis_osc.h
kinetis_pdb.h
kinetis_pin.c
kinetis_pindma.c
kinetis_pingpio.c
kinetis_pinirq.c
kinetis_pinmux.h Basic support for the Kinetis K20 architecture. Taken from PX4. This is the work of Jakob Odersky. 2015-05-26 15:03:35 -06:00
kinetis_pit.h
kinetis_pmc.h
kinetis_port.h
kinetis_rngb.h
kinetis_rtc.h
kinetis_sdhc.c Two r's and only two r's in the word interrupt 2015-04-23 14:04:43 -06:00
kinetis_sdhc.h
kinetis_serial.c More missing semicolons after DEBUGASSERT 2015-05-27 13:32:39 -06:00
kinetis_sim.h
kinetis_slcd.h
kinetis_smc.h
kinetis_start.c Make some file section headers more consistent with standard 2015-04-08 08:04:12 -06:00
kinetis_timerisr.c Make some file section headers more consistent with standard 2015-04-08 08:04:12 -06:00
kinetis_tsi.h
kinetis_uart.h
kinetis_usbdcd.h
kinetis_usbotg.h
kinetis_userspace.c Rename CONFIG_NUTTX_KERNEL to CONFIG_BUILD_PROTECTED; Partially integrate new CONFIG_BUILD_KERNEL 2014-08-29 14:47:22 -06:00
kinetis_userspace.h Rename CONFIG_NUTTX_KERNEL to CONFIG_BUILD_PROTECTED; Partially integrate new CONFIG_BUILD_KERNEL 2014-08-29 14:47:22 -06:00
kinetis_vectors.S Basic support for the Kinetis K20 architecture. Taken from PX4. This is the work of Jakob Odersky. 2015-05-26 15:03:35 -06:00
kinetis_vrefv1.h
kinetis_wdog.c Make some file section headers more consistent with standard 2015-04-08 08:04:12 -06:00
kinetis_wdog.h
Make.defs There used to be two ways to pass parameters to new tasks, depending upon the configuration: Either (1) argv[] as created as an array with each string strdup'ed. Or (1) argv[] array and strings were created on the stack before the new task was started. Now, there is only one way, way (1). Way (2) might be slightly more compact, but this is not worth carry the complexity of two different ways of doing the same thing. 2014-09-01 15:39:34 -06:00