LuminaSensum/barebox

Fork: 0

LuminaSensum / barebox

2015-05-06	10fb785 Browse files » Merge branch 'for-next/mips' Sascha Hauer committed on 6 May 2015
	4a854c9 Browse files » Merge branch 'for-next/imx' Sascha Hauer committed on 6 May 2015
	15e906a Browse files » Merge branch 'for-next/dts' Sascha Hauer committed on 6 May 2015
	3892185 Browse files » Merge branch 'for-next/defer' Sascha Hauer committed on 6 May 2015
	461f8cf Browse files » dts: update to v4.1-rc1 ... Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sascha Hauer committed on 6 May 2015
	v2015.05.0 3bc7f48 Browse files » Release v2015.05.0 ... Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sascha Hauer committed on 6 May 2015
2015-05-05	c05380f Browse files » net: phy: Do not double remove phy device ... This fixes: 80264a8 driver: Call bus->remove instead of driver->remove On mvebu it happens that: Upon device shutdown, when iterating through the active device list, the phy0 device is removed before mdio-mvebu. Then, when the mdio bus device is removed, the phy0 device is removed again, here: mdio_bus_remove(on mdio-mvebu) mvebu_mdio_remove mdiobus_unregister unregister_device mdio_bus_remove(on phy0) Fix this by setting the mdio busses phy_map[phy->addr] to NULL when unregistering the phy device, so that mdiobus_unregister no longer finds a valid phy_device when iterating over the busses device list. Reported-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Tested-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar> Sascha Hauer committed on 5 May 2015
	f76ef11 Browse files » Documentation: mips: fix tplink-mr3020 instruction ... Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Antony Pavlov authored on 4 May 2015 Sascha Hauer committed on 5 May 2015
	16886bf Browse files » MIPS: tplink-mr3020: enable nmon ... Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Antony Pavlov authored on 4 May 2015 Sascha Hauer committed on 5 May 2015
	cd855dd Browse files » MIPS: mach-ath79: debug_ll.h: add assembler routines ... Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Antony Pavlov authored on 4 May 2015 Sascha Hauer committed on 5 May 2015
	9035f20 Browse files » MIPS: debug_ll_ns16550.h: drop _ns16550 suffix ... This commit makes it possible to have unified debug_ll_* assembler routines for differrent UART program model. E.g. we can use debug_ll_putc() routine in common code without knowledge on exact UART model: ns16550 or ar933x. Also rename _check_char -> _tstc. Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Antony Pavlov authored on 4 May 2015 Sascha Hauer committed on 5 May 2015
	660d4ef Browse files » MIPS: tplink-mr3020: enable PBL and compression ... Signed-off-by: Oleksij Rempel <linux@rempel-privat.de> Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Oleksij Rempel authored on 4 May 2015 Sascha Hauer committed on 5 May 2015
