<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/u-boot/arch/arm/mach-keystone/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-12T12:05:46Z</updated>
<entry>
<title>ARM: k2g: add a workaround to reset the phy</title>
<updated>2019-04-12T12:05:46Z</updated>
<author>
<name>Murali Karicheri</name>
</author>
<published>2019-02-21T17:02:04Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=f748ec9d328b95cc246c960c1cd6c6478b57e788'/>
<id>urn:sha1:f748ec9d328b95cc246c960c1cd6c6478b57e788</id>
<content type='text'>
This patch adds a workaround to reset the phy one time during boot
using GPIO0 pin 10 to make sure, the Phy latches the configuration
from the input pins correctly.

Signed-off-by: Murali Karicheri &lt;m-karicheri2@ti.com&gt;
Acked-by: Joe Hershberger &lt;joe.hershberger@ni.com&gt;
</content>
</entry>
<entry>
<title>ARM: k2g-ice: Add pinmux support for rgmii interface</title>
<updated>2019-04-12T12:05:45Z</updated>
<author>
<name>Murali Karicheri</name>
</author>
<published>2019-02-21T17:02:01Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=c7206e978920bb87dd08679a11990a5548b62f36'/>
<id>urn:sha1:c7206e978920bb87dd08679a11990a5548b62f36</id>
<content type='text'>
This add pinmux configuration for rgmii interface so that network
driver can be supported on K2G ICE boards. The pinmux configurations
for this are generated using the pinmux tool at
https://dev.ti.com/pinmux/app.html#/default

As this required some BUFFER_CLASS definitions, same is re-used
from the linux defnitions in include/dt-bindings/pinctrl/keystone.h

Signed-off-by: Murali Karicheri &lt;m-karicheri2@ti.com&gt;
Reviewed-by: Lokesh Vutla &lt;lokeshvutla@ti.com&gt;
Acked-by: Joe Hershberger &lt;joe.hershberger@ni.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>cmd: ti: Generalize cmd_ddr3 command</title>
<updated>2018-01-19T20:49:26Z</updated>
<author>
<name>Lokesh Vutla</name>
</author>
<published>2017-12-29T06:17:50Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=8a8af8a2fd5cbe98b5680ba6822fe38686b6bdb6'/>
<id>urn:sha1:8a8af8a2fd5cbe98b5680ba6822fe38686b6bdb6</id>
<content type='text'>
Keystone and DRA7 based TI platforms uses same
EMIF memory controller. cmd_ddr3 command is customized
for keystone platforms, make it generic so that it can
be re used for DRA7  platforms.

Signed-off-by: Lokesh Vutla &lt;lokeshvutla@ti.com&gt;
</content>
</entry>
<entry>
<title>board: ti: K2G FC SoC 1GHz and DDR3 1066 MT/s support</title>
<updated>2018-01-19T20:49:24Z</updated>
<author>
<name>Rex Chang</name>
</author>
<published>2017-12-28T15:09:59Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=4849d9540751cdf66d5169e2bcc4ee0ea9a6f647'/>
<id>urn:sha1:4849d9540751cdf66d5169e2bcc4ee0ea9a6f647</id>
<content type='text'>
Added support for K2G EVM with FlipChip SoC of which
ARM/DDR3 runs at 1GHz/1066 MT/s. The patch is also
backward compatible with old revision EVM and EVM
with WireBond SoC. Their ARM/DDR3 run at 600MHz/800 MT/s.

The new SoC supports 2 different speeds at 1GHz and 600MHz.
Modyfied the CPU Name to show which SoC is used in the EVM.
Modified the DDR3 configuration to reflect New SoC supports
2 different CPU and DDR3 speeds, 1GHz/1066MT and 600MHz/800MT.

Added new inline function board_it_k2g_g1() for the new FlipChip 1GHz,
and set the u-boot env variable board_name accordingly.

Modified findfdt script in u-boot environment variable to include new k2g board type.

