summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | ARM: i.MX6ul: Add SoC specific lowlevel_init functionSascha Hauer2017-10-176-2/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On i.MX6ul(l) (Cortex A7) We have to set the SMP bit before enabling the caches, otherwise they won't work. Add a SoC specific lowlevel_init function to be called by the i.MX6ul(l) boards. Since this is a quirk of the Cortex A7 core we put the functionality into a separate function to be reused by other Cortex A7 cores. Change existing i.MX6ul(l) boards to use the new initialisation function. It seems this is only needed when booting from USB, in other boot modes the ROM will already have done the initialisation. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | ARM: rename flush_icache to icache_invalidateSascha Hauer2017-09-275-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | flush_icache is a misnomer since the icache is invalidated, not flushed. Rename the function accordingly. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | ARM: cache-armv7: Use designated instructions for isb/dsb/dmbSascha Hauer2017-09-271-11/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | armv7 has designated instructions for the barrier operations, so use these rather than cp15 operations. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | scripts: imx imx-usb-loader: Fix last transfer error messageSascha Hauer2017-09-261-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When doing memory read transfers there will always be 64 bytes transferred, even when less bytes are requested. This is expected and there is a test skipping the error message in this case. The test is wrong though since cnt is not decremented and will never be equal to rem. Fix the test so that verifying memory does not give a bogus error message. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | scripts: imx imx-usb-loader: Add support for i.MX6ullSascha Hauer2017-09-261-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | Same as other i.MX6 variants, just add the product id. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | ARM: i.MX53 QSB: drop phy reset handling in board fileUwe Kleine-König2017-09-261-11/+0
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit 5c1846b62524 ("ARM: i.mx53: Parse Reset GPIO pin in FEC driver from Devicetree") the fec driver ensures a phy reset. As there is little use in resetting twice, drop the reset from the board file. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | | Merge branch 'for-next/graphics'Sascha Hauer2017-10-192-5/+121
|\ \ \
| * | | fbtest: add gradients patternNikita Yushchenko2017-10-161-2/+108
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This pattern draws red, green, blue, and white color gradients, together with 3 anchor rectangles in corners. To be used with automated screen testing via computer vision methods. Suggested-by: Chris Healy <cphealy@gmail.com> Signed-off-by: Nikita Yushchenko <nikita.yoush@cogentembedded.com> Tested-by: Chris Healy <[1]cphealy@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | fbtest: add solid patternNikita Yushchenko2017-10-161-2/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This just fills entire screen with single color, as passed in -c argument in RRGGBB format. Suggested-by: Chris Healy <cphealy@gmail.com> Signed-off-by: Nikita Yushchenko <nikita.yoush@cogentembedded.com> Tested-by: Chris Healy <[1]cphealy@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | 2d-primitives: fix missing pixel in gu_draw_line()Nikita Yushchenko2017-10-161-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When drawing line from (x1, y1) to (x2, y2), pixel at (x2, y2) should be included. Signed-off-by: Nikita Yushchenko <nikita.yoush@cogentembedded.com> Tested-by: Chris Healy <[1]cphealy@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | | | Merge branch 'for-next/e1000'Sascha Hauer2017-10-193-28/+17
|\ \ \ \
| * | | | e1000: Don't poll for FLSWCTL.GLDONE before starting a flash transactionUwe Kleine-König2017-10-161-11/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | While FLSWCTL.GLDONE is set when the last transaction was fully completed, there is no good reason to depend on this. According to the i210 datasheet having FLSWCTL.DONE is enough. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | e1000: implement support for smaller flash chipsUwe Kleine-König2017-10-162-14/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Even though the register description of the FLA register suggests (on page 386 of the i210 datasheet (rev. 3.1)) that 2 MB, 4 MB and 8 MB are the only supported flash sizes, the list of supported flashes (on page 794 of the same document) lists for example a Micron M25PE80 which only has a size of 1 MB. Also in general it seems sensible to stick to the formula given for the meaning of the values that are not explicitly listed. Acked-by: Andrey Smirnov <andrew.smirnov@gmail.com> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | e1000: implement register mapping for E1000_FLSW{CTL, DATA, CNT}Uwe Kleine-König2017-10-162-3/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes: 4ff3269a70b5 ("e1000: Expose i210's external flash as MTD") Acked-by: Andrey Smirnov <andrew.smirnov@gmail.com> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | | | | Merge branch 'for-next/dts'Sascha Hauer2017-10-19995-4386/+30497
|\ \ \ \ \
| * | | | | dts: update to v4.14-rc4Sascha Hauer2017-10-1639-478/+816
| | | | | | | | | | | | | | | | | | | | | | | | Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | | dts: update to v4.14-rc3Sascha Hauer2017-10-062-13/+25
| | | | | | | | | | | | | | | | | | | | | | | | Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | | dts: update to v4.14-rc2Sascha Hauer2017-10-063-2/+8
| | | | | | | | | | | | | | | | | | | | | | | | Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | | dts: update to v4.14-rc1Sascha Hauer2017-10-06981-4030/+29785
| | |_|/ / | |/| | | | | | | | | | | | | Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | | | | Merge branch 'for-next/arm'Sascha Hauer2017-10-1926-455/+474
|\ \ \ \ \
| * | | | | ARM: socfpga: dts: sockit: remove upstreamed nodesSteffen Trumtrar2017-10-171-108/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove devicetree entries that are already in the upstream devicetree. Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | | ARM: vexpress: add fixup handler for 'virtio, mmio' devicesMichael Olbrich2017-10-171-0/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Qemu adds 'virtio,mmio' nodes to the device tree. Before passing it to the bootloader or the Linux kernel. This fixup handler copies these nodes to the new device tree. Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de> Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de> Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | | of: base: add function to copy a device tree nodeMichael Olbrich2017-10-172-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de> Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | | vexpress: add bootstate node to the device treeMichael Olbrich2017-10-171-0/+63
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de> Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | | vexpress: use device tree provided by QEMU if availableMichael Olbrich2017-10-171-2/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de> Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | | docs: add qemu vexpressLucas Stach2017-10-171-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a basic command line for QEMU vexpress. Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | | ARM: vexpress: regenerate configLucas Stach2017-10-171-3/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Enable some more features, so the default configuration gets more in line with other platforms. Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | | ARM: vexpress: switch to DT probe and multi-image buildLucas Stach2017-10-1714-285/+92
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This switches the VExpress support to use an internal DT, instead of probing the peripherals from a board file. It also switches to a multi-iamge build with both CA9 and CA15 variants of the VExpress board being supported. Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | | mci: mmci: add DT supportLucas Stach2017-10-171-3/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Just adds the minimal implementation to fill platform_data from the DT properties with Linux binding. As all MMC controllers are supposed to support at least the 3.3V signalling level, this gets exposed regardless of the platform data, just as other controller drivers in Barebox handle this. Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | | clocksource: sp804: silently ignore secondary instacesLucas Stach2017-10-171-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When probing from an upstream DT, we don't always have influence on how many timer instances are enabled. Just use the first one and silently skip the other instances. Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | | clk: versatile: add basic clocksLucas Stach2017-10-175-0/+181
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds the necessary basic clocks used on the ARM versatile platforms. Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | | of: populate clock providers before other devicesLucas Stach2017-10-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Clocks are a basic resource, which may be needed early by other devices or even the bus driver (as is the case with the ARM AMBA bus). Register them before populating other devices. Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | | ARM: vexpress: always build relocatable imageLucas Stach2017-10-163-53/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This allows to make more space available for the malloc area and allows us to drop the special CA9 defconfig, which had a different text base. Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | | | | | graphic_utils: Fix freeing uninitialzed pointer in fb_open()Sascha Hauer2017-10-191-3/+1
| |_|/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | In fb_open() when fb_create_screen() fails then sc contains an error pointer which is then freed in the failure path. Fix this. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | | | | eeprom: at24: fix 'assignment from incompatible pointer type' warningAntony Pavlov2017-10-161-1/+1
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The patch fixes this compiler's warning: CC drivers/eeprom/at24.o drivers/eeprom/at24.c: In function ‘at24_probe’: drivers/eeprom/at24.c:453:21: warning: assignment from incompatible pointer type [-Wincompatible-pointer-types] at24->fops.protect = at24_cdev_protect, ^ Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | / / efi: add missing Kconfig selectsEnrico Jorns2017-10-161-0/+2
| |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Building EFI code without block device and partition support enabled will fail with: | drivers/built-in.o: In function `efi_bio_probe': | (.text+0x125d): undefined reference to `blockdevice_register' | drivers/built-in.o: In function `efi_bio_probe': | (.text+0x126c): undefined reference to `parse_partition_table' | Makefile:766: recipe for target 'barebox' failed Thus always select BLOCK and PARTITION_DISK when enabling EFI_BOOTUP. Signed-off-by: Enrico Jorns <ejo@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | | Release v2017.10.0v2017.10.0Sascha Hauer2017-10-061-1/+1
|/ / | | | | | | Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | memtest: fix list iteration in region setupSteffen Trumtrar2017-09-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When memory regions start at 0, the current mem_test_request_regions function wrongly assumes that struct resource *r points at the correct region. It points to the first region however (which starts at 0). The comment states, that the code starts from the second entry. In include/linux/list.h the macro documentation however says: list_for_each_entry_from - iterate over list of given type from the current point The correct list iteration macro to use here is list_for_each_entry_continue, where the documentation says: Continue to iterate over list of given type, continuing after the current position. Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | bootm: bootm_open_initrd_uimage(): propagate error if initrd verification failsMarc Kleine-Budde2017-09-201-0/+1
|/ | | | | | | | | | If the verification of an initrd inside of an uImage fails an error message is printed but the error is not propagated. Although this is not security relevant, as the verification is currently only a CRC32 check, the error should be returned. This patch fixes the problem. Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* Merge branch 'for-next/state'Sascha Hauer2017-09-0810-341/+1258
|\
| * state: don't use uninitialized variableJuergen Borleis2017-09-061-1/+1
| | | | | | | | | | | | | | Printing 'ret' makes no sense. Signed-off-by: Juergen Borleis <jbe@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * state: use the given backend storage type nameJuergen Borleis2017-09-062-6/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Change 119f92b27e131a0cb506fe8d8bffe8010fb14a3d already tried to fix it, but forgets the 'direct' usecase. The 'backend-storage-type' node is optional. Its default depends on the capability of the used backend memory, which means "circular" or NULL. The latter defaults to 'direct' in the routines. If it is NULL, the devicetree fixup routine skips exporting a 'backend-storage-type' node to the kernel's devicetree. But currently if the 'backend-storage-type' node is explicitly given as 'direct', it will be skipped silently and set to NULL instead. In this case the user of the 'barebox-state' tool then ends up with the warning: "No backend-storage-type found, using default" which is annoying, because it was given. Storing the given value will still use a NULL if the 'backend-storage-type' node isn't defined, but stores everything else if it is defined. Then the 'backend-storage-type' node is present in the kernel's devicetree as well. Signed-off-by: Juergen Borleis <jbe@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * state command: extend help part IIJuergen Borleis2017-09-061-1/+2
| | | | | | | | | | | | | | | | | | Since commit 0c7436753c73e71ee512e5ed8029e7ccceedcd89 the 'state' command supports authentification and a related parameter. Honor this in the help text. Signed-off-by: Juergen Borleis <jbe@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * state command: extend help part IJuergen Borleis2017-09-061-2/+3
| | | | | | | | | | | | | | | | | | | | The loading parameter and its help text was removed in commit 446f3d07dd59f1b15b83a31fa88fba919ce4f47d and the loading parameter was re-added in commit 3a5ddf3d0db006e9256c8e256e7dc7b4a3f89a14 but the help was forgotten. Re-add the help as well. Signed-off-by: Juergen Borleis <jbe@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * state: provide an error message when an error occursJuergen Borleis2017-09-061-0/+1
| | | | | | | | | | | | | | | | A simple typo makes the state framework fail, but without an error message the developer is lost in the dark. Signed-off-by: Juergen Borleis <jbe@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * docs: rework and extend the 'state' and 'bootchooser' documentationJuergen Borleis2017-09-063-317/+1204
| | | | | | | | | | | | | | | | Many links between sections and examples were added to give the developer the help to get it work. Signed-off-by: Juergen Borleis <jbe@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * state: add debugging helpJuergen Borleis2017-09-062-1/+8
| | | | | | | | | | | | | | | | | | While working on the state documentation it turns out to be helpful to have more debug messages while a developer implements a 'state' variable set and tries to configure it correctly. Signed-off-by: Juergen Borleis <jbe@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * docs: remove build warningJuergen Borleis2017-09-061-0/+1
| | | | | | | | | | | | | | | | | | This change removes: "devicetree/bindings/rtc/dallas,ds1307.rst: WARNING: document isn't included in any toctree" warning Signed-off-by: Juergen Borleis <jbe@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * bootchooser: allow an empty namespaceJuergen Borleis2017-09-061-6/+4
| | | | | | | | | | | | | | | | | | The bootchooser's documentation states the 'namespace' for the state storage backend is optional. This change makes it really optional to allow a flat state variable set definition for the 'bootchooser' as well. Signed-off-by: Juergen Borleis <jbe@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * bootchooser: avoid a use after freeJuergen Borleis2017-09-061-1/+1
| | | | | | | | | | Signed-off-by: Juergen Borleis <jbe@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>