We only need to run driver-model tests with this config, since this is the
only thing that is different when CONFIG_OF_LIVE is not defined. Filter
out the other tests to same time.
Signed-off-by: Simon Glass
---
Changes in v2:
- Add new patch to reduce the number of tests run with sandbox_flattr
Now that we fixed the pre-relocation driver binding for driver marked
with DM_FLAG_PRE_RELOC flag, add a test case to cover that scenario.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
arch/sandbox/dts/test.dts | 4
test/dm/bus.c
This is currently out of order. Sort it.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3:
- rebase on u-boot/master so that patch [4/8] can be applied cleanly
Changes in v2: None
drivers/timer/Kconfig | 110 +-
1 file change
Commit f2006808f099: ("dm: core: parse chosen node") added a logic
to parse the chosen node during dm_scan_fdt_node(), but unfortunately
it missed adding the same logic in dm_scan_fdt_live(). This mirrors
the logic in the livetree version.
The weird thing is that commit f2006808f099 did update the
Currently the comments of several APIs (eg: dm_init_and_scan()) say:
@pre_reloc_only: If true, bind only drivers with the DM_FLAG_PRE_RELOC
flag. If false bind all drivers.
The 'Pre-Relocation Support' chapter in doc/driver-model/README.txt
documents the same that both device tree properties and
It was observed that current output of print_cpuinfo() on QEMU
x86 targets does not have an ending '\n', neither have a leading
'CPU:' any more. However it used to have these before.
It turns out commit c0434407b595 introduced a unified DM version
of print_cpuinfo() that exposed such issue on QEMU
The pre_reloc_only parameter description currently only mentions
drivers with the DM_FLAG_PRE_RELOC flag, but does not mention the
special device tree properties. Correct them.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
include/dm/device-inter
The description string should not contain unnecessary characters,
like the ending '\n' or the leading 'CPU:'.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
drivers/cpu/mpc83xx_cpu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Applied t
This adds a new API dm_ofnode_pre_reloc(), a livetree equivalent
API of dm_fdt_pre_reloc().
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
drivers/core/util.c | 25 +
include/dm/util.h | 27 ++-
2
Add a driver for gdsys IHS (Integrated Hardware Systems) FPGAs, which
supports initialization of the FPGA, as well as information gathering.
Reviewed-by: Simon Glass
Signed-off-by: Mario Six
---
v10 -> v11:
No changes
v9 -> v10:
No changes
v8 -> v9:
No changes
v7 -> v8:
No changes
v6 -> v7:
ofnode_read_simple_addr_cells may fail and return a negative error code.
Check for this when initializing regmaps.
Also check if both_len is zero, since this is perfectly possible, and
would lead to a division-by-zero further down the line.
Reviewed-by: Anatolij Gustschin
Reviewed-by: Simon Glas
Document the regmap_alloc() function.
Reviewed-by: Anatolij Gustschin
Reviewed-by: Simon Glass
Signed-off-by: Mario Six
---
v10 -> v11:
No changes
v9 -> v10:
No changes
v8 -> v9:
No changes
v7 -> v8:
No changes
v6 -> v7:
No changes
v5 -> v6:
No changes
v4 -> v5:
No changes
v3 -> v4:
No
The upcoming changes to the regmap interface will contain a proper check
for plausibility when reading/writing from/to a register map. To still
have the current tests pass, increase the size of the memory region for
the syscon0 device, since one of the tests reads and writes beyond this
range.
Rev
This patch adds a driver for the bus associated with a IHS FPGA.
Reviewed-by: Simon Glass
Signed-off-by: Mario Six
---
v10 -> v11:
No changes
v9 -> v10:
No changes
v8 -> v9:
No changes
v7 -> v8:
No changes
v6 -> v7:
No changes
v5 -> v6:
No changes
v4 -> v5:
No changes
v3 -> v4:
No change
The documentation in regmap.h is not in kernel-doc format. Correct this.
Reviewed-by: Anatolij Gustschin
Reviewed-by: Simon Glass
Signed-off-by: Mario Six
---
v10 -> v11:
No changes
v9 -> v10:
No changes
v8 -> v9:
No changes
v7 -> v8:
No changes
v6 -> v7:
No changes
v5 -> v6:
No changes
Makefile entries should be sorted.
Reviewed-by: Anatolij Gustschin
Reviewed-by: Simon Glass
Signed-off-by: Mario Six
Signed-off-by: Anatolij Gustschin
---
v10 -> v11:
No changes
v9 -> v10:
No changes
v8 -> v9:
No changes
v7 -> v8:
No changes
v6 -> v7:
No changes
v5 -> v6:
No changes
v4
A newly created property is currently not freed if a name could not be
allocated. This patch fixes the resulting memory leak in the error
patch.
Reported-by: Coverity (CID: 184085)
Fixes: e369e58df79c ("core: Add functions to set properties in live-tree")
Signed-off-by: Mario Six
---
drivers/cor
Add REAME.virtio to describe the information about U-Boot support for
VirtIO devices, including supported boards, build instructions, driver
details etc.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Changes in v2:
- Added driver remove and flags description in the d
On 15 October 2018 at 03:21, Bin Meng wrote:
> This driver provides support for Sandbox implementation of virtio
> transport driver which is used for testing purpose only.
>
> Two drivers are provided. The 2nd one is a driver that lacks the
> 'notify' op.
>
> Signed-off-by: Bin Meng
>
> ---
>
> C
Add virtio drivers for QEMU x86 targets.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
board/emulation/qemu-x86/Kconfig | 3 +++
1 file changed, 3 insertions(+)
Applied to u-boot-dm/next, thanks!
___
U
On 15 October 2018 at 03:21, Bin Meng wrote:
> Now that we have a sandbox virtio transport driver, add some test
> cases to test virtio uclass driver.
>
> Signed-off-by: Bin Meng
>
> ---
>
> Changes in v3:
> - Exclude VIRTIO_BLK in sandbox_noblk_defconfig build
>
> Changes in v2:
> - new patch to
This adds a Kconfig file in the board directory, so that some
board-specific options can be specified there.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
arch/arm/Kconfig | 1 +
board/emulation/qemu-arm/Kconfig | 9 +
con
Add test cases to cover the two newly added PCI APIs:
dm_pci_find_next_capability() & dm_pci_find_next_ext_capability().
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Changes in v2:
- adjust swap_case driver to handle request from
_dm_pci_find_next_capability()
d
This adds a transport driver that implements UCLASS_VIRTIO for
virtio over pci, which is commonly used on x86.
It only supports the legacy interface of the pci transport, which
is the default device that QEMU emulates.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Ch
This introduces two new APIs dm_pci_find_next_capability() and
dm_pci_find_next_ext_capability() to get PCI capability address
and PCI express extended capability address for a given PCI device
starting from a given offset.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: No
For v1.0 compliant device, it always assumes the member 'num_buffers'
exists in the struct virtio_net_hdr while the legacy driver only
presented 'num_buffers' when VIRTIO_NET_F_MRG_RXBUF was negotiated.
Without that feature the structure was 2 bytes shorter.
Update the driver to support the non-le
From: Tuomas Tynkkynen
This adds a new block interface type for VirtIO block devices.
Signed-off-by: Tuomas Tynkkynen
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
disk/part.c| 6 ++
drivers/block/blk-uclass.c | 2 ++
inclu
On Tue, Oct 23, 2018 at 11:01 AM Marek Vasut wrote:
>
> On 10/19/2018 05:25 AM, Simon Glass wrote:
> > On 9 August 2018 at 13:04, Simon Goldschmidt
> > wrote:
> >> If _debug_uart_putc() is called before _debug_uart_init(), the
> >> ns16550 debug uart driver hangs in a tight loop waiting for the
>
Currently devices on the virtio bus is not automatically enumerated,
which means peripherals on the virtio bus are not discovered by their
drivers. This uses board_init() to do the virtio enumeration.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Changes in v2:
- imp
Hi Livu,
On 28 September 2018 at 10:02, Liviu Dudau wrote:
> On Fri, Sep 28, 2018 at 09:57:49AM -0600, Simon Glass wrote:
>> On 28 September 2018 at 06:12, Liviu Dudau wrote:
>> > Use the uclass_foreach_dev() macro instead of the open coded version.
>> >
>> > Signed-off-by: Liviu Dudau
>> > ---
From: Tuomas Tynkkynen
Add 'virtio' command in U-Boot command line.
Signed-off-by: Tuomas Tynkkynen
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
cmd/Kconfig | 7 +++
cmd/Makefile | 1 +
cmd/virtio.c | 38 +++
On 15 October 2018 at 03:21, Bin Meng wrote:
> This adds a new virtio uclass driver for “virtio” [1] family of
> devices that are are found in virtual environments like QEMU,
> yet by design they look like physical devices to the guest.
>
> The uclass driver provides child_pre_probe() and child_po
At present the generic io{read,write}{8,16,32} routines only support
MMIO access. With architecture like x86 that has a separate IO space,
these routines cannot be used to access I/O ports.
Implement x86-specific version to support both PIO and MMIO access,
so that drivers for multiple architectur
With the virtio net and blk drivers, we can do more stuff with some
useful commands. Imply those in the board Kconfig.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
board/emulation/qemu-riscv/Kconfig | 8
1 file changed, 8 insertions(+)
VirtIO can use various different buses and virtio devices are
commonly implemented as PCI devices. But virtual environments
without PCI support (a common situation in embedded devices
models) might use simple memory mapped device (“virtio-mmio”)
instead of the PCI device.
This adds a transport dri
On 15 October 2018 at 03:20, Bin Meng wrote:
> Some buses need to set up their child devices after they are probed.
> Support a common child_post_probe() method for the uclass.
>
> With this change, the two APIs uclass_pre_probe_device() and
> uclass_post_probe_device() become symmetric.
>
> Signe
Currently devices on the virtio bus is not automatically enumerated,
which means peripherals on the virtio bus are not discovered by their
drivers. This uses board_init() to do the virtio enumeration.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
Both fdtdec_get_addr_size_fixed and of_address_to_resource can fail with
an error, which is not currently checked during regmap initialization.
Since the indentation depth is already quite deep, extract a new
'init_range' method to do the initialization.
Reviewed-by: Anatolij Gustschin
Reviewed-
Add test for regmap_{set,get} functions.
Reviewed-by: Anatolij Gustschin
Reviewed-by: Simon Glass
Signed-off-by: Mario Six
---
v10 -> v11:
No changes
v9 -> v10:
No changes
v8 -> v9:
No changes
v7 -> v8:
No changes
v6 -> v7:
No changes
v5 -> v6:
No changes
v4 -> v5:
No changes
v3 -> v4:
It would be convenient if one could use the regmap API in conjunction
with register maps defined as structs (i.e. structs that directly mirror
the memory layout of the registers in question). A similar approach was
planned with the regmap_write32/regmap_read32 macros, but was never
used.
Hence, im
blk_next_free_devnum() can be helpful in some cases. Make it
a public API.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
drivers/block/blk-uclass.c | 2 +-
include/blk.h | 11 +++
2 files changed, 12 insertions(+), 1 deletio
The blk_base test case creates a USB mass storage block device with
the Sandbox host block device as its parent. This does not make any
sense and causes potential issue, for example if the test case tries
to read/write anything on the USB mass storage block device it will
definitely fail as its par
From: Tuomas Tynkkynen
This adds virtio net device driver support.
Signed-off-by: Tuomas Tynkkynen
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Changes in v2:
- Changed virtio net driver feature table to const
drivers/virtio/Kconfig | 7 ++
drivers/virt
On 15 October 2018 at 03:20, Bin Meng wrote:
> Add test case to cover uclass driver's child_post_probe() method.
>
> Signed-off-by: Bin Meng
>
> ---
>
> Changes in v3: None
> Changes in v2:
> - new patch to add test case for uclass driver's child_post_probe()
>
> include/dm/test.h | 1 +
> tes
On 15 October 2018 at 03:20, Bin Meng wrote:
> This adds a call to dm_remove_devices_flags() to do_bootm_linux()
> so that drivers that have one of the removal flags set (e.g.
> DM_FLAG_ACTIVE_DMA_REMOVE) in their driver struct, may do some
> last-stage cleanup before the OS is started.
>
> arm an
part_init() is currently called in every DM BLK driver, either
in its bind() or probe() method. However we can use the BLK
uclass driver's post_probe() method to do it automatically.
Update all DM BLK drivers to adopt this change.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in
It is useful to be able to treat the different ranges of a regmap
separately to be able to use distinct offset for them, but this is
currently not implemented in the regmap API.
To preserve backwards compatibility, add regmap_read_range and
regmap_write_range functions that take an additional para
Currently the efi block driver uses priv_auto_alloc_size for the
driver data, however that's only available after the device probe
phase. In order to make it accessible in an earlier phase, switch
to use platdata_auto_alloc_size instead.
This patch is the prerequisite for the follow up patch of DM
With the post_probe() changes, this API is no longer needed.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
drivers/block/blk-uclass.c | 9 -
include/blk.h | 10 --
2 files changed, 19 deletions(-)
Applied to u-boot-
From: Tuomas Tynkkynen
This adds virtio block device driver support.
Signed-off-by: Tuomas Tynkkynen
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Changes in v2:
- Correct desc->vendor for PCI transport
drivers/virtio/Kconfig | 7 +++
drivers/virtio/Makef
From: Tuomas Tynkkynen
This adds support for managing virtual queue/ring, the channel
for high performance I/O between host and guest.
Signed-off-by: Tuomas Tynkkynen
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
drivers/virtio/Makefile |
By default QEMU creates legacy PCI transport devices, but we can
ask QEMU to create non-legacy one if we pass additional device
property/value pairs in the command line:
-device virtio-blk-pci,disable-legacy=true,disable-modern=false
This adds a new driver driver to support non-legacy (modern)
Introduce a new Kconfig option for architecture codes to control
whether it provides io{read,write}{8,16,32} I/O accessor functions.
Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
include/linux/io.h | 4
lib/Kconfig| 6 ++
2 files
Currently the sandbox block driver uses priv_auto_alloc_size for
the driver data, however that's only available after the device
probe phase. In order to make it accessible in an earlier phase,
switch to use platdata_auto_alloc_size instead.
This patch is the prerequisite for the follow up patch o
Add some overview documentation that explains the purpose and some of
the features and limitations of the regmap interface.
Reviewed-by: Bin Meng
Signed-off-by: Mario Six
---
v10 -> v11:
No changes
v9 -> v10:
No changes
v8 -> v9:
* Amended for inclusion of endianness setting via DT
v7 -> v8:
On 15 October 2018 at 01:24, Mario Six wrote:
> The regmap functions currently assume that all register map accesses
> have a data width of 32 bits, but there are maps that have different
> widths.
>
> To rectify this, implement the regmap_raw_read and regmap_raw_write
> functions from the Linux k
Add support for switching the endianness of regmap accesses via the
"little-endian", "big-endian", and "native-endian" boolean properties in
the device tree.
The default endianness is native endianness.
Signed-off-by: Mario Six
Reviewed-by: Simon Glass
Reviewed-by: Daniel Schwierzeck
---
v10
Add some debug output in cases where the initialization of a regmap
fails.
Reviewed-by: Anatolij Gustschin
Reviewed-by: Simon Glass
Signed-off-by: Mario Six
---
v10 -> v11:
No changes
v9 -> v10:
No changes
v8 -> v9:
No changes
v7 -> v8:
No changes
v6 -> v7:
No changes
v5 -> v6:
No changes
On 24 October 2018 at 07:36, Bin Meng wrote:
> When a driver declares DM_FLAG_PRE_RELOC flag, it wishes to be
> bound before relocation. However due to a bug in the DM core,
> the flag only takes effect when devices are statically declared
> via U_BOOT_DEVICE(). This bug has been fixed recently by
On 24 October 2018 at 07:36, Bin Meng wrote:
> When a driver declares DM_FLAG_PRE_RELOC flag, it wishes to be
> bound before relocation. However due to a bug in the DM core,
> the flag only takes effect when devices are statically declared
> via U_BOOT_DEVICE(). This bug has been fixed recently by
On 24 October 2018 at 07:36, Bin Meng wrote:
> When a driver declares DM_FLAG_PRE_RELOC flag, it wishes to be
> bound before relocation. However due to a bug in the DM core,
> the flag only takes effect when devices are statically declared
> via U_BOOT_DEVICE(). This bug has been fixed recently by
On 24 October 2018 at 07:36, Bin Meng wrote:
> When a driver declares DM_FLAG_PRE_RELOC flag, it wishes to be
> bound before relocation. However due to a bug in the DM core,
> the flag only takes effect when devices are statically declared
> via U_BOOT_DEVICE(). This bug has been fixed recently by
On 24 October 2018 at 07:36, Bin Meng wrote:
> Add some description about pre-relocation driver binding, including
> usage of DM_FLAG_PRE_RELOC flag and caveats.
>
> Signed-off-by: Bin Meng
>
> ---
>
> doc/driver-model/README.txt | 16
> 1 file changed, 12 insertions(+), 4 delet
> From: U-Boot On Behalf Of Bin Meng
> Sent: mercredi 24 octobre 2018 15:36
>
> When a driver declares DM_FLAG_PRE_RELOC flag, it wishes to be bound before
> relocation. However due to a bug in the DM core, the flag only takes effect
> when devices are statically declared via U_BOOT_DEVICE(). This
On 24 October 2018 at 07:36, Bin Meng wrote:
> When a driver declares DM_FLAG_PRE_RELOC flag, it wishes to be
> bound before relocation. However due to a bug in the DM core,
> the flag only takes effect when devices are statically declared
> via U_BOOT_DEVICE(). This bug has been fixed recently by
On 24 October 2018 at 07:36, Bin Meng wrote:
> When a driver declares DM_FLAG_PRE_RELOC flag, it wishes to be
> bound before relocation. However due to a bug in the DM core,
> the flag only takes effect when devices are statically declared
> via U_BOOT_DEVICE(). This bug has been fixed recently by
On 24 October 2018 at 07:36, Bin Meng wrote:
> When a driver declares DM_FLAG_PRE_RELOC flag, it wishes to be
> bound before relocation. However due to a bug in the DM core,
> the flag only takes effect when devices are statically declared
> via U_BOOT_DEVICE(). This bug has been fixed recently by
On 24 October 2018 at 07:36, Bin Meng wrote:
> When a driver declares DM_FLAG_PRE_RELOC flag, it wishes to be
> bound before relocation. However due to a bug in the DM core,
> the flag only takes effect when devices are statically declared
> via U_BOOT_DEVICE(). This bug has been fixed recently by
On 24 October 2018 at 07:36, Bin Meng wrote:
> When a driver declares DM_FLAG_PRE_RELOC flag, it wishes to be
> bound before relocation. However due to a bug in the DM core,
> the flag only takes effect when devices are statically declared
> via U_BOOT_DEVICE(). This bug has been fixed recently by
On 14.10.2018 10:07, Bin Meng wrote:
> It turns out commit c0434407b595 broke some boards which have DM CPU
> driver with CONFIG_DISPLAY_CPUINFO option on. These boards just fail
> to boot when print_cpuinfo() is called during boot.
>
> Fixes: c0434407b595 ("board_f: Use static print_cpuinfo if CON
On 24 October 2018 at 07:36, Bin Meng wrote:
> When a driver declares DM_FLAG_PRE_RELOC flag, it wishes to be
> bound before relocation. However due to a bug in the DM core,
> the flag only takes effect when devices are statically declared
> via U_BOOT_DEVICE(). This bug has been fixed recently by
> From: U-Boot On Behalf Of Bin Meng
> Sent: mercredi 24 octobre 2018 15:37
> Subject: [U-Boot] [PATCH 03/13] gpio: Remove DM_FLAG_PRE_RELOC flag in
> various drivers
>
> When a driver declares DM_FLAG_PRE_RELOC flag, it wishes to be bound before
> relocation. However due to a bug in the DM core,
On 14.10.2018 10:07, Bin Meng wrote:
> To support CONFIG_DISPLAY_CPUINFO, add "u-boot,dm-pre-reloc" for
> all cpu nodes in Sandbox test.dts.
>
> Signed-off-by: Bin Meng
Reviewed-by: Stefan Roese
Thanks,
Stefan
Applied to u-boot-dm/master, thanks!
___
From: Simon Glass
To: U-Boot Mailing List
Cc: Tom Rini ,
Marek Vasut ,
Simon Glass ,
Masahiro Yamada ,
Rasmus Villemoes ,
Baruch Siach ,
Jagdish Gediya ,
Stephen Warren
Subject: [PATCH 1/3] Makefile: Add a warning for boards that don't use
It is useful to obtain the block-protect setting of the SPI flash, so we
know whether it is fully open or (perhaps partially) write-protected. Add
a method for this. Update the sandbox driver to process this operation and
add a test.
Signed-off-by: Simon Glass
---
arch/sandbox/include/asm/test.
At present the config header is not included in this file, but it does use
a CONFIG option. Fix it.
Signed-off-by: Simon Glass
---
lib/string.c | 1 +
1 file changed, 1 insertion(+)
Applied to u-boot-dm/master, thanks!
___
U-Boot mailing list
U-Boot@
The current test is a functional test, covering all the way from the
command line to the sandbox SPI driver. This is useful, but it is easier
to diagnose failures with a smaller test.
Add a simple test which reads and writes data and checks that it is stored
and retrieved correctly.
Signed-off-by
Hi Simon,
> From: Simon Glass
> Sent: mardi 6 novembre 2018 23:22
> Subject: [PATCH 22/25] misc: Update read() and write() methods to return bytes
>
> At present these functions return 0 on success. For some devices we want to
> know how many bytes were transferred. It seems useful to adjust the
It seems useful to make sandbox its own log category since it is used for
so much testing. Add this as a new category.
Signed-off-by: Simon Glass
---
include/log.h | 1 +
1 file changed, 1 insertion(+)
Applied to u-boot-dm/master, thanks!
___
U-Boot
It is useful to be able to invert the colours in some cases so that the
text matches the background colour. Add a parameter to the function to
support this.
It is strange that function takes a private data structure from another
driver as an argument. It seems better to pass the device and have th
When the build fails due to something wrong in binman it is sometimes
useful to get a full backtrace showing the location of the failure. Add
a BINMAN_DEBUG environment variable to support this along with some
documentation.
Signed-off-by: Simon Glass
---
Makefile| 6 --
tools/b
Add a way to read a file from the host filesystem. This can be useful for
reading test data, for example. Also fix up the writing function which was
not the right version, and drop the debugging lines.
Signed-off-by: Simon Glass
---
arch/sandbox/cpu/os.c | 44 +++
This adds new commands to the EC related to setting and clearing events
as well as controlling power-related settings.
Signed-off-by: Simon Glass
---
drivers/misc/cros_ec.c | 345 -
drivers/misc/cros_ec_sandbox.c | 2 +-
include/cros_ec.h |
Add some more logging to provide more information on failures.
Signed-off-by: Simon Glass
---
drivers/misc/cros_ec.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
Applied to u-boot-dm/master, thanks!
___
U-Boot mailing list
U-Boot
At present sandbox drivers are mostly not used before relocation. Some of
these are needed by Chromium OS verified boot, since it uses sandbox TPL,
so update them accordingly.
Signed-off-by: Simon Glass
---
arch/sandbox/dts/sandbox.dts | 15 +++
1 file changed, 15 insertions(+)
App
Hi Bin,
Thanks a lot for your review!
Thanks,
Zhiqiang
> -Original Message-
> From: Bin Meng
> Sent: 2018年10月8日 16:53
> To: Z.q. Hou
> Cc: U-Boot Mailing List ; Simon Glass
> ; Christian Gmeiner ;
> Tuomas Tynkkynen ; Bernhard Messerklinger
> ; Masahiro Yamada
> ; Mingkai Hu ;
> M.h. L
On 14 October 2018 at 13:40, Heinrich Schuchardt wrote:
> The command to set environment variables is setenv.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> board/sandbox/README.sandbox | 16
> 1 file changed, 8 insertions(+), 8 deletions(-)
Reviewed-by: Simon Glass
Applied t
This comma is not needed. Drop it.
Signed-off-by: Simon Glass
---
tools/binman/etype/blob.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Applied to u-boot-dm/master, thanks!
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de
With drivers that have prefix names that are quite long (like
'versatile_') it is useful to have a wider column for the driver's
name when dumping the device driver tree.
Also update the tests to take into account the wider output format.
Signed-off-by: Liviu Dudau
Reviewed-by: Simon Glass
---
On 07/11/18 07:21, Simon Glass wrote:
> This function is really just a call to uclass_get_device() and there is no
> reason why the caller cannot do it. Update sandbox and snow accordingly.
>
> Signed-off-by: Simon Glass
> ---
>
> board/samsung/common/board.c | 10 ++
> board/sandbox/sand
The LPC driver expects its buffer to be word-aligned. Add the required
flag to the uclass driver to ensure this.
Signed-off-by: Simon Glass
---
drivers/misc/cros_ec.c | 1 +
1 file changed, 1 insertion(+)
Applied to u-boot-dm/master, thanks!
___
U-Bo
In some cases U-Boot is compressed and it is useful to be able to
decompress it in SPL. Add a Kconfig and Makefile change to allow this.
Note that this does not actually implement decompression.
Signed-off-by: Simon Glass
---
lib/Kconfig | 8
lib/Makefile | 2 +-
2 files changed, 9 in
At present we don't distinguish between errors and warnings when printing
the architecture summary. Rename the variables to better describe their
purpose.
'Worse' at present means we got an error, so use that as the name.
Signed-off-by: Simon Glass
---
tools/buildman/builder.py | 28 ++
There is no advantage to using a u8 for function parameters. It forces
the compiler to mask values and can increase code size. Also the command
enum has been extended to 16 bits. Update the functions to use uint
instead.
Signed-off-by: Simon Glass
---
drivers/misc/cros_ec.c | 10 --
1 f
At present messages from the device-tree compiler like this:
arch/arm/dts/socfpga_arria10_socdk_sdmmc.dtb: Warning
(avoid_unnecessary_addr_size): /clocks: unnecessary
#address-cells/#size-cells without "ranges" or child "reg" property
are detected as errors since they don't match the
This value is required for flashing to work correctly. Add a check for
it.
Signed-off-by: Simon Glass
---
drivers/misc/cros_ec.c | 3 +++
1 file changed, 3 insertions(+)
Applied to u-boot-dm/master, thanks!
___
U-Boot mailing list
U-Boot@lists.denx.d
This is not normally useful, so change the code to avoid writing out every
data package. This can be enabled with #define DEBUG.
Signed-off-by: Simon Glass
---
drivers/tpm/tpm_tis_sandbox.c | 6 ++
1 file changed, 6 insertions(+)
Applied to u-boot-dm/master, thanks!
___
On Sun, 14 Oct 2018 at 14:01, Heinrich Schuchardt wrote:
>
> If we want to control which network interface is actually used, we have to
> issue 'setenv ethrotate no'. If ethrotate is not set any interface may be
> used.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> board/sandbox/README.sandbox
At present --list-tool-chains prints a lot of information about the
toolchain-probing process. This is generally not very interesting.
Update buildman to print this only if --list-tool-chains is given
with -v.
Signed-off-by: Simon Glass
---
tools/buildman/cmdline.py | 2 +-
tools/buildman/contr
At present these features are supported in SPL but not TPL. Update the
Kconfig and Makefile to allow this.
Also add a few Makefile comments to make earier to track what is going on.
Signed-off-by: Simon Glass
---
common/Kconfig | 35 +++
common/Makefile | 10 ++
301 - 400 of 1121 matches
Mail list logo
