<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/u-boot/drivers/remoteproc, 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-10T00:22:05Z</updated>
<entry>
<title>remoteproc: k3_system_controller: Increase rx timeout</title>
<updated>2019-05-10T00:22:05Z</updated>
<author>
<name>Lokesh Vutla</name>
</author>
<published>2019-05-02T10:05:52Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=0d7b6cffa532eecfdc7cb87c2c65cd311344981f'/>
<id>urn:sha1:0d7b6cffa532eecfdc7cb87c2c65cd311344981f</id>
<content type='text'>
There is one case where 400ms is not sufficient for loading the
system firmware:
- System firmware is not signed with rsa degenerate key.
- ROM loading the sysfw directly from SPI flash which is in memory
  mapped mode.

The above scenario is definitely not desired in production use cases
as it effects boot time. But still keeping this support as this is
a valid boot scenario.

Signed-off-by: Lokesh Vutla &lt;lokeshvutla@ti.com&gt;
</content>
</entry>
<entry>
<title>spl: Allow remoteproc drivers to be used within SPL</title>
<updated>2018-09-11T12:32:55Z</updated>
<author>
<name>Lokesh Vutla</name>
</author>
<published>2018-08-27T10:27:53Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=08c45314a8f780aff8c2c9f39d57235f950bcee0'/>
<id>urn:sha1:08c45314a8f780aff8c2c9f39d57235f950bcee0</id>
<content type='text'>
Add an option for building remoteproc drivers within SPL.

Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
Signed-off-by: Lokesh Vutla &lt;lokeshvutla@ti.com&gt;
</content>
</entry>
<entry>
<title>remoteproc: Introduce K3 remoteproc driver</title>
<updated>2018-09-11T12:32:55Z</updated>
<author>
<name>Lokesh Vutla</name>
</author>
<published>2018-08-27T10:27:52Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=c365ed7d4bc4173baad05a0c2d40d48ce8e41394'/>
<id>urn:sha1:c365ed7d4bc4173baad05a0c2d40d48ce8e41394</id>
<content type='text'>
Add support for K3 based remoteproc driver that
communicates with TISCI to start start a remote processor.

Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
Signed-off-by: Lokesh Vutla &lt;lokeshvutla@ti.com&gt;
</content>
</entry>
<entry>
<title>remoteproc: Introduce K3 system controller</title>
<updated>2018-09-11T12:32:55Z</updated>
<author>
<name>Lokesh Vutla</name>
</author>
<published>2018-08-27T10:27:51Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=1ad190bf5936ad87d0bd80ecf55a1ce09e9d3ae9'/>
<id>urn:sha1:1ad190bf5936ad87d0bd80ecf55a1ce09e9d3ae9</id>
<content type='text'>
K3 specific SoCs have a dedicated microcontroller for doing
resource management. Any HLOS/firmware on compute clusters should
load a firmware to this microcontroller before accessing any resource.
Adding support for loading this firmware.

After the K3 system controller got loaded with firmware and started
up it sends out a boot notification message through the secure proxy
facility using the TI SCI protocol. Intercept and receive this message
through the rproc start operation which will need to get invoked
explicitly after the firmware got loaded.