2015-05-04	15422e3 Browse files » net: phy: Do not double remove phy device ... This fixes: 80264a8 driver: Call bus->remove instead of driver->remove On mvebu it happens that: Upon device shutdown, when iterating through the active device list, the phy0 device is removed before mdio-mvebu. Then, when the mdio bus device is removed, the phy0 device is removed again, here: mdio_bus_remove(on mdio-mvebu) mvebu_mdio_remove mdiobus_unregister unregister_device mdio_bus_remove(on phy0) Fix this by setting the mdio busses phy_map[phy->addr] to NULL when unregistering the phy device, so that mdiobus_unregister no longer finds a valid phy_device when iterating over the busses device list. Reported-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sascha Hauer committed on 4 May 2015
2015-05-01	cbc2492 Browse files » PCI: fill in bus primary field ... This was erroneously left uninitialzed as nothing was using it. The i.MX6 PCI driver needs this to be filled properly to decide if a config space access is allowed for a specific devfn. This fixes PCI enumeration on the Gateworks GW54xx board. Signed-off-by: Lucas Stach <dev@lynxeye.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Lucas Stach authored on 29 Apr 2015 Sascha Hauer committed on 1 May 2015
2015-05-01	2a8bc95 Browse files » PCI: register and active bridge device before proceeding to scan ... The bridge device needs to be registered and activated before the scanning can proceed, as the bridge is the parent for other devices. This fixes a NULL ptr derefernce when scanning PCI hierarchies with bridges behind bridges. Signed-off-by: Lucas Stach <dev@lynxeye.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Lucas Stach authored on 29 Apr 2015 Sascha Hauer committed on 1 May 2015
2015-04-28	92207cd Browse files » net: e1000: add HAS_DMA dependency ... The e1000 driver uses the dma coherent functions and thus can only be build for architectures implementing them. Here is mips malta build error log: drivers/built-in.o: In function `e1000_transmit': drivers/net/e1000.c:(.text.e1000_transmit+0x80): undefined reference to `dma_sync_single_for_device' drivers/built-in.o: In function `e1000_poll': drivers/net/e1000.c:(.text.e1000_poll+0x60): undefined reference to `dma_sync_single_for_cpu' Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Antony Pavlov authored on 28 Apr 2015 Sascha Hauer committed on 28 Apr 2015
	6345d37 Browse files » dts: update to v4.0 ... Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sascha Hauer committed on 28 Apr 2015
	13ca5ce Browse files » dts: update to v4.0-rc7 ... Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sascha Hauer committed on 28 Apr 2015
	10e6930 Browse files » mtd: partition: Fix OF partition fixup ... To get the number of address cells and size cells we have to use the newly created partition node, not the parent device node. The parent device node returns the address/size cells of the controller node, not the partition node. On an am335x machine this fixes the device tree passed to Linux. The situation there is: ... gpmc@50000000 { ... #address-cells = <0x2>; #size-cells = <0x1>; ranges = <0x0 0x0 0x8000000 0x10000000>; ... nand@0,0 { reg = <0x0 0x0 0x0>; #address-cells = <0x1>; #size-cells = <0x1>; ... partition@7 { label = "system"; reg = <0x220000 0x7de0000>; }; }; }; and without this patch barebox passes three bytes for partition@7's reg property instead of only two which naturally confuses Linux and yields to the system partition to start at 0 with a size of 0x220000. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Reported-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Tested-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Sascha Hauer committed on 28 Apr 2015
2015-04-20	dbe6023 Browse files » ARM: highbank: select OFTREE ... The board code uses quite a few OF functions and it doesn't seem reasonable to run this board without DT support. Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Lucas Stach authored on 25 Mar 2015 Sascha Hauer committed on 20 Apr 2015
	c0fed56 Browse files » gpio: orion: Convert to platform_driver ... With support for deferred probing, we can now relax driver registration for Marvell Orion GPIO driver from postcore_initcall() to normal platform_driver. Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sebastian Hesselbarth authored on 14 Apr 2015 Sascha Hauer committed on 20 Apr 2015
	4c5f742 Browse files » led: gpio: Free GPIOs on unregister() ... Free requested GPIOs on unregistration of mono-, bi-, and tri-color GPIO leds. Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sebastian Hesselbarth authored on 14 Apr 2015 Sascha Hauer committed on 20 Apr 2015
	9d309e5 Browse files » led: Fix led_gpio_rgb_unregister prototype ... Analog to the other led_unregister prototypes this must take the LED type specific struct. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sascha Hauer committed on 20 Apr 2015
2015-04-17	62adc52 Browse files » led: gpio: Properly deal with deferred probing ... GPIO LEDs can suffer from deferred probing due to failing gpio request. Instead of registering each gpio led independently, pre-allocate an array of struct gpio_led for all and tear it down properly if probing of one leds fails. While at it, silence error messages on -EPROBE_DEFER. Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sebastian Hesselbarth authored on 14 Apr 2015 Sascha Hauer committed on 17 Apr 2015
	c6a9698 Browse files » OF: gpio: Silence error message on -EPROBE_DEFER ... With deferred probing, -EPROBE_DEFER is not worth spilling an error. Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sebastian Hesselbarth authored on 14 Apr 2015 Sascha Hauer committed on 17 Apr 2015
	9744da2 Browse files » gpio: Return -EPROBE_DEFER on gpio_get_num() ... GPIO drivers can be registered quite late in registration process causing dependant devices to fail probing. If we know gpio_get_num will be called with a non-NULL device, return -EPROBE_DEFER instead of -ENODEV to allow re-probing later. Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sebastian Hesselbarth authored on 14 Apr 2015 Sascha Hauer committed on 17 Apr 2015
	ab3da15 Browse files » base: Introduce deferred probing ... As expected, we would need deferred probing sooner or later. This is a first approach to allow devices to return -EPROBE_DEFER and get sorted into a list of deferred devices that will be re-probed later. Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sebastian Hesselbarth authored on 14 Apr 2015 Sascha Hauer committed on 17 Apr 2015
2015-04-15	11045f8 Browse files » USB: xHCI: Sync non-coherent DMA buffers ... When working with non-coherent transfer buffers, we have to sync device and cpu for outgoing and incoming buffers. Fix the driver where non-coherent buffers are used in device context. Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> Reviewed-by: Lucas Stach <l.stach@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Sebastian Hesselbarth authored on 13 Apr 2015 Sascha Hauer committed on 15 Apr 2015
	29abc10 Browse files » habv4: add High Assurance Boot v4 ... This patch adds the code to check the HAB ROM for failures during development. Add a cal to "habv4_get_status();" to your board file, to get the current system state from the ROM. _NOTE_: On i.MX6 this has to happen before barebox starts the MMU, because the HAB ROM vector table is placed at 0x94, which is not accessible after the MMU has setup the zero page. This patch contains code ported from u-boot patches [1][2] by Shaojun Wang [3] which were found in the "Mx28 Secure Boot" and "Mx6 HAB (High Assurance Boot)" thread on the freescale community forum [4][5]. [1] https://community.freescale.com/servlet/JiveServlet/download/370047-269174/0001-enable-mx28-u-boot-hab.patch.txt.zip [1] https://community.freescale.com/servlet/JiveServlet/download/96451-11-266175/0001-u-boot-enable-mx6-hab.patch.zip [2] https://community.freescale.com/people/ShaojunWang [3] https://community.freescale.com/thread/317254 [3] https://community.freescale.com/docs/DOC-96451 Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Marc Kleine-Budde authored on 13 Apr 2015 Sascha Hauer committed on 15 Apr 2015
	d3be1ab Browse files » images: add HABv4 support for i.MX6 ... This patch adds high assurance boot support (HABv4) image generation to barebox, currently tested on i.MX6 only. In order to build a signed barebox image, add a new image target to images/Makefile.imx as illustrated in the diff below: - - - a/images/Makefile.imx + + + b/images/Makefile.imx @@ -163,10 +163,14 @@ image-$(CONFIG_MACH_SABRELITE) += barebox-freescale-imx6dl-sabrelite.img pblx-$(CONFIG_MACH_SABRESD) += start_imx6q_sabresd CFG_start_imx6q_sabresd.pblx.imximg = $(board)/freescale-mx6-sabresd/flash-header-mx6-sabresd.imxcfg FILE_barebox-freescale-imx6q-sabresd.img = start_imx6q_sabresd.pblx.imximg image-$(CONFIG_MACH_SABRESD) += barebox-freescale-imx6q-sabresd.img +CSF_start_imx6q_sabresd.pblx.imximg = $(havb4_imx6csf) +FILE_barebox-freescale-imx6q-sabresd-signed.img = start_imx6q_sabresd.pblx.imximg.signed +image-$(CONFIG_MACH_SABRESD) += barebox-freescale-imx6q-sabresd-signed.img + Here the default i.MX6 CSF file $(havb4_imx6csf) is used, it's generated during build on from the template "scripts/habv4/habv4-imx6.csf.in". You can configure the paths to the SRK table and certificates via: System Type -> i.MX specific settings -> HABv4 support. The proprietary tool "cst" by Freescale tool is expected in the PATH. Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> Marc Kleine-Budde authored on 13 Apr 2015 Sascha Hauer committed on 15 Apr 2015