Signed-off-by: Rex Chang &lt;rchang@ti.com&gt;
Signed-off-by: Lokesh Vutla &lt;lokeshvutla@ti.com&gt;
</content>
</entry>
<entry>
<title>omap: Update the base address of the MMC controllers</title>
<updated>2018-01-19T03:04:21Z</updated>
<author>
<name>Jean-Jacques Hiblot</name>
</author>
<published>2017-09-21T14:51:33Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=f844d5f4e6bd97c3a4a39e180b5efa8b0b0abd56'/>
<id>urn:sha1:f844d5f4e6bd97c3a4a39e180b5efa8b0b0abd56</id>
<content type='text'>
Align the base address defined in header files with the base address used
in the DTS. This will facilitate the introduction of the DMA support.

Of all HSMMC users, only omap3 doesn't have the 0x100 reserved region at
the top. This region will be used to determine if the controller supports
DMA transfers

Signed-off-by: Jean-Jacques Hiblot &lt;jjhiblot@ti.com&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>arm: mach-keystone: Updates mon_install for K2G HS</title>
<updated>2017-07-26T15:26:51Z</updated>
<author>
<name>Madan Srinivas</name>
</author>
<published>2017-07-17T17:59:15Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=1d73ce6f68f2799735d65448f8211de3f83110fd'/>
<id>urn:sha1:1d73ce6f68f2799735d65448f8211de3f83110fd</id>
<content type='text'>
On early K2 devices (eg. K2HK) the secure ROM code does not support
loading secure code to firewall protected memory, before decrypting,
authenticating and executing it.

To load the boot monitor on these devices, it is necessary to first
authenticate and run a copy loop from non-secure memory that copies
the boot monitor behind firewall protected memory, before decrypting
and executing it.

On K2G, the secure ROM does not allow secure code executing from
unprotected memory. Further, ROM first copies the signed and encrypted
image into firewall protected memory, then decrypts, authenticates
and executes it.

As a result of this, we cannot use the copy loop for K2G. The
mon_install has to be modified to pass the address the signed and
encrypted secure boot monitor image to the authentication API.

For backward compatibility with other K2 devices and K2G GP,
the mon_install API still supports a single argument. In this case
the second argument is set to 0 by u-boot and is ignored by ROM

Signed-off-by: Thanh Tran &lt;thanh-tran@ti.com&gt;
Signed-off-by: Madan Srinivas &lt;madans@ti.com&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>ARM: keystone2: Add additional fields used for DDR3 configuration</title>
<updated>2017-07-10T18:25:56Z</updated>
<author>
<name>Cooper Jr., Franklin</name>
</author>
<published>2017-06-16T22:25:19Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=f8b4a2d7e219abfd22cf93de043f4102052e3a9d'/>
<id>urn:sha1:f8b4a2d7e219abfd22cf93de043f4102052e3a9d</id>
<content type='text'>
Future boards will need to configure DDR3 registers in a slightly
different manner. Support this by defining additional variables and
defines that will be utilized later.

Signed-off-by: Franklin S Cooper Jr &lt;fcooper@ti.com&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>ARM: keystone2: Add support for getting external clock dynamically</title>
<updated>2017-05-08T16:34:29Z</updated>
<author>
<name>Lokesh Vutla</name>
</author>
<published>2017-05-03T11:28:26Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=ee3c6532be343e495d11adfe15a457d24d9747d9'/>
<id>urn:sha1:ee3c6532be343e495d11adfe15a457d24d9747d9</id>
<content type='text'>
One some keystone2 platforms like K2G ICE, there is an option
to switch between 24MHz or 25MHz as sysclk. But the existing
driver assumes it is always 24MHz. Add support for getting
all reference clocks dynamically by reading boot pins.

Signed-off-by: Lokesh Vutla &lt;lokeshvutla@ti.com&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>ARM: k2g: Add support for dynamic programming of PLL based on SYSCLK</title>
<updated>2017-05-08T16:34:29Z</updated>
<author>
<name>Lokesh Vutla</name>
</author>
<published>2017-05-03T11:28:25Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=c5f177debc8b430c0a0038a9d8f6309eb3bd6299'/>
<id>urn:sha1:c5f177debc8b430c0a0038a9d8f6309eb3bd6299</id>
<content type='text'>
K2G supports various sysclk frequencies which can be
determined using sysboot pins. PLLs should be configured
based on this sysclock frequency. Add PLL configurations
for all supported sysclk frequencies.

Signed-off-by: Lokesh Vutla &lt;lokeshvutla@ti.com&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
</feed>
