<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/u-boot/arch/Kconfig, 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-06-13T07:21:06Z</updated>
<entry>
<title>Kconfig: Add SPI / SPI_FLASH as dependencies</title>
<updated>2019-06-13T07:21:06Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2019-05-29T21:01:28Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=a4298ddaf8bbccf8a14acb6be33764eecbea9abd'/>
<id>urn:sha1:a4298ddaf8bbccf8a14acb6be33764eecbea9abd</id>
<content type='text'>
In order to use CMD_SF / CMD_SPI / ENV_IS_IN_SPI_FLASH we need to have
the SPI (or SPI_FLASH/DM_SPI_FLASH, for CMD_SF) enabled.  Express this
in the Kconfigs.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
Reviewed-by: Jagan Teki &lt;jagan@amarulasolutions.com&gt;
</content>
</entry>
<entry>
<title>m68k: add OF control support to m68k</title>
<updated>2019-05-24T12:11:58Z</updated>
<author>
<name>Angelo Dureghello</name>
</author>
<published>2019-03-13T20:46:51Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=abe0f879996b3bf7bc3bfdb35b83a8dd8ee3ea7d'/>
<id>urn:sha1:abe0f879996b3bf7bc3bfdb35b83a8dd8ee3ea7d</id>
<content type='text'>
Add SUPPORT_OF_CONTROL at this stage, to avoid to break build
bisectability.

Signed-off-by: Angelo Dureghello &lt;angelo@sysam.it&gt;
</content>
</entry>
<entry>
<title>Merge tag 'rockchip-for-v2019.07-rc1' of git://git.denx.de/u-boot-rockchip</title>
<updated>2019-05-09T16:36:17Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2019-05-09T11:12:51Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=f30f268a07b0c9e4418366debc9ad0100a47cea4'/>
<id>urn:sha1:f30f268a07b0c9e4418366debc9ad0100a47cea4</id>
<content type='text'>
Improvements and new features:
- split more rockchip pinctrl_core feature into per SoC
- enable TPL for evb-rk3399 board
- enable TPL/SPL for evb-px5 board
- enable TPL and OP-TEE support for evb-rk3229
- update fix in arm common assembly start code for rockchip header file
- update default SPL_FIT_GENERATOR for rockchip
- rk3399 boards update to use '-u-boot.dtsi'
- add new rk3399 boards: Nanopi M4, Nanopc T4
- enable sound for chromebook_minnie
</content>
</entry>
<entry>
<title>sysreset: enable driver support in SPL/TPL</title>
<updated>2019-05-08T09:34:12Z</updated>
<author>
<name>Kever Yang</name>
</author>
<published>2019-04-02T12:41:25Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=09259fce1e8b4ac34a47d4590f42878a38b42826'/>
<id>urn:sha1:09259fce1e8b4ac34a47d4590f42878a38b42826</id>
<content type='text'>
SPL/TPL also need use sysreset for some feature like panic callback.

Signed-off-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
</content>
</entry>
<entry>
<title>x86: Enable the RTC on all boards</title>
<updated>2019-05-08T05:02:18Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2019-05-02T16:52:24Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=31d5261d3599dd7e1868e93e95076ac5d7468b3c'/>
<id>urn:sha1:31d5261d3599dd7e1868e93e95076ac5d7468b3c</id>
<content type='text'>
With the move to Kconfig this option should be set in Kconfig, not in the
config header file. Move it.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
</content>
</entry>
<entry>
<title>x86: Support SPL and TPL</title>
<updated>2019-05-08T05:02:11Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2019-04-26T03:58:45Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=9898790247040772e068f1ef9ac8a16c01d197ac'/>
<id>urn:sha1:9898790247040772e068f1ef9ac8a16c01d197ac</id>
<content type='text'>
At present only chromebook_link64 supports SPL. It is useful to eb able to
support both TPL and SPL to implement verified boot on x86.

