On 01/17/2018 12:54 PM, Jaehoon Chung wrote:
> Hi Anand,
>
> On 01/17/2018 02:18 AM, Anand Moon wrote:
>> Hi Jaehoon
>>
>> On 16 January 2018 at 12:03, Jaehoon Chung wrote:
>>> S2MPS11 has the 10-bucks and 38-ldos regulators.
>>> To control the each power, add the s2mps11 regulator driver.
>>> Te
On 16.01.18 22:32, Heinrich Schuchardt wrote:
> On 01/16/2018 02:47 PM, Alexander Graf wrote:
>> Currently our serial device search chokes on the fact that the serial
>> probe function could fail. If it does, instead of searching for the next
>> usable serial device, it just quits.
>>
>> This pat
Hi Masahiro,
On 01/12/2018 06:10 PM, Masahiro Yamada wrote:
> Add HS200 timing setting and the MMC tuning callback.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> Changes in v2:
> - Surround .execute_tuning hook with #ifdef MMC_SUPPORTS_TUNING
>
> drivers/mmc/sdhci-cadence.c | 90
> +
Hi Jaehoon,
2018-01-17 17:34 GMT+09:00 Jaehoon Chung :
>> + /*
>> + * This handler only implements the eMMC tuning that is specific to
>> + * this controller. The tuning for SD timing should be handled by the
>> + * SDHCI core.
>> + */
>> + if (!IS_MMC(mmc))
>> +
From: Patrice Chotard
Add ETHMAC, ETHMACRX and ETHMACTX clocks for STMMAC.
Signed-off-by: Patrice Chotard
---
arch/arm/dts/stm32f746.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/dts/stm32f746.dtsi b/arch/arm/dts/stm32f746.dtsi
index 929bf82..46d148e 100644
--- a/arch/ar
From: Patrice Chotard
As STMMAC designware driver is now able to get and enable STMMAC clocks,
we can remove code related to STMMAC clock setup in board and in
clk_stm32f driver.
Set SYSCFG clock directly in configure_clocks()
Add missing STMMAC clocks in stm32f746 dts file.
Patrice Chotard (
From: Patrice Chotard
Thanks to 'commit ba1f96672522 ("net: designware: add clock support")'
we don't need anymore to setup the STMMAC clock in board.
Signed-off-by: Patrice Chotard
---
arch/arm/include/asm/arch-stm32f7/stm32_periph.h | 1 -
board/st/stm32f746-disco/stm32f746-disco.c | 1
From: Patrice Chotard
Move SYSCFG clock setup into configure_clocks() instead of calling
clock_setup() from drivers.
Move the RMII setup from board_early_init_f() to board_init()
to insure that RMII bit is set only when clock driver is initialized.
Signed-off-by: Patrice Chotard
---
arch/arm/i
We are switching to a model where a serial device doesn't even get probed when
it's not muxed properly, so we don't need device specific disabling
functionality anymore.
Signed-off-by: Alexander Graf
---
drivers/serial/serial_bcm283x_mu.c | 18 +-
include/dm/platform_da
Firmware on the Raspberry Pi family of devices can dynamically configure either
the PL011, Mini-UART or no device at all to be routed to the user accessible
UART pins.
That means we need to always include both drivers, because we can never be sure
which of the two serial devices firmware actually
On some boards, serial devices may or may not be muxed properly to actual
pins, depending on firmware configuration. To determine whether we should
use a serial device for U-Boot in-/output, we need to check whether it
is muxed properly.
This is something only the board file can do, so let's expos
Now that we have all infrastructure in place to dynamically determine whether
a serial device is actually usable (read: routed to user accessible pins), we
can wire it up to the board.
This patch adds support to determine whether the pl011 or mini-uart or no serial
is routed to the UART RX/TX pins
We are switching to a model where our board file can directly fail probing
of serial devices when they're not usable, so remove the current runtime
hack we have.
Signed-off-by: Alexander Graf
---
arch/arm/mach-bcm283x/include/mach/gpio.h | 1 -
board/raspberrypi/rpi/rpi.c | 43 ---
The serial devices on the raspberry pi are based on clocks we can't easily
read and influence in U-Boot. However, the serial devices are always already
properly set up when coming up, so all we need to do is leave them alone.
The way to do that is to specify "skip-init" in device tree usually, but
The RPi has proprietary firmware that can be configured (using config.txt)
to expose either the PL11, Mini-UART or no serial device to the UART pins
on the GPIO pin bar of the RPi.
So far we've only half-heartedly dealt with that, with lost of heuristics
that ended up falling apart at times. For e
Currently our serial device search chokes on the fact that the serial
probe function could fail. If it does, instead of searching for the next
usable serial device, it just quits.
This patch changes the fallback logic so that even when a serial device
was not probed correctly, we just try the next
Hi,
On Tue, Jan 16, 2018 at 04:56:49PM -0500, Tom Rini wrote:
> On Tue, Jan 16, 2018 at 10:16:36AM +0100, Maxime Ripard wrote:
> > Hi,
> >
> > Here is a second attempt at transitioning away from the MMC raw environment
> > to a FAT-based one for Allwinner SoCs. Since the RFC was quite well
> > re
The same change is done for others zynq boards to get uart as early as
possible.
Signed-off-by: Michal Simek
---
arch/arm/dts/zynq-cc108.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/dts/zynq-cc108.dts b/arch/arm/dts/zynq-cc108.dts
index a55e82b2102c..4804da5235dd 100644
---
Hi,
> + val = readl(&gpios->reg->gpfsel[BCM2835_GPIO_FSEL_BANK(gpio)]);
> + val &= ~(BCM2835_GPIO_FSEL_MASK << BCM2835_GPIO_FSEL_SHIFT(gpio));
> + val |= (func << BCM2835_GPIO_FSEL_SHIFT(gpio));
> + writel(val, &gpios->reg->gpfsel[BCM2835_GPIO_FSEL_BANK(gpio)]);
Can clrset
Hi Guillaume,
On 01/09/2018 11:37 PM, Guillaume Gardet wrote:
> Hi,
>
>
> Le 17/11/2017 à 10:48, Jaehoon Chung a écrit :
>> Hi,
>>
>> On 2017년 11월 16일 21:29, Guillaume Gardet wrote:
>>> I found a workaround. If I disable MMC_MODE_HS_52MHz, then it is working
>>> fine.
>>>
>>> I guess there is a
When power is off, clock is not disabling.
Because it's passed to 1, mmc->clock should be set to f_min value.
Some drivers can't initialize the eMMC/SD card with current status.
This patch is to fix the disabling clock value to 0.
Fixes: 2e7410d76ad1 ("mmc: disable the mmc clock during power off"
Adds LTC3882 voltage regulator chip support in common VID driver.
And adds VID support for LS1088A QDS and RDB platforms.
Also, Tested LS1088ARDB secure boot with VID support.
Rajesh Bhagat (11):
armv8: lsch3: Add serdes and DDR voltage setup
board: common:vid: Add LS1088A VID Supported volta
Adds SERDES voltage and reset SERDES lanes API and makes
enable/disable DDR controller support 0.9V API common.
Signed-off-by: Ashish Kumar
Signed-off-by: Rajesh Bhagat
---
Changes in v8:
- Added a NULL entry prctl array
- Added balank line before return
Adds below voltage values supported by LS1088A Soc:
1.025 V(default), 0.9875V, 0.9750 V, 0.9V, 1.0 V, 1.0125 V, 1.0250 V
Signed-off-by: Ashish Kumar
Signed-off-by: Rajesh Bhagat
---
Changes in v8:
- Created a different vdd array
Restructures common driver to support LTC3882 voltage regulator
chip.
Signed-off-by: Ashish Kumar
Signed-off-by: Rajesh Bhagat
---
Changes in v8:
- Added blank line before return
Changes in v7:
Adds a board specific API namely board_adjust_vdd which
is required to define the board VDD adjust settings.
Signed-off-by: Ashish Kumar
Signed-off-by: Rajesh Bhagat
---
Changes in v8:
None
Changes in v7:
Sets DDR configuration parameter cdr1 before all other settings
to support case 0.9v VDD is enabled for some SoCs
Signed-off-by: Ashish Kumar
Signed-off-by: Rajesh Bhagat
---
Changes in v8:
None
drivers/ddr/fsl/fsl_ddr_gen4.c |
Adds a VID specific API in init_sequence_f and spl code flow
namely init_func_vid which is required to adjust core voltage.
VID specific code is required in spl, hence moving flag CONFIG_VID
out of spl flags.
Signed-off-by: Ashish Kumar
Signed-off-by: Rajesh Bhagat
---
Changes in v8:
None
a
Moves IR chip (IR36021) specific code in flag to resolve
compilation issue where it is not present. For example,
LS1088A is having a new LTC3882 voltage chip.
Signed-off-by: Ashish Kumar
Signed-off-by: Rajesh Bhagat
---
Changes in v8:
Adds below LTC3882 voltage regulator config:
CONFIG_VOL_MONITOR_LTC3882_READ
CONFIG_VOL_MONITOR_LTC3882_SET
Signed-off-by: Ashish Kumar
Signed-off-by: Rajesh Bhagat
---
Changes in v8:
None
Changes in v7:
This patch adds the support for VID on LS1088AQDS and LS1088ARDB systems.
It reads the fusesr register and changes the VDD accordingly by adjusting
the voltage via LTC3882 regulator.
This patch also takes care of the special case of 0.9V VDD is present in
fusesr register. In that case,it also chan
Hi,
On 01/04/2018 06:40 PM, Siva Durga Prasad Paladugu wrote:
> This patch adds support to disable clock if clk_disable
> was set and then enable or set clock if the clock was changed
> or clock was disabled when clock needs to be enabled.
>
> Signed-off-by: Siva Durga Prasad Paladugu
> ---
> d
Enables and compiles VID specific functions for SPL
Signed-off-by: Pankit Garg
Signed-off-by: Rajesh Bhagat
---
board/freescale/ls1088a/ls1088a.c | 4
1 file changed, 4 insertions(+)
diff --git a/board/freescale/ls1088a/ls1088a.c
b/board/freescale/ls1088a/ls1088a.c
index 10865fe..bf64ff8
When VID feature is supported, check the contents of fuse register
and configure DDR operate at 0.9v.
Signed-off-by: Ashish Kumar
Signed-off-by: Rajesh Bhagat
---
Changes in v8:
- Changed fsl_ddr_setup_0v9_volt function to static
- Moved printf to debug for DDR voltage adjustment
None
board
On 01/17/2018 09:54 AM, Alexander Graf wrote:
> Currently our serial device search chokes on the fact that the serial
> probe function could fail. If it does, instead of searching for the next
> usable serial device, it just quits.
>
> This patch changes the fallback logic so that even when a seri
Hi,
On 01/04/2018 06:40 PM, Siva Durga Prasad Paladugu wrote:
> This patch adds support of SD3.0 for ZynqMP.
>
> Signed-off-by: Siva Durga Prasad Paladugu
> ---
> Changes for v2:
> - Added zynqmp_tap_delay.h which was missed
> in v1.
> ---
> board/xilinx/zynqmp/Makefile | 2 +
> board/x
Hi,
On 01/17/2018 07:36 PM, Jaehoon Chung wrote:
> When power is off, clock is not disabling.
> Because it's passed to 1, mmc->clock should be set to f_min value.
> Some drivers can't initialize the eMMC/SD card with current status.
>
> This patch is to fix the disabling clock value to 0.
Subje
On 01/16/2018 10:46 PM, Alexander Graf wrote:
> The Raspberry Pi (bcm283x SoC) family contains 2 IP blocks to drive SD
> peripherals: A pretty standard SDHCI one called iProc and a home grown
> one called "sdhost".
>
> When driving U-Boot by the same device tree that we use for Linux, we
> end up
Hi,
> -Original Message-
> From: Jaehoon Chung [mailto:jh80.ch...@samsung.com]
> Sent: Wednesday, January 17, 2018 4:16 PM
> To: Siva Durga Prasad Paladugu ; u-
> b...@lists.denx.de
> Cc: Siva Durga Prasad Paladugu
> Subject: Re: [PATCH v2 1/7] mmc: sdhci: Add support for disabling clock
Heiko, Martin,
Am Dienstag, 16. Januar 2018, 10:11:41 CET schrieb Martin Townsend:
> Ah. Must be the mail client. Sorry about that I'll setup git send-mail
> for v2. I'll wait to see what Richard has to say in case there is a
> better fix.
Thanks for letting me know!
Indeed, there is a problem.
The hash command function were not flushing the dcache before passing data
to CAAM/DMA and not invalidating the dcache when getting data back.
Due the data cache incoherency, HW accelerated hash commands used to fail
with CAAM errors like "Invalid KEY Command".
Check if pbuf and pout buffers are
On 01/10/2018 12:06 PM, Peng Fan wrote:
> Allow the dm driver be omitted by SPL.
>
> Signed-off-by: Peng Fan
> Reviewed-by: Simon Glass
> Cc: Jaehoon Chung
> Cc: Stefano Babic
Reviewed-by: Jaehoon Chung
> ---
> drivers/power/pmic/Makefile | 2 +-
> drivers/power/regulator/Makefile | 2
On 01/10/2018 02:20 PM, Peng Fan wrote:
> Allow the dm driver be omitted by SPL.
>
> Signed-off-by: Peng Fan
> Reviewed-by: Simon Glass
> Cc: Jaehoon Chung
> Cc: Stefano Babic
Sorry, i add the reviewed-by tag at previous version.
Reviewed-by: Jaehoon Chung
> ---
> drivers/power/pmic/Makef
On Wed, Jan 17, 2018 at 01:08:19PM +0530, Faiz Abbas wrote:
> Hi,
>
> +Vignesh
>
> On Tuesday 16 January 2018 08:55 PM, Tom Rini wrote:
> > On Tue, Jan 16, 2018 at 01:43:40PM +0530, Faiz Abbas wrote:
> >> Now the u-boot spi image is greater than 0x9, increase the same in
> >> env during spi e
hey, i downloaded the september and november versions and i applied the
patches on both of them, re-compiled the u boot,
and still, it gives me the same error when trying the command "sf probe"
i'm not sure what to do, is it possible that i missed something? like a
define or something in the make m
On Wed, Jan 17, 2018 at 09:58:53AM +0100, Maxime Ripard wrote:
> Hi,
>
> On Tue, Jan 16, 2018 at 04:56:49PM -0500, Tom Rini wrote:
> > On Tue, Jan 16, 2018 at 10:16:36AM +0100, Maxime Ripard wrote:
> > > Hi,
> > >
> > > Here is a second attempt at transitioning away from the MMC raw
> > > enviro
On 17.01.2018 14:01, RB23 wrote:
hey, i downloaded the september and november versions and i applied
the patches on both of them, re-compiled the u boot,
and still, it gives me the same error when trying the command "sf probe"
i'm not sure what to do, is it possible that i missed something? like
On Wed, Jan 17, 2018 at 08:01:34AM -0500, Tom Rini wrote:
> On Wed, Jan 17, 2018 at 09:58:53AM +0100, Maxime Ripard wrote:
> > Hi,
> >
> > On Tue, Jan 16, 2018 at 04:56:49PM -0500, Tom Rini wrote:
> > > On Tue, Jan 16, 2018 at 10:16:36AM +0100, Maxime Ripard wrote:
> > > > Hi,
> > > >
> > > > Her
On 01/17/2018 02:06 PM, Simon Goldschmidt wrote:
> On 17.01.2018 14:01, RB23 wrote:
>> hey, i downloaded the september and november versions and i applied
>> the patches on both of them, re-compiled the u boot,
>> and still, it gives me the same error when trying the command "sf probe"
>> i'm not s
i checked, and if you mean these patches:
https://patchwork.ozlabs.org/patch/765992/
https://patchwork.ozlabs.org/patch/765996/
https://patchwork.ozlabs.org/patch/765997/
https://patchwork.ozlabs.org/patch/765998/
i already applied them, and they didn't work as well.
i also found these patches wh
This series aims at adding support for CPU information display.
While here, following suggestions from Michal, the FPGA
initialization is cleaned up.
Ezequiel Garcia (5):
zynq: Define macros for the device names
zynq: Rework FPGA initialization
zynq: Support CPU info display
zynq: board: R
This will allow to reuse the macros when showing
the CPU info.
Signed-off-by: Ezequiel Garcia
---
include/zynqpl.h | 32 ++--
1 file changed, 22 insertions(+), 10 deletions(-)
diff --git a/include/zynqpl.h b/include/zynqpl.h
index 5a34a17daefe..e10a266643bd 100644
--
This commit moves the FPGA descriptor definition
to mach-zynq, where it makes more sense.
Also, the implementation is reworked to be cleaner
and a bit smaller.
add/remove: 2/11 grow/shrink: 0/1 up/down: 420/-608 (-188)
function old new delta
zynq_fpga_des
Now that silicon version has been moved from checkboard()
to print_cpuinfo(), we need to enable DISPLAY_CPUINFO option.
Signed-off-by: Ezequiel Garcia
---
configs/syzygy_hub_defconfig | 1 -
configs/topic_miami_defconfig | 1 -
configs/topic_miamilite_defconfig | 1 -
configs/topic_m
This commit adds CPU and silicon version information
consuming the SLCR IDCODE and DEVCFG MCTRL registers,
respectively.
Signed-off-by: Ariel D'Alessandro
Signed-off-by: Ezequiel Garcia
---
arch/arm/mach-zynq/cpu.c | 46 ++
1 file changed, 46 insertio
Now that showing silicon version is part of the CPU
info display, let's remove checkboard().
Note that the generic show_board_info() will still
show the DT 'model' property. For instance:
U-Boot 2018.01-00172-g5e296ab7317a (Jan 17 2018 - 09:57:36 -0300)
CPU: Zynq 7z010
Silicon: v3.1
Mo
On 17/01/2018 11:56, Jaehoon Chung wrote:
Hi,
On 01/17/2018 07:36 PM, Jaehoon Chung wrote:
When power is off, clock is not disabling.
Because it's passed to 1, mmc->clock should be set to f_min value.
Some drivers can't initialize the eMMC/SD card with current status.
This patch is to fix th
Hi Peng,
2018-01-16 10:25 GMT-02:00 Peng Fan :
>
>
>> -Original Message-
>> From: Diego Dorta [mailto:diegohdo...@gmail.com]
>> Sent: Tuesday, January 16, 2018 8:15 PM
>> To: Peng Fan
>> Cc: Peng Fan ; Fabio Estevam
>> ; U-Boot-Denx
>> Subject: Re: [U-Boot] [PATCH V5 00/31] imx: add i.MX
Hi Marek and Stefan,
Am 09.06.2017 um 19:28 schrieb Marek Behún:
> This is the fourth version of patches for adding support for the
> Turris Omnia board, a router developed by the CZ.NIC.
I'm still facing trouble testing turris_omnia on latest v2018.01.
First, that made me notice there's no READ
Martin,
Am Dienstag, 16. Januar 2018, 15:13:04 CET schrieb Martin Townsend:
> > Martin, can you please explain what corruption you see?
> > From reading the code I'd assume that you miss volumes but a full scan
> > would recover everything.
>
> I didn't do much analysis of the corruption I'm afra
On 15/01/18 04:48, Peng Fan wrote:
On Mon, Jan 15, 2018 at 11:25:00AM +0800, Kever Yang wrote:
Bryan,
On 01/12/2018 11:10 PM, Bryan O'Donoghue wrote:
On 12/01/18 11:27, Philipp Tomsich wrote:
OP-TEE is an open source trusted OS, in armv7, its loading and
running are like this:
loading:
-
When running the Travis test suite for master I see warnings
arch/sandbox/dts/sandbox.dtb: Warning (gpios_property): Could not get
phandle node for /gpios@0:num-gpios(cell 0)
(https://travis-ci.org/xypron2/u-boot/jobs/329755777)
The warning is created by check_gpios_property() in scripts/dtc/chec
Tom,
The following changes since commit 3dde8f20377c3a051dda64497bdf0cdb23e03a2d:
Merge git://git.denx.de/u-boot-mmc (2018-01-14 22:26:38 -0500)
are available in the git repository at:
git://git.denx.de/u-boot-fsl-qoriq.git
for you to fetch changes up to 2eb2dbd4577898bf289e911b2286df3f236
Hi Tom,
On Mon, Jan 15, 2018 at 8:25 PM, Tom Rini wrote:
> On Mon, Jan 15, 2018 at 12:06:17PM -0600, Joe Hershberger wrote:
>
>> Hi Tom,
>>
>> The following changes since commit 3dde8f20377c3a051dda64497bdf0cdb23e03a2d:
>>
>> Merge git://git.denx.de/u-boot-mmc (2018-01-14 22:26:38 -0500)
>>
>>
For the construction of device paths we need to call the
AllocatePool service. We should not ignore if it fails due to an
out of memory situation.
This patch changes the device path functions to return NULL if
the memory allocation fails.
Additional patches will be needed to fix the callers.
Sig
With this patch series an EFI application or driver can supply
a block device which in turn can be used to download an image.
E.g. we can load iPXE, connect iSCSI drives, download grub from the
SAN and afterwards with grub download and run an EFI application.
Booting Linux from an iSCSI drive was
When installing the the simple file system protocol we have to path
the address of the structure and not the address of a pointer ot the
structure.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
lib/efi_loader/efi_disk.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
dif
On a block device and its partions the same protocols can be
installed. To tell the apart we can use the type of the last
node of the device path which is not the end node.
The patch provides a utility function to find this last node.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
-
The category of memory allocated for an EFI image should depend on
its type (application, bootime service driver, runtime service driver).
Our helloworld.efi built on arm64 has an illegal image type. Treat it
like an EFI application.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
--
In contrast to the description the code did not split the device
path into device part and file part.
The code should use the installed protocol and not refer to the
internal structure of the the disk object.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
lib/efi_loader/efi_dis
Use %pD to print the device path instead of its address when
entering efi_load_image.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
lib/efi_loader/efi_boottime.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/efi_loader/efi_boottime.c b/lib/efi_loader/e
Up to now we have been using efi_disk_create_partitions() to create
partions for block device that existed before starting an EFI
application.
We need to to call it for for block devices created by EFI
applications at run time. The EFI application will define the
handle for the block device and in
The calling convention for the entry point of an EFI image
is always 'asmlinkage'.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
lib/efi_loader/efi_boottime.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/efi_loader/efi_boottime.c b/lib/efi_loader/ef
The interface type name can be used to look up the interface type.
Don't confound it with the driver name which may be different.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
lib/efi_loader/efi_disk.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/efi_
Check if the device tree and the SMBIOS table are available.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
lib/efi_loader/helloworld.c | 26 ++
1 file changed, 26 insertions(+)
diff --git a/lib/efi_loader/helloworld.c b/lib/efi_loader/helloworld.c
index
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
lib/efi_selftest/Makefile| 4 +
lib/efi_selftest/efi_selftest_block_device.c | 395 +++
lib/efi_selftest/efi_selftest_disk_image.h | 69 +
3 files changed, 468 insertions(+)
creat
U-Boot devices and EFI handles can be related, e.g. an
IDE disk relates to a handle with the EFI_BLOCK_IO_PROTOCOL.
Provide pointers to store these links.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
include/dm/device.h | 4
include/efi_loader.h | 2 ++
This patch provides
* a uclass for EFI drivers
* a EFI driver for block devices
For each EFI driver the uclass
* creates a handle
* adds the driver binding protocol
The uclass provides the bind, start, and stop entry points for the driver
binding protocol.
In bind() and stop() it checks if the c
This patch lets the implementation of ExitBootServices conform to
the UEFI standard.
The timer events must be disabled before calling the notification
functions of the exit boot services events.
The boot services must be disabled in the system table.
The handles in the system table should be def
Provide new function efi_dp_part_node() to create a device
node for a partition.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
include/efi_loader.h | 2 +
lib/efi_loader/efi_device_path.c | 106 ++-
2 files changed, 72 insertion
The GUID of the EFI_BLOCK_IO_PROTOCOL is needed in different code
parts. To avoid duplication make efi_block_io_guid a global symbol.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
include/efi_loader.h | 2 ++
lib/efi_loader/efi_disk.c | 2 +-
2 files changed, 3 insertions(
Add the revision constants.
Depending on the revision additional fields are needed in the
media descriptor.
Use efi_uintn_t for number of bytes to read or write.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
include/efi_api.h | 10 --
lib/efi_loader/efi_disk.c |
For testing EFI disk management we need an in-memory image of
a disk.
The tool file2include converts a file to a C include. The file
is separated into strings of 8 bytes. Only the non-zero strings
are written to the include. The output format has been designed
to maintain readability.
#define EF
On 17 January 2018 at 00:54, Alexander Graf wrote:
> Currently our serial device search chokes on the fact that the serial
> probe function could fail. If it does, instead of searching for the next
> usable serial device, it just quits.
>
> This patch changes the fallback logic so that even when a
Hi Alex,
On 17 January 2018 at 00:54, Alexander Graf wrote:
> On some boards, serial devices may or may not be muxed properly to actual
> pins, depending on firmware configuration. To determine whether we should
> use a serial device for U-Boot in-/output, we need to check whether it
> is muxed p
Hi Alex,
On 17 January 2018 at 00:54, Alexander Graf wrote:
> The serial devices on the raspberry pi are based on clocks we can't easily
> read and influence in U-Boot. However, the serial devices are always already
> properly set up when coming up, so all we need to do is leave them alone.
>
> T
Hi Alex,
On 17 January 2018 at 00:54, Alexander Graf wrote:
> Now that we have all infrastructure in place to dynamically determine whether
> a serial device is actually usable (read: routed to user accessible pins), we
> can wire it up to the board.
>
> This patch adds support to determine wheth
Hi,
On 01/17/2018 12:46 AM, patrice.chot...@st.com wrote:
> From: Patrice Chotard
>
> Add ETHMAC, ETHMACRX and ETHMACTX clocks for STMMAC.
>
> Signed-off-by: Patrice Chotard
Reviewed-by: Vikas Manocha
Cheers,
Vikas
> ---
> arch/arm/dts/stm32f746.dtsi | 3 +++
> 1 file changed, 3 insertion
On 15 January 2018 at 22:33, Jaehoon Chung wrote:
> exynos5422 has the s2mps11 PMIC.
> s2mps11 pmic has the 10-BUCK and 38-LDO regulators.
> Each IP and devices in exynos5422 can be controlled by each regulators.
> This patch is support for s2mps11 regulator driver.
>
> Signed-off-by: Jaehoon Chun
On 15 January 2018 at 22:33, Jaehoon Chung wrote:
> Add the probe function to support the s2mps11 regulator driver.
>
> Signed-off-by: Jaehoon Chung
> ---
> drivers/power/pmic/s2mps11.c | 28
> 1 file changed, 28 insertions(+)
Reviewed-by: Simon Glass
_
On 15 January 2018 at 22:33, Jaehoon Chung wrote:
> Enable the CONFIG_CMD_REGULATOR and CONFIG_DM_REGULATOR_S2MPS11.
>
> Signed-off-by: Jaehoon Chung
> ---
> configs/odroid-xu3_defconfig | 2 ++
> 1 file changed, 2 insertions(+)
Reviewed-by: Simon Glass
Hi Alex,
On 16 January 2018 at 05:46, Alexander Graf wrote:
> The bcm2835 firmware provided device trees expect device tree users
> to support pin muxing for the SD devices to work properly.
>
> This patch adds pin muxing support to the sdhci based SD controller
> on said family of SoCs, so that
Hi Alex,
On 16 January 2018 at 05:46, Alexander Graf wrote:
> On the bcm2835 the GPIO IP block is responsible to control pin muxing
> of the configurable pins on the chip.
>
> This adds a simple helper function that allows a device driver to set
> pin muxing according to device tree configuration
Hi Patrice,
On 01/17/2018 12:46 AM, patrice.chot...@st.com wrote:
> From: Patrice Chotard
>
> Move SYSCFG clock setup into configure_clocks() instead of calling
> clock_setup() from drivers.
It is in board configuration.
> Move the RMII setup from board_early_init_f() to board_init()
> to insu
Hi,
On 01/17/2018 12:46 AM, patrice.chot...@st.com wrote:
> From: Patrice Chotard
>
> Thanks to 'commit ba1f96672522 ("net: designware: add clock support")'
> we don't need anymore to setup the STMMAC clock in board.
>
> Signed-off-by: Patrice Chotard
Reviewed-by: Vikas Manocha
Cheers,
Vika
Thank you Bin,
I managed to fully boot Broadwell-DE on platform with memory down enabled :)
Now before submitting the patch I have to solve a small problem.
In either case memory down is enable or not the booting process takes 1 hour
and 20 minutes. On the output there are no error at all. I tri
On 17.01.18 21:06, Simon Glass wrote:
> Hi Alex,
>
> On 16 January 2018 at 05:46, Alexander Graf wrote:
>> The bcm2835 firmware provided device trees expect device tree users
>> to support pin muxing for the SD devices to work properly.
>>
>> This patch adds pin muxing support to the sdhci base
On 17.01.18 10:26, Amit Tomer wrote:
> Hi,
>
>> + val = readl(&gpios->reg->gpfsel[BCM2835_GPIO_FSEL_BANK(gpio)]);
>> + val &= ~(BCM2835_GPIO_FSEL_MASK << BCM2835_GPIO_FSEL_SHIFT(gpio));
>> + val |= (func << BCM2835_GPIO_FSEL_SHIFT(gpio));
>> + writel(val, &gpios->reg->gpf
Hi,
On Wed, Jan 17, 2018 at 3:47 PM, Richard Weinberger
wrote:
> Martin,
>
> Am Dienstag, 16. Januar 2018, 15:13:04 CET schrieb Martin Townsend:
>> > Martin, can you please explain what corruption you see?
>> > From reading the code I'd assume that you miss volumes but a full scan
>> > would rec
On 17.01.18 20:34, Simon Glass wrote:
> On 17 January 2018 at 00:54, Alexander Graf wrote:
>> Currently our serial device search chokes on the fact that the serial
>> probe function could fail. If it does, instead of searching for the next
>> usable serial device, it just quits.
>>
>> This patch
1 - 100 of 142 matches
Mail list logo
