<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/u-boot/arch/arm/mach-mvebu/include, branch master</title>
<subtitle>Broadcom-s U-Boot</subtitle>
<id>https://git.openwrt.org/project/bcm63xx/u-boot/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/project/bcm63xx/u-boot/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/'/>
<updated>2019-04-26T05:35:38Z</updated>
<entry>
<title>mmc: mv_sdhci: add driver model support</title>
<updated>2019-04-26T05:35:38Z</updated>
<author>
<name>Pierre Bourdon</name>
</author>
<published>2019-04-11T02:56:58Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=4ec9dd4071cb3e7d2c0c42f2eea935edceba5b7e'/>
<id>urn:sha1:4ec9dd4071cb3e7d2c0c42f2eea935edceba5b7e</id>
<content type='text'>
The new DM implementation currently does not support the Sheeva
88SV331xV5 specific quirk present in the legacy implementation. The
legacy code is thus kept for this SoC and others not yet migrated to
DM_MMC.

Signed-off-by: Pierre Bourdon &lt;delroth@gmail.com&gt;
Cc: Jaehoon Chung &lt;jh80.chung@samsung.com&gt;
Cc: Stefan Roese &lt;sr@denx.de&gt;
Reviewed-by: Stefan Roese &lt;sr@denx.de&gt;
Signed-off-by: Stefan Roese &lt;sr@denx.de&gt;
</content>
</entry>
<entry>
<title>arm: mvebu: NAND clock support for MSYS devices</title>
<updated>2019-04-12T05:04:18Z</updated>
<author>
<name>Chris Packham</name>
</author>
<published>2019-04-11T10:22:51Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=689f9cf6aa9edff89c4d4d3b843f500fc5582300'/>
<id>urn:sha1:689f9cf6aa9edff89c4d4d3b843f500fc5582300</id>
<content type='text'>
One difference with the integrated CPUs is that they use a different
clock control block to the Armada devices. Update mvebu_get_nand_clock()
accordingly.

Signed-off-by: Chris Packham &lt;judge.packham@gmail.com&gt;
Reviewed-by: Stefan Roese &lt;sr@denx.de&gt;
Signed-off-by: Stefan Roese &lt;sr@denx.de&gt;
</content>
</entry>
<entry>
<title>arm: mvebu: Add Marvell's integrated CPUs</title>
<updated>2019-04-12T05:04:18Z</updated>
<author>
<name>Chris Packham</name>
</author>
<published>2019-04-11T10:22:50Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=0d0df46ee7323506df2e38738c52d68699c2abca'/>
<id>urn:sha1:0d0df46ee7323506df2e38738c52d68699c2abca</id>
<content type='text'>
Marvell's switch chips with integrated CPUs (collectively referred to as
MSYS) share common ancestry with the Armada SoCs. Some of the IP blocks
(e.g. xor) are located at different addresses and DFX server exists as a
separate target on the MBUS (on Armada-38x it's just part of the core
complex registers).

Signed-off-by: Chris Packham &lt;judge.packham@gmail.com&gt;
Reviewed-by: Stefan Roese &lt;sr@denx.de&gt;
Signed-off-by: Stefan Roese &lt;sr@denx.de&gt;
</content>
</entry>
<entry>
<title>Convert CONFIG_ENV_SPI_* to Kconfig</title>
<updated>2019-03-25T21:36:59Z</updated>
<author>
<name>Patrick Delaunay</name>
</author>
<published>2019-02-27T14:20:38Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=abe66b1b5decf9cc2fb5daad42c9e870e5b99b67'/>
<id>urn:sha1:abe66b1b5decf9cc2fb5daad42c9e870e5b99b67</id>
<content type='text'>
This converts the following to Kconfig:
  CONFIG_ENV_SPI_BUS
  CONFIG_ENV_SPI_CS
  CONFIG_ENV_SPI_MAX_HZ
  CONFIG_ENV_SPI_MODE

Most of time these value are not needed, CONFIG_SF_DEFAULT
with same value is used, so I introduced CONFIG_USE_ENV_SPI_*
to force the associated value for the environment.

Signed-off-by: Patrick Delaunay &lt;patrick.delaunay@st.com&gt;
</content>
</entry>
<entry>
<title>video: Armada XP: Move driver to DM_VIDEO</title>
<updated>2019-02-05T13:23:21Z</updated>
<author>
<name>Stefan Roese</name>
</author>
<published>2019-01-30T07:54:11Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=6d9a98c58390156033e31a3a4078347bec618202'/>
<id>urn:sha1:6d9a98c58390156033e31a3a4078347bec618202</id>
<content type='text'>
This patch moves the Armada XP video / LCD driver to DM_VIDEO. With this
move, the legacy interface board_video_init() is removed from the
theadorable board code (only user of this video driver). The support
via DT will be added in a separate patch.

This patch also enables DM_VIDEO for the theadorable board, as this is
needed to not break git bisect'ability.

