<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/u-boot/include/configs/arndale.h, 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-05-16T07:11:42Z</updated>
<entry>
<title>arm: exynos: arndale: Remove unused CONFIG_POWER and CONFIG_POWER_I2C</title>
<updated>2019-05-16T07:11:42Z</updated>
<author>
<name>Krzysztof Kozlowski</name>
</author>
<published>2019-05-11T11:24:31Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=7d075055acf4a1d095234fd0f7efa16a817f2d36'/>
<id>urn:sha1:7d075055acf4a1d095234fd0f7efa16a817f2d36</id>
<content type='text'>
The CONFIG_POWER and CONFIG_POWER_I2C were introduced in
include/configs/exynos5-common.h in commit 19bd3aaa5991 ("exynos5: fix
build break by adding CONFIG_POWER") and then it propagated up to
include/configs/arndale.h.  However before that commit, there was no
build break at all on Arndale and SMDK5250 boards.  It seems the commit
fixed nothing and just added unused defines.

In fact, the Arndale board is not configuring its PMIC (S5M8767) which
uses I2C bus.

Signed-off-by: Krzysztof Kozlowski &lt;krzk@kernel.org&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Signed-off-by: Minkyu Kang &lt;mk7.kang@samsung.com&gt;
</content>
</entry>
<entry>
<title>Convert CONFIG_SUPPORT_EMMC_BOOT to Kconfig</title>
<updated>2019-05-04T17:04:12Z</updated>
<author>
<name>Alex Kiernan</name>
</author>
<published>2019-05-01T07:58:27Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=623de3f08631bd8aab79f38b71ada18a1f9d836f'/>
<id>urn:sha1:623de3f08631bd8aab79f38b71ada18a1f9d836f</id>
<content type='text'>
This converts the following to Kconfig:
   CONFIG_SUPPORT_EMMC_BOOT

As requested by Michal Simek &lt;michal.simek@xilinx.com&gt;, these boards
have no eMMC so CONFIG_SUPPORT_EMMC_BOOT has not been migrated:

  xilinx_zynqmp_zc1275_revB
  xilinx_zynqmp_zc1751_xm018_dc4
  xilinx_zynqmp_zc1751_xm019_dc5
  xilinx_zynqmp_zcu100_revC
  xilinx_zynqmp_zcu102_rev1_0
  xilinx_zynqmp_zcu102_revA
  xilinx_zynqmp_zcu102_revB
  xilinx_zynqmp_zcu104_revA
  xilinx_zynqmp_zcu104_revC
  xilinx_zynqmp_zcu106_revA
  xilinx_zynqmp_zcu111_revA

Signed-off-by: Alex Kiernan &lt;alex.kiernan@gmail.com&gt;
Acked-by: Lukasz Majewski &lt;lukma@denx.de&gt;
Acked-by: Patrick Delaunay &lt;patrick.delaunay@st.com&gt;
Acked-by: Ramon Fried &lt;ramon.fried@gmail.com&gt;
Reviewed-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;
Tested-by: Sébastien Szymanski &lt;sebastien.szymanski@armadeus.com&gt;
</content>
</entry>
<entry>
<title>SPDX: Convert all of our single license tags to Linux Kernel style</title>
<updated>2018-05-07T13:34:12Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2018-05-06T21:58:06Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=83d290c56fab2d38cd1ab4c4cc7099559c1d5046'/>
<id>urn:sha1:83d290c56fab2d38cd1ab4c4cc7099559c1d5046</id>
<content type='text'>
When U-Boot started using SPDX tags we were among the early adopters and
there weren't a lot of other examples to borrow from.  So we picked the
area of the file that usually had a full license text and replaced it
with an appropriate SPDX-License-Identifier: entry.  Since then, the
Linux Kernel has adopted SPDX tags and they place it as the very first
line in a file (except where shebangs are used, then it's second line)
and with slightly different comment styles than us.

In part due to community overlap, in part due to better tag visibility
and in part for other minor reasons, switch over to that style.

This commit changes all instances where we have a single declared
license in the tag as both the before and after are identical in tag
contents.  There's also a few places where I found we did not have a tag
and have introduced one.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>Convert CONFIG_ENV_IS_IN_MMC/NAND/UBI and NOWHERE to Kconfig</title>
<updated>2017-07-26T01:08:01Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2017-07-24T03:19:39Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=2be296538e2e9d2893dc495b3fc8f9f6acb1454c'/>
<id>urn:sha1:2be296538e2e9d2893dc495b3fc8f9f6acb1454c</id>
<content type='text'>
This converts the following to Kconfig:
   CONFIG_ENV_IS_IN_MMC
   CONFIG_ENV_IS_IN_NAND
   CONFIG_ENV_IS_IN_UBI
   CONFIG_ENV_IS_NOWHERE

In fact this already exists for sunxi as a 'choice' config. However not
all the choices are available in Kconfig yet so we cannot use that. It
would lead to more than one option being set.

In addition, one purpose of this series is to allow the environment to be
stored in more than one place. So the existing choice is converted to a
normal config allowing each option to be set independently.

There are not many opportunities for Kconfig updates to reduce the size of
this patch. This was tested with

   ./tools/moveconfig.py -i CONFIG_ENV_IS_IN_MMC

And then manual updates.  This is because for CHAIN_OF_TRUST boards they
can only have ENV_IS_NOWHERE set, so we enforce that via Kconfig logic
now.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>power: Drop CONFIG_PMIC</title>
<updated>2017-04-30T14:29:54Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2017-04-27T04:27:48Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=92572ecf8069858b3bea282cd4ee6010aaa65c21'/>
<id>urn:sha1:92572ecf8069858b3bea282cd4ee6010aaa65c21</id>
<content type='text'>
This option is not used in U-Boot. Drop it.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>ARM: Migrate errata to Kconfig</title>
<updated>2017-03-10T00:52:50Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2017-03-07T12:13:42Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=8dda2e2f9e0976249f4a390e72f12533dbcb5ef4'/>
<id>urn:sha1:8dda2e2f9e0976249f4a390e72f12533dbcb5ef4</id>
<content type='text'>
This moves all of the current ARM errata from various header files and in to
Kconfig.  This allows for a minor amount of cleanup as we had some instances
where both a general common header file was enabling errata as well as the
board config.  We now just select these once at the higher level in Kconfig

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>Kconfig: Move config IDENT_STRING to Kconfig</title>
<updated>2016-09-20T13:30:23Z</updated>
<author>
<name>Siva Durga Prasad Paladugu</name>
</author>
<published>2016-07-29T10:01:47Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=a4d88920e5d0b67a92f8041f5e0fac0ce027bb48'/>
<id>urn:sha1:a4d88920e5d0b67a92f8041f5e0fac0ce027bb48</id>
<content type='text'>
Move the config IDENT_STRING to Kconfig and migrate all boards

[sivadur: Migrate zynq boards]
Signed-off-by: Siva Durga Prasad Paladugu &lt;sivadur@xilinx.com&gt;
[trini: Update configs, add some default to sunxi Kconfig]
Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>ARM: armv7: move ARMV7_PSCI_NR_CPUS to Kconfig</title>
<updated>2016-09-07T12:48:54Z</updated>
<author>
<name>Masahiro Yamada</name>
</author>
<published>2016-08-30T07:22:23Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=1544698816a32284947322d0f0fe1478a9b65ad3'/>
<id>urn:sha1:1544698816a32284947322d0f0fe1478a9b65ad3</id>
<content type='text'>
Move this option to Kconfig and set its default value to 4; this
increases the number of supported CPUs for some boards.

It consumes 1KB memory per CPU for PSCI stack, but it should not
be a big deal, given the amount of memory used for the modern OSes.

Reviewed-by: Alexander Graf &lt;agraf@suse.de&gt;
Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;
</content>
</entry>
<entry>
<title>configs: Add more CONFIG_ARMV7_PSCI_NR_CPUS entries</title>
<updated>2016-07-16T13:42:51Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2016-07-15T19:30:33Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=fc5d54b7fa3fa602e06e2f0863c0b134d6afca70'/>
<id>urn:sha1:fc5d54b7fa3fa602e06e2f0863c0b134d6afca70</id>
<content type='text'>
The code had assumed 4 CPUS before and now we have this configurable.
For now, set this to the previous default.

Cc: Chander Kashyap &lt;k.chander@samsung.com&gt;
Cc: Steve Rae &lt;steve.rae@raedomain.com&gt;
Cc: Minkyu Kang &lt;mk7.kang@samsung.com&gt;
Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
Reviewed-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
</content>
</entry>
<entry>
<title>arndale: Apply Cortex-A15 errata #773022 and #774769</title>
<updated>2015-10-11T21:12:11Z</updated>
<author>
<name>Ian Campbell</name>
</author>
<published>2015-09-29T09:27:09Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=e392b923ed6d6acff08b0a7aa5f457fff80fb0de'/>
<id>urn:sha1:e392b923ed6d6acff08b0a7aa5f457fff80fb0de</id>
<content type='text'>
We run 4 Arndale boards in our automated test framework, they have
been running quite happily for quite some time using a Debian Wheezy
userspace.

However when upgrading to a Debian Jessie we started seeing frequent
segmentation faults from gcc when building the kernel, to the extent
that it is unable to successfully build the kernel twice in a row, and
often fails on the first attempt.

Searching around I found https://bugs.launchpad.net/arndale/+bug/1081417
which pointed towards http://www.spinics.net/lists/kvm-arm/msg03723.html
and CPU Errata 773022 and 774769.

This errata needs to be applied to all processors in an SMP system,
meaning that the usual strategy of applying them in
arch/arm/cpu/armv7/start.S is not appropriate (since that applies to
the boot processor only). Instead we apply these errata in the secure
monitor which is code that is traversed by all processors as they are
brought up.

The net affect on Arndale is that ACTLR changes from 0x40 to
0x2000042. I ran 17 kernel compile iterations overnight with no
segfaults.

Runtime testing was done on our v2014.10 based branch and forward
ported (with only minimal and trivial contextual conflicts) to current
master, where it has been build tested only.

I suppose in theory these errata apply to any Exynos5250 based boards,
but Arndale is the only one I have access to and I have therefore
chosen to be conservative and only apply it there.

Also, reorder CONFIG_ARM_ERRATA_794072 in README to make the list
numerically sorted.

Signed-off-by: Ian Campbell &lt;ian.campbell@citrix.com&gt;
</content>
</entry>
</feed>
