- 23 10月, 2015 40 次提交
-
-
由 Vitaly Andrianov 提交于
Coreect base addresses for SPI, Queue Manager, Ethernet, GPIO, and MSMC segments. Signed-off-by: NVitaly Andrianov <vitalya@ti.com> Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Vitaly Andrianov 提交于
Add pin mux data for k2g-evm Signed-off-by: NVitaly Andrianov <vitalya@ti.com> Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Vitaly Andrianov 提交于
Add api for configuring pin mux. Signed-off-by: NVitaly Andrianov <vitalya@ti.com> Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Vitaly Andrianov 提交于
Add ddr3 related info Signed-off-by: NVitaly Andrianov <vitalya@ti.com> Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Vitaly Andrianov 提交于
Add psc information for k2g Signed-off-by: NVitaly Andrianov <vitalya@ti.com> Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Vitaly Andrianov 提交于
Add clock information for Galileo Signed-off-by: NVitaly Andrianov <vitalya@ti.com> Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com> Signed-off-by: NMugunthan V N <mugunthanvnm@ti.com>
-
由 Vitaly Andrianov 提交于
Add pll data for k2g Signed-off-by: NVitaly Andrianov <vitalya@ti.com> Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Lokesh Vutla 提交于
Add Kconfig support Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Lokesh Vutla 提交于
Adding CPU detection support for Keystone2 Galileo. Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Lokesh Vutla 提交于
Now that OF_CONTROL is enabled on all keystone2 platforms, build the default images with DT. Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Lokesh Vutla 提交于
Import k2e specific DT files from Linux Kernel and enable OF_CONTROL, DM, DM_SERIAL. Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Lokesh Vutla 提交于
Import k2l specific DT files from Linux Kernel and enable OF_CONTROL, DM, DM_SERIAL. Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Lokesh Vutla 提交于
Import k2hk specific DT files from Linux Kernel and enable OF_CONTROL, DM, DM_SERIAL. Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Lokesh Vutla 提交于
Keystone dts files assumes that LPAE is enabled and top level root node uses 64bit addresses. This breaks the keystone boot with CONFIG_OF_CONTROL enabled. So do not use 64 bit addresse in U-Boot DT. Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Lokesh Vutla 提交于
Import various generic dts files from Linux kernel so that all keystone2 platforms can be DT in U-boot. Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Lokesh Vutla 提交于
If CONFIG_SYS_MALLOC_F_LEN is enabled, the stack is moved down to the specified size to make the malloc function available before relocation. But on keystone platforms SYS_SPL_MALLOC is immediately preceding stack, which is causing an overlap with this config enabled. So leave a gap between malloc space and stack space. Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Lokesh Vutla 提交于
With CONFIG_DM_SERIAL is enabled NS16550_init() cannot be called directly. Driver probe should be taking care of this. So call this function only when DM_SERIAL is not enabled. Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Tom Rini 提交于
Tested on J6Eco EVM. Signed-off-by: NTom Rini <trini@konsulko.com> Tested-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Tom Rini 提交于
Tested on J6Eco EVM Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Tom Rini 提交于
Tested on Pandaboard Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Nishanth Menon 提交于
Use the sandbox environment for the basic tests. Reviewed-by: NSimon Glass <sjg@chromium.org> Tested-by: NSimon Glass <sjg@chromium.org> Signed-off-by: NNishanth Menon <nm@ti.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Nishanth Menon 提交于
Introduce dummy devices for sandbox remoteproc device and enable it by default Reviewed-by: NSimon Glass <sjg@chromium.org> Signed-off-by: NNishanth Menon <nm@ti.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Nishanth Menon 提交于
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: NSimon Glass <sjg@chromium.org> Signed-off-by: NNishanth Menon <nm@ti.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Nishanth Menon 提交于
Many System on Chip(SoC) solutions are complex with multiple processors on the same die dedicated to either general purpose of specialized functions. Many examples do exist in today's SoCs from various vendors. Typical examples are micro controllers such as an ARM M3/M0 doing a offload of specific function such as event integration or power management or controlling camera etc. Traditionally, the responsibility of loading up such a processor with a firmware and communication has been with a High Level Operating System(HLOS) such as Linux. However, there exists classes of products where Linux would need to expect services from such a processor or the delay of Linux and operating system being able to load up such a firmware is unacceptable. To address these needs, we need some minimal capability to load such a system and ensure it is started prior to an Operating System(Linux or any other) is started up. NOTE: This is NOT meant to be a solve-all solution, instead, it tries to address certain class of SoCs and products that need such a solution. A very simple model is introduced here as part of the initial support that supports microcontrollers with internal memory (no MMU, no execution from external memory, or specific image format needs). This basic framework can then (hopefully) be extensible to other complex SoC processor support as need be. Reviewed-by: NSimon Glass <sjg@chromium.org> Signed-off-by: NNishanth Menon <nm@ti.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Mugunthan V N 提交于
enable ethernet driver model for am335x gp evm as cpsw supports driver model Signed-off-by: NMugunthan V N <mugunthanvnm@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Mugunthan V N 提交于
enable ethernet driver model for am335x beagle bone black as cpsw supports driver model Signed-off-by: NMugunthan V N <mugunthanvnm@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Mugunthan V N 提交于
adopt cpsw driver to device driver model Signed-off-by: NMugunthan V N <mugunthanvnm@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Mugunthan V N 提交于
prepare driver for device model migration Signed-off-by: NMugunthan V N <mugunthanvnm@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Mugunthan V N 提交于
Since usb ether gadget doesn't have support for driver model, so not defining usb ether gadget when ethernet driver model is defined. Signed-off-by: NMugunthan V N <mugunthanvnm@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Mugunthan V N 提交于
Prepare board file so that ethernet registration are commented for DM conversion Signed-off-by: NMugunthan V N <mugunthanvnm@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Sjoerd Simons 提交于
Add support for distro bootcmds and network booting while retaining backwards compatibility with the current "legacy" setup. With these changes the default boot sequence becomes: * SD card (standard distro boot) * SD card (legacy boot) * EMMC (standard distro boot) * EMMC (legacy boot) * Nand (legacy boot) * PXE (standard distro boot) * DHCP (standard distro boot) The older boot scripts have some overlap with what the distro bootcommands to however i've left them unchanged to prevent introduction of subtle bugs. Signed-off-by: NSjoerd Simons <sjoerd.simons@collabora.co.uk>
-
由 Sjoerd Simons 提交于
Add mandatory address variables for loading scripts and pxe configuration as per README.distro Signed-off-by: NSjoerd Simons <sjoerd.simons@collabora.co.uk>
-
由 Sjoerd Simons 提交于
Hush has an oddity where using ${var} causes var to resolved in the the global address space (iotw the environment) first and only afterwards will the local variable space be searched. This causes odd side-effects when iterating over the boot partitions using ${bootpart} if the environment also has a bootpart variable (e.g. for the various TI boards). Fix this by using the hopefully more unique ${distro_bootpart} instead of ${bootpart}. Signed-off-by: NSjoerd Simons <sjoerd.simons@collabora.co.uk> Acked-by: NStephen Warren <swarren@wwwdotorg.org>
-
由 Paul Kocialkowski 提交于
Since there is a common function to grab the serial number from the die id bits, it makes sense have one to parse that serial number and feed it to the serial ATAG. Signed-off-by: NPaul Kocialkowski <contact@paulk.fr> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Paul Kocialkowski 提交于
This introduces omap_die_id_display to display the full die id. There is no need to store it in an environment variable, that no boot script is using anyway. Signed-off-by: NPaul Kocialkowski <contact@paulk.fr> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Paul Kocialkowski 提交于
Now that we have a common prototype to grab the omap die id, functions to figure out a serial number and usb ethernet address can use it directly. Those also get an omap_die_id prefix for better consistency. Signed-off-by: NPaul Kocialkowski <contact@paulk.fr> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Paul Kocialkowski 提交于
This introduces omap5 support for omap_die_id, which matches the common omap_die_id definition. It replaces board-specific code to grab the die id bits. Signed-off-by: NPaul Kocialkowski <contact@paulk.fr> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Paul Kocialkowski 提交于
This introduces omap4 support for omap_die_id, which matches the common omap_die_id definition. It replaces board-specific code to grab the die id bits. Signed-off-by: NPaul Kocialkowski <contact@paulk.fr> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Paul Kocialkowski 提交于
This replaces the previous get_dieid definition with omap_die_id, that matches the common omap_die_id definition. Signed-off-by: NPaul Kocialkowski <contact@paulk.fr> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Paul Kocialkowski 提交于
This introduces a common definition for omap_die_id, that aims at providing a common interface for accessing omap platform's die id bits. Signed-off-by: NPaul Kocialkowski <contact@paulk.fr> Reviewed-by: NTom Rini <trini@konsulko.com>
-