Signed-off-by: Lokesh Vutla &lt;lokeshvutla@ti.com&gt;
Signed-off-by: Andreas Dannenberg &lt;dannenberg@ti.com&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>remoteproc: Allow for individual remoteproc initialization</title>
<updated>2018-09-11T12:32:55Z</updated>
<author>
<name>Lokesh Vutla</name>
</author>
<published>2018-08-27T10:27:50Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=81ae6e6d0098c9ad7d6746b4f2952a046130999c'/>
<id>urn:sha1:81ae6e6d0098c9ad7d6746b4f2952a046130999c</id>
<content type='text'>
Existing rproc_init() api tries to initialize all available
remoteproc devices. This will fail when there is dependency
among available remoteprocs. So introduce a separate api
that allows to initialize remoteprocs individually based
on id.

Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
Signed-off-by: Lokesh Vutla &lt;lokeshvutla@ti.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>dm: core: Replace of_offset with accessor</title>
<updated>2017-02-08T13:12:14Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2017-01-17T23:52:55Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=e160f7d430f163bc42757aff3bf2bcac0a459f02'/>
<id>urn:sha1:e160f7d430f163bc42757aff3bf2bcac0a459f02</id>
<content type='text'>
At present devices use a simple integer offset to record the device tree
node associated with the device. In preparation for supporting a live
device tree, which uses a node pointer instead, refactor existing code to
access this field through an inline function.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>remoteproc: Add support for TI power processor</title>
<updated>2016-03-14T23:18:37Z</updated>
<author>
<name>Nishanth Menon</name>
</author>
<published>2016-02-25T18:53:45Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=42392849739d2bd9eaadd89184909079c8ab760c'/>
<id>urn:sha1:42392849739d2bd9eaadd89184909079c8ab760c</id>
<content type='text'>
Many TI System on Chip (SoC) solutions do have a dedicated
microcontroller for doing power management functionality. These include
the AM335x, AM437x, Keystone K2G SoCs. The functionality provided by
these microcontrollers and the communication mechanisms vary very
widely. However, we are able to consolidate some basic functionality to
be generic enough starting with K2G SoC family. Introduce a basic remote
proc driver to support these microcontrollers. In fact, on SoCs starting
with K2G, basic power management functions are primarily accessible for
the High Level Operating Systems(HLOS) via these microcontroller solutions.

Hence, having these started at a bootloader level is pretty much
mandatory.

Signed-off-by: Nishanth Menon &lt;nm@ti.com&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>drivers: remoteproc: rproc-uclass: Fix check for NULL pointers</title>
<updated>2015-12-05T23:22:32Z</updated>
<author>
<name>Nishanth Menon</name>
</author>
<published>2015-12-01T04:05:58Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=9cb05a8f9f87297820a5ff6a487f100cb1cd69c1'/>
<id>urn:sha1:9cb05a8f9f87297820a5ff6a487f100cb1cd69c1</id>
<content type='text'>
Neither uc_pdata-&gt;name nor check_name are supposed to be NULL in
_rproc_name_is_unique(). if uc_pdata-&gt;name is NULL, we are not
intialized yet, however if check_data is NULL, we do not have
proper data. Further, if either were NULL, strlen will crap out
while attempting to derefence NULL.

Instead, just check if either of these are NULL and bail out.

This should also fix the following coverity scan warnings:
*** CID 132281:  Null pointer dereferences  (FORWARD_NULL)
/drivers/remoteproc/rproc-uclass.c: 73 in _rproc_name_is_unique()

Reported-by: Tom Rini &lt;trini@konsulko.com&gt;
Signed-off-by: Nishanth Menon &lt;nm@ti.com&gt;
</content>
</entry>
<entry>
<title>remoteproc: Introduce a sandbox dummy driver</title>
<updated>2015-10-22T18:18:39Z</updated>
<author>
<name>Nishanth Menon</name>
</author>
<published>2015-09-17T20:42:40Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=3df0b8b4dad19c764c1cc81d283bf903f4ab9e69'/>
<id>urn:sha1:3df0b8b4dad19c764c1cc81d283bf903f4ab9e69</id>
<content type='text'>
Introduce a dummy driver for sandbox that allows us to verify basic
functionality. This is not meant to do anything functional - but is
more or less meant as a framework plumbing debug helper.

The sandbox remoteproc driver maintains absolutey no states and is a
simple driver which just is filled with empty hooks. Idea being to give
an approximate idea to implement own remoteproc driver using this as a
template.

Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Signed-off-by: Nishanth Menon &lt;nm@ti.com&gt;
Acked-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
</feed>