Enable the options for both along with some suitable default options
needed to boot through these phases.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
</content>
</entry>
<entry>
<title>arch: armv8: Provide a way to disable cache maintenance ops</title>
<updated>2019-05-05T12:48:50Z</updated>
<author>
<name>Vignesh Raghavendra</name>
</author>
<published>2019-04-22T16:13:32Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=add4967124f6b212fef4fa8e1e68143b1400c994'/>
<id>urn:sha1:add4967124f6b212fef4fa8e1e68143b1400c994</id>
<content type='text'>
On AM654 SoC(arm64) which is IO coherent and has L3 Cache, cache
maintenance operations being done to support non-coherent platforms
causes issues.

For example, here is how U-Boot prepares/handles a buffer to receive
data from a device (DMA Write). This may vary slightly depending on the
driver framework:

	Start DMA to write to destination buffer
	Wait for DMA to be done (dma_receive()/dma_memcpy())
	Invalidate destination buffer (invalidate_dcache_range())
	Read from destination buffer

The invalidate after the DMA is needed in order to read latest data from
memory that’s updated by DMA write. Also, in case random prefetch has
pulled in buffer data during the “wait for DMA” before the DMA has
written to it. This works well for non-coherent architectures.

In case of coherent architecture with L3 cache, DMA write would directly
update L3 cache contents (assuming cacheline is present in L3) without
updating the DDR memory. So invalidate after “wait for DMA” in above
sequence would discard latest data and read will cause stale data to be
fetched from DDR. Therefore invalidate after “wait for DMA” is not
always correct on coherent architecture.

Therefore, provide a Kconfig option to disable cache maintenance ops on
coherent architectures. This has added benefit of improving the
performance of DMA transfers as we no longer need to invalidate/flush
individual cache lines(especially for buffer thats several KBs in size).

In order to facilitate use of same Kconfig across different
architecture, I have added the symbol to top level arch/Kconfig file.
Patch currently disables cache maintenance ops for arm64 only.
flush_dcache_all() and invalidate_dcache_all() are exclusively used
during enabling/disabling dcache and hence are not disabled.

Signed-off-by: Vignesh Raghavendra &lt;vigneshr@ti.com&gt;
</content>
</entry>
<entry>
<title>riscv: Enable create symlink using kconfig</title>
<updated>2019-02-27T01:12:33Z</updated>
<author>
<name>Anup Patel</name>
</author>
<published>2019-02-25T08:14:04Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=7c8d210b91a192e89be3bfc9c0e943422df108b0'/>
<id>urn:sha1:7c8d210b91a192e89be3bfc9c0e943422df108b0</id>
<content type='text'>
We select CREATE_ARCH_SYMLINK for RISC-V so that we can have
include/asm/arch linked to include/asm/arch-xyz.

Signed-off-by: Anup Patel &lt;anup.patel@wdc.com&gt;
Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
</content>
</entry>
<entry>
<title>x86: sandbox: pch: Add a CONFIG option for PCH</title>
<updated>2019-02-20T07:25:30Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2019-02-17T03:24:49Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=c882163b09b8a2c52e3dd8acd7d296d6d06d1f2e'/>
<id>urn:sha1:c882163b09b8a2c52e3dd8acd7d296d6d06d1f2e</id>
<content type='text'>
At present this uclass is selected only on x86. In order to add a test for
it, it must also support sandbox. Create a new CONFIG_PCH option and
enable it on x86 and sandbox.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
</content>
</entry>
<entry>
<title>dm: sound: Create an option to use driver model for sound</title>
<updated>2018-12-13T23:32:49Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2018-12-10T17:37:31Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=2a0495724133058ab7c6aa1e8dc9433344d45231'/>
<id>urn:sha1:2a0495724133058ab7c6aa1e8dc9433344d45231</id>
<content type='text'>
The U-Boot sound system provides basic support for beeping. At present it
does not use driver model, but it needs to be converted. Add an option to
enable driver model for sound. For now it is not connected to anything.
Future work will add drivers which use this option. It will then be
removed once everything is converted.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
</feed>
