<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Kconfig</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2025</copyright>
    <generator>Java</generator><item>
        <title>42392849739d2bd9eaadd89184909079c8ab760c - remoteproc: Add support for TI power processor</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_rockchip-uboot/drivers/remoteproc/Kconfig#42392849739d2bd9eaadd89184909079c8ab760c</link>
        <description>remoteproc: Add support for TI power processorMany TI System on Chip (SoC) solutions do have a dedicatedmicrocontroller for doing power management functionality. These includethe AM335x, AM437x, Keystone K2G SoCs. The functionality provided bythese microcontrollers and the communication mechanisms vary verywidely. However, we are able to consolidate some basic functionality tobe generic enough starting with K2G SoC family. Introduce a basic remoteproc driver to support these microcontrollers. In fact, on SoCs startingwith K2G, basic power management functions are primarily accessible forthe High Level Operating Systems(HLOS) via these microcontroller solutions.Hence, having these started at a bootloader level is pretty muchmandatory.Signed-off-by: Nishanth Menon &lt;nm@ti.com&gt;Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;

            List of files:
            /rk3399_rockchip-uboot/drivers/remoteproc/Kconfig</description>
        <pubDate>Thu, 25 Feb 2016 18:53:45 +0000</pubDate>
        <dc:creator>Nishanth Menon &lt;nm@ti.com&gt;</dc:creator>
    </item>
<item>
        <title>a69fdc7787bfa2f27eed74c2ee58c28ce932d502 - Merge branch &apos;master&apos; of git://git.denx.de/u-boot</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_rockchip-uboot/drivers/remoteproc/Kconfig#a69fdc7787bfa2f27eed74c2ee58c28ce932d502</link>
        <description>Merge branch &apos;master&apos; of git://git.denx.de/u-boot

            List of files:
            /rk3399_rockchip-uboot/drivers/remoteproc/Kconfig</description>
        <pubDate>Fri, 23 Oct 2015 10:35:42 +0000</pubDate>
        <dc:creator>Stefano Babic &lt;sbabic@denx.de&gt;</dc:creator>
    </item>
<item>
        <title>3df0b8b4dad19c764c1cc81d283bf903f4ab9e69 - remoteproc: Introduce a sandbox dummy driver</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_rockchip-uboot/drivers/remoteproc/Kconfig#3df0b8b4dad19c764c1cc81d283bf903f4ab9e69</link>
        <description>remoteproc: Introduce a sandbox dummy driverIntroduce a dummy driver for sandbox that allows us to verify basicfunctionality. This is not meant to do anything functional - but ismore or less meant as a framework plumbing debug helper.The sandbox remoteproc driver maintains absolutey no states and is asimple driver which just is filled with empty hooks. Idea being to givean approximate idea to implement own remoteproc driver using this as atemplate.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;

            List of files:
            /rk3399_rockchip-uboot/drivers/remoteproc/Kconfig</description>
        <pubDate>Thu, 17 Sep 2015 20:42:40 +0000</pubDate>
        <dc:creator>Nishanth Menon &lt;nm@ti.com&gt;</dc:creator>
    </item>
<item>
        <title>ddf56bc7e3ef43920b4a23320e70c1998f1ef843 - drivers: Introduce a simplified remoteproc framework</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/rk3399_rockchip-uboot/drivers/remoteproc/Kconfig#ddf56bc7e3ef43920b4a23320e70c1998f1ef843</link>
        <description>drivers: Introduce a simplified remoteproc frameworkMany System on Chip(SoC) solutions are complex with multiple processorson the same die dedicated to either general purpose of specializedfunctions. Many examples do exist in today&apos;s SoCs from various vendors.Typical examples are micro controllers such as an ARM M3/M0 doing aoffload of specific function such as event integration or powermanagement or controlling camera etc.Traditionally, the responsibility of loading up such a processor with afirmware and communication has been with a High Level OperatingSystem(HLOS) such as Linux. However, there exists classes of productswhere Linux would need to expect services from such a processor or thedelay of Linux and operating system being able to load up such afirmware is unacceptable.To address these needs, we need some minimal capability to load such asystem and ensure it is started prior to an Operating System(Linux orany other) is started up.NOTE: This is NOT meant to be a solve-all solution, instead, it tries toaddress certain class of SoCs and products that need such a solution.A very simple model is introduced here as part of the initial supportthat supports microcontrollers with internal memory (no MMU, noexecution from external memory, or specific image format needs). Thisbasic framework can then (hopefully) be extensible to other complex SoCprocessor support as need be.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;

            List of files:
            /rk3399_rockchip-uboot/drivers/remoteproc/Kconfig</description>
        <pubDate>Thu, 17 Sep 2015 20:42:39 +0000</pubDate>
        <dc:creator>Nishanth Menon &lt;nm@ti.com&gt;</dc:creator>
    </item>
</channel>
</rss>
