- Feb 06, 2015
-
-
Bin Meng authored
Add COMPAT_INTEL_QRK_MRC and "intel,quark-mrc" so that fdtdec can decode Intel Quark MRC node. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
- Jan 30, 2015
-
-
Simon Glass authored
This has moved to driver model so we don't need the fdtdec support. Signed-off-by:
Simon Glass <sjg@chromium.org> Acked-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Simon Glass authored
These have moved to driver model so we don't need the fdtdec support. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Now that we support device tree GPIO bindings directly in the driver model GPIO uclass we can remove these functions. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
For GPIOs and other functions we want to look up a phandle and then decode a list of arguments for that phandle. Each phandle can have a different number of arguments, specified by a property in the target node. This is the "#gpio-cells" property for GPIOs. Add a function to provide this feature, taken modified from Linux 3.18. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Jan 24, 2015
-
-
Simon Glass authored
Add this to the enum so that we can use the various fdtdec functions. A later commit will move this driver to driver model. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Jan 13, 2015
-
-
Bin Meng authored
This commit adds several APIs to decode PCI device node according to the Open Firmware PCI bus bindings, including: - fdtdec_get_pci_addr() for encoded pci address - fdtdec_get_pci_vendev() for vendor id and device id - fdtdec_get_pci_bdf() for pci device bdf triplet - fdtdec_get_pci_bar32() for pci device register bar Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Acked-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Simon Glass <sjg@chromium.org> (Include <pci.h> in fdtdec.h and adjust tegra to fix build error)
-
- Dec 18, 2014
-
-
Thierry Reding authored
Add support for the PCIe controller found on some generations of Tegra. Tegra20 has 2 root ports with a total of 4 lanes, Tegra30 has 3 root ports with a total of 6 lanes and Tegra124 has 2 root ports with a total of 5 lanes. This is based on the Linux kernel driver, originally submitted upstream by Mike Rapoport. Signed-off-by:
Mike Rapoport <mike@compulab.co.il> Signed-off-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Thierry Reding authored
This controller was introduced on Tegra114 to handle XUSB pads. On Tegra124 it is also used for PCIe and SATA pin muxing and PHY control. Only the Tegra124 PCIe and SATA functionality is currently implemented, with weak symbols on Tegra114. Tegra20 and Tegra30 also provide weak symbols for these functions so that drivers can use the same API irrespective of which SoC they're being built for. Signed-off-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
Thierry Reding authored
The AS3722 provides a number of DC/DC converters and LDOs as well as 8 GPIOs. Signed-off-by:
Thierry Reding <treding@nvidia.com> Signed-off-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
- Nov 27, 2014
-
-
Masahiro Yamada authored
The fdt_path_offset() checks an alias too. fdtdec_get_alias_node(blob, "foo") is equivalent to fdt_path_offset(blob, "foo"). Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
- Nov 25, 2014
-
-
Simon Glass authored
Intel's Graphics Media Accelerator (GMA) is a generic name for a wide range of video devices. Add code to set up the hardware on ivybridge. Part of the init happens in native code, part of it happens in a 16-bit option ROM for those nostalgic for the 1970s. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Add the setup code for the CPU so that it can be used at full speed. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Add code to set up the SATA interfaces on boot. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Nov 21, 2014
-
-
Simon Glass authored
Implement SDRAM init using the Memory Reference Code (mrc.bin) provided in the board directory and the SDRAM SPD information in the device tree. This also needs the Intel Management Engine (me.bin) to work. Binary blobs everywhere: so far we have MRC, ME and microcode. SDRAM init works by setting up various parameters and calling the MRC. This in turn does some sort of magic to work out how much memory there is and the timing parameters to use. It also sets up the DRAM controllers. When the MRC returns, we use the information it provides to map out the available memory in U-Boot. U-Boot normally moves itself to the top of RAM. On x86 the RAM is not generally contiguous, and anyway some RAM may be above 4GB which doesn't work in 32-bit mode. So we relocate to the top of the largest block of RAM we can find below 4GB. Memory above 4GB is accessible with special functions (see physmem). It would be possible to build U-Boot in 64-bit mode but this wouldn't necessarily provide any more memory, since the largest block is often below 4GB. Anyway U-Boot doesn't need huge amounts of memory - even a very large ramdisk seldom exceeds 100-200MB. U-Boot has support for booting 64-bit kernels directly so this does not pose a limitation in that area. Also there are probably parts of U-Boot that will not work correctly in 64-bit mode. The MRC is one. There is some work remaining in this area. Since memory init is very slow (over 500ms) it is possible to save the parameters in SPI flash to speed it up next time. Suspend/resume support is not fully implemented, or at least it is not efficient. With this patch, link boots to a prompt. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Microcode updates are stored in the device tree. Work through these and apply any that are needed. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Sometimes an array can be of variable size up to a maximum. Add a helper function to decode this. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Permit decoding of a named memory region from the device tree. This allows easy run-time configuration of the address of on-chip SRAM, SDRAM, etc. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Tom Rini <trini@ti.com>
-
Simon Glass authored
Flash regions can optionally be compressed or hashed. Add the ability to read this information from the flashmap. Signed-off-by:
Simon Glass <sjg@chromium.org> Acked-by:
Anatolij Gustschin <agust@denx.de> Reviewed-by:
Tom Rini <trini@ti.com>
-
Simon Glass authored
Use the correct FDT data types for this function. Also add more debugging. Acked-by:
Anatolij Gustschin <agust@denx.de> Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Tom Rini <trini@ti.com>
-
- Oct 23, 2014
-
-
Simon Glass authored
Add this to the table so that it can be recognised. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Oct 22, 2014
-
-
Thierry Reding authored
The fdtdec_pci_get_bdf() function returns the bus, device, function triplet of a PCI device by parsing the "reg" property according to the PCI device tree binding. Acked-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Thierry Reding <treding@nvidia.com>
-
Thierry Reding authored
Add the fdt_get_resource() and fdt_get_named_resource() functions which can be used to parse resources (memory regions) from an FDT. A helper to compute the size of a region is also provided. Signed-off-by:
Thierry Reding <treding@nvidia.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
- Sep 10, 2014
-
-
Simon Glass authored
Within /chosen we may have a node which points to another node, similar to how /aliases works. Add a helper function to do this lookup. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Sep 05, 2014
-
-
Vadim Bendebury authored
The initialization table comes from the "Illustration of I2C command for initialing PS8625" document supplied by Parade. Signed-off-by:
Vadim Bendebury <vbendeb@chromium.org> Signed-off-by:
Ajay Kumar <ajaykumar.rs@samsung.com> Acked-by:
Simon Glass <sjg@chromium.org> Tested-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Ajay Kumar authored
On Exynos5420 and newer versions, the FIMD sysmmus are in "on state" by default. We have to disable them in order to make FIMD DMA work. This patch adds the required framework to exynos_fimd driver, and disables FIMD sysmmu on Exynos5420. Signed-off-by:
Ajay Kumar <ajaykumar.rs@samsung.com> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
- Jul 23, 2014
-
-
Simon Glass authored
This simple function returns the node offset of a named alias. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Aliases are used to provide U-Boot's numbering of devices, such as: aliases { spi0 = "/spi@12330000"; } spi@12330000 { ... } This tells us that the SPI controller at 12330000 is considered to be the first SPI controller (SPI 0). So we have a numbering for the SPI node. Add a function that returns the numbering for a node assume that it exists in the list of aliases. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- May 28, 2014
-
-
Simon Glass authored
The backlight uses FETs on the TPS65090. Enable this so that the display is visible. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Lukasz Majewski <l.majewski@samsung.com> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Tom Wai-Hong Tam authored
This adds driver support for the TPS65090 PMU. Support includes hooking into the pmic infrastructure so that the pmic commands can be used on the console. The TPS65090 supports the following functionality: - fet enable/disable/querying - getting and setting of charge state Even though it is connected to the pmic infrastructure it does not hook into the pmic charging charging infrastructure. The device tree binding is from Linux, but only a small subset of functionality is supported. Signed-off-by:
Tom Wai-Hong Tam <waihong@chromium.org> Signed-off-by:
Hatim Ali <hatim.rv@samsung.com> Signed-off-by:
Katie Roberts-Hoffman <katierh@chromium.org> Signed-off-by:
Rong Chang <rongchang@chromium.org> Signed-off-by:
Sean Paul <seanpaul@chromium.org> Signed-off-by:
Vincent Palatin <vpalatin@chromium.org> Signed-off-by:
Aaron Durbin <adurbin@chromium.org> Signed-off-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
- May 16, 2014
-
-
Jaehoon Chung authored
Exynos serise can be supported the dw-mmc controller. So, it's good that used the general prefix as "_EXYNOS_DWMMC". Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
- Mar 18, 2014
-
-
Simon Glass authored
Add a simple LCD driver which uses SDL to display the image. We update the image regularly, while still providing for reasonable performance. Adjust the common lcd code to support sandbox. For command-line runs we do not want the LCD to be displayed, so add a --show_lcd option to enable it. Tested-by:
Che-Liang Chiou <clchiou@chromium.org> Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Add a simple emulation of the Chrome OS EC for sandbox, so that it can perform various EC tasks such as keyboard handling. Reviewed-by:
Vadim Bendebury <vbendeb@chromium.org> Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
A flash map describes the layout of flash memory in terms of offsets and sizes for each region. Add a function to read a flash map entry from the device tree. Reviewed-by:
Che-Liang Chiou <clchiou@chromium.org> Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Mar 12, 2014
-
-
Piotr Wilczek authored
This patch enables support for device tree for sdhci driver. Non DT case is still supported. Signed-off-by:
Piotr Wilczek <p.wilczek@samsung.com> Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Piotr Wilczek authored
This patch enables parsing mipi data from device tree. Non device tree case is still supported. Signed-off-by:
Piotr Wilczek <p.wilczek@samsung.com> Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> Signed-off-by:
Minkyu Kang <mk7.kang@samsung.com>
-
- Feb 03, 2014
-
-
Stephen Warren authored
Tegra124's MMC controller is very similar to earlier SoC generations, and can be supported by the same driver. However, there are some non-backwards-compatible HW differences, and hence a new DT compatible value must be used to describe the HW. This patch updates the driver to support that new compatible value. That said, the HW differences are only relevant when enabling certain high-performance transfer modes. Since the driver is currently very simple and doesn't enable those modes, we don't actually need to address any of these HW differences in the code yet, hence the simple nature of this patch. Signed-off-by:
Stephen Warren <swarren@nvidia.com> Acked-by:
Pantelis Antoniou <panto@antoniou-consulting.com> Tested-by:
Thierry Reding <treding@nvidia.com> Acked-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Tom Warren <twarren@nvidia.com>
-
- Oct 20, 2013
-
-
Vivek Gautam authored
Adding required compatible string for xHCI host controller as well as USB 3.0 PHY to enable dt support for usb 3.0 on exynos5. Signed-off-by:
Vivek Gautam <gautam.vivek@samsung.com> Cc: Julius Werner <jwerner@chromium.org> Cc: Simon Glass <sjg@chromium.org> Cc: Minkyu Kang <mk7.kang@samsung.com> Cc: Dan Murphy <dmurphy@ti.com> Cc: Marek Vasut <marex@denx.de>
-
- Jul 24, 2013
-
-
Wolfgang Denk authored
Signed-off-by:
Wolfgang Denk <wd@denx.de> [trini: Fixup common/cmd_io.c] Signed-off-by:
Tom Rini <trini@ti.com>
-
- Jul 23, 2013
-
-
Adds a new COMPAT string exynos5-hsi2c for high speed i2c controller available on exynos5 SoCs from Samsung. Signed-off-by:
Naveen Krishna Chatradhi <ch.naveen@samsung.com>
-