Hi
On Monday 23 October 2017 01:28 PM, Faiz Abbas wrote:
> The dra7xx series of SOCs contain a temperature sensor and an
> associated analog-to-digital converter (ADC) which produces
> an output which is proportional to the SOC temperature.
> Add support for this temperature sensor.
>
>
On Mon, Nov 13, 2017 at 06:26 AM, Baruch Siach wrote:
>On Sun, Nov 12, 2017 at 08:42:28PM +0100, Heinrich Schuchardt wrote:
>> On 11/12/2017 04:30 PM, Baruch Siach wrote:
>> > Calling .set_speed with zero speed is definitely a bug. Instead of
>> > crashing, set hz to 1 so that we get the lowest
Restructures common driver to support LTC3882 voltage regulator
chip.
Signed-off-by: Ashish Kumar
Signed-off-by: Rajesh Bhagat
---
Changes in v5:
None
Changes in v4:
None
Changes in v3:
Restructured LS1088A VID support to use common VID driver
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
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 v5:
None
Changes in v4:
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 v5:
None
Changes in v4:
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 v5:
None
Changes
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 v5:
None
Changes in v4:
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 v5:
Adds LTC3882 voltage regulator chip support in common VID driver.
And adds VID support for LS1088A QDS and RDB platforms.
Rajesh Bhagat (7):
armv8: lsch3: Add serdes and DDR voltage setup
board: common:vid: Add LS1088A VID Supported voltage values
board: common: vid: Add board specific vdd
All current ClearFog SOMs have the SPI flash populated. Enable SPI flash in
the device tree.
Add an alias to the SPI bus so that the 'sf' command can probe the flash on
bus 1.
Add the "spi-flash" compatible string to make the standard SPI flash driver
probe the device.
Reviewed-by: Jagan Teki
From: Jon Nettleton
The production variant of the SPI flash used by the clearfog
devices are based on winbond chips. Additionally enable
SPI_FLASH_BAR since some variants will have 16MB of flash
that requires this to be enabled.
Remove the default speed and mode; these
Binman has 100% test coverage for the code as it is at present. To
encourage it to stay that way, run the code-coverage test as part of the
normal U-Boot tests.
This is RFC because it requires the Python code coverage tools to be
available.
Signed-off-by: Simon Glass
---
There is a little check at the top of entry.py which decides if importlib
is available. At present this has no test coverage. To add this we will
need to import the module twice, once with importlib and once without.
In preparation for allowing a test to control the importing of this
module,
Return exit code 1 when test fail so that callers can detect this.
Signed-off-by: Simon Glass
---
tools/binman/binman.py | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/tools/binman/binman.py b/tools/binman/binman.py
index 7ad4d3030b9..3ccf25f1f88
MRC (Memory Reference Code) is a binary blob used to set up the SDRAM
controller on some Intel boards. Add a test for this feature.
With this test coverage on binman is back up to 100%.
Signed-off-by: Simon Glass
---
tools/binman/ftest.py | 7 +++
Add a main program so that the tests can be executed directly, without
going through the main binman program.
Signed-off-by: Simon Glass
---
tools/binman/entry_test.py | 4
tools/binman/ftest.py | 4
2 files changed, 8 insertions(+)
diff --git
At present these tests use the same filename as patman. This adds
confusion when running all tests, since error messages look very similar.
In fact binman tries to run the wrong tests at present.
Rename the tests.
Signed-off-by: Simon Glass
---
tools/binman/binman.py
The tests were broken by two separate commits which adjusted the output
when boards are listed. Fix this by adding back a PowerPC board and
putting the name of each board in the test.
Fixes: b9f7d881 (powerpc, 5xx: remove some "5xx" remains)
Fixes: 8d7523c5 (buildman: Allow showing the list of
This allows us to put the 16-bit x86 start-up code in SPL. Add a test for
it.
Signed-off-by: Simon Glass
---
tools/binman/ftest.py| 10 +-
tools/binman/test/48_x86-start16-spl.dts | 13 +
2 files changed, 22 insertions(+), 1
Make a minor tweak to fix test coverage.
Signed-off-by: Simon Glass
---
tools/binman/etype/u_boot_ucode.py | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/tools/binman/etype/u_boot_ucode.py
b/tools/binman/etype/u_boot_ucode.py
index
This script runs the tests but does not report failure. Also it always
returns an exit code of 0 even on failure.
Fix these problems by checking the result of each test.
Signed-off-by: Simon Glass
---
test/run | 20 +---
1 file changed, 17 insertions(+), 3
Add a test that we can pad the BSS with zero bytes.
Signed-off-by: Simon Glass
---
tools/binman/ftest.py| 9 +
tools/binman/test/47_spl_bss_pad.dts | 17 +
tools/binman/test/Makefile | 5 -
tools/binman/test/bss_data
Rather that overwrite this, append to it, in case the caller has already
set up the path correctly.
Signed-off-by: Simon Glass
---
tools/binman/binman.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/binman/binman.py b/tools/binman/binman.py
index
These warnings are not useful for binman tests. Disable them.
Signed-off-by: Simon Glass
---
tools/dtoc/fdt_util.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/dtoc/fdt_util.py b/tools/dtoc/fdt_util.py
index 338d47a5e14..ba0b6cc3815 100644
---
Add a test for this feature. It allows SPL to hold a pointer to the
microcode block. This is used for 64-bit U-Boot on x86.
Signed-off-by: Simon Glass
---
tools/binman/etype/u_boot_spl_with_ucode_ptr.py | 2 +-
tools/binman/ftest.py | 84
Add a test that the 'entry' module works with or without importlib.
The tests are numbered so that they are executed in the correct order.
Signed-off-by: Simon Glass
---
tools/binman/binman.py | 8 ++--
tools/binman/entry_test.py | 30 ++
Update the test script to run the dtoc tests also.
Signed-off-by: Simon Glass
---
test/run | 1 +
1 file changed, 1 insertion(+)
diff --git a/test/run b/test/run
index f695f2ecc5d..d40a5cdc807 100755
--- a/test/run
+++ b/test/run
@@ -19,6 +19,7 @@ run_test ./test/py/test.py
Accessing the network slows down the test and limits the environment in
which it can be run. Add an option to disable network tests.
Signed-off-by: Simon Glass
---
tools/buildman/buildman.py | 6 --
tools/buildman/cmdline.py | 2 ++
tools/buildman/test.py | 7
Files that are never imported are not shown in the test-coverage report.
Detect these and show an error.
Signed-off-by: Simon Glass
---
tools/binman/binman.py | 22 +++---
1 file changed, 19 insertions(+), 3 deletions(-)
diff --git a/tools/binman/binman.py
The tool has changed slightly since it was originally written. Update the
tests to suit.
Signed-off-by: Simon Glass
---
tools/dtoc/test_dtoc.py | 82 ++---
1 file changed, 37 insertions(+), 45 deletions(-)
diff --git
These test programs are includedd as binary files in U-Boot to avoid
having to build them (and associated toolchain differences). Instructions
on building are in the files themselves, but it seems better to provide
a Makefile which can be manually run when desired.
Add a Makefile, separate from
Update the test script to run the buildman tests also.
Signed-off-by: Simon Glass
---
test/run | 1 +
1 file changed, 1 insertion(+)
diff --git a/test/run b/test/run
index f18e36e05e2..f695f2ecc5d 100755
--- a/test/run
+++ b/test/run
@@ -18,6 +18,7 @@ run_test
Update the test script to run the binman tests also.
Signed-off-by: Simon Glass
---
test/run | 2 ++
1 file changed, 2 insertions(+)
diff --git a/test/run b/test/run
index caee4f83f2c..b9ed3edb3e4 100755
--- a/test/run
+++ b/test/run
@@ -16,6 +16,8 @@ run_test
Update the test script to run the patman tests also.
Signed-off-by: Simon Glass
---
test/run | 1 +
1 file changed, 1 insertion(+)
diff --git a/test/run b/test/run
index b9ed3edb3e4..f18e36e05e2 100755
--- a/test/run
+++ b/test/run
@@ -17,6 +17,7 @@ run_test
The checkpatch tool was updated but the patman tests were not. Fix this.
Signed-off-by: Simon Glass
---
tools/patman/test.py | 41 ++---
1 file changed, 26 insertions(+), 15 deletions(-)
diff --git a/tools/patman/test.py
The process is not obvious. Add a little section to explain how to move a
board to use binman.
Signed-off-by: Simon Glass
---
tools/binman/README | 21 +
1 file changed, 21 insertions(+)
diff --git a/tools/binman/README b/tools/binman/README
index
There is a debugging option in the Makefile to allow people to figure out
which u-boot.dtsi files are used in the build. But is it not easy to use
since it only shows files it finds, not those it is looking for. Update it
and update the mention of it to the docs.
Signed-off-by: Simon Glass
At present there are a number of tools in U-Boot which have tests which
are not widely used:
patman - prepare, check and send patches
buildman - multi-threaded multi-commit builder
dtoc - convert device tree file to C
binman - produce firmware images
In fact many tests are broken
On Jum, 2017-11-10 at 11:04 +0100, Marek Vasut wrote:
> On 11/10/2017 10:05 AM, Chee, Tien Fong wrote:
> >
> > On Kha, 2017-11-09 at 11:31 +0100, Marek Vasut wrote:
> > >
> > > On 11/09/2017 11:00 AM, Lukasz Majewski wrote:
> > > >
> > > >
> > > > On Thu, 9 Nov 2017 08:05:18 +0100
> > > >
Hi Anton,
On Sat, Nov 11, 2017 at 1:34 AM, Anton Gerasimov
wrote:
> Hooray, changing SYS_CAR_ADDR to 0x1 in arch/x86/cpu/qemu/Kconfig
> does the trick. Bin, what do you think about it?
>
Great! Would you please create a patch against U-Boot QEMU?
> Best
Hi,
2017-11-03 22:30 GMT+09:00 Chris Brandt :
> First, this table could never be included in the build anyway because
> SH_ETH_TYPE_RZ is not defined until later in the file.
> Second, the register PIR was missing, so PHY MDIO never worked.
> Third, after adding the PIR
Hi,
2017-11-03 22:30 GMT+09:00 Chris Brandt :
> Since the return value is a signed int, if the leading MSB of rdreg is a 1,
> it will get signed extended and will return a negative value which is an
> error even though we read the correct value.
>
> Fixes: dfcc496ed7e2
Hi,
2017-11-03 22:30 GMT+09:00 Chris Brandt :
> The macros inl and outl maybe already be defined from file
> arch/arm/include/asm/io.h so there may be no reason to define them.
> And if you do try defined them here, you get a redefined complier warning.
>
>
Hi,
I am sorry that my comment was delayed.
2017-11-01 11:09 GMT+09:00 Tom Rini :
> On Tue, Oct 31, 2017 at 03:26:02PM +, Chris Brandt wrote:
>> Hi Tom,
>>
>> Thanks for the reply!
>>
>> On Tuesday, October 31, 2017 1, Tom Rini wrote:
>> > On Tue, Oct 31, 2017 at
Hi,
2017-11-11 7:20 GMT+09:00 Marek Vasut :
> Fix handling of the reset GPIO. Drop the _nodev() suffix from the
> gpio_request_by_name() call as there is now a proper DM capable
> GPIO driver. Also check if the GPIO is valid before freeing it in
> remove path, otherwise
Hi,
2017-11-11 7:19 GMT+09:00 Marek Vasut :
> Add xHCI entry into the clock tables, so that the xHCI USB driver
> can enable the clock for the xHCI block via clock framework.
>
> Signed-off-by: Marek Vasut
> Cc: Nobuhiro Iwamatsu
On Sat, Nov 04, 2017 at 04:14:09PM +0100, Soeren Moch wrote:
> This reverts commit c61d0009feb966e0e93254a8c435a1889085e6b8.
>
> A tbs2910 board user reported a very slow console frambuffer as
> regression in current u-boot. I could bisect this down to the
> above mentioned commit.
>
> This
On Thu, Nov 02, 2017 at 08:54:59PM +0100, Angelo Dureghello wrote:
> Signed-off-by: Angelo Dureghello
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Description: PGP signature
___
U-Boot mailing list
U-Boot@lists.denx.de
On Thu, Nov 09, 2017 at 07:58:40PM +0100, Marek Vasut wrote:
> The eMMC is 1V8 device only and the signaling is always 1V8,
> fix the DT for Salvator-X/XS to describe the hardware correctly.
>
> Signed-off-by: Marek Vasut
> Cc: Nobuhiro Iwamatsu
On 11/12/2017 09:02 PM, Jeroen Hofstee wrote:
Hello Heinrich,
On 11/10/2017 09:46 PM, Heinrich Schuchardt wrote:
0 is not a pointer. So do not compare pointers to 0.
Do not return 0 from functions with a pointer return
type.
Problem identified with Coccinelle.
Perhaps you can elaborate on
fix typo
Signed-off-by: Heinrich Schuchardt
---
drivers/spi/omap3_spi.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/spi/omap3_spi.c b/drivers/spi/omap3_spi.c
index ebbdcaf14a..1da4542af0 100644
--- a/drivers/spi/omap3_spi.c
+++
Hello Heinrich,
On 11/10/2017 09:46 PM, Heinrich Schuchardt wrote:
0 is not a pointer. So do not compare pointers to 0.
Do not return 0 from functions with a pointer return
type.
Problem identified with Coccinelle.
Perhaps you can elaborate on what problem you are solving? As far as I
know
fix typo
Signed-off-by: Heinrich Schuchardt
---
drivers/spi/rk_spi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/spi/rk_spi.c b/drivers/spi/rk_spi.c
index b18db74e7e..03d3fa6763 100644
--- a/drivers/spi/rk_spi.c
+++ b/drivers/spi/rk_spi.c
@@
On 11/12/2017 04:30 PM, Baruch Siach wrote:
Calling .set_speed with zero speed is definitely a bug. Instead of crashing,
set hz to 1 so that we get the lowest possible frequency rate.
Did this actually occur? Why?
Signed-off-by: Baruch Siach
---
v2: Don't fail; set
Calling .set_speed with zero speed is definitely a bug. Instead of crashing,
set hz to 1 so that we get the lowest possible frequency rate.
Signed-off-by: Baruch Siach
---
v2: Don't fail; set lowest rate (Jagan)
---
drivers/spi/kirkwood_spi.c | 3 +++
1 file changed, 3
Hello Konstantin, hello Stefan,
in which git repository do you consolidate the MVEBU_ARMADA_8K and
MACCHIATOBin work?
I could not find this information in
board/Marvell/mvebu_armada-8k/MAINTAINERS
It would be helpful if you could add a line like:
T: git://github.com/foo/u-boot.git
Use efi_add_protocol to add protocol.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
lib/efi_loader/efi_gop.c | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/lib/efi_loader/efi_gop.c b/lib/efi_loader/efi_gop.c
index
We need to implement to different functions for the
EFI_DEVICE_PATH_TO_TEXT_PROTOCOL:
ConvertDeviceNodeToText
ConvertDevicePathToText
A recent patch screwed up efi_convert_device_node_to_text
to expect a device path and not a node.
The patch makes both service functions work again.
efi_dp_str is meant to print a device path and not a device
node.
The old coding only worked because efi_convert_device_node_to_text
was screwed up to expect paths instead of nodes.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
Assignments should not be made in the middle of nowhere.
Signed-off-by: Heinrich Schuchardt
---
v2
Call efi_dp_str in debug mode only.
---
lib/efi_loader/efi_bootmgr.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
To avoid duplicate coding provide a helper function that
initializes an EFI object and adds it to the EFI object
list.
efi_exit() is the only place where we dereference a handle
to obtain a protocol interface. Add a comment to the function.
Suggested-by: Alexander Graf
Use function efi_search_protocol.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
lib/efi_loader/efi_boottime.c | 36 ++--
1 file changed, 6 insertions(+), 30 deletions(-)
diff --git a/lib/efi_loader/efi_boottime.c
The handle of a loaded image is the value of the handle
member of the loaded image info object and not the
address of the loaded image info.
Signed-off-by: Heinrich Schuchardt
---
v2
new patch
---
cmd/bootefi.c | 7 ---
Use efi_add_protocol to add protocols.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
lib/efi_loader/efi_net.c | 34 --
1 file changed, 20 insertions(+), 14 deletions(-)
diff --git a/lib/efi_loader/efi_net.c
Provide a test for the EFI_DEVICE_PATH_TO_TEXT_PROTOCOL protocol.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
lib/efi_selftest/Makefile | 3 +
lib/efi_selftest/efi_selftest_devicepath.c | 340 +
2 files
Up to now the protocols of an EFI handle where contained in an
array of fixed size. With the patch series the protocols are
managed in a linked list. This both saves memory and gives
more flexibility.
The LocateDevicePath boot service is implemented according
to the UEFI specification.
A unit
Check that helloworld.efi returns EFI_SUCCESS.
Signed-off-by: Heinrich Schuchardt
---
v2
new patch
---
test/py/tests/test_efi_loader.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/test/py/tests/test_efi_loader.py b/test/py/tests/test_efi_loader.py
index
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
include/efi_loader.h | 6 ++-
lib/efi_loader/efi_boottime.c | 107 --
lib/efi_loader/efi_disk.c | 1 +
lib/efi_loader/efi_gop.c | 1 +
We need to test if we pass a valid image handle when loading
and EFI application. This cannot be done in efi_selftest as
it is not loaded as an image.
So let's enhance helloworld to write the load options to the
console.
Signed-off-by: Heinrich Schuchardt
---
v2
new
Add a missing line feed for an error message.
Signed-off-by: Heinrich Schuchardt
---
v2
new patch
---
lib/efi_selftest/efi_selftest.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/efi_selftest/efi_selftest.c b/lib/efi_selftest/efi_selftest.c
Use function efi_search_protocol.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
lib/efi_loader/efi_device_path.c | 43 ++--
1 file changed, 19 insertions(+), 24 deletions(-)
diff --git a/lib/efi_loader/efi_device_path.c
Use efi_add_protocol to install protocols.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
lib/efi_loader/efi_disk.c | 39 +++
1 file changed, 23 insertions(+), 16 deletions(-)
diff --git a/lib/efi_loader/efi_disk.c
As the selftest is not compiled as an EFI binary we do not
need special compiler flags.
This avoids the checkarmreloc error on vexpress_ca15_tc2.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
lib/efi_selftest/Makefile | 25 -
1 file
In the format specifier we want to specify the maximum width
in case an ending \0 is missing.
So slen must be used as precision and not as field width.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
lib/efi_loader/efi_device_path_to_text.c | 2 +-
1 file
The current implementation of efi_locate_device_path does not match
the UEFI specification. It completely ignores the protocol
parameters.
Signed-off-by: Heinrich Schuchardt
---
v2
no change
---
lib/efi_loader/efi_boottime.c | 106
SATA image from here:
http://wiki.espressobin.net/tiki-index.php?page=Boot+ESPRESSObin+from+SATA+drive
doesn't even print "TIM-1.0" for me
12.11.2017 13:36, Matwey V. Kornilov пишет:
> Hello,
>
> I am trying to follow this thread:
>
Hello,
I am trying to follow this thread:
https://www.mail-archive.com/u-boot@lists.denx.de/msg257116.html to boot
espressobin from SATA device.
Currently, the only thing what I see when try to boot is the following:
TIM-1.0
After some time, I see > from UART bootloader.
How could I figure
78 matches
Mail list logo