Follow Linux commit 10b62a2f785a (".gitignore: move *.dtb and *.dtb.S
patterns to the top-level .gitignore").
Signed-off-by: Masahiro Yamada
---
.gitignore | 2 ++
arch/arc/dts/.gitignore| 1 -
arch/arm/dts/.gitignore| 1 -
arch/microblaze/dts/.gitignore | 1
Follow Linux commit 1377dd3e2987 (".gitignore: sort normal pattern
rules alphabetically").
This would allow us to easily catch duplicated patterns if any.
Signed-off-by: Masahiro Yamada
---
.gitignore | 30 +-
1 file changed, 13 insertions(+), 17 deletions(-)
diff
On 06/11/2018 08:01 AM, Bin Meng wrote:
Hi Alex,
On Mon, Jun 11, 2018 at 1:52 PM, Alexander Graf wrote:
On 11.06.18 01:29, Bin Meng wrote:
On Mon, Jun 11, 2018 at 3:16 AM, Alexander Graf wrote:
On 10.06.18 15:25, Bin Meng wrote:
If UEFI BIOS has the graphics output protocol (GOP), let's
Hi Alex,
On Mon, Jun 11, 2018 at 3:34 PM, Alexander Graf wrote:
> On 06/11/2018 08:01 AM, Bin Meng wrote:
>>
>> Hi Alex,
>>
>> On Mon, Jun 11, 2018 at 1:52 PM, Alexander Graf wrote:
>>>
>>>
>>> On 11.06.18 01:29, Bin Meng wrote:
On Mon, Jun 11, 2018 at 3:16 AM, Alexander Graf wrote:
>
From: Carlo Caione
These patches toghether with the previously submitted patch [0] enable
the chromebook veyron jerry to use the SDMMC interface when U-Boot is
not chainloaded by depthcharge but booted directly from SPI.
[0] https://marc.info/?l=u-boot&m=152836928803742&w=2
Changelog:
V2:
- Ad
From: Carlo Caione
On the veyron board the vcc33_sd regulator is used as vmmc-supply for
the SD card. This regulator is powered in the MMC core during power on
but its value is never actually set.
In the veyron platform the reset value for the LDO output is 1.8V while
the standard (min and max)
From: Carlo Caione
Use regulators_enable_boot_on() to init all the regulators with
regulator-boot-on property.
Signed-off-by: Carlo Caione
Reviewed-by: Simon Glass
---
arch/arm/mach-rockchip/rk3288-board.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/mach-rockchip/rk3288
From: Carlo Caione
The GRF_SOC_CON0.grf_force_jtag bit is automatically set at boot and it
is preventing the SDMMC to work correctly. Disable the JTAG function on
the assumption that a working SD has higher priority over JTAG.
Signed-off-by: Carlo Caione
Reviewed-by: Simon Glass
---
arch/arm/
On Sat, Jun 9, 2018 at 5:59 AM, Simon Glass wrote:
> Hi Ley Foon,
>
> On 3 June 2018 at 23:19, Ley Foon Tan wrote:
>> Add reset ctrl to dwmmc socfpga, designware Ethernet and ns16550 serial
>> drivers.
>>
>> A reset property is an optional feature, so only print out a warning and
>> do not fail
On 06/11/2018 09:44 AM, Bin Meng wrote:
Hi Alex,
On Mon, Jun 11, 2018 at 3:34 PM, Alexander Graf wrote:
On 06/11/2018 08:01 AM, Bin Meng wrote:
Hi Alex,
On Mon, Jun 11, 2018 at 1:52 PM, Alexander Graf wrote:
On 11.06.18 01:29, Bin Meng wrote:
On Mon, Jun 11, 2018 at 3:16 AM, Alexander Gr
> On 11 Jun 2018, at 10:08, Carlo Caione wrote:
>
> From: Carlo Caione
>
> On the veyron board the vcc33_sd regulator is used as vmmc-supply for
> the SD card. This regulator is powered in the MMC core during power on
> but its value is never actually set.
>
> In the veyron platform the reset
> On 11 Jun 2018, at 10:08, Carlo Caione wrote:
>
> From: Carlo Caione
>
> Use regulators_enable_boot_on() to init all the regulators with
> regulator-boot-on property.
>
> Signed-off-by: Carlo Caione
> Reviewed-by: Simon Glass
Reviewed-by: Philipp Tomsich
Acked-by: Philipp Tomsich
> On 11 Jun 2018, at 10:08, Carlo Caione wrote:
>
> From: Carlo Caione
>
> The GRF_SOC_CON0.grf_force_jtag bit is automatically set at boot and it
> is preventing the SDMMC to work correctly. Disable the JTAG function on
> the assumption that a working SD has higher priority over JTAG.
>
> Si
On Mon, Jun 11, 2018 at 8:09 AM, Michal Simek wrote:
> There is no reason to keep this gpio based code in architecture. Use
> ledtrig-heartbeat.c instead which is much more flexible then this
> ancient code.
>
> Signed-off-by: Michal Simek
Reviewed-by: Linus Walleij
Maybe the arch maintainers
Hi Alex,
On Mon, Jun 11, 2018 at 4:33 PM, Alexander Graf wrote:
> On 06/11/2018 09:44 AM, Bin Meng wrote:
>>
>> Hi Alex,
>>
>> On Mon, Jun 11, 2018 at 3:34 PM, Alexander Graf wrote:
>>>
>>> On 06/11/2018 08:01 AM, Bin Meng wrote:
Hi Alex,
On Mon, Jun 11, 2018 at 1:52 PM, Alex
Hi Alex,
On Sun, Jun 10, 2018 at 9:25 PM, Bin Meng wrote:
> Since commit bb0bb91cf0aa ("efi_stub: Use efi_uintn_t"), EFI x86
> 64-bit payload does not work anymore. The call to GetMemoryMap()
> in efi_stub.c fails with return code EFI_INVALID_PARAMETER. Since
> the payload itself is still 32-bit
Update the DWC3 USB driver to support a live tree.
Signed-off-by: Vipul Kumar
---
drivers/usb/common/common.c | 11 +--
drivers/usb/dwc3/dwc3-generic.c | 17 +++--
drivers/usb/host/xhci-dwc3.c| 3 ++-
drivers/usb/host/xhci-zynqmp.c | 3 +--
include/linux/usb/otg.h
Hi Dennis,
On 06.06.2018 15:25, dgilm...@redhat.com wrote:
> From: Dennis Gilmore
>
> The helios4 is built on the SolidRun Armada 38x SOM.
> The port os based on the ClearFog board, using information from
> https://github.com/helios-4/u-boot-marvell as well as dtb input
> from https://github.com
Hi,
2018년 6월 10일 (일) 05:22, Heinrich Schuchardt 님이 작성:
> On 06/09/2018 07:34 PM, Simon Glass wrote:
> > Hi,
> >
> > On 6 May 2018 at 12:31, Tom Rini wrote:
> >> On Sun, May 06, 2018 at 09:49:42PM +0200, Alexander Graf wrote:
> >>
> >>> On 06.05.18 18:02, Heinrich Schuchardt wrote:
> On 05/0
On 06/11/2018 07:01 AM, Chee, Tien Fong wrote:
[...]
This is a configuration. You do not need (new) a DT compatible
for
that.
So why is the DT compatible even needed in the FW loader at all ?
>>> I thought DT compatible is used by driver to find the fs_loader
>>> node in
>>
This patchset adds SoC support for Actions Semi S900 SoC and ucRobotics
Bubblegum-96 board along with UART and Clock drivers.
S900 SoC consists of 4 ARM Cortex-A53 cores up to 1.8GHz with
Imagination Power VR G6230 GPU. More information on this SoC can be
found in Actions Semi product page:
http:/
This commit adds Clock Management Unit (CMU) nodes for Actions Semi
S900 SoC.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm/dts/s900.dtsi | 22 ++
1 file changed, 22 insertions(+)
diff --git a/arch/arm/dts/s900.dtsi b/arch/arm/dts/s900.dtsi
index 3bd14b82d4..e9d47b1ff1 1
This commit adds uCRobotics Bubblegum-96 board support. This board is
one of the 96Boards Consumer Edition platform based on Actions Semi
S900 SoC.
Features:
- Actions Semi S900 SoC (4xCortex A53, Power VR G6230 GPU)
- 2GiB RAM
- 8GiB eMMC, uSD slot
- WiFi, Bluetooth and GPS module
- 2x Host, 1x D
This commit adds Actions Semi OWL SoC family support with S900 as the
first target SoC.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm/Kconfig| 9 +
arch/arm/Makefile | 1 +
arch/arm/dts/s900.dtsi | 23 +++
arch/arm/mach-owl
This commit enables UART5 found in S900 SoC for serial console support.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm/dts/bubblegum_96.dts | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/dts/bubblegum_96.dts b/arch/arm/dts/bubblegum_96.dts
index 4e34ebaa49..5b58d15
This commit adds Actions Semi S900 CMU register definitions to clock
bindings.
---
include/dt-bindings/clock/s900_cmu.h | 77
1 file changed, 77 insertions(+)
create mode 100644 include/dt-bindings/clock/s900_cmu.h
diff --git a/include/dt-bindings/clock/s900_cmu.h
b
This commit adds Actions Semi OWL family UART support. This driver
relies on baudrate configured by primary bootloaders.
Signed-off-by: Manivannan Sadhasivam
---
drivers/serial/Kconfig | 8 +++
drivers/serial/Makefile | 1 +
drivers/serial/serial_owl.c | 136
On 01/25/2018 10:45 PM, Nishanth Menon wrote:
> As recommended by Arm in [1], IBE[2] has to be enabled unconditionally
> for BPIALL to be functional on Cortex-A8 processors. Provide a config
> option for platforms to enable this option based on impact analysis
> for products.
>
> NOTE: This patch
Hi Linus,
On Mon, Jun 11, 2018 at 10:47 AM Linus Walleij wrote:
> On Mon, Jun 11, 2018 at 8:09 AM, Michal Simek wrote:
> > There is no reason to keep this gpio based code in architecture. Use
> > ledtrig-heartbeat.c instead which is much more flexible then this
> > ancient code.
> >
> > Signed-o
Add myself as the Maintainer for Actions Semi OWL family and its
relevant board, drivers.
Signed-off-by: Manivannan Sadhasivam
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 642c448093..0f70cb04fe 100644
--- a/MAINTAINERS
+++ b/MAINTA
This commit adds Actions Semi OWL family base clock and S900 SoC specific
clock support. For S900 peripheral clock support, only UART clock has been
added for now.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm/include/asm/arch-owl/clk_owl.h | 61 +
arch/arm/include/asm/arch-ow
This commit adds UART node for Actions Semi S900 SoC.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm/dts/s900.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/dts/s900.dtsi b/arch/arm/dts/s900.dtsi
index e9d47b1ff1..2bbb30a5a8 100644
--- a/arch/arm/dts/s900.dtsi
+++ b
This is the case when reading freshly created filesystem.
The error message is like the following:
btrfs_read_superblock: No valid root_backup found!
Since the data from super_roots/root_backups is not actually used -
decided to rework btrfs_newest_root_backup() into
btrfs_check_super_roots()
Hi Stefan,
Interesting, I got your point. First of all, Could you please let me know on
how do you created the encrypted bitstream?
I hope this is not the Xilinx bootgen flow(may be through other Xilinx flow)
because, I don't think bootgen will update these fields while creating
encrypted bits
This patch basically adds two new commands for loadig secure
images/bitstreams.
1. zynq rsa adds support to load secure image which can be both
authenticated or encrypted or both authenticated and encrypted
image in xilinx bootimage(BOOT.bin) format.
2. zynq aes command adds support to decryp
On Mon, 2018-06-11 at 11:39 +0200, Marek Vasut wrote:
> On 06/11/2018 07:01 AM, Chee, Tien Fong wrote:
> [...]
> >
> > >
> > > >
> > > > >
> > > > > This is a configuration. You do not need (new) a DT
> > > > > compatible
> > > > > for
> > > > > that.
> > > > > So why is the DT compatible even
On 06/11/2018 01:53 PM, Chee, Tien Fong wrote:
> On Mon, 2018-06-11 at 11:39 +0200, Marek Vasut wrote:
>> On 06/11/2018 07:01 AM, Chee, Tien Fong wrote:
>> [...]
>>>
>
>>
>> This is a configuration. You do not need (new) a DT
>> compatible
>> for
>> that.
>> So why
On 11.6.2018 11:39, Vipul Kumar wrote:
> Update the DWC3 USB driver to support a live tree.
>
> Signed-off-by: Vipul Kumar
> ---
> drivers/usb/common/common.c | 11 +--
> drivers/usb/dwc3/dwc3-generic.c | 17 +++--
> drivers/usb/host/xhci-dwc3.c| 3 ++-
> drivers/usb
On Sat, Jun 09, 2018 at 04:46:59AM +, York Sun wrote:
> Thanks for the feedback. I didn't catch the failure. Travis build
> failed on many targets due to toolchain download. My setup doesn't
> cover i.mx.
FWIW, when that happens you can just re-run that particular job and it
usually then work
The IN_PROGRESS macro has been removed in commit bd47c13583f (mmc: Fix
splitting device initialization). Remove it from the mmc_start_init()
function description.
Signed-off-by: Baruch Siach
---
include/mmc.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/mmc.h b/inc
The newer rev 1.5 of the SolidRun i.MX6 SOM can optionally come with eMMC on
the SOM. This series adds support for the eMMC device on these SOMs.
Since eMMC has card detect signal this series uses the new mmc_get_op_cond()
function that is broken out of mmc_init_start(). Successful completion of
m
From: Jon Nettleton
The HB2 boards as well as rev 1.5 soms support eMMC
booting as well as SDHC. Add the infrastructure to support
booting these devices.
Signed-off-by: Jon Nettleton
Signed-off-by: Baruch Siach
---
board/solidrun/mx6cuboxi/mx6cuboxi.c | 102 ---
1 fil
From: Jon Nettleton
This code is useful for testing the existance of devices that
do not have card detect capabilities. This breaks out the core
functionality and leaves the actual init logic and error reporting
in mmc_start_init().
Signed-off-by: Jon Nettleton
Signed-off-by: Baruch Siach
---
From: Jon Nettleton
Previously we had just made broad assumptions with which of our
boards had an eMMC or not even though this is a manufacturing time
assembly option. This takes the guessing away and actually checks for
the existence of an eMMC and sets up the has_emmc environment variable.
Si
From: Jon Nettleton
Mainline and now the SolidRun 4.9 nxp based tree use the new
reorganization of device-tree files that separate out the emmc
into its own dtb. u-boot will now look for -emmc in the device
tree name if one is detected.
Signed-off-by: Jon Nettleton
Signed-off-by: Baruch Siach
This macro is not used.
Signed-off-by: Baruch Siach
---
include/configs/mx6cuboxi.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/configs/mx6cuboxi.h b/include/configs/mx6cuboxi.h
index 803661cfa843..1f7297d11463 100644
--- a/include/configs/mx6cuboxi.h
+++ b/include/configs/mx6cubo
On Sat, Jun 09, 2018 at 04:57:44AM +, York Sun wrote:
> On 06/08/2018 09:39 PM, Tom Rini wrote:
> > On Fri, Jun 08, 2018 at 11:49:32PM +, York Sun wrote:
> >
> >> Tom,
> >>
> >> The following changes since commit
> >> 71002b508a1bc0986023764f155f0db26f548db2:
> >>
> >> cmd: add missing
On Mon, 2018-06-11 at 13:55 +0200, Marek Vasut wrote:
> On 06/11/2018 01:53 PM, Chee, Tien Fong wrote:
> >
> > On Mon, 2018-06-11 at 11:39 +0200, Marek Vasut wrote:
> > >
> > > On 06/11/2018 07:01 AM, Chee, Tien Fong wrote:
> > > [...]
> > > >
> > > >
> > > > >
> > > > >
> > > > > >
> > > >
On Sat, Jun 09, 2018 at 10:21:53PM +0200, Heinrich Schuchardt wrote:
> On 06/09/2018 07:34 PM, Simon Glass wrote:
> > Hi,
> >
> > On 6 May 2018 at 12:31, Tom Rini wrote:
> >> On Sun, May 06, 2018 at 09:49:42PM +0200, Alexander Graf wrote:
> >>
> >>> On 06.05.18 18:02, Heinrich Schuchardt wrote:
>
From: Christophe Kerello
Sometimes, at boot time, following issue appears:
Error reading superblock on volume 'ubi0:boot' errno=-22!
This error is coming from wrong ubi_num and wrong ubi_id in the superblock.
(ubi_num = -1 and vol_id = -1).
It appears that following line in sget function:
hlist_
On 06/11/2018 02:42 PM, Chee, Tien Fong wrote:
> On Mon, 2018-06-11 at 13:55 +0200, Marek Vasut wrote:
>> On 06/11/2018 01:53 PM, Chee, Tien Fong wrote:
>>>
>>> On Mon, 2018-06-11 at 11:39 +0200, Marek Vasut wrote:
On 06/11/2018 07:01 AM, Chee, Tien Fong wrote:
[...]
>
>
On Mon, 2018-06-11 at 15:38 +0200, Marek Vasut wrote:
> On 06/11/2018 02:42 PM, Chee, Tien Fong wrote:
> >
> > On Mon, 2018-06-11 at 13:55 +0200, Marek Vasut wrote:
> > >
> > > On 06/11/2018 01:53 PM, Chee, Tien Fong wrote:
> > > >
> > > >
> > > > On Mon, 2018-06-11 at 11:39 +0200, Marek Vasut
On 06/11/2018 03:55 PM, Chee, Tien Fong wrote:
[...]
> Linux firmware loading method is different with this
> Linux loading firmware with
> 1. Firmware search paths - which is hardcoded in root file
> system
> 2. Built-in firmware - part of kernel binaries
>
> This patch
On Mon, 2018-06-11 at 16:03 +0200, Marek Vasut wrote:
> On 06/11/2018 03:55 PM, Chee, Tien Fong wrote:
> [...]
> >
> > >
> > > >
> > > > >
> > > > > >
> > > > > > Linux firmware loading method is different with this
> > > > > > Linux loading firmware with
> > > > > > 1. Firmware search paths -
On 06/11/2018 04:13 PM, Chee, Tien Fong wrote:
> On Mon, 2018-06-11 at 16:03 +0200, Marek Vasut wrote:
>> On 06/11/2018 03:55 PM, Chee, Tien Fong wrote:
>> [...]
>>>
>
>>
>>>
>>> Linux firmware loading method is different with this
>>> Linux loading firmware with
>>> 1.
On 06/10/2018 10:37 PM, Bin Meng wrote:
> On Tue, Jun 5, 2018 at 9:28 AM, Bin Meng wrote:
>> Hi Alison, Prabhakar,
>>
>> On Fri, Jun 1, 2018 at 12:06 PM, York Sun wrote:
>>> On May 31, 2018, at 20:58, Bin Meng wrote:
Hi,
> On Wed, May 30, 2018 at 11:06 AM, York Sun wrote:
>>>
Hi Ramon,
On 9 June 2018 at 03:06, Ramon Fried wrote:
> The Shared Memory Manager driver implements an interface for allocating
> and accessing items in the memory area shared among all of the
> processors in a Qualcomm platform.
>
> Adapted from the Linux driver (4.17)
>
> Changes from the origi
On 9 June 2018 at 21:17, Peter Robinson wrote:
> To build U-Boot on a Nyan Big Chromebook the docs outline adjusting the
> Tegra124
> defined CONFIG_SYS_TEXT_BASE but this has since been moved to individual
> config
> files. We should have the default required for U-Boot chain loading on the
> c
Hi,
On 10 June 2018 at 05:25, Bin Meng wrote:
> If UEFI BIOS has the graphics output protocol (GOP), let's pass its
> information to U-Boot payload so that U-Boot can utilize it (eg:
> an EFI framebuffer driver).
>
> Signed-off-by: Bin Meng
> ---
>
> include/efi.h | 35
On 10 June 2018 at 05:25, Bin Meng wrote:
> If GetMemoryMap() fails, we really want to know EFI_BITS_PER_LONG
> instead of BITS_PER_LONG. A space and LF are added in places where
> error message is output to improve readability.
>
> Signed-off-by: Bin Meng
> ---
>
> lib/efi/efi_stub.c | 8 +-
On 10 June 2018 at 05:25, Bin Meng wrote:
> The EFI application does not boot currently. It's due to the call
> to syscon_get_by_driver_data() in cpu_init_r() maps to nowhere as
> CONFIG_SYSCON is not included in the configuration.
>
> EFI application is built as a shared library, so GCC won't com
On 10 June 2018 at 05:25, Bin Meng wrote:
> Attempting to use a toolchain that is preconfigured to generate code
> for the 32-bit architecture (i386), for example, the i386-linux-gcc
> toolchain on kernel.org, to compile the 64-bit EFI payload does not
> build. This updates the makefile fragments
On 10 June 2018 at 05:25, Bin Meng wrote:
> From: Christian Gmeiner
>
> If U-Boot gets used as coreboot payload all pci resources got
> assigned by coreboot. If a dts without any pci ranges gets used
> the dm is not able to access pci device memory. To get things
> working make use of a 1:1 mappi
On 10 June 2018 at 05:25, Bin Meng wrote:
> From: Christian Gmeiner
>
> If we use U-Boot as coreboot payload with a generic dts without
> any ranges specified we fail in pci pre_probe and our pci bus
> is not usable.
>
> So convert decode_regions(..) into a void function and do the simple
> error
On 10 June 2018 at 05:25, Bin Meng wrote:
> To avoid confusion, let's rename the efi-x86 target to efi-x86_app.
>
> Signed-off-by: Bin Meng
> ---
>
> arch/x86/cpu/efi/Makefile| 2 +-
> arch/x86/cpu/efi/{efi.c => app.c}| 0
> arch/x86/cpu/intel_comm
On 10 June 2018 at 05:25, Bin Meng wrote:
> It is possible to create a generic EFI payload for all x86 boards.
> The payload is configured to include as many generic drivers as
> possible. All stuff that touches low-level initialization are not
> allowed as such is the EFI BIOS's responsibility. P
Hi Ramon,
On 9 June 2018 at 03:06, Ramon Fried wrote:
>
> This is a simple uclass for SOC drivers.
> It is intend to serve as uclass for SOC specific drivers
> that don't fall into any other uclass catagories.
> Currently, it doesn't define any special ops.
>
> Signed-off-by: Ramon Fried
>
> ---
On 10 June 2018 at 05:25, Bin Meng wrote:
> The pinctrl_ich6 driver is currently unconditionally built for all
> x86 boards. Let's use a Kconfig option to control the build.
>
> Signed-off-by: Bin Meng
> ---
>
> arch/x86/Kconfig | 6 ++
> arch/x86/cpu/baytrail/Kconfig | 1 +
>
On 10 June 2018 at 05:25, Bin Meng wrote:
> At present the EFI application and payload support codes in the x86
> directory is distributed in a hybrid way. For example, the Kconfig
> options for both app and payload are in arch/x86/lib/efi/Kconfig,
> but the source codes in the same directory get
On 10 June 2018 at 05:25, Bin Meng wrote:
> This adds arch_cpu_init() to the payload codes, in preparation for
> supporting a generic efi payload.
>
> Signed-off-by: Bin Meng
> ---
>
> arch/x86/cpu/efi/payload.c | 11 ---
> 1 file changed, 8 insertions(+), 3 deletions(-)
Reviewed-by: Si
On 10 June 2018 at 05:25, Bin Meng wrote:
> Now that we have generic EFI payload support, drop EFI-specific test
> logics in BayTrail Kconfig and codes, and all BayTrail boards too.
>
> Signed-off-by: Bin Meng
> ---
>
> arch/x86/cpu/baytrail/Kconfig | 6 +++---
> arch/x86/cpu/ba
On 10 June 2018 at 05:25, Bin Meng wrote:
> This turns on the EFI framebuffer driver support so that a graphics
> console can be of additional help.
>
> Signed-off-by: Bin Meng
> ---
>
> arch/x86/dts/efi-x86_payload.dts | 4
> board/efi/efi-x86_payload/Kconfig | 1 +
> 2 files changed, 5 i
On 10 June 2018 at 05:25, Bin Meng wrote:
> Currently when EFI application boots, it says:
>
> CPU: x86_64, vendor , device 0h
>
> Fix this by calling x86_cpu_init_f() in arch_cpu_init().
>
> Signed-off-by: Bin Meng
>
> ---
>
> arch/x86/cpu/efi/app.c | 2 +-
> 1 file changed, 1 insertion(+), 1
On 10 June 2018 at 05:25, Bin Meng wrote:
> Now that we have generic EFI payload support for all x86 boards,
> drop the QEMU-specific one.
>
> Signed-off-by: Bin Meng
> ---
>
> arch/x86/cpu/qemu/Makefile | 2 --
> arch/x86/cpu/qemu/qemu.c | 4 ---
> board/emulatio
Hi Bin,
On 10 June 2018 at 05:24, Bin Meng wrote:
> Unfortunately the EFI x86 application and payload support have been
> broken for quite a while. This series addresses various bug fixes,
> plus several enhancements like toolchain compatibility (eg: kernel.org
> i386-linux-gcc), introduction of
On 06/11/2018 01:36 AM, Bin Meng wrote:
> Hi Heinrich,
>
> On Mon, Jun 11, 2018 at 2:17 AM, Heinrich Schuchardt
> wrote:
>> On 06/10/2018 04:30 PM, Bin Meng wrote:
>>> Hi Heinrich,
>>>
>>> On Sun, Jun 10, 2018 at 10:02 PM, Heinrich Schuchardt
>>> wrote:
On 06/10/2018 03:25 PM, Bin Meng wro
This patchset adds SoC support for Actions Semi S900 SoC and ucRobotics
Bubblegum-96 board along with UART and Clock drivers.
S900 SoC consists of 4 ARM Cortex-A53 cores up to 1.8GHz with
Imagination Power VR G6230 GPU. More information on this SoC can be
found in Actions Semi product page:
http:/
This commit adds Actions Semi OWL SoC family support with S900 as the
first target SoC.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm/Kconfig| 9 +
arch/arm/Makefile | 1 +
arch/arm/dts/s900.dtsi | 23 +++
arch/arm/mach-owl
This commit adds uCRobotics Bubblegum-96 board support. This board is
one of the 96Boards Consumer Edition platform based on Actions Semi
S900 SoC.
Features:
- Actions Semi S900 SoC (4xCortex A53, Power VR G6230 GPU)
- 2GiB RAM
- 8GiB eMMC, uSD slot
- WiFi, Bluetooth and GPS module
- 2x Host, 1x D
This commit adds Actions Semi S900 CMU register definitions to clock
bindings.
---
include/dt-bindings/clock/s900_cmu.h | 77
1 file changed, 77 insertions(+)
create mode 100644 include/dt-bindings/clock/s900_cmu.h
diff --git a/include/dt-bindings/clock/s900_cmu.h
b
This commit adds Actions Semi OWL family UART support. This driver
relies on baudrate configured by primary bootloaders.
Signed-off-by: Manivannan Sadhasivam
---
drivers/serial/Kconfig | 8 +++
drivers/serial/Makefile | 1 +
drivers/serial/serial_owl.c | 136
This commit adds Clock Management Unit (CMU) nodes for Actions Semi
S900 SoC.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm/dts/s900.dtsi | 22 ++
1 file changed, 22 insertions(+)
diff --git a/arch/arm/dts/s900.dtsi b/arch/arm/dts/s900.dtsi
index 3bd14b82d4..e9d47b1ff1 1
This commit enables UART5 found in S900 SoC for serial console support.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm/dts/bubblegum_96.dts | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/dts/bubblegum_96.dts b/arch/arm/dts/bubblegum_96.dts
index 4e34ebaa49..5b58d15
This commit adds UART node for Actions Semi S900 SoC.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm/dts/s900.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/dts/s900.dtsi b/arch/arm/dts/s900.dtsi
index e9d47b1ff1..2bbb30a5a8 100644
--- a/arch/arm/dts/s900.dtsi
+++ b
Hi Simon,
On Mon, Jun 11, 2018 at 10:54 PM, Simon Glass wrote:
> On 10 June 2018 at 05:25, Bin Meng wrote:
>> To avoid confusion, let's rename the efi-x86 target to efi-x86_app.
>>
>> Signed-off-by: Bin Meng
>> ---
>>
>> arch/x86/cpu/efi/Makefile| 2 +-
>> arch/x86/
This commit adds Actions Semi OWL family base clock and S900 SoC specific
clock support. For S900 peripheral clock support, only UART clock has been
added for now.
Signed-off-by: Manivannan Sadhasivam
---
arch/arm/include/asm/arch-owl/clk_owl.h | 61 +
arch/arm/include/asm/arch-ow
Add myself as the Maintainer for Actions Semi OWL family and its
relevant board, drivers.
Signed-off-by: Manivannan Sadhasivam
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 642c448093..0f70cb04fe 100644
--- a/MAINTAINERS
+++ b/MAINTA
Hi Simon,
On Mon, Jun 11, 2018 at 10:53 PM, Simon Glass wrote:
> Hi Bin,
>
> On 10 June 2018 at 05:24, Bin Meng wrote:
>> Unfortunately the EFI x86 application and payload support have been
>> broken for quite a while. This series addresses various bug fixes,
>> plus several enhancements like to
On 06/11/2018 03:03 PM, Tom Rini wrote:
> On Sat, Jun 09, 2018 at 10:21:53PM +0200, Heinrich Schuchardt wrote:
>> On 06/09/2018 07:34 PM, Simon Glass wrote:
>>> Hi,
>>>
>>> On 6 May 2018 at 12:31, Tom Rini wrote:
On Sun, May 06, 2018 at 09:49:42PM +0200, Alexander Graf wrote:
> On 06
Hi Siva,
> -Ursprüngliche Nachricht-
> Von: Siva Durga Prasad Paladugu [mailto:siva...@xilinx.com]
> Gesendet: Montag, 11. Juni 2018 13:40
> An: ste...@herbrechtsmeier.net
> Cc: Herbrechtsmeier Dr.-Ing. , Stefan
> ; u-boot@lists.denx.de;
> Michal Simek ; mon...@monstr.eu
> Betreff: RE: [RF
When the `mmc hwpartition` command is disabled, remove the associated help
text.
Signed-off-by: Alex Kiernan
---
cmd/mmc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/cmd/mmc.c b/cmd/mmc.c
index c2ee2d9c0a..3920a1836a 100644
--- a/cmd/mmc.c
+++ b/cmd/mmc.c
@@ -935,6 +935,7 @@ U_BOOT_C
On 06/11/2018 05:29 AM, Tom Rini wrote:
> On Sat, Jun 09, 2018 at 04:57:44AM +, York Sun wrote:
>> On 06/08/2018 09:39 PM, Tom Rini wrote:
>>> On Fri, Jun 08, 2018 at 11:49:32PM +, York Sun wrote:
>>>
Tom,
The following changes since commit
71002b508a1bc0986023764f155f0
Hi Heinrich,
On Mon, Jun 11, 2018 at 11:31 PM, Heinrich Schuchardt
wrote:
> On 06/11/2018 01:36 AM, Bin Meng wrote:
>> Hi Heinrich,
>>
>> On Mon, Jun 11, 2018 at 2:17 AM, Heinrich Schuchardt
>> wrote:
>>> On 06/10/2018 04:30 PM, Bin Meng wrote:
Hi Heinrich,
On Sun, Jun 10, 2018 a
On Sat, Jun 9, 2018 at 3:46 AM, Chris Packham wrote:
> Combine repeated code from smi_reg_read/smi_reg_write into a common
> function smi_wait_ready.
>
> Reviewed-by: Stefan Roese
> Signed-off-by: Chris Packham
Acked-by: Joe Hershberger
___
U-Boot ma
On 06/10/2018 03:25 PM, Bin Meng wrote:
> The EFI application does not boot currently. It's due to the call
> to syscon_get_by_driver_data() in cpu_init_r() maps to nowhere as
> CONFIG_SYSCON is not included in the configuration.
>
> EFI application is built as a shared library, so GCC won't compl
(ping Jagan)
On 06/06/2018 10:51 AM, Martin Kelly wrote:
On 06/06/2018 07:58 AM, Maxime Ripard wrote:
On Mon, Jun 04, 2018 at 11:15:34AM -0700, Martin Kelly wrote:
[snip as the thread is getting long]
On 06/04/2018 01:21 AM, Maxime Ripard wrote:
On Fri, Jun 01, 2018 at 10:16:32AM -0700, Mart
On 11 Jun 2018, at 19:08, Carlo Caione wrote:
>
> On Mon, 2018-06-11 at 10:41 +0200, Dr. Philipp Tomsich wrote:
>>> On 11 Jun 2018, at 10:08, Carlo Caione wrote:
>
> /cut
>>> +#define GRF_SOC_CON0 0xff770244
>>> #define GRF_SOC_CON2 0xff77024c
>>
>> Could you convert these to ‘const uintptr_t
We should use the baudrate variable available inside U-Boot
environment to allow it to be changed dynamically.
Signed-off-by: Otavio Salvador
---
include/configs/wandboard.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/configs/wandboard.h b/include/configs/wandboa
From: Fabio Estevam
ARCH_MX6 has default values for SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR
and SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR.
Do the same for ARCH_MX7 so that users may have a consistent
experience through the i.MX families.
Signed-off-by: Fabio Estevam
Signed-off-by: Otavio Salvador
---
c
From: Fabio Estevam
Since kernel commit 41bbeadceb03 ("ARM: dts: imx7d-pico-pi: Separate
into cpu and baseboard dts") the dtb name has changed.
Fix it accordingly.
Signed-off-by: Fabio Estevam
Signed-off-by: Otavio Salvador
---
include/configs/pico-imx7d.h | 2 +-
1 file changed, 1 insertio
1 - 100 of 190 matches
Mail list logo
