summaryrefslogtreecommitdiffstats
path: root/arch/arm/include/asm/arch-stm32f4/stm32.h
Commit message (Collapse)AuthorAgeFilesLines
* stm32: stm32f4: move flash driver to mtd driver locationVikas Manocha2016-03-261-22/+9
| | | | | | | Same flash driver can be used by other stm32 families like stm32f7. Better place for this driver would be mtd driver location. Signed-off-by: Vikas Manocha <vikas.manocha@st.com>
* gpio: stm32_gpio: move base addresses to the soc fileVikas Manocha2016-02-241-0/+10
| | | | | | | Base addresses for GPIOs could be different for different socs, this patch moves the base addresses from driver to the soc specific location. Signed-off-by: Vikas Manocha <vikas.manocha@st.com>
* stm32: Convert serial driver to DMKamil Lulko2015-12-121-1/+9
| | | | | | Signed-off-by: Kamil Lulko <kamil.lulko@gmail.com> Cc: Simon Glass <sjg@chromium.org> Reviewed-by: Simon Glass <sjg@chromium.org>
* arm: stm32f4: fix a bug when a random sector gets erasedVadzim Dambrouski2015-11-101-0/+1
| | | | | | | | | | Old sector number is not being cleared from FLASH_CR register. For example when first erased sector was 001 and then you want to erase sector 010, sector 011 gets erased instead. This patch clears old sector number from FLASH_CR register before a new one is written. Signed-off-by: Vadzim Dambrouski <pftbest@gmail.com>
* stm32f429: pass the device unique ID in DTBAntonio Borneo2015-07-271-0/+10
| | | | | | | | | | | | | | | | Read device unique ID and set environment variable "serial#". Value would then be passed to kernel through DTB. To read ID from DTB, kernel is required to have commit: 3f599875e5202986b350618a617527ab441bf206 (ARM: 8355/1: arch: Show the serial number from devicetree in cpuinfo) This commit is already mainline since v4.1-rc1. Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com> To: Albert Aribaud <albert.u.boot@aribaud.net> To: Tom Rini <trini@konsulko.com> To: Kamil Lulko <rev13@wp.pl> Cc: u-boot@lists.denx.de
* ARMv7M: Add STM32F4 supportrev13@wp.pl2015-04-221-0/+108
Signed-off-by: Kamil Lulko <rev13@wp.pl> Reviewed-by: Tom Rini <trini@konsulko.com>
OpenPOWER on IntegriCloud