diff options
| author | Hauke Mehrtens <hauke@hauke-m.de> | 2017-08-20 00:18:10 +0200 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2017-09-01 11:33:22 +0100 |
| commit | 1a41aa1376df9e24d0c760df1a6f59765316c457 (patch) | |
| tree | 6cc38e05602ac701031e7a0e47f51334d8411d07 /MAINTAINERS | |
| parent | 5771a8c08880cdca3bfb4a3fc6d309d6bba20877 (diff) | |
| download | linux-stable-1a41aa1376df9e24d0c760df1a6f59765316c457.tar.gz linux-stable-1a41aa1376df9e24d0c760df1a6f59765316c457.tar.bz2 linux-stable-1a41aa1376df9e24d0c760df1a6f59765316c457.zip | |
spi: spi-falcon: drop check of boot select
Do not check which flash type the SoC was booted from before
using this driver. Assume that the device tree is correct and use this
driver when it was added to device tree. This also removes a build
dependency to the SoC code.
All device trees I am aware of only have one correct flash device entry
in it. The device tree is anyway bundled with the kernel in all systems
using device tree I know of.
The boot mode can be specified with some pin straps and will select the
flash type the rom code will boot from. One SPI, NOR or NAND flash chip
can be connect to the EBU and used to load the first stage boot loader
from.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Cc: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org
Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions