+Bharat Gooty
On Tue, Oct 5, 2021 at 9:50 AM Roman Bacik wrote:
>
> Add request tests to dm_test_pinctrl_single with corresponding node in
> test.dts
>
> Signed-off-by: Roman Bacik
>
> ---
>
> Changes in v3:
> - Add request API test to dm_test_pinctrl_single
>
> arch/sandbox/dts/test.dts | 17
When a test hands on a real board there is no way on the console to obtain
any information about why it hung.
With sandbox we can actually find out that it died and get a signal or
exit code. Add this to make it easier to figure out what happened.
So instead of:
test/py/u_boot_spawn.py:171: in
This produces a lot of code output which is not very helpful and is quite
annoying to wade through. Use the short format by default.
Signed-off-by: Simon Glass
---
doc/develop/py_testing.rst | 7 +++
test/py/test.py| 5 +
2 files changed, 12 insertions(+)
diff --git
On Sun, 12 Sep 2021 09:47:25 -0500
Samuel Holland wrote:
> Add a driver so the clocks/resets for these peripherals (especially I2C,
> RSB, and UART) can be enabled using the normal uclass methods.
>
Compared against the respective Linux bits.
> Signed-off-by: Samuel Holland
Reviewed-by:
On Sun, 12 Sep 2021 09:47:24 -0500
Samuel Holland wrote:
> Currently, the I2C clocks are configured in the sunxi board code. Add
> the I2C clocks to the DM clock driver so they can be enabled from the
> DM I2C driver using the normal uclass methods.
>
> Signed-off-by: Samuel Holland
Compared
On Sun, Sep 19, 2021 at 03:14:51PM -0600, Simon Glass wrote:
> Add documentation for this so people can try it out. At present it does
> not fully work.
>
> Signed-off-by: Simon Glass
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Description: PGP signature
On Sun, Sep 19, 2021 at 03:14:50PM -0600, Simon Glass wrote:
> These tests currently run in a particular sequence, with some of them
> depending on the actions of earlier tests.
>
> Add a check for sandbox and reset to a known state at the start of each
> test, so that all tests can run in
On Sun, Sep 19, 2021 at 03:14:49PM -0600, Simon Glass wrote:
> The -z tests don't really need to be part of the main set. Separate them
> out so we can drop the test setup/cleans functions and thus run all tests
> in parallel.
>
> Signed-off-by: Simon Glass
Applied to u-boot/master, thanks!
On Sun, Sep 19, 2021 at 03:14:48PM -0600, Simon Glass wrote:
> Update the tests to use separate working directories, so we can run them
> in parallel. It also makes it possible to see the individual output files
> after the tests have completed.
>
> Signed-off-by: Simon Glass
Applied to
On Wed, Sep 15, 2021 at 02:33:01PM -0500, Alexandru Gagniuc wrote:
> Target code and mkimage share the same hashing infrastructure. If one
> is wrong, it's very likely that both are wrong in the same way. Thus
> testing won't catch hash regressions. This already happened in
> commit 92055e138f28
On Tue, Aug 24, 2021 at 03:46:32PM +0530, Bharat Kumar Reddy Gooty wrote:
> From: Bharat Gooty
>
> Add pinctrl_ops->request api to configure pctrl
> pad register in gpio mode.
>
> Signed-off-by: Rayagonda Kokatanur
> Signed-off-by: Bharat Gooty
> Acked-by: Rayagonda Kokatanur
> Reviewed-by:
On Tue, Aug 24, 2021 at 03:46:31PM +0530, Bharat Kumar Reddy Gooty wrote:
> From: Bharat Gooty
>
> Parse different gpio properties from dt as part of probe
> function. This detail is required to enable pinctrl pad
> later when gpio lines are requested.
>
> Signed-off-by: Rayagonda Kokatanur
>
On Mon, Sep 20, 2021 at 06:27:20PM +0200, Patrick Delaunay wrote:
> Use dev_ function to support a live tree.
>
> Signed-off-by: Patrick Delaunay
> Reviewed-by: Simon Glass
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Description: PGP signature
On Mon, Sep 20, 2021 at 05:58:33PM +0200, Patrick Delaunay wrote:
> Use dev_ function to read the sides and colour to support a live tree.
>
> Signed-off-by: Patrick Delaunay
> Reviewed-by: Simon Glass
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Description: PGP signature
On Sat, Sep 11, 2021 at 05:05:53PM -0500, Samuel Holland wrote:
> The generic GPIO flags binding is shared across many drivers, some of
> which need their own xlate function. Factor out the flag translation
> code from gpio_xlate_offs_flags so it does not need to be duplicated.
>
>
On Mon, Sep 20, 2021 at 05:56:06PM +0200, Patrick Delaunay wrote:
> Use dev_ function to read the name and boolean to support a live tree.
>
> Signed-off-by: Patrick Delaunay
> Reviewed-by: Simon Glass
Applied to u-boot/master, thanks!
--
Tom
signature.asc
Description: PGP signature
On Sat, Sep 11, 2021 at 05:05:52PM -0500, Samuel Holland wrote:
> Translation of an OF GPIO specifier should fail if the pin offset is
> larger than the number of pins in the GPIO bank.
>
> Signed-off-by: Samuel Holland
> Reviewed-by: Simon Glass
Applied to u-boot/master, thanks!
--
Tom
On Sat, Sep 11, 2021 at 05:05:52PM -0500, Samuel Holland wrote:
> Translation of an OF GPIO specifier should fail if the pin offset is
> larger than the number of pins in the GPIO bank.
>
> Signed-off-by: Samuel Holland
> Reviewed-by: Simon Glass
Applied to u-boot/master, thanks!
--
Tom
On Tue, Sep 07, 2021 at 12:07:09PM -0500, Alexandru Gagniuc wrote:
> This config is only used by three boards with this SOC. Most other
> platforms derive this information from devicetree, and are unlikely
> to ever need this config.
>
> Moreover, it is confusing when Kconfig asks for this value
On Sat, Sep 11, 2021 at 05:05:51PM -0500, Samuel Holland wrote:
> Translation of a pin name to a device+offset should fail if the offset
> is larger than the number of pins in the GPIO bank.
>
> Signed-off-by: Samuel Holland
> Reviewed-by: Simon Glass
Applied to u-boot/master, thanks!
--
On Tue, Sep 07, 2021 at 12:07:08PM -0500, Alexandru Gagniuc wrote:
> This value is not used by u-boot, and it should not. The load address
> of an OPTEE image is defined by said image. Either a uImage or a FIT
> will have a defined load address and entry point. Those values are the
> correct
On Tue, Sep 07, 2021 at 12:07:07PM -0500, Alexandru Gagniuc wrote:
> It is no longer used in u-boot. Information about the TZDRAM location
> is usually available in the devicetree as "/reserved-memory/" nodes.
> Because this isn't used, remove it.
>
> Signed-off-by: Alexandru Gagniuc
Applied
On Tue, Sep 07, 2021 at 12:07:06PM -0500, Alexandru Gagniuc wrote:
> The configs TZDRAM_BASE and TZDRAM_SIZE are expected to describe the
> memory allocated to the OPTEE region. according to according to commit
> c5a6e8bd00cc ("optee: Add optee_verify_bootm_image()"). The TZDRAM is
> with some
On Thu, Sep 02, 2021 at 11:56:17AM +0200, Patrick Delaunay wrote:
> Add stub for tee_find_device function when CONFIG_TEE is not activated
> to simplify the caller code.
>
> This patch allows to remove the CONFIG_IS_ENABLED(OPTEE) tests
> for stm32 platform.
>
> Signed-off-by: Patrick Delaunay
On Thu, Sep 02, 2021 at 11:56:16AM +0200, Patrick Delaunay wrote:
> The configuration CONFIG_OPTEE is defined 2 times:
> 1- in lib/optee/Kconfig for support of OPTEE images loaded by bootm command
> 2- in drivers/tee/optee/Kconfig for support of OP-TEE driver.
>
> It is abnormal to have the same
On Sunday 26 September 2021 00:54:42 Marek Behún wrote:
> @@ -355,20 +369,55 @@ static int pcie_advk_read_config(const struct udevice
> *bus, pci_dev_t bdf,
>enum pci_size_t size)
> {
> struct pcie_advk *pcie = dev_get_priv(bus);
> + int busno =
On 9/25/21 8:43 PM, Simon Glass wrote:
We can use the new host_build() function for this, so drop it.
s/host_build/tools_build/
Signed-off-by: Simon Glass
Reviewed-by: Alexandru Gagniuc
---
(no changes since v1)
common/image-fit.c | 2 +-
include/image.h| 3 ---
2 files
On 9/25/21 8:43 PM, Simon Glass wrote:
This is not needed with Kconfig, since we can use IS_ENABLED() easily
enough. Drop it.
Signed-off-by: Simon Glass
Reviewed-by: Alexandru Gagniuc
---
(no changes since v1)
common/image-fdt.c | 2 +-
include/image.h| 6 --
2 files
On 9/25/21 8:43 PM, Simon Glass wrote:
This is not needed with Kconfig, since we can use IS_ENABLED() easily
enough. Drop it.
Signed-off-by: Simon Glass
Reviewed-by: Alexandru Gagniuc
---
(no changes since v1)
common/image-fdt.c | 4 ++--
include/image.h| 6 --
2 files
On 9/25/21 8:43 PM, Simon Glass wrote:
This is not needed with Kconfig, since we can use IS_ENABLED() easily
enough and the board code is now in a separate file. Update the only place
where this is used and drop it.
Signed-off-by: Simon Glass
Reviewed-by: Alexandru Gagniuc
---
Changes
On 9/25/21 8:43 PM, Simon Glass wrote:
Add a host Kconfig for CRC32. With this we can use CONFIG_IS_ENABLED(CRC32)
directly in the host build, so drop the unnecessary indirection.
Add a few more conditions to SPL_CRC32 to avoid build failures as well as
TPL_CRC32. Also update hash.c to make
On 9/25/21 8:43 PM, Simon Glass wrote:
Add a host Kconfig for FIT_RSASSA_PSS. With this we can use
CONFIG_IS_ENABLED(FIT_RSASSA_PSS) directly in the host build, so drop the
forcing of this in the image.h header.
Drop the #ifdef around padding_pss_verify() too since it is not needed.
Use the
On 9/25/21 8:43 PM, Simon Glass wrote:
Add a host Kconfig for FIT_VERBOSE. With this we can use
CONFIG_IS_ENABLED(FIT_VERBOSE) directly in the host build, so drop the
s/host build/ tools build/
forcing of this in the image.h header.
Signed-off-by: Simon Glass
Reviewed-by: Alexandru
On 9/25/21 8:43 PM, Simon Glass wrote:
Add a host Kconfig for OF_LIBFDT. With this we can use
CONFIG_IS_ENABLED(OF_LIBFDT) directly in the host build, so drop the
s/host build/tools build/
unnecessary indirection.
Signed-off-by: Simon Glass
Reviewed-by: Alexandru Gagniuc
---
On 9/25/21 8:43 PM, Simon Glass wrote:
Make use of the host Kconfig for FIT. With this we can use
CONFIG_IS_ENABLED(FIT) directly in the host build, so drop the unnecessary
indirection.
Signed-off-by: Simon Glass
Reviewed-by: Alexandru Gagniuc
---
Changes in v5:
- Rebase to next
On 9/25/21 8:43 PM, Simon Glass wrote:
We can use the __maybe_unused attribute to avoid some of the #ifdefs in
this file. Update the functions accordingly.
Note: The actual hashing interface is still a mess, with four separate
combinations and lots of #ifdefs. This should really use a driver
On 9/25/21 8:43 PM, Simon Glass wrote:
At present when building host tools, we force CONFIG_SHAxxx to be enabled
regardless of the board Kconfig setting. This is done in the image.h
header file.
For SPL we currently just assume the algorithm is desired if U-Boot proper
enables it.
Clean
On 9/25/21 8:43 PM, Simon Glass wrote:
Unfortunately these were removed by mistake. This means that adding hash
support to SPL brings in all software algorithms, with a substantial
increase in code size.
The origin of the problem was renaming them to SPL_FIT_xxx and then these
were removed
On 9/25/21 8:43 PM, Simon Glass wrote:
In preparation for enabling CONFIG_IS_ENABLED() on the host build, add
some options to enable the various FIT options expected in these tools.
This will ensure that the code builds correctly when CONFIG_TOOLS_xxx
is distinct from CONFIG_xxx.
Drop some
On 9/25/21 8:43 PM, Simon Glass wrote:
In preparation for enabling CONFIG_IS_ENABLED() on the host build, add
some options to enable the various FIT options expected in these tools.
This will ensure that the code builds correctly when CONFIG_TOOLS_xxx
is distinct from CONFIG_xxx.
Drop some
On 9/25/21 8:43 PM, Simon Glass wrote:
At present we must separately test for the host build for many options,
since we force them to be enabled. For example, CONFIG_FIT is always
enabled in the host tools, even if CONFIG_FIT is not enabled by the
board itself.
It would be more convenient if we
On 9/25/21 8:43 PM, Simon Glass wrote:
With the new TOOLS_LIBCRYPTO and some other changes, it seems that we are
heading towards calling this a tools build rather than a host build,
although of course it does happen on the host.
I cannot think of anything built by the host which cannot be
- Switch sources and CI scripts to install and use LLVM-13
- Update to latest "focal" tag.
Signed-off-by: Tom Rini
---
.azure-pipelines.yml| 4 ++--
.gitlab-ci.yml | 4 ++--
tools/docker/Dockerfile | 6 +++---
3 files changed, 7 insertions(+), 7 deletions(-)
diff --git
Hi Tom,
On Tue, 5 Oct 2021 at 09:52, Tom Rini wrote:
>
> On Tue, Oct 05, 2021 at 09:33:18AM -0600, Simon Glass wrote:
> > Hi Wolfgang,
> >
> > On Tue, 5 Oct 2021 at 08:56, Wolfgang Denk wrote:
> > >
> > > Dear Simon,
> > >
> > > In message
> > > you
> > > wrote:
> > > >
> > > > > > Add a
Hi Stefan,
On Tue, 5 Oct 2021 at 09:21, Stefan Agner wrote:
>
> dev_err seems to be moved to different header file. Include
> dm/device_compat.h file to compile properly.
>
> Fixes: 69dae8902b16 ("linux/compat.h: Remove redefinition of dev_xxx macros")
> Signed-off-by: Stefan Agner
> ---
>
>
On Thu, Sep 23, 2021 at 09:57:28PM +0300, dsankou...@gmail.com wrote:
> From: Dzmitry Sankouski
>
> Currently driver supports only version 1 and 2.
> Version 5 has slightly different registers structure
>
> Signed-off-by: Dzmitry Sankouski
> Cc: Ramon Fried
> Cc: Tom Rini
When building for
On Thu, Sep 23, 2021 at 09:57:32PM +0300, dsankou...@gmail.com wrote:
> From: Dzmitry Sankouski
>
> Samsung S9 SM-G9600 - Snapdragon SDM845 version of the phone,
> for China \ Hong Kong markets.
> Has unlockable bootloader, unlike SM-G960U (American market version),
> which allows running
Add request tests to dm_test_pinctrl_single with corresponding node in
test.dts
Signed-off-by: Roman Bacik
---
Changes in v3:
- Add request API test to dm_test_pinctrl_single
arch/sandbox/dts/test.dts | 17 +
test/dm/pinmux.c | 13 +
2 files changed, 30
From: Bharat Gooty
Add pinctrl_ops->request api to configure pctrl
pad register in gpio mode.
Signed-off-by: Rayagonda Kokatanur
Signed-off-by: Bharat Gooty
Acked-by: Rayagonda Kokatanur
Reviewed-by: Simon Glass
Signed-off-by: Roman Bacik
---
(no changes since v2)
Changes in v2:
-
From: Bharat Gooty
Parse different gpio properties from dt as part of probe
function. This detail is required to enable pinctrl pad
later when gpio lines are requested.
Signed-off-by: Rayagonda Kokatanur
Signed-off-by: Bharat Gooty
Acked-by: Rayagonda Kokatanur
Signed-off-by: Roman Bacik
While CI has been using gcc-11.1.0 for a long time, we have not updated
buildman to match. Correct this omission.
Signed-off-by: Tom Rini
---
tools/buildman/toolchain.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/buildman/toolchain.py
This patch enables clock for the r_pio gpios for the h3
r_pio is required to access gpios from port L
Signed-off-by: Manuel Dipolt
---
drivers/clk/sunxi/Makefile | 1 +
drivers/clk/sunxi/clk_h3-r.c | 51
drivers/gpio/sunxi_gpio.c| 8 ++
3 files
On Tue, Oct 05, 2021 at 09:33:18AM -0600, Simon Glass wrote:
> Hi Wolfgang,
>
> On Tue, 5 Oct 2021 at 08:56, Wolfgang Denk wrote:
> >
> > Dear Simon,
> >
> > In message
> > you
> > wrote:
> > >
> > > > > Add a feature that brings in a .env file associated with the board
> > > > > config, if
Hi Wolfgang,
On Tue, 5 Oct 2021 at 08:56, Wolfgang Denk wrote:
>
> Dear Simon,
>
> In message
> you
> wrote:
> >
> > > > Add a feature that brings in a .env file associated with the board
> > > > config, if present. To use it, create a file in a board//env
> > > > directory called .env (or
dev_err seems to be moved to different header file. Include
dm/device_compat.h file to compile properly.
Fixes: 69dae8902b16 ("linux/compat.h: Remove redefinition of dev_xxx macros")
Signed-off-by: Stefan Agner
---
drivers/usb/host/xhci-brcm.c | 1 +
1 file changed, 1 insertion(+)
diff --git
On 10/5/21 4:03 PM, Jorge Ramirez-Ortiz, Foundries wrote:
> On 05/10/21, Michal Simek wrote:
>>
>>
>> On 10/5/21 1:13 PM, Jorge Ramirez-Ortiz wrote:
>>> Add new compatible string u-boot,zynqmp-fpga-ddrauth to handle this
>>> use case.
>>>
>>> Signed-off-by: Jorge Ramirez-Ortiz
>>> ---
>>>
Hi,
On 10/5/21 3:41 PM, patrick.delau...@foss.st.com wrote:
Hi,
ST Restricted
-Original Message-
From: Marek Vasut
Sent: mardi 5 octobre 2021 15:33
To: patrick.delau...@foss.st.com; u-boot@lists.denx.de
Cc: 'Lukasz Majewski'
Subject: Re: [PATCH v2] dfu: dfu_sf: Add support for
Dear Simon,
In message
you wrote:
>
> > > Add a feature that brings in a .env file associated with the board
> > > config, if present. To use it, create a file in a board//env
> > > directory called .env (or common.env if you want the same
> > > environment for all boards).
> >
> > This should
Dear Matthias,
In message <9dd349a3-75ff-ecce-4f4d-957d15a15...@suse.com> you wrote:
>
> I wasn't able to find any commits from Novell email addresses. I wonder if
> SUSE
> still maps to Novell, which would be a long-time oversight :)
The fllowing domain names are mapped to Novell:
Hi Rasmus,
On Mon, 4 Oct 2021 at 01:28, Rasmus Villemoes
wrote:
>
> On 02/10/2021 02.38, Simon Glass wrote:
> > At present U-Boot environment variables, and thus scripts, are defined
> > by CONFIG_EXTRA_ENV_SETTINGS. It is painful to add large amounts of text
> > to this file and dealing with
Hi Wolfgang,
On Mon, 4 Oct 2021 at 06:08, Wolfgang Denk wrote:
>
> Dear Simon,
>
> In message
> <20211001183842.v5.3.If789ba3e2667c46c03eda3386ca84a863baeda55@changeid> you
> wrote:
> >
> > Add a feature that brings in a .env file associated with the board
> > config, if present. To use it,
Hi Wolfgang,
On 05/10/2021 13:01, Wolfgang Denk wrote:
Dear Tom,
In message <20211004151108.GR31748@bill-the-cat> you wrote:
In terms of a changelog,
git log --merges v2021.10-rc4..v2021.10-rc5
contains what I've pulled since the last RC or:
git log --merges v2021.07..v2021.10
for changes
On 05/10/21, Michal Simek wrote:
>
>
> On 10/5/21 1:13 PM, Jorge Ramirez-Ortiz wrote:
> > Add new compatible string u-boot,zynqmp-fpga-ddrauth to handle this
> > use case.
> >
> > Signed-off-by: Jorge Ramirez-Ortiz
> > ---
> > drivers/fpga/xilinx.c | 29 +
> >
From: Marek Behún
The original purpose of mtd_erase_callback() in Linux at the time it was
imported to U-Boot, was to inform the caller that erasing is done (since
it was an asynchronous operation).
All supplied callback methods in U-Boot do nothing, but the
mtd_erase_callback() function was
From: Marek Behún
May it possible to interrupt the spi_nor_erase() function.
Signed-off-by: Marek Behún
Reviewed-by: Simon Glass
Tested-by: Masami Hiramatsu
---
drivers/mtd/spi/spi-nor-core.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/mtd/spi/spi-nor-core.c
From: Marek Behún
The _erase() method of the mtdpart driver, part_erase(), currently
implements offset shifting (for given mtdpart partition) in a weird way:
1. part_erase() adds partition offset to block address
2. parent driver's _erase() method is called
3. parent driver's _erase()
From: Marek Behún
The spi_nor_erase() function does not call mtd_erase_callback() as it
should.
The mtdpart code currently implements the subtraction of partition
offset in mtd_erase_callback().
This results in partition offset being added prior calling
spi_nor_erase(), but not subtracted back
From: Marek Behún
This check is already done in all callers: mtdcore's mtd_write() /
mtd_erase(), legacy spi_nor_write() / spi_flash_erase(). No reason to do
this here as well.
Signed-off-by: Marek Behún
---
Changes since v2:
- remove check for zero length also from spi_nor_write()
---
From: Marek Behún
Check for zero length in the legacy spi_flash_read() /
spi_flash_write() / spi_flash_erase() functions.
On zero length, return 0 immediately, don't call the underlying method.
Rationale:
- these legacy functions call the _read(), _write() and _erase() methods
of struct mtd
-
From: Marek Behún
The cleanup code of the spi_nor_erase() function overwrites the ret
variable with return value of clean_bar(), even if the ret variable is
already set. Fix this.
Signed-off-by: Marek Behún
Reviewed-by: Simon Glass
Tested-by: Masami Hiramatsu
---
From: Marek Behún
The spi_nor_erase() function does not check return value of the
write_enable() call. Fix this.
Signed-off-by: Marek Behún
Reviewed-by: Simon Glass
Reviewed-by: Jagan Teki
Reviewed-by: Pratyush Yadav
Tested-by: Masami Hiramatsu
---
drivers/mtd/spi/spi-nor-core.c | 4 +++-
From: Marek Behún
The cleanup code of spi_nor_erase() function calls write_disable(), but
does not return it's return value even in case of failure. Fix this.
Signed-off-by: Marek Behún
Reviewed-by: Simon Glass
Tested-by: Masami Hiramatsu
---
drivers/mtd/spi/spi-nor-core.c | 4 +++-
1 file
From: Marek Behún
Use the cleanup codepath of spi_nor_erase() also in the event of failure
of writing the BAR register.
Signed-off-by: Marek Behún
Reviewed-by: Simon Glass
Reviewed-by: Jagan Teki
Reviewed-by: Pratyush Yadav
Tested-by: Masami Hiramatsu
---
drivers/mtd/spi/spi-nor-core.c |
From: Marek Behún
The original cover letter said:
this patch series fixes the `mtd erase` command when used with mtdpart
with a partition of non-zero offset.
Currently when the `mtd erase` command is used for such a partition,
it does not erase all blocks. Instead after a block is erased, the
Hi,
ST Restricted
> -Original Message-
> From: Marek Vasut
> Sent: mardi 5 octobre 2021 15:33
> To: patrick.delau...@foss.st.com; u-boot@lists.denx.de
> Cc: 'Lukasz Majewski'
> Subject: Re: [PATCH v2] dfu: dfu_sf: Add support for multiple flashes
>
> On 10/5/21 2:50 PM,
On 10/5/21 2:50 PM, patrick.delau...@foss.st.com wrote:
Hi Marek,
ST Restricted
-Original Message-
From: U-Boot On Behalf Of Marek Vasut
Sent: mardi 5 octobre 2021 14:40
To: u-boot@lists.denx.de
Cc: Marek Vasut ; Lukasz Majewski
Subject: [PATCH v2] dfu: dfu_sf: Add support for
Hi,
ST Restricted
> -Original Message-
> From: patrick.delau...@foss.st.com
> Sent: mardi 5 octobre 2021 14:50
> To: 'Marek Vasut' ; 'u-boot@lists.denx.de' b...@lists.denx.de>
> Cc: 'Lukasz Majewski'
> Subject: RE: [PATCH v2] dfu: dfu_sf: Add support for multiple flashes
>
> Hi
Hi Marek,
ST Restricted
> -Original Message-
> From: U-Boot On Behalf Of Marek Vasut
> Sent: mardi 5 octobre 2021 14:40
> To: u-boot@lists.denx.de
> Cc: Marek Vasut ; Lukasz Majewski
> Subject: [PATCH v2] dfu: dfu_sf: Add support for multiple flashes
>
> Add dfu_alt_info option which
Add dfu_alt_info option which allows specifying multiple SPI flashes
as an alt info. The syntax is as follows:
altname sf bus:cs[:speed[:mode]]
Example:
dfu_alt_info=qspi0 sf 0:0;qspi1 sf 0:1
Signed-off-by: Marek Vasut
Cc: Lukasz Majewski
---
V2: Fix device string parsing in all cases
---
On 10/5/21 1:13 PM, Jorge Ramirez-Ortiz wrote:
> Add new compatible string u-boot,zynqmp-fpga-ddrauth to handle this
> use case.
>
> Signed-off-by: Jorge Ramirez-Ortiz
> ---
> drivers/fpga/xilinx.c | 29 +
> drivers/fpga/zynqmppl.c | 4 ++--
> include/xilinx.h
Hi,
ST Restricted
> -Original Message-
> From: Marek Vasut
> Sent: lundi 4 octobre 2021 18:45
> To: Patrick DELAUNAY ; u-boot@lists.denx.de
> Cc: Patrice Chotard
> Subject: Re: [PATCH] Revert "configs: stm32mp1: only support SD card after
> NOR in bootcmd_stm32mp"
>
> On 10/4/21 6:34
On Mon, Sep 20, 2021 at 11:14 AM Adam Ford wrote:
>
> There are three boards from Beacon, RZ/G2 M/N/H which all
> use the same board file, but different device trees.
> Add code to automatically select the proper device tree
> based on the CPU type.
>
> Signed-off-by: Adam Ford
Marek,
You
On 10/5/21 1:13 PM, Jorge Ramirez-Ortiz wrote:
> Confirm the secure boot configuration on the console.
>
> Signed-off-by: Jorge Ramirez-Ortiz
> ---
> arch/arm/mach-zynqmp/include/mach/hardware.h | 3 ++-
> board/xilinx/zynqmp/zynqmp.c | 16 +++-
> 2 files
Hi,
On 10/5/21 8:08 AM, Jorge Ramirez-Ortiz, Foundries wrote:
> On 05/10/21, Jorge Ramirez-Ortiz, Foundries wrote:
>> On 04/10/21, Alex G. wrote:
>>> On 10/4/21 3:32 PM, Jorge Ramirez-Ortiz, Foundries wrote:
Hello,
>>
>> hi Alex,
>>
We are enabling secure boot on Zynqmp with SPL.
This adds support for amlogic efuse write and provides two subcommands
of "sm" command: "efuseread" and "efusewrite" to read/write bytes between
memory and efuse.
Signed-off-by: Vyacheslav Bocharov
---
arch/arm/mach-meson/sm.c | 68 +++-
1 file changed, 67
On 05.10.21 13:37, Tom Rini wrote:
> On Tue, Oct 05, 2021 at 12:04:49PM +0200, Jan Kiszka wrote:
>
>> From: Jan Kiszka
>>
>> Account for the changes done between merge proposal and the final merge.
>>
>> Signed-off-by: Jan Kiszka
>
> Ah, the navss name thing, sorry I didn't remember that
On Tue, Oct 05, 2021 at 12:04:49PM +0200, Jan Kiszka wrote:
> From: Jan Kiszka
>
> Account for the changes done between merge proposal and the final merge.
>
> Signed-off-by: Jan Kiszka
Ah, the navss name thing, sorry I didn't remember that yesterday.
Reviewed-by: Tom Rini
--
Tom
On Tue, Oct 5, 2021 at 2:13 PM Jorge Ramirez-Ortiz wrote:
>
> Confirm the secure boot configuration on the console.
>
> Signed-off-by: Jorge Ramirez-Ortiz
Acked-by: Oleksandr Suvorov
> ---
> arch/arm/mach-zynqmp/include/mach/hardware.h | 3 ++-
> board/xilinx/zynqmp/zynqmp.c
Hi Jorge,
On Tue, Oct 5, 2021 at 2:13 PM Jorge Ramirez-Ortiz wrote:
>
> Confirm the secure boot configuration on the console.
>
> Signed-off-by: Jorge Ramirez-Ortiz
> ---
> arch/arm/mach-zynqmp/include/mach/hardware.h | 3 ++-
> board/xilinx/zynqmp/zynqmp.c | 16
Add new compatible string u-boot,zynqmp-fpga-ddrauth to handle this
use case.
Signed-off-by: Jorge Ramirez-Ortiz
---
drivers/fpga/xilinx.c | 29 +
drivers/fpga/zynqmppl.c | 4 ++--
include/xilinx.h| 2 +-
3 files changed, 28 insertions(+), 7 deletions(-)
Instead of ignoring the mandatory fpga compatible string, let the
different implementations decide how to handle it
Signed-off-by: Jorge Ramirez-Ortiz
---
cmd/fpga.c | 8
common/image.c | 4 ++--
common/spl/spl_fit.c | 4 +---
drivers/fpga/fpga.c | 11 +--
Confirm the secure boot configuration on the console.
Signed-off-by: Jorge Ramirez-Ortiz
---
arch/arm/mach-zynqmp/include/mach/hardware.h | 3 ++-
board/xilinx/zynqmp/zynqmp.c | 16 +++-
2 files changed, 17 insertions(+), 2 deletions(-)
diff --git
Late fix for 49c8ef0e45a91ec894ef15e7d043dafe8f1c5efd commit by Tom Rini.
Signed-off-by: Vyacheslav Bocharov
---
configs/jethub_j100_defconfig | 1 +
configs/jethub_j80_defconfig | 1 +
2 files changed, 2 insertions(+)
diff --git a/configs/jethub_j100_defconfig b/configs/jethub_j100_defconfig
Dear Tom,
In message <20211004151108.GR31748@bill-the-cat> you wrote:
>
> In terms of a changelog,
> git log --merges v2021.10-rc4..v2021.10-rc5
> contains what I've pulled since the last RC or:
> git log --merges v2021.07..v2021.10
> for changes since the last full release. As always, more
From: Jan Kiszka
This fixes the usage of the USB 3.0-capable port under U-Boot as USB
2.0-only port.
Original patch by Chao Zeng.
Signed-off-by: Jan Kiszka
---
.../k3-am65-iot2050-common-pg2-u-boot.dtsi| 27 +++
arch/arm/dts/k3-am65-iot2050-common-pg2.dtsi | 4 ++-
2
This fixes the freshly merged IOT2050 board and also enables the usage
of the USB 3.0 port under U-Boot (as USB 2.0).
Jan
Jan Kiszka (2):
board: siemens: iot2050: Adjust to changes in DT and configuration
arm: dts: Update IOT2050 device tree files
.../k3-am65-iot2050-common-pg2-u-boot.dtsi
From: Jan Kiszka
Account for the changes done between merge proposal and the final merge.
Signed-off-by: Jan Kiszka
---
arch/arm/dts/k3-am65-iot2050-common-u-boot.dtsi | 2 +-
configs/iot2050_defconfig | 6 --
include/configs/iot2050.h | 2 --
3
On 05.10.21 10:58, Marek Vasut wrote:
This ID disappeared in 5b66fdb29dc ("mtd: spi: Remove unused files"),
add the ID back, since the chip is used on devices supported by U-Boot.
Fixes: 5b66fdb29dc ("mtd: spi: Remove unused files")
Signed-off-by: Marek Vasut
Cc: Horatiu Vultur
Cc: Jagan Teki
This ID disappeared in 5b66fdb29dc ("mtd: spi: Remove unused files"),
add the ID back, since the chip is used on devices supported by U-Boot.
Fixes: 5b66fdb29dc ("mtd: spi: Remove unused files")
Signed-off-by: Marek Vasut
Cc: Horatiu Vultur
Cc: Jagan Teki
Cc: Simon Goldschmidt
Cc: Stefan
Now that everything is prepared, copy the fsl-ls1028a.dtsi from the
linux kernel v5.14.
Notable changes:
- second watchdog added
- the number of chip selects of the SPI controller is now correct and
reflects what the hardware offers
- the LPUARTs have the correct clock parent
- USB
1 - 100 of 134 matches
Mail list logo
