Retrieve clock rate through device tree. This mimics the behavior of
arm_global_timer in Linux.
Signed-off-by: Nicolas Heemeryck
Cc: Patrice Chotard
---
Changes for v2:
- Fall back on CONFIG_SYS_HZ_CLOCK if clk_get_by_index returns an
error or no clock driver is provided.
---
This series update the sti-timer for cortex-a9 CPU (arm global timer) to mimic
the behavior presents in Linux.
Therefor, the same device tree node can be use for U-Boot and Linux.
Changes in v2:
Since some boards do not necessary have a clock driver, fall back on
CONFIG_SYS_HZ_CLOCK. This is
Update STI timer to support a live tree
Signed-off-by: Nicolas Heemeryck
Cc: Patrice Chotard
---
Changes for v2: None
---
drivers/timer/sti-timer.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/drivers/timer/sti-timer.c b/drivers/timer/sti-timer.c
index
Hellow,
I have a Galaxy Tab S3 (SM-T825) WiFi and LTE, stuck in a bootloop. I have
tried everything with no luck. Then i saw a video about reviving a dead
Galaxy S3. My question is this. Can i use U-BOOT to revive my tablet and
how??
Thank you in advance
It does not seem to be necessary to run buildman again to show errors,
since any errors can be shown by the first invocation and there is only
a single board being built. Update this to simplify the code, using the
-e flag to make sure errors are shown.
Signed-off-by: Simon Glass
---
Changes in
It seems unnecessary to read the exit code and then check it again. Drop
this and just let the test.py provide the exit code directly.
Signed-off-by: Simon Glass
---
Changes in v2:
- Update travis, azure also
.azure-pipelines.yml | 4
.gitlab-ci.yml | 6 +-
.travis.yml
This is not needed in the test.py part of the config, now since we use the
same name as the pytests.
Drop BUILDMAN, retaining it only for the 'build' parts of the config, i.e.
where we build multiple boards and don't run any tests.
Signed-off-by: Simon Glass
---
Changes in v2:
- Update travis,
It is a pain to have to set the CROSS_COMPILE environment variable when
using test.py's --build option. It is possible to get this using the -A
option from buildman. But it seems better to just use buildman to do the
build when it is available.
However using buildman adds a new dependency to the
Avoid needing to know about the internal .bm-work directory, by passing
the -w flag to buildman.
This does not affect travis since the previous commit already used the -w
flag.
Signed-off-by: Simon Glass
---
Changes in v2:
- Update azure also
.azure-pipelines.yml | 4 ++--
.gitlab-ci.yml
It doesn't seem to make sense to tell buildman to report warning as errors
(thus ensuring there are no warnings) and then ignore the warnings.
The simplist thing is to just drop the -E flag. This allows us to drop the
check for exit code 129.
Dropping -E is not enough to cover all warnings
Ensure that this SPL test runs on gitlab.
Signed-off-by: Simon Glass
---
Changes in v2:
- Update travis, azure also
.azure-pipelines.yml | 2 +-
.gitlab-ci.yml | 2 +-
.travis.yml | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/.azure-pipelines.yml
Since TEST_PY_BD is always defined we can drop this check.
This does not affect travis since it has a single, unified script.
Signed-off-by: Simon Glass
---
Changes in v2:
- Update azure also
.azure-pipelines.yml | 22 +-
.gitlab-ci.yml | 30
Avoid needing to know about the internal .bm-work directory, by passing
the -w flag to buildman.
This is not needed on travis since the -w flag is already used (from a
previous patch).
Drop the -P flag since this has no effect if -w is used.
Signed-off-by: Simon Glass
---
Changes in v2:
-
This has no effect since -S is not given also. Drop it.
Signed-off-by: Simon Glass
---
Changes in v2:
- Update travis, azure also
.azure-pipelines.yml | 4 ++--
.gitlab-ci.yml | 10 +-
.travis.yml | 4 ++--
3 files changed, 9 insertions(+), 9 deletions(-)
diff --git
Bash allows for variables to expand only if non-empty:
$ var=test
$ echo ${var:+"$var"}
test
$ echo ${var:+"-k $var"}
-k test
$ var=
$ echo ${var:+"-k $var"}
Use this feature to avoid the workaround.
Signed-off-by: Simon Glass
---
The current method of selecting the board to build with test.py is a bit
error-prone, e.g. with "^sandbox$" it actually builds 5 boards (all of
those in the sandbox architecture).
Use the (newish) --board flag instead, to get the same result.
Signed-off-by: Simon Glass
---
Changes in v2:
-
At present if TEST_PY_BD is empty the script copies various files into a
directory, to no purpose. This happens because UBOOT_TRAVIS_BUILD_DIR is
set before TEST_PY_BD is tested.
Move the 'if' to fix this.
Signed-off-by: Simon Glass
---
Changes in v2:
- Add a new patch to avoid copying files
Buildman is used in two ways:
- to build a selection of boards (with no testing)
- to build a single board (and run pytest)
The gitlab and azure scrips do this in separate places, but travis does
not. To aid the refactoring process and keep the following patches in sync
across all three
There is no point in setting the ARCH environment variable since the
U-Boot build system no-longer uses it.
It seems safe to drop this feature since it was only recently added.
Signed-off-by: Simon Glass
---
Changes in v2:
- Add a new patch to drop the -a option
tools/buildman/cmdline.py |
It is useful to run a simple build and put all the output in a single
directory. Add a -w option to support this.
Signed-off-by: Simon Glass
---
Changes in v2: None
tools/buildman/README | 11 ++
tools/buildman/builder.py | 15 +++--
At present buildman removes any directory it doesn't intend to write
output into. This is overly expansive since if the output directory
happens to be somewhere with existing files, they may be removed. Using
an existing directory for buildman is not a good practice, but since the
result might be
This is useful in some situations, in particular with -w and when building
in-tree. Now that we are more careful about what we remove in
_PrepareOutputSpace(), it should be safe to relax this restriction.
Update the progress information also so it is clear what buildman is
doing. Remove files can
Sometimes we don't want to get an error with warnings. Add a -W option to
support this. If buildman detects warnings (and no error) it will return
an exit code of 0 (success).
Signed-off-by: Simon Glass
---
Changes in v2: None
tools/buildman/README | 2 +-
tools/buildman/cmdline.py | 2 ++
This help is a bit ambiguous. It only does anything if asked to show size
changes with -S. Update the help and the function comments.
Signed-off-by: Simon Glass
---
Changes in v2:
- Reword the commit message for clarity
tools/buildman/builder.py | 6 +++---
tools/buildman/cmdline.py | 2 +-
2
Quite a few packages are used by sandbox or tools. Add a list of these to
help people setting up for the first time.
Signed-off-by: Simon Glass
---
Changes in v2: None
doc/arch/sandbox.rst | 10 ++
1 file changed, 10 insertions(+)
diff --git a/doc/arch/sandbox.rst
This class has a few more members now. Add documentation for them and fix
a nit in the 'commits' comment.
Signed-off-by: Simon Glass
---
Changes in v2: None
tools/buildman/builderthread.py | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/tools/buildman/builderthread.py
At present there are several things in the gitlab, travis and azure
scripts which work around limitations in buildman. With a few small
feature additions these can be removed.
This series adds some new features to buildman and simplifies the script:
- Option to run a single build in a specified
This is defined in bootstage.h and is not called in this file anyway. Drop
it.
Signed-off-by: Simon Glass
---
Changes in v2: None
common/main.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/common/main.c b/common/main.c
index ec8994ad45..06d7ff56d6 100644
--- a/common/main.c
+++
Introduce a private data structure for this driver with embedded
struct eth_device and pass it around. This prepares the driver to
work with both DM and non-DM systems.
Signed-off-by: Marek Vasut
Cc: Joe Hershberger
Cc: Masahiro Yamada
---
drivers/net/smc911x.c | 234
Add support for U-Boot DM and DT probing. Furthermore, build the
SMC911x standalone EEPROM example only for the non-DM case, as it
is not converted yet.
Signed-off-by: Marek Vasut
Cc: Joe Hershberger
Cc: Masahiro Yamada
---
board/renesas/blanche/blanche.c | 2 +
drivers/net/smc911x.c
Inline all the functions from the header file, as they are not used
outside of the driver or the standalone EEPROM example.
Note that this does introduce considerable amount of duplication in
the standalone EEPROM example, however that one has to be rewritten
anyway, roughly such that the SMC911x
These accessors are not overriden by any board, and even if they were,
this is something which should be handled via DM now, so remove the
weak alias option. Moreover, drop the inline keyword, as the compiler
can decide better.
Signed-off-by: Marek Vasut
Cc: Joe Hershberger
Cc: Masahiro Yamada
Split network handling functions into non-DM specific parts and
common code in preparation for conversion to DM.
Signed-off-by: Marek Vasut
Cc: Joe Hershberger
Cc: Masahiro Yamada
---
drivers/net/smc911x.c | 57 ---
1 file changed, 43 insertions(+), 14
Convert the IO accessors to standard ones instead of using volatile
void pointers, as those do not cover all the bus access details.
Signed-off-by: Marek Vasut
Cc: Joe Hershberger
Cc: Masahiro Yamada
---
drivers/net/smc911x.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
Invest the status handling logic in smc911x_recv(), to make the
function easier to read, no functional change.
Signed-off-by: Marek Vasut
Cc: Joe Hershberger
Cc: Masahiro Yamada
---
drivers/net/smc911x.c | 31 +--
1 file changed, 17 insertions(+), 14 deletions(-)
Fix memleak in the init fail path, where if allocation or registration
of MDIO bus fails, then ethernet interface is not unregistered and the
private data are not freed, yet the probe function reports a failure.
Signed-off-by: Marek Vasut
Cc: Joe Hershberger
Cc: Masahiro Yamada
---
Invert the logic in the aforementioned functions to reduce indent,
no functional change.
Signed-off-by: Marek Vasut
Cc: Joe Hershberger
Cc: Masahiro Yamada
---
drivers/net/smc911x.c | 27 ---
1 file changed, 16 insertions(+), 11 deletions(-)
diff --git
These functions are never used and are likely a pre-DM remnant
from times long past, just remove them.
Signed-off-by: Marek Vasut
Cc: Joe Hershberger
Cc: Masahiro Yamada
---
drivers/net/smc911x.c | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git
Replace combination of malloc()+memset() with calloc() as the behavior
is exactly the same and the amount of code is reduced.
Signed-off-by: Marek Vasut
Cc: Joe Hershberger
Cc: Masahiro Yamada
---
drivers/net/smc911x.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
Rename the function to keep the naming scheme consistent,
no functional change.
Signed-off-by: Marek Vasut
Cc: Joe Hershberger
Cc: Masahiro Yamada
---
drivers/net/smc911x.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/smc911x.c b/drivers/net/smc911x.c
Perform DM conversion of the SMC911x driver. Note that as I do not have
any hardware with this chip, I only compile-tested this conversion. But
it seems Yamada-san has one, so please test.
Note that the DT compatible is set only for 9115 , so this might need
to be changed.
Note that this is
Hi Tom,
On Sun, 15 Mar 2020 at 10:18, Tom Rini wrote:
>
> On Sun, Mar 15, 2020 at 09:50:30AM -0600, Simon Glass wrote:
> > Hi Tom,
> >
> > On Sun, 15 Mar 2020 at 09:23, Tom Rini wrote:
> > >
> > > On Sun, Mar 15, 2020 at 09:07:54AM -0600, Simon Glass wrote:
> > > > Hi Tom,
> > > >
> > > > On
On 15.03.20 16:25, Peter Robinson wrote:
On Wed, Feb 26, 2020 at 7:54 PM Wolfram Joost wrote:
This patch adds the four clock gates
- ACLK_VOP0
- ACLK_VOP1
- HCLK_VOP0
- HCLK_VOP1
to the rockchip rk3399 clock drivers.
These clock gates were referenced by arch/arm/dts/rk3399.dtsi for
vopb
On Sun, Mar 15, 2020 at 09:50:30AM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Sun, 15 Mar 2020 at 09:23, Tom Rini wrote:
> >
> > On Sun, Mar 15, 2020 at 09:07:54AM -0600, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Sun, 15 Mar 2020 at 07:03, Tom Rini wrote:
> > > >
> > > > On Sat, Mar 14,
Hi Heinrich,
On Sun, 15 Mar 2020 at 02:16, Heinrich Schuchardt wrote:
>
> On 3/14/20 9:35 PM, Simon Glass wrote:
> > On Sat, 14 Mar 2020 at 05:27, Heinrich Schuchardt
> > wrote:
> >>
> >> 'bootefi hello' is used in one of the Python tests.
> >>
> >> efidebug can be used to verify the correct
Hi Tom,
On Sun, 15 Mar 2020 at 09:23, Tom Rini wrote:
>
> On Sun, Mar 15, 2020 at 09:07:54AM -0600, Simon Glass wrote:
> > Hi Tom,
> >
> > On Sun, 15 Mar 2020 at 07:03, Tom Rini wrote:
> > >
> > > On Sat, Mar 14, 2020 at 09:10:07PM -0600, Simon Glass wrote:
> > > > Hi Tom,
> > > >
> > > > On
On Wed, Feb 26, 2020 at 7:54 PM Wolfram Joost wrote:
>
> This patch adds the four clock gates
>
> - ACLK_VOP0
> - ACLK_VOP1
> - HCLK_VOP0
> - HCLK_VOP1
>
> to the rockchip rk3399 clock drivers.
>
> These clock gates were referenced by arch/arm/dts/rk3399.dtsi for
> vopb and vopl.
>
> The driver
On Sun, Mar 15, 2020 at 09:07:54AM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Sun, 15 Mar 2020 at 07:03, Tom Rini wrote:
> >
> > On Sat, Mar 14, 2020 at 09:10:07PM -0600, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Mon, 9 Mar 2020 at 11:58, Tom Rini wrote:
> > > >
> > > > On Fri, Mar 06,
On Sun, Mar 15, 2020 at 09:07:48AM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Sun, 15 Mar 2020 at 07:02, Tom Rini wrote:
> >
> > On Sat, Mar 14, 2020 at 09:10:09PM -0600, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Mon, 9 Mar 2020 at 11:55, Tom Rini wrote:
> > > >
> > > > On Fri, Mar 06,
Hi Tom,
On Sun, 15 Mar 2020 at 07:03, Tom Rini wrote:
>
> On Sat, Mar 14, 2020 at 09:10:07PM -0600, Simon Glass wrote:
> > Hi Tom,
> >
> > On Mon, 9 Mar 2020 at 11:58, Tom Rini wrote:
> > >
> > > On Fri, Mar 06, 2020 at 08:07:26PM -0700, Simon Glass wrote:
> > > > Avoid needing to know about
Hi Tom,
On Sun, 15 Mar 2020 at 07:02, Tom Rini wrote:
>
> On Sat, Mar 14, 2020 at 09:10:09PM -0600, Simon Glass wrote:
> > Hi Tom,
> >
> > On Mon, 9 Mar 2020 at 11:55, Tom Rini wrote:
> > >
> > > On Fri, Mar 06, 2020 at 08:07:14PM -0700, Simon Glass wrote:
> > >
> > > > At present there are
On Sun, Mar 15, 2020 at 08:56:14PM +0900, Masahiro Yamada wrote:
> On Thu, Mar 12, 2020 at 7:12 AM Tom Rini wrote:
> >
> > In a few boards we had overridden, intentionally, the value used for
> > CONFIG_SPL_LDSCRIPT. However, rather than using the ARCH value (arm)
> > they used the $(ARCH)
On Sat, Mar 14, 2020 at 09:10:07PM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Mon, 9 Mar 2020 at 11:58, Tom Rini wrote:
> >
> > On Fri, Mar 06, 2020 at 08:07:26PM -0700, Simon Glass wrote:
> > > Avoid needing to know about the internal .bm-work directory, by passing
> > > the -w flag to
On Sat, Mar 14, 2020 at 09:10:09PM -0600, Simon Glass wrote:
> Hi Tom,
>
> On Mon, 9 Mar 2020 at 11:55, Tom Rini wrote:
> >
> > On Fri, Mar 06, 2020 at 08:07:14PM -0700, Simon Glass wrote:
> >
> > > At present there are several things in the gitlab script which work around
> > > limitations in
From: Atish Patra
Currently, bootefi only parses memory reservation block to setup
EFI reserved memory mappings. However, it doesn't parse the
reserved-memory[1] device tree node that also can contain the
reserved memory regions.
Add capability to parse reserved-memory node and update the EFI
On Thu, Mar 12, 2020 at 7:12 AM Tom Rini wrote:
>
> In a few boards we had overridden, intentionally, the value used for
> CONFIG_SPL_LDSCRIPT. However, rather than using the ARCH value (arm)
> they used the $(ARCH) variable in make. This doesn't help really, so
> switch to a hard-coded value.
On Thu, Mar 12, 2020 at 7:12 AM Tom Rini wrote:
>
> As there is only one machine under mach-orion5x, having a Kconfig entry
> for SPL_LDSCRIPT is not helpful, move this to the defconfig file.
>
> Suggested-by: Masahiro Yamada
> Signed-off-by: Tom Rini
> ---
Reviewed-by: Masahiro Yamada
>
On Thu, Mar 12, 2020 at 7:12 AM Tom Rini wrote:
>
> As there is only one linker script to use in this case, rather than use
> the BOARDDIR variable hard-code the path.
>
> Cc: Lokesh Vutla
> Suggested-by: Masahiro Yamada
> Signed-off-by: Tom Rini
> ---
Reviewed-by: Masahiro Yamada
>
On 3/14/20 9:35 PM, Simon Glass wrote:
On Sat, 14 Mar 2020 at 05:27, Heinrich Schuchardt wrote:
'bootefi hello' is used in one of the Python tests.
efidebug can be used to verify the correct initialization of the UEFI
sub-system.
Signed-off-by: Heinrich Schuchardt
---
59 matches
Mail list logo