1. Moved gpio structure declaration to gpio.h
2. Moved gpio configuration bit value macros to dt-bindings
Change-Id: I9da1cc3703a92e02cfa86765c8d4afe5321fed35
Signed-off-by: Gokul Sriram Palanisamy <gpalan@codeaurora.org>
Added device tree based IPQ common GPIO driver.
Updated device tree with uart_gpio data.
Change-Id: I4752609a766716d3bdd97f6ca1c1c20ffa3caa47
Signed-off-by: Aditya Kumar Patra S <apatr@codeaurora.org>
Diagnostics support includes read, write and probe
commands.
Change-Id: I899be70b69c5965e72ae413b913e4f837ffc9f40
Signed-off-by: Ajay Kishore <akisho@codeaurora.org>
Sets qpic-nand base address by reading from device tree using the
compatible string
Change-Id: I6e23ea579d9472fc9c977f9b549c312d61e9402b
Signed-off-by: Gokul Sriram Palanisamy <gpalan@codeaurora.org>
Moved to DM approach to make it more flexible to support
AK/DK/HK chipset.
Change-Id: I0fded02c97b7ace500df44bbf39285ef6fb58321
Signed-off-by: Saravanan Jaganathan <sjaganat@codeaurora.org>
This would allow us to define architecture specific base address
in the respective config files.
Change-Id: Ide1573525cfe09d8db51d397ee55b907b256f47e
Signed-off-by: Saravanan Jaganathan <sjaganat@codeaurora.org>
Step 1 to make this file generic to support AK/DK/DK.
Change-Id: Ie058337135b73510d29a3e563c1c341aa6b1fd8e
Signed-off-by: Saravanan Jaganathan <sjaganat@codeaurora.org>
Fixed warnings for both ipq807x and ipq40xx
builds.
Change-Id: I69accebf525ee52f470335a14474378f5e7f65b0
Signed-off-by: Saravanan Jaganathan <sjaganat@codeaurora.org>
Basic USB enumuration support has been added.
Only storage devices are identified. Hubs are not supported.
Change-Id: Ia6532d7cec4e531270fc403381a1d690a9e455f0
Signed-off-by: Ajay Kishore <akisho@codeaurora.org>
Signed-off-by: Saravanan Jaganathan <sjaganat@codeaurora.org>
check the image header, if the magic signature matches then
perform and indirect jump to 64 bit EL1 through TZ.
Change-Id: I92888faa7ed908652671bf09a4f6d4599340db5b
Signed-off-by: Manoharan Vijaya Raghavan <mraghava@codeaurora.org>
dtbs are made as .o
a table specifying their machid and address is added
the dtbs and header are added to u-boot image in a seperate section
dtb will be chosen based on machid detected from SMEM
Change-Id: I50ac5b56da3a431c1a75cb9fc113fafaedbc09b8
Signed-off-by: Manoharan Vijaya Raghavan <mraghava@codeaurora.org>
The SMEM is used for all the platforms like ipq40xx and ipq807x.
So moving this into a common place to use all qcom platforms.
Change-Id: I04f0bf0e7aad0eae71024d734d8049a3470d510d
Signed-off-by: Sham Muthayyan <smuthayy@codeaurora.org>
u-boot and dtb are seperate images. This patch combines them as
single ELF image.
Change-Id: Ib3c72c26844ffd4fd8489d0595c243a15434802e
Signed-off-by: Manoharan Vijaya Raghavan <mraghava@codeaurora.org>
DDR base address is now fixed to be at 0x40000000 and this patch
changes u-boot load address in accordance with that.
Change-Id: I13d0da43a7b0db0e6e322e3828e42da46ebd53cb
Signed-off-by: Manoharan Vijaya Raghavan <mraghava@codeaurora.org>
If CONFIG_SYS_STDIO_DEREGISTER is not enabled, usb reset
will fail every time. Enabling it allows usb reset to
work.
Signed-off-by: Andy Fleming <afleming@gmail.com>
The default kernel load offset for an arm64 kernel is 0x80000, so
U-Boot takes cares of moving the loaded kernel to a matching memory
location just before booting it.
Since we run with caches off, this takes a while for any decently
sized kernel - with no output explaining the reason for the delay
(unless one uses a DEBUG build).
By adjusting the default load offset for Juno and VFP to be 512K
aligned in the first place we can skip this copying and boot much
faster.
Tested on Juno.
Signed-off-by: Andre Przywara <andre.przywara@arm.com>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Tested-by: Ryan Harkin <ryan.harkin@linaro.org>
Various updates did not make it through to this board. Also the instructions
for building a SPI image are no-longer correct. Fix these so that Jerry can
boot to a prompt again.
Signed-off-by: Simon Glass <sjg@chromium.org>
The current limit of 5 is not enough for the driver model USB tests. Really
we should not have a limit but the driver model code still uses the
usb_dev_desc[] array, which has a limit.
Increasing the limit by 2 should not bother anyone. Adjust it.
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Marek Vasut <marex@denx.de>
The problem is that timeout bits in WCR register were leaved unchanged.
So previously set timeout value was applied and therefore 'reset'
command takes any value up to two minutes, depending on previous
watchdog settings, instead of minimal 0.5 seconds.
Signed-off-by: Andrey Skvortsov <andrej.skvortzov@gmail.com>
Table 41 of the JEDEC standard for eMMC says that bit 31 of
the command argument is obsolete when issuing the ERASE
command (CMD38) on page 115 of this document:
http://www.jedec.org/sites/default/files/docs/jesd84-B45.pdf
The SD Card Association Physical Layer Simplified Specification also
makes no mention of the use of bit 31.
https://www.sdcard.org/downloads/pls/part1_410.pdf
The Linux kernel distinguishes between secure (bit 31 set) and
non-secure erase, and this patch copies the macro names from
include/linux/mmc/core.h.
Tested-by: Fabio Estevam <fabio.estevam@freescale.com>
Signed-off-by: Eric Nelson <eric@nelint.com>
Tested-by: Hector Palacios <hector.palacios@digi.com>
