On 23/09/2020 07.02, Heiko Schocher wrote:
> Hi Rasmus,
>
> Am 22.09.2020 um 16:34 schrieb Rasmus Villemoes:
>> The board already used OF_CONTROL, so I've tried extending the
>> device-tree based partly on you changes for the km boards, partly from
>> our linux device tree - the two mostly agree:
Am 2020-09-23 19:28, schrieb Tom Rini:
On Wed, Sep 23, 2020 at 07:21:57PM +0200, Heinrich Schuchardt wrote:
On 9/23/20 6:45 PM, Michael Walle wrote:
> Let the user choose between three different behaviours of the watchdog:
> (1) Keep the watchdog disabled
> (2) Supervise u-boot
> (3) Supervis
On 24.09.20 01:22, Andre Przywara wrote:
The cfi-flash driver uses an open-coded version of the generic
algorithm to decode and translate multiple frames of a "reg" property.
This starts off the wrong foot by using the address-cells and size-cells
properties of *this* very node, and not of the p
Hi Priyanka,
> -Original Message-
> From: Priyanka Jain (OSS)
> Sent: 2020年9月23日 21:25
> To: Z.q. Hou ; u-boot@lists.denx.de;
> bmeng...@gmail.com; olte...@gmail.com
> Cc: Vladimir Oltean ; Z.q. Hou
>
> Subject: RE: [PATCHv6 01/18] phy: make phy_connect_fixed work with a null
> mdio bus
From: Jean-Jacques Hiblot
The tests rely on a dummy driver to allocate and initialize the regmaps
and the regmap fields using the managed API. The first test checks if
the regmap config fields like width, reg_offset_shift, range specifiers,
etc work. The second test checks if regmap fields behave
Right now, the base of a regmap can only be obtained from the device
tree. This makes it impossible for devices which calculate the base at
runtime to use a regmap. An example of such a device is the Cadence
Sierra PHY.
Allow creating a regmap with one range whose start and size can be
specified b
From: Jean-Jacques Hiblot
A regmap field is an abstraction available in Linux. It provides to access
bitfields in a regmap without having to worry about shifts and masks.
Signed-off-by: Jean-Jacques Hiblot
Reviewed-by: Simon Glass
Signed-off-by: Pratyush Yadav
---
Notes:
No changes in v3
Drivers can configure it to adjust the final read/write location.
Signed-off-by: Pratyush Yadav
Reviewed-by: Simon Glass
---
Notes:
No changes in v3.
drivers/core/regmap.c | 6 +-
include/regmap.h | 6 ++
2 files changed, 11 insertions(+), 1 deletion(-)
diff --git a/drivers/
Some fields will be introduced in the regmap structure that should be
set to 0 by default. So, once we allocate a regmap, make sure it is
zeroed out to avoid unexpected defaults for those values.
Signed-off-by: Pratyush Yadav
Reviewed-by: Simon Glass
---
Notes:
No changes in v3.
drivers/c
When more nodes are added for a uclass the index might go into two or
more digits. This means that there are less spaces printed because they
are used up by the extra digits. Update the regular expression to allow
variable-length spacing between the class name and and index.
This was discovered wh
Right now, regmap_read() and regmap_write() read/write a 32-bit value
only. To write other lengths, regmap_raw_read() and regmap_raw_write()
need to be used.
This means that any driver ported from Linux that relies on
regmap_{read,write}() to know the size already has to be updated at each
callsit
Some devices need to calculate the regmap base address at runtime. This
makes it impossible to use device tree to get the regmap base. Instead,
allow devices to specify it in the regmap config. This will create a
regmap with a single range that corresponds to the start and size given
by the driver.
From: Jean-Jacques Hiblot
Most of new linux drivers are using managed-API to allocate resources. To
ease porting drivers from linux to U-Boot, introduce devm_regmap_init() as
a managed API to get a regmap from the device tree.
Signed-off-by: Jean-Jacques Hiblot
Reviewed-by: Simon Glass
Signed-
Hi,
This series is a re-spin of Jean-Jacques' earlier effort [0], the goal
of which was to facilitate porting drivers from the Linux kernel. It
adds the managed API, using the same API as Linux. It also adds support
for regmap fields.
Jean-Jacques' series added support for custom regmap read/writ
Hi Simon,
On Thu, Sep 24, 2020 at 11:22 AM Bin Meng wrote:
>
> On Wed, Sep 23, 2020 at 6:04 AM Simon Glass wrote:
> >
> > Hi Bin,
> >
> > On Tue, 22 Sep 2020 at 01:11, Bin Meng wrote:
> > >
> > > Hi Simon,
> > >
> > > On Fri, Sep 4, 2020 at 9:28 AM Simon Glass wrote:
> > > >
> > > > At present
On Wed, Sep 23, 2020 at 6:04 AM Simon Glass wrote:
>
> Hi Bin,
>
> On Tue, 22 Sep 2020 at 01:11, Bin Meng wrote:
> >
> > Hi Simon,
> >
> > On Fri, Sep 4, 2020 at 9:28 AM Simon Glass wrote:
> > >
> > > At present it is painful to put Edison in a hardware lab because it has
> > > two separate reco
From: Abbie Chang
Add Cortina Access Ethernet device driver for CA SoCs.
This driver supports both legacy and DM_ETH network models.
Signed-off-by: Aaron Tseng
Signed-off-by: Alex Nemirovsky
Signed-off-by: Abbie Chang
CC: Joe Hershberger
CC: Abbie Chang
CC: Tom Rini
---
Changes in v
Tom,
v3 submitted after Abbie reviewed and updated per your request.
> On Sep 10, 2020, at 4:54 PM, Tom Rini wrote:
>
> On Thu, Sep 10, 2020 at 11:18:46PM +, Alex Nemirovsky wrote:
>
>> bump.
>
> Sorry, I've meant to reply on some of this. Please fix the usage of
> ca_status_t and use
Add CA Ethernet support for the Cortina Access
Presidio Engineering Board
Signed-off-by: Alex Nemirovsky
CC: Tom Rini
---
(no changes since v2)
Changes in v2:
- only support DM_ETH network models by removing
code for legacy mode support
arch/arm/dts/ca-presidio-engboard.dts| 6
From: Abbie Chang
Add phy driver support for MACs embedded inside Cortina Access SoCs
Signed-off-by: Abbie Chang
Signed-off-by: Alex Nemirovsky
CC: Joe Hershberger
CC: Tom Rini
CC: Aaron Tseng
Moved out PHY specific code out of Cortina NI Ethernet driver
and into a Cortina Access PHY inte
Currently we hard-code the number and initial addresses of QEMU's flash
banks, even though our code is perfectly able to gather the same
information from the DTB provided by QEMU.
This is especially annoying, since we have two slightly different
U-Boot configurations ("bare-metal" vs. loaded via Ar
Currently selecting CONFIG_POSITION_INDEPENDENT also forces us to use an
initial stack pointer address relative to the load address. This makes
some sense, assuming there is some usable memory nearby.
However if U-Boot is started from some kind of ROM, a stack pointer
nearby will probably also end
CONFIG_ARCH_SUPPORT_TFABOOT seems to be a guard option to enable various
platform specific hacks, when U-Boot is run under TF-A.
Now that the QEMU port does not need to differentiate between secure
vs. non-secure anymore (this is taken care of by the DTB), there is
no need for a build-time option a
Now that PIE works when U-Boot is started from ROM, let's enable
CONFIG_POSITION_INDEPENDENT, which allows to load U-Boot also via
ARM Trusted-Firmware's fip.bin to DRAM, without tweaking the
configuration.
To get a writable initial stack, we need to keep the fixed initial
stack pointer, which poi
When the actual offset between link and runtime address is zero, there
is no need for patching up U-Boot early when running with
CONFIG_POSITION_INDEPENDENT.
Skip the whole routine when the distance is 0.
This helps when U-Boot is loaded into ROM, or in otherwise sensitive
memory locations.
Sign
U-Boot on QEMU-arm64 can be used in two configurations: Loaded directly
via QEMU's -bios option, or as a non-secure payload (BL33) via
ARM Trusted Firmware-A (TF-A).
In the latter case we need to define CONFIG_TFABOOT, to accommodate
the first flash bank being secure only, and manually set SYS_TEXT
The cfi-flash driver uses an open-coded version of the generic
algorithm to decode and translate multiple frames of a "reg" property.
This starts off the wrong foot by using the address-cells and size-cells
properties of *this* very node, and not of the parent. This somewhat
happened to work back
On Wednesday 23 September 2020 08:45:20 Stefan Roese wrote:
> On 22.09.20 13:21, Pali Rohár wrote:
> > As required by PCI Express spec a delay for at least 100ms after
> > de-asserting PERST# signal is needed before link training is enabled.
> >
> > Linux kernels prior to 5.8 version do not automa
Am Mittwoch, den 23.09.2020, 20:27 +0200 schrieb Mauro Condarelli:
> Thanks for the review,
> I'll prepare a v2 ASAP.
>
> On 9/23/20 12:05 AM, Daniel Schwierzeck wrote:
> > Am Sonntag, den 20.09.2020, 21:21 -0400 schrieb Tom Rini:
> > > On Sun, Sep 20, 2020 at 06:29:01PM +0200, Mauro Condarelli wr
Am 23. September 2020 23:15:50 MESZ schrieb Michael Walle :
>Currently, the EFI bootmgr is only called if there is a EFI binary
>inside the path for removable media is found, i.e. /EFI/boot/. This
>doesn't make sense. It is the duty of the bootmgr to find out the
>path and name of the EFI binary to
Currently, the EFI bootmgr is only called if there is a EFI binary
inside the path for removable media is found, i.e. /EFI/boot/. This
doesn't make sense. It is the duty of the bootmgr to find out the
path and name of the EFI binary to boot. It should be called even
if there is no /EFI/boot directo
On Wed, Sep 23, 2020 at 10:58:00PM +0200, Heinrich Schuchardt wrote:
> On 9/23/20 10:23 PM, Tom Rini wrote:
> > On Wed, Sep 23, 2020 at 10:01:29PM +0200, Heinrich Schuchardt wrote:
> >> On 9/23/20 9:02 PM, Tom Rini wrote:
> >>> On Wed, Sep 23, 2020 at 08:51:53PM +0200, Heinrich Schuchardt wrote:
>
On 9/23/20 10:38 PM, Michael Walle wrote:
> Hi,
>
> Am 2020-09-23 20:51, schrieb Heinrich Schuchardt:
>> On 9/23/20 7:53 PM, Mark Kettenis wrote:
Date: Wed, 23 Sep 2020 13:14:09 -0400
From: Tom Rini
On Wed, Sep 23, 2020 at 07:01:54PM +0200, Mark Kettenis wrote:
>> From: Mic
On 9/23/20 10:23 PM, Tom Rini wrote:
> On Wed, Sep 23, 2020 at 10:01:29PM +0200, Heinrich Schuchardt wrote:
>> On 9/23/20 9:02 PM, Tom Rini wrote:
>>> On Wed, Sep 23, 2020 at 08:51:53PM +0200, Heinrich Schuchardt wrote:
On 9/23/20 7:53 PM, Mark Kettenis wrote:
>> Date: Wed, 23 Sep 2020 13:
Hi,
Am 2020-09-23 20:51, schrieb Heinrich Schuchardt:
On 9/23/20 7:53 PM, Mark Kettenis wrote:
Date: Wed, 23 Sep 2020 13:14:09 -0400
From: Tom Rini
On Wed, Sep 23, 2020 at 07:01:54PM +0200, Mark Kettenis wrote:
From: Michael Walle
Date: Wed, 23 Sep 2020 18:45:27 +0200
Let the user choose b
On 9/23/20 9:49 PM, Thomas Petazzoni wrote:
> On Wed, 23 Sep 2020 21:13:51 +0200
> Heinrich Schuchardt wrote:
>
>> We should check if the incoming parameter file_mapping is not NULL instead
>> of checking after adding an offset.
>>
>> Reported-by: Coverity CID 307210
>> Signed-off-by: Heinrich Sch
On Wed, Sep 23, 2020 at 10:01:29PM +0200, Heinrich Schuchardt wrote:
> On 9/23/20 9:02 PM, Tom Rini wrote:
> > On Wed, Sep 23, 2020 at 08:51:53PM +0200, Heinrich Schuchardt wrote:
> >> On 9/23/20 7:53 PM, Mark Kettenis wrote:
> Date: Wed, 23 Sep 2020 13:14:09 -0400
> From: Tom Rini
> >>>
The algo name should match between the FIT's signature node and the
U-Boot's control FDT.
If we do not check it, U-Boot's control FDT can expect sha512 hash but
nothing will prevent to accept image with sha1 hash if the signature is correct.
Signed-off-by: Matthieu CASTET
---
lib/rsa/rsa-verify
On 9/23/20 9:02 PM, Tom Rini wrote:
> On Wed, Sep 23, 2020 at 08:51:53PM +0200, Heinrich Schuchardt wrote:
>> On 9/23/20 7:53 PM, Mark Kettenis wrote:
Date: Wed, 23 Sep 2020 13:14:09 -0400
From: Tom Rini
On Wed, Sep 23, 2020 at 07:01:54PM +0200, Mark Kettenis wrote:
>> From
On Wed, 23 Sep 2020 21:13:51 +0200
Heinrich Schuchardt wrote:
> We should check if the incoming parameter file_mapping is not NULL instead
> of checking after adding an offset.
>
> Reported-by: Coverity CID 307210
> Signed-off-by: Heinrich Schuchardt
Acked-by: Thomas Petazzoni
However, I won
We should check if the incoming parameter file_mapping is not NULL instead
of checking after adding an offset.
Reported-by: Coverity CID 307210
Signed-off-by: Heinrich Schuchardt
---
fs/squashfs/sqfs_inode.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/squashfs/sqfs
On Wed, Sep 23, 2020 at 08:51:53PM +0200, Heinrich Schuchardt wrote:
> On 9/23/20 7:53 PM, Mark Kettenis wrote:
> >> Date: Wed, 23 Sep 2020 13:14:09 -0400
> >> From: Tom Rini
> >>
> >> On Wed, Sep 23, 2020 at 07:01:54PM +0200, Mark Kettenis wrote:
> From: Michael Walle
> Date: Wed, 23 S
On 9/23/20 7:53 PM, Mark Kettenis wrote:
>> Date: Wed, 23 Sep 2020 13:14:09 -0400
>> From: Tom Rini
>>
>> On Wed, Sep 23, 2020 at 07:01:54PM +0200, Mark Kettenis wrote:
From: Michael Walle
Date: Wed, 23 Sep 2020 18:45:27 +0200
Let the user choose between three different behavi
On Wed, Sep 23, 2020 at 07:34:59PM +0100, Jack Mitchell wrote:
>
> On 23/09/2020 19:23, Tom Rini wrote:
> > This converts the following to Kconfig:
> >CONFIG_WATCHDOG
> >CONFIG_WATCHDOG_TIMEOUT
> >CONFIG_WDT
> >CONFIG_HW_WATCHDOG
> >CONFIG_DESIGNWARE_WATCHDOG
> >
> > Signed-of
On Wed, Sep 23, 2020 at 08:27:24PM +0200, Mauro Condarelli wrote:
> Thanks for the review,
> I'll prepare a v2 ASAP.
>
> On 9/23/20 12:05 AM, Daniel Schwierzeck wrote:
> > Am Sonntag, den 20.09.2020, 21:21 -0400 schrieb Tom Rini:
> >> On Sun, Sep 20, 2020 at 06:29:01PM +0200, Mauro Condarelli wrot
On 23/09/2020 19:23, Tom Rini wrote:
> This converts the following to Kconfig:
>CONFIG_WATCHDOG
>CONFIG_WATCHDOG_TIMEOUT
>CONFIG_WDT
>CONFIG_HW_WATCHDOG
>CONFIG_DESIGNWARE_WATCHDOG
>
> Signed-off-by: Tom Rini
Before setting this in stone, after much recent personal confusio
Thanks for the review,
I'll prepare a v2 ASAP.
On 9/23/20 12:05 AM, Daniel Schwierzeck wrote:
> Am Sonntag, den 20.09.2020, 21:21 -0400 schrieb Tom Rini:
>> On Sun, Sep 20, 2020 at 06:29:01PM +0200, Mauro Condarelli wrote:
>>
>>> Signed-off-by: Mauro Condarelli
>>> ---
>>> fs/squashfs/sqfs.c
This converts the following to Kconfig:
CONFIG_WATCHDOG
CONFIG_WATCHDOG_TIMEOUT
CONFIG_WDT
CONFIG_HW_WATCHDOG
CONFIG_DESIGNWARE_WATCHDOG
Signed-off-by: Tom Rini
---
README | 15 ---
configs/MPC8610HPCD_defconfig | 1 +
configs/
> Date: Wed, 23 Sep 2020 13:14:09 -0400
> From: Tom Rini
>
> On Wed, Sep 23, 2020 at 07:01:54PM +0200, Mark Kettenis wrote:
> > > From: Michael Walle
> > > Date: Wed, 23 Sep 2020 18:45:27 +0200
> > >
> > > Let the user choose between three different behaviours of the watchdog:
> > > (1) Keep t
On Wed, Sep 23, 2020 at 07:31:00PM +0200, Heinrich Schuchardt wrote:
> On 9/23/20 7:14 PM, Tom Rini wrote:
> > On Wed, Sep 23, 2020 at 07:01:54PM +0200, Mark Kettenis wrote:
> >>> From: Michael Walle
> >>> Date: Wed, 23 Sep 2020 18:45:27 +0200
> >>>
> >>> Let the user choose between three differen
From: Alexandre GRIVEAUX
Adding Z-turn board V5 to resolve the change between:
"Z-TURNBOARD_schematic.pdf" schematics state version 1 to 4 has Atheros AR8035
"Z-Turn_Board_sch_V15_20160303.pdf" schematics state version 5 has Micrel
KSZ9031
At this time the S25FL128SAGNFI003 doesn't work becaus
On 9/23/20 7:14 PM, Tom Rini wrote:
> On Wed, Sep 23, 2020 at 07:01:54PM +0200, Mark Kettenis wrote:
>>> From: Michael Walle
>>> Date: Wed, 23 Sep 2020 18:45:27 +0200
>>>
>>> Let the user choose between three different behaviours of the watchdog:
>>> (1) Keep the watchdog disabled
>>> (2) Superv
On Wed, Sep 23, 2020 at 07:21:57PM +0200, Heinrich Schuchardt wrote:
> On 9/23/20 6:45 PM, Michael Walle wrote:
> > Let the user choose between three different behaviours of the watchdog:
> > (1) Keep the watchdog disabled
> > (2) Supervise u-boot
> > (3) Supervise u-boot and the operating syste
On 9/23/20 6:45 PM, Michael Walle wrote:
> Let the user choose between three different behaviours of the watchdog:
> (1) Keep the watchdog disabled
> (2) Supervise u-boot
> (3) Supervise u-boot and the operating systen (default)
>
> Option (2) will disable the watchdog right before handing contr
On Wed, Sep 23, 2020 at 07:01:54PM +0200, Mark Kettenis wrote:
> > From: Michael Walle
> > Date: Wed, 23 Sep 2020 18:45:27 +0200
> >
> > Let the user choose between three different behaviours of the watchdog:
> > (1) Keep the watchdog disabled
> > (2) Supervise u-boot
> > (3) Supervise u-boot
Most users don't need the standalone API examples. Distributions like SUSE
do not supply libgcc for cross-compiling and we cannot do without on ARMv8
for building examples/.
Make examples selectable via symbol CONFIG_EXAMPLES. It defaults to
yes on ARCH_QEMU to ensure that we compile the API as pa
> From: Michael Walle
> Date: Wed, 23 Sep 2020 18:45:27 +0200
>
> Let the user choose between three different behaviours of the watchdog:
> (1) Keep the watchdog disabled
> (2) Supervise u-boot
> (3) Supervise u-boot and the operating systen (default)
>
> Option (2) will disable the watchdog
The PWM device provided by Chrome OS EC doesn't really support anything
other than setting a relative duty cycle. To support it as a backlight,
this patch makes the PWM period optional in the device tree and pretends
the valid brightness range is its period_ns.
Signed-off-by: Alper Nebi Yasak
---
This PWM is used in rk3399-gru-bob and rk3399-gru-kevin to control
the display brightness. We can only change the duty cycle, so on
set_config() we just try to match the duty cycle that dividing duty_ns
by period_ns gives us. To disable, we set the duty cycle to zero while
keeping the old value for
Let the user choose between three different behaviours of the watchdog:
(1) Keep the watchdog disabled
(2) Supervise u-boot
(3) Supervise u-boot and the operating systen (default)
Option (2) will disable the watchdog right before handing control to the
operating system. This is useful when the
This option is only supported by the IMX watchdog and seems to be
similar to CONFIG_WATCHDOG.
Move it below the IMX watchdog and make it dependent on IMX_WATCHDOG.
Signed-off-by: Michael Walle
---
drivers/watchdog/Kconfig | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff
On 23/09/2020 06:26, Stefan Roese wrote:
> Hi Simon,
>
> On 22.09.20 15:51, Simon Glass wrote:
>> Hi Stefan,
>>
>> On Mon, 21 Sep 2020 at 07:28, Stefan Roese wrote:
>>>
>>> Hi Andre,
>>>
>>> (added Simon)
>>>
>>> On 18.09.20 19:45, Andre Przywara wrote:
The cfi-flash driver uses an open-code
Hi Simon,
> From: Simon Glass
> Sent: mardi 22 septembre 2020 20:49
>
> On Thu, 10 Sep 2020 at 10:44, Patrick Delaunay
> wrote:
> >
> > The cell_count argument is required when cells_name is NULL.
> >
> > This patch adds this parameter in live tree API
> > - of_count_phandle_with_args
> > - ofn
Set the defaults on probe for the packet buffer size registers
for the i210.
The TXPBSIZE register of the i210 resets to its default value only
at power-on. It doesn't reset if you reboot the system, only if you
pull power. If something (another driver, another OS, etc.) modifies
this register fro
On 20. 09. 20 18:50, Ovidiu Panait wrote:
> Implement early init by calling generic board_init_f_alloc_reserve and
> board_init_f_init_reserve functions:
> * drop SYS_MALLOC_F_LEN related code, as allocation and gd->malloc_base
> assignment are taken care of by the generic functions
> * drop _
On 20. 09. 20 18:50, Ovidiu Panait wrote:
> Currently, the exceptions setup code is duplicated in pre-relocation and
> post-relocation init. Factor out this code to __setup_exceptions asm
> routine to get rid of the duplication.
>
> __setup_exceptions is called with a relocation offset paramete
Add Microchip PIT64B timer.
Signed-off-by: Claudiu Beznea
---
Hi Eugen,
I chosed to have it under AT91 hood to not create an entry only for this
driver as there are mostly architecture/subsystem related entries in
MAINTAINERS file.
Thank you,
Claudiu Beznea
MAINTAINERS | 1 +
1 file changed,
>-Original Message-
>From: U-Boot On Behalf Of Michael Walle
>Sent: Monday, August 10, 2020 8:24 PM
>To: u-boot@lists.denx.de
>Cc: Priyanka Jain ; Horia Geanta
>; Michael Walle
>Subject: [PATCH v2] armv8: layerscape: don't remove crypto node if just
>partially disabled
>
>On all newer Lay
>-Original Message-
>From: U-Boot On Behalf Of Biwen Li (OSS)
>Sent: Friday, July 10, 2020 7:24 AM
>To: Rasmus Villemoes ; Biwen Li (OSS)
>; Jagdish Gediya ; Priyanka
>Jain
>Cc: Jiafei Pan ; u-boot@lists.denx.de
>Subject: RE: [EXT] Re: [PATCH] rtc: pcf2127: fix uninitialized variable msg
>-Original Message-
>From: U-Boot On Behalf Of Zhiqiang Hou
>Sent: Thursday, June 4, 2020 8:47 PM
>To: u-boot@lists.denx.de; Priyanka Jain ; Shengzhou
>Liu ; ja...@amarulasolutions.com;
>s...@chromium.org; Biwen Li ; bmeng...@gmail.com
>Cc: Jiafei Pan ; Chuanhua Han
>; Xiaowei Bao ; Z.q. H
>-Original Message-
>From: U-Boot On Behalf Of Rasmus Villemoes
>Sent: Friday, September 18, 2020 1:51 PM
>To: Stefan Roese ; u-boot@lists.denx.de
>Cc: Christophe Leroy ; Wolfgang Denk
>; Simon Glass ; Tom Rini
>
>Subject: Re: [PATCH] powerpc: reduce number of WATCHDOG_RESET calls
>from fl
>-Original Message-
>From: U-Boot On Behalf Of Ran Wang
>Sent: Tuesday, June 30, 2020 10:39 AM
>To: Priyanka Jain
>Cc: u-boot@lists.denx.de; Ran Wang
>Subject: [PATCH] configs: powerpc: add usb (host) mass storage support
>
>commit 0cfccb54014b ("configs: Resync with savedefconfig") remo
>-Original Message-
>From: U-Boot On Behalf Of Zhiqiang Hou
>Sent: Tuesday, September 22, 2020 2:20 PM
>To: u-boot@lists.denx.de; bmeng...@gmail.com; olte...@gmail.com;
>Priyanka Jain
>Cc: Vladimir Oltean ; Z.q. Hou
>
>Subject: [PATCHv6 01/18] phy: make phy_connect_fixed work with a null
Dear Tom,
Please find my pull-request for u-boot-mpc85xx
https://travis-ci.org/github/p-priyanka-jain/u-boot/builds/729353915
Summary
Add DM_SPI, DM_SPI_FLASH support for powerpc platforms
Add DM_ETH support on P1010RDB, P1020RDB, P2020RDB
reduce number of WATCHDOG_RESET calls from flush_cache
R
On Wed, Sep 23, 2020 at 01:40:09AM +0200, Daniel Schwierzeck wrote:
> Hi Tom,
>
> this contains some small fixes isolated to two MIPS boards which are
> currently broken.
>
> Gitlab CI:
> https://gitlab.denx.de/u-boot/custodians/u-boot-mips/-/pipelines/4758
>
>
> The following changes since c
On Tue, Sep 22, 2020 at 02:58:48PM -0600, Simon Glass wrote:
> Hi Tom,
>
> This is for upstream/next
>
> Build here:
>
> https://gitlab.denx.de/u-boot/custodians/u-boot-dm/-/pipelines/4750
>
>
> The following changes since commit 2512b3b88ba6b193c3cada7e29e386613e8f9a6b:
>
> Merge branch '
Dear Rasmus,
In message you wrote:
> On 04/06/2020 12.31, Stefan Roese wrote:
> > On 04.06.20 11:30, Rasmus Villemoes wrote:
> >> Calling WATCHDOG_RESET for each and every cache line is overkill.
> >>
> >> In our case, the kernel image is a little over 7MB, and the almost
> >> 50 calls of WAT
Add missing documentation for Xilinx ZynqMP R5 configuration with steps how
to run it.
Signed-off-by: Michal Simek
---
(no changes since v1)
doc/board/xilinx/index.rst | 1 +
doc/board/xilinx/zynqmp-r5.rst | 137 +
2 files changed, 138 insertions(+)
creat
Add missing documentation for Xilinx ZynqMP configuration with steps how
to configure it and run it.
Signed-off-by: Michal Simek
---
Changes in v2:
- Add more information about PMU config object and how to get it.
doc/board/xilinx/index.rst | 1 +
doc/board/xilinx/zynqmp.rst | 115 +
Several drivers have been added without updating documentation.
And also some dt bindings have been moved to yaml.
Signed-off-by: Michal Simek
---
(no changes since v1)
doc/board/xilinx/xilinx.rst | 16 +---
1 file changed, 13 insertions(+), 3 deletions(-)
diff --git a/doc/board/x
Add fragment to cover documenation for Xilinx platforms.
Signed-off-by: Michal Simek
Reviewed-by: Heinrich Schuchardt
---
Changes in v2:
- Sort it - reported by Heinrich
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 7e46470c709a..950780e487a1
- Correct location of BSP code
- Remove TODO which is done already
Signed-off-by: Michal Simek
---
(no changes since v1)
doc/board/xilinx/zynq.rst | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/doc/board/xilinx/zynq.rst b/doc/board/xilinx/zynq.rst
index f564434b69c4.
Hi,
this series is trying to update documentation for Xilinx SoCs.
Based on this documentation developers should be able to configure and run
u-boot on their platforms.
Thanks,
Michal
Changes in v2:
- Sort it - reported by Heinrich
- Add more information about PMU config object and how to get it
st 16. 9. 2020 v 13:40 odesílatel Michal Simek napsal:
>
> fixed-rate driver is not different from clk_fixed_factor and it is required
> very early in boot that's why setup flag for it.
>
> Signed-off-by: Michal Simek
> ---
>
> drivers/clk/clk_fixed_rate.c | 1 +
> 1 file changed, 1 insertion(+)
st 16. 9. 2020 v 13:38 odesílatel Michal Simek napsal:
>
> There is not enough space for early allocation. That's why increase it.
>
> Signed-off-by: Michal Simek
> ---
>
> configs/xilinx_zynqmp_r5_defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/configs/xilinx_zynqmp_r5_defcon
st 16. 9. 2020 v 10:48 odesílatel Michal Simek napsal:
>
> From: T Karthik Reddy
>
> pxe sub commands need to be manually relocated for architectures which
> enables MANUAL_RELOC as Microblaze.
>
> Signed-off-by: T Karthik Reddy
> Signed-off-by: Michal Simek
> ---
>
> cmd/pxe.c | 14 ++
On 16. 09. 20 10:18, Michal Simek wrote:
> PXE and DHCP shouldn't be listed when commands are not enabled that's why
> handle it in the same way as is done for Zynq and ZynqMP.
>
> Fixes: ec48b6c991f4 ("arm64: versal: Add support for new Xilinx Versal ACAPs")
> Signed-off-by: Michal Simek
> --
po 14. 9. 2020 v 16:38 odesílatel Michal Simek napsal:
>
> Map all resource for R5 to operate properly.
> The patch is done based on the commit 23f7b1a77602 ("armv7R: K3: am654:
> Enable MPU regions") which also map the whole 4GB at first and then change
> mapping for DDR.
>
> Signed-off-by: Micha
po 14. 9. 2020 v 16:39 odesílatel Michal Simek napsal:
>
> Xilinx ZynqMP R5 configuration is quite minimal and there is no reason to
> enable EFI for it.
>
> Signed-off-by: Michal Simek
> ---
>
> configs/xilinx_zynqmp_r5_defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/configs/
čt 3. 9. 2020 v 12:02 odesílatel Michal Simek napsal:
>
> ATF support was all the time based on FIT image support but this dependency
> is not recorded anywhere.
> For !SPL_FIT && SPL_ATF there is compilation error:
> common/spl/spl.c: In function 'board_init_r':
> common/spl/spl.c:689:26: error:
po 14. 9. 2020 v 13:02 odesílatel Michal Simek napsal:
>
> Trivial fix.
>
> Fixes: d1f4e39d58db ("mmc: zynq_sdhci: Add support for SD3.0"
> Signed-off-by: Michal Simek
> ---
>
> drivers/mmc/zynq_sdhci.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/zynq_sdh
po 14. 9. 2020 v 13:06 odesílatel Michal Simek napsal:
>
> Both SOCs shouldn't have any problem with 64bit dma accesses. Also with PIE
> enabled when u-boot is placed above 4GB without any memory mapped below 4GB
> address space efi_memory_init() call is failing due to missing memory node.
>
> For
čt 10. 9. 2020 v 12:41 odesílatel Michal Simek napsal:
>
> There is no need to use these macros because enum pm_api_id can be used
> instead.
>
> Signed-off-by: Michal Simek
> ---
>
> drivers/fpga/zynqmppl.c | 8
> include/zynqmppl.h | 3 ---
> 2 files changed, 4 insertions(+), 7 d
čt 10. 9. 2020 v 13:02 odesílatel Michal Simek napsal:
>
> if conditions should match.
>
> Fixes: a18d09ea384f ("fpga: zynqmp: Add secure bitstream loading for ZynqMP")
> Signed-off-by: Michal Simek
> ---
>
> drivers/fpga/zynqmppl.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> dif
čt 10. 9. 2020 v 12:53 odesílatel Michal Simek napsal:
>
> The patch does sed 's/SPL_FPGA_SUPPORT/SPL_FPGA/g' but also fixing Makefile
> and zynqmp.c to simplify if/endif logic in zynqmp.c.
>
> This change is mostly done to be able to use CONFIG_IS_ENABLED macro and
> obj-$(CONFIG_$(SPL_)FPGA) in
st 8. 1. 2020 v 12:42 odesílatel Michal Simek napsal:
>
> Enable position independent pre-relocation to let users options to put
> u-boot to different locations.
>
> Signed-off-by: Michal Simek
> ---
>
> configs/xilinx_versal_virt_defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
st 19. 8. 2020 v 10:44 odesílatel Michal Simek napsal:
>
> Add missing dependencies for DM_SPI_FLASH.
> Kconfig reports it as:
> WARNING: unmet direct dependencies detected for SPL_DM_SPI_FLASH
> Depends on [n]: SPL [=n] && SPL_DM [=n]
> Selected by [y]:
> - ARCH_ZYNQMP [=y] && && SPL_DM_SP
pá 4. 9. 2020 v 16:41 odesílatel Michal Simek napsal:
>
> For SPL flow without specifying address for DT loading DTB is automatically
> appended behind U-Boot code. Specifically _end symbol is used. Just behind
> it there is place for bss section.
> It means if early code is using static variable
čt 30. 7. 2020 v 14:42 odesílatel Michal Simek napsal:
>
> Enabling saving variables to MMC(FAT), NAND, SPI based on primary bootmode.
> Maybe that logic can be tuned for more complicated use cases and better
> tested for different bootmodes.
>
> Tested on zcu104 to SD(FAT) and JTAG(NOWHERE).
>
>
pá 11. 9. 2020 v 10:12 odesílatel Michal Simek napsal:
>
> Hi,
>
> This patch series is intended to cleanup the functions used to get
> the silicon name for ZynqMPSoC devices. It make use the firmware driver
> rather than SMC call and impements more understandable agorithm to
> compute the device
1 - 100 of 148 matches
Mail list logo