Signed-off-by: Stefan Roese &lt;sr@denx.de&gt;
Reviewed-by: Anatolij Gustschin &lt;agust@denx.de&gt;
Acked-by: Anatolij Gustschin &lt;agust@denx.de&gt;
</content>
</entry>
<entry>
<title>Kconfig: Migrate CONFIG_BUILD_TARGET</title>
<updated>2019-02-02T13:23:57Z</updated>
<author>
<name>Jagan Teki</name>
</author>
<published>2019-01-18T07:22:49Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=dc146ca111873b1eabb9d0249ce0c1ec44e82a26'/>
<id>urn:sha1:dc146ca111873b1eabb9d0249ce0c1ec44e82a26</id>
<content type='text'>
Migrate CONFIG_BUILD_TARGET into Kconfig.

Signed-off-by: Jagan Teki &lt;jagan@amarulasolutions.com&gt;
</content>
</entry>
<entry>
<title>ARM: mvebu: add revision id for Armada-385 B0</title>
<updated>2018-11-30T09:58:10Z</updated>
<author>
<name>Chris Packham</name>
</author>
<published>2018-11-27T21:32:00Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=d997ad034b6a2e840fefb8224bfd85391cafd71d'/>
<id>urn:sha1:d997ad034b6a2e840fefb8224bfd85391cafd71d</id>
<content type='text'>
Marvell have release a B0 revision of the Armada-385 SoC. This fixes a
hardware errata enabling RGMII to work when the Ethernet voltage is
configured to 3.3V.

Signed-off-by: Chris Packham &lt;judge.packham@gmail.com&gt;
Reviewed-by: Stefan Roese &lt;sr@denx.de&gt;
Signed-off-by: Stefan Roese &lt;sr@denx.de&gt;
</content>
</entry>
<entry>
<title>arm: mvebu: Move PCI(e) MBUS window to end of RAM</title>
<updated>2018-11-06T12:21:13Z</updated>
<author>
<name>Stefan Roese</name>
</author>
<published>2018-10-22T12:21:17Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=a8483505e88e9e90bf4e166093dca5f99acbe2b2'/>
<id>urn:sha1:a8483505e88e9e90bf4e166093dca5f99acbe2b2</id>
<content type='text'>
With patch 49b23e035d96 (pci: mvebu: Increase size of PCIe default mapping)
the mapping size for each PCI(e) controller was increased from 32MiB to
128MiB. This leads to problems on boards with multiple PCIe slots / ports
which are unable to map all PCIe ports, e.g. the Armada-XP theadorable:

DRAM:  2 GiB (667 MHz, 64-bit, ECC not enabled)
SF: Detected m25p128 with page size 256 Bytes, erase size 256 KiB, total 16 MiB
Cannot add window '4:f8', conflicts with another window
PCIe unable to add mbus window for mem at f0000000+08000000
Model: Marvell Armada XP theadorable

This patch moves the base address for the PCI(e) memory spaces from
0xe8000000 to the end of SDRAM (clipped to a max of 0xc0000000 right now).
This gives move room and flexibility for PCI(e) mappings.

Signed-off-by: Stefan Roese &lt;sr@denx.de&gt;
Cc: VlaoMao &lt;vlaomao@gmail.com&gt;
Tested-by: VlaoMao &lt;vlaomao at gmail.com&gt;
</content>
</entry>
<entry>
<title>ARM: mach-mvebu: handle fall-back to UART boot</title>
<updated>2018-09-19T06:59:26Z</updated>
<author>
<name>Chris Packham</name>
</author>
<published>2018-08-17T08:47:42Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=2fd4284051e33763e3424cbd7e106e0a75dfd16e'/>
<id>urn:sha1:2fd4284051e33763e3424cbd7e106e0a75dfd16e</id>
<content type='text'>
The bootROM in the Armada-38x (and similar) SoC has two modes for UART
boot. The first is when the normal boot media is blank (or otherwise
missing the kwb header). The second is when the boot sequence has been
interrupted with the magic byte sequence on the UART lines.

In the first mode the bootROM routine and error code register will
indicate that there was an error booting from the configured media in
bits 7:0. In the second mode there is no error to indicate but the boot
source is provided via bits 31:28.

Handle both situations so that kwboot can be used for both boot
strapping a blank board and for intercepting a regular boot sequence.

Signed-off-by: Chris Packham &lt;judge.packham@gmail.com&gt;
Signed-off-by: Sean Nyekjaer &lt;sean.nyekjaer@prevas.dk&gt;
Signed-off-by: Stefan Roese &lt;sr@denx.de&gt;
</content>
</entry>
<entry>
<title>Revert "arm: mvebu: fix boot from UART when in fallback mode"</title>
<updated>2018-09-19T06:59:26Z</updated>
<author>
<name>Chris Packham</name>
</author>
<published>2018-08-17T08:47:41Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=e0977297e89c19701f6ac9cf7b2743b8f1490159'/>
<id>urn:sha1:e0977297e89c19701f6ac9cf7b2743b8f1490159</id>
<content type='text'>
This reverts commit e83e2b390038c9075642cb243a6292241beb8d73. This
prevents kwboot from overriding the hardware strapped boot source.

Signed-off-by: Chris Packham &lt;judge.packham@gmail.com&gt;
Signed-off-by: Stefan Roese &lt;sr@denx.de&gt;
</content>
</entry>
</feed>
