On Tue, Sep 22, 2020 at 7:41 PM Marek Vasut wrote:
>
> On 9/22/20 6:54 AM, Ran Wang wrote:
> > In functiion xhci_bulk_tx(), when buffer cross 64KB boundary, it will
> > send request in more than 1 Transfer TRB by chaining them, but then handle
> > only 1 event TRB to mark request completed.
> >
>
On 05/11/2020 17.40, Wolfgang Denk wrote:
> Dear Rasmus,
>
> In message <8ff3b8ad-8c4e-fe99-69c8-7c174e997...@prevas.dk> you wrote:
>>
Not in a none standard way! Instead you can define more than one
environment storage devices and load them in a board specific order
(defined
On 06.11.20 05:08, Joshua Scott wrote:
Hardware testing of a board using the Armada 385 has shown that an
impedance threshold setting of 0x7 performs better in an eye-diagram
test than with Marvell's recommended value 0x6.
As other boards may still perform better with Marvell's reccomended
Device tree alignment with kernel v5.10-rc1.
Signed-off-by: Patrice Chotard
---
arch/arm/dts/stm32429i-eval-u-boot.dtsi | 2 +-
arch/arm/dts/stm32429i-eval.dts | 21 +++--
arch/arm/dts/stm32746g-eval-u-boot.dtsi | 4 +-
arch/arm/dts/stm32746g-eval.dts | 13 ++-
Fix typo "firsct"
Signed-off-by: Patrice Chotard
---
arch/arm/dts/stm32h7-u-boot.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/dts/stm32h7-u-boot.dtsi b/arch/arm/dts/stm32h7-u-boot.dtsi
index 7182533cc9..54dd406b6b 100644
---
Since kernel v4.8-rc1, commit 05b23ebc2bd9 ("ARM: dts: armv7-m: remove
skeleton.dtsi include"),
skeleton.dtsi file is no more included.
This synchronization is needed to avoid to get 2 memory node
in DTB file if, in DTS file, memory node is declared with the correct
syntax as following:
Commit 4b2be78ab66c ("time: Fix get_ticks being non-monotonic")
puts in evidence that get_ticks is called before timer initialization.
Fix it by initializing timer before relocation.
Signed-off-by: Patrice Chotard
---
arch/arm/dts/stm32429i-eval-u-boot.dtsi | 4
- Sync STM32 MCU's DT with kernel v5.10-rc1
- Fix typo
- Fix timer init
- Sync armv7-m.dtsi with kernel v5.10-rc1
Patrice Chotard (4):
ARM: dts: sync armv7-m.dtsi with kernel v5.10-rc1
ARM: dts: stm32: DT sync with kernel v5.10-rc1 for MCU's boards
ARM: dts: stm32: Fix timer
When CONFIG_DM_REGULATOR is disabled, there are some warnings.
This patch-set is fixed them.
drivers/phy/meson-g12a-usb2.c: In function 'phy_meson_g12a_usb2_power_on':
drivers/phy/meson-g12a-usb2.c:70:35: warning: unused variable 'priv'
[-Wunused-variable]
70 | struct
Fix the potential build warning.
Signed-off-by: Jaehoon Chung
---
drivers/video/meson/meson_dw_hdmi.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/video/meson/meson_dw_hdmi.c
b/drivers/video/meson/meson_dw_hdmi.c
index 7b2ff94eba58..5d74f7f1a740 100644
---
Fix the potential build warning.
Signed-off-by: Jaehoon Chung
---
drivers/phy/meson-g12a-usb2.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/phy/meson-g12a-usb2.c b/drivers/phy/meson-g12a-usb2.c
index a1e621975867..447ce7283db2 100644
---
Hi Tom,
This PR includes the following changes for v2021.01 release:
- Add a new SMBIOS parser and enable it when booting from coreboot
- Fix up various driver names to avoid dtoc warnings
- Fully enable ACPI support on Google Chromebook Coral
- Add a way to set SMBIOS properties using the
Hardware testing of a board using the Armada 385 has shown that an
impedance threshold setting of 0x7 performs better in an eye-diagram
test than with Marvell's recommended value 0x6.
As other boards may still perform better with Marvell's reccomended value,
a configuration option is added with a
On Thu, Nov 5, 2020 at 9:32 PM Simon Glass wrote:
>
> At present there are a few Kconfig options which allow SMBIOS fields to
> be specified at build time.
>
> Not all fields are supported. Also, defining these at build-time is
> limiting since a factory system cannot insert values for particular
On Thu, Nov 5, 2020 at 9:36 PM Simon Glass wrote:
>
> Now that we can use devicetree to specify this information, drop the old
> CONFIG options.
>
> Signed-off-by: Simon Glass
> ---
>
> (no changes since v5)
>
> Changes in v5:
> - Rename smbios_add_prop_default() to smbios_add_prop()
>
> Changes
On Thu, Nov 5, 2020 at 9:32 PM Simon Glass wrote:
>
> Add a file containing defaults for these, using the existing CONFIG
> options. This file must be included with #include since it needs to
> are not passed through the C preprocessor.
it needs to be ?
>
> Enable the driver for all x86 boards
Hi,
I have checked U-boot on Odroid-C4 with v2020.10.
I found a problem about reset behavior.
In my environment,
- Boot to SD-card,
- built u-boot v2020.10 with ordoid-c4_defconfig
- Referred to doc/board/amlogic/odroid-c4.rst
If do "reset" command after run command "mmcinfo", it didn't work
On Thu, Nov 5, 2020 at 9:24 PM Simon Glass wrote:
>
> This file needs to use the global data pointer. Add the required
> declaration.
>
> This is a fixup patch for the following:
>
>09218442ca7 x86: Allow putting some tables in the bloblist
>
> Signed-off-by: Simon Glass
> ---
>
>
modify the designware_i2c_xfer function to use 1 byte per
address, it was set to 0 before which makes it think its
reading a register type. Added offset of where it is
supposed to read from. Before it was always reading from
offset 0 despite specifying the offset in the higher level
function.
A following patch introduces EFI_TCG2_PROTOCOL.
Add the required TPMv2 headers to support that and remove the (now)
redundant definitions from tpm2_tis_sandbox
Signed-off-by: Ilias Apalodimas
---
include/tpm-v2.h | 69
1 file changed, 69
Since U-boot EFI implementation is getting richer it makes sense to
add support for EFI_TCG2_PROTOCOL taking advantage of any hardware TPM
available on the device.
This is the initial implementation of the protocol which only adds
support for GetCapability(). It's limited in the newer and safer
For implementing the EFI_TCG2_PROTOCOL we need the count field returned by
the TPM when reading capabilities via tpm2_get_capability().
Adjust the implementation of the 'tpm2 get_capability' command accordingly.
Suggested-by: Heinrich Schuchardt
Signed-off-by: Ilias Apalodimas
---
Changes
W dniu 05.11.2020 o 17:49, Alper Nebi Yasak pisze:
I suspect this change in that commit (rk3399-u-boot.dtsi):
/ {
aliases {
mmc0 =
mmc1 =
pci0 =
+ spi1 =
};
Can you test adding spi0 = above that in the
During build of simple panel driver backlight is needed so let's enable
it:
aarch64-linux-gnu-ld.bfd: drivers/built-in.o: in function
`simple_panel_set_backlight':
u-boot/drivers/video/simple_panel.c:43: undefined reference to
`backlight_set_brightness'
aarch64-linux-gnu-ld.bfd:
Hi Wolfgang,
On Thu, 5 Nov 2020 at 12:10, Wolfgang Denk wrote:
>
> Dear Simon.
>
> In message
> you
> wrote:
> >
> > > > setexpr c *10 + *100
> > >
> > > I don't get it. The equivalent to "${a}${b}" would be
> > >
> > > setexpr c "*10*100"
> > >
> > > which is even simpler?
> >
> > I
I wanted to update U-Boot on my RockPro64 board from some random build
of 2020.07-rc with out of tree patches to official one. Built, flashed
and then got this:
Loading Environment from SPI Flash... Invalid bus 0 (err=-19)
*** Warning - spi_flash_probe_bus_cs() failed, using default
On 05/11/2020 20:04, Marcin Juszkiewicz wrote:
> W dniu 05.11.2020 o 17:49, Alper Nebi Yasak pisze:
>
>> I suspect this change in that commit (rk3399-u-boot.dtsi):
>>
>>> / {
>>> aliases {
>>> mmc0 =
>>> mmc1 =
>>> pci0 =
>>> +
Dear Simon.
In message
you wrote:
>
> > > setexpr c *10 + *100
> >
> > I don't get it. The equivalent to "${a}${b}" would be
> >
> > setexpr c "*10*100"
> >
> > which is even simpler?
>
> I don't see how that works. The *10 thing in my example reads a string
> out of address 10.
Ah,
On Thu, 5 Nov 2020 10:27:28 -0700
Simon Glass wrote:
> I don't see how that works. The *10 thing in my example reads a string
> out of address 10.
/o\ ah, OK, that makes sense. So setexpr can dereference strings.
I didn't know about that, I thouth the resulting string would be
"*10*100".
In some cases it is necessary to pass parameters to Linux so that it will
boot correctly. For example, the rootdev parameter is often used to
specify the root device. However the root device may change depending on
whence U-Boot loads the kernel. At present it is necessary to build up
the command
At present zimage does its own command-line processing and does not
support the 'silent console' feature. There doesn't seem to be any good
reason for this.
Add support for silent console to zimage.
Signed-off-by: Simon Glass
---
(no changes since v1)
arch/x86/lib/zimage.c | 14
At present cli_simple_process_macros() requires that the caller provide
an output buffer that is exactly CONFIG_SYS_CBSIZE bytes in length. This
makes sense since it is designed to be used from the command line. But we
also want to use it for bootargs substitution.
Update the function to allow
At present we only support updating the 'bootargs' environment
variable. Add another function to update a buffer instead. This will
allow zimage to use this feature.
Also add a lot more tests to cover various cases.
Signed-off-by: Simon Glass
---
(no changes since v1)
common/bootm.c | 18
At present only one transformation is supported: making the Linux console
silent. To prepare for adding more, convert the boolean parameter into a
flag value.
Signed-off-by: Simon Glass
---
(no changes since v1)
common/bootm.c | 8 +---
include/bootm.h | 11 +--
test/bootm.c
Use the size (including terminator) for in this function, rather than
the length. This is arguably easier to follow, with the coming
refactor.
Signed-off-by: Simon Glass
---
(no changes since v1)
common/bootm.c | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git
At present bootm_process_cmdline_env() reads the 'bootargs' variable and
then writes it back afterwards. This is painful for tests, which would
rather use a simple buffer.
It is also useful for zimage to use a buffer, since it does not actually
put the Linux command line in the bootargs variable.
At present this function returns 1 on success and 0 on failure. But in
the latter case it provides no indication of what went wrong.
If an attempt is made to delete a non-existent variable, the caller may
want to ignore this error. This happens when setting a non-existent
variable to "", for
This function will soon do more than just handle the 'silent linux'
feature. As a first step, update it to take a boolean parameter,
indicating whether or not the processing is required.
Signed-off-by: Simon Glass
---
(no changes since v1)
common/bootm.c | 20 ++--
We want to add more processing to this function. Before doing so, rename
it to bootm_process_cmdline_env(), which is more generic.
Signed-off-by: Simon Glass
---
(no changes since v1)
common/bootm.c | 4 ++--
include/bootm.h | 4 ++--
test/bootm.c| 10 +-
3 files changed, 9
At present this function fails silently on error. Update it to produce
an error code. Report this error to the user and abort the boot, since it
likely will prevent a successful start.
No tests are added at this stage, since additional refactoring is taking
place in subsequent patches.
This function currently has no tests. Export it so that we can implement
a simple test on sandbox. Use IS_ENABLED() to remove the unused code,
instead #ifdef.
Signed-off-by: Simon Glass
---
(no changes since v1)
arch/Kconfig | 1 +
common/bootm.c| 14 +-
This series adds tests to the fixup_silent_linux() function and extends
the 'zimage' command to use it.
It also adds a new string-substition feature to allow bootargs to be a
template, rather than having to build it up piece by piece with
information obtained in a build script.
It also updates
Hi Marek,
On Tue, 3 Nov 2020 at 09:30, Marek Behun wrote:
>
> On Tue, 3 Nov 2020 08:12:17 -0700
> Simon Glass wrote:
>
> > Hi Marek,
> >
> > On Sun, 1 Nov 2020 at 16:08, Marek Behun wrote:
> > >
> > > What is the purpose of + operator on strings?
> > > Can't we use setenv "${a}${b}" ?
> >
> >
Hi Wolfgang,
On Thu, 5 Nov 2020 at 09:47, Wolfgang Denk wrote:
>
> Dear Simon,
>
> In message
> you
> wrote:
> >
> > > What is the purpose of + operator on strings?
> > > Can't we use setenv "${a}${b}" ?
> >
> > Yes, that does the same thing, although it is a bit clumsy.
> >
> > setenv a *10
Hi Tom,
The following changes since commit 35b7ca768f7d826b77d5d3d6ccd6b1b8ed21f186:
arch: Move NEEDS_MANUAL_RELOC symbol to Kconfig (2020-11-04 10:13:44
-0500)
are available in the Git repository at:
git://git.denx.de/u-boot-dm.git tags/dm-pull5nov20
for you to fetch changes up to
Dear Marek,
In message <20201103173011.08e22...@nic.cz> you wrote:
>
> PS: What I think would be more useful is to add substringing
> functionality into hush, so e.g. ${a:3:5}, and pattern substitions:
> ${parameter/pattern/string} ...
No, NAK, don't.
At least not to the current imple,entation
On 05/11/2020 18:55, Marcin Juszkiewicz wrote:
> I wanted to update U-Boot on my RockPro64 board from some random build
> of 2020.07-rc with out of tree patches to official one. Built, flashed
> and then got this:
>
> Loading Environment from SPI Flash... Invalid bus 0 (err=-19)
> *** Warning -
at:
https://gitlab.denx.de/u-boot/custodians/u-boot-imx.git
tags/u-boot-imx-20201105
for you to fetch changes up to b431970e7f0ce5b83fae1502eddc3568115207ad:
board: ge: b1x5v2: Add MAINTAINERS (2020-11-04 19:47:30 +0100)
u-boot-imx
Dear Simon,
In message
you wrote:
>
> > What is the purpose of + operator on strings?
> > Can't we use setenv "${a}${b}" ?
>
> Yes, that does the same thing, although it is a bit clumsy.
>
> setenv a *10
> setenv b *100
> setenv c "${a}${b}"
>
> instead of
>
> setexpr c *10 + *100
I don't get
Dear Rasmus,
In message <8ff3b8ad-8c4e-fe99-69c8-7c174e997...@prevas.dk> you wrote:
>
> >> Not in a none standard way! Instead you can define more than one
> >> environment storage devices and load them in a board specific order
> >> (defined thorugh board specfif function env_get_location())
> >
Update the matrix table with new supported features and
new SoC features to support.
Signed-off-by: Neil Armstrong
---
doc/board/amlogic/index.rst | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/doc/board/amlogic/index.rst b/doc/board/amlogic/index.rst
index
The build instructions were buggy and changed a little since they
were written.
Signed-off-by: Neil Armstrong
---
doc/board/amlogic/khadas-vim3.rst | 9 +
doc/board/amlogic/khadas-vim3l.rst | 11 +++
2 files changed, 12 insertions(+), 8 deletions(-)
diff --git
On Fri, Oct 30, 2020 at 10:08 AM Kever Yang wrote:
>
> Hi Peter,
>
>
> Could you add you signature for this patch?
Apologies, not sure how I missed that, included below, let me know if
you want me to resend the patch instead.
Signed-off-by: Peter Robinson
>
> Thanks,
>
> - Kever
>
> On
On 05/11/2020 15:35, Jerome Brunet wrote:
>
> On Thu 05 Nov 2020 at 15:22, Neil Armstrong wrote:
>
>> Hi,
>>
>> On 05/11/2020 15:15, Jerome Brunet wrote:
>>> Add support for the Amlogic based libretech cc version 2.
>>> As version 1, it is based on the s905x SoC.
>>>
>>> Signed-off-by: Jerome
On Thu 05 Nov 2020 at 15:22, Neil Armstrong wrote:
> Hi,
>
> On 05/11/2020 15:15, Jerome Brunet wrote:
>> Add support for the Amlogic based libretech cc version 2.
>> As version 1, it is based on the s905x SoC.
>>
>> Signed-off-by: Jerome Brunet
>> ---
>> arch/arm/dts/Makefile
Hi,
On 05/11/2020 15:15, Jerome Brunet wrote:
> Add support for the Amlogic based libretech cc version 2.
> As version 1, it is based on the s905x SoC.
>
> Signed-off-by: Jerome Brunet
> ---
> arch/arm/dts/Makefile | 1 +
> ...eson-gxl-s905x-libretech-cc-v2-u-boot.dtsi
Add support for the Amlogic based libretech cc version 2.
As version 1, it is based on the s905x SoC.
Signed-off-by: Jerome Brunet
---
arch/arm/dts/Makefile | 1 +
...eson-gxl-s905x-libretech-cc-v2-u-boot.dtsi | 7 ++
configs/libretech-cc_v2_defconfig | 82
Sync the libretech cc v2 device tree from Linux v5.10-rc1
commit 3650b228f83a ("Linux 5.10-rc1")
Signed-off-by: Jerome Brunet
---
.../dts/meson-gxl-s905x-libretech-cc-v2.dts | 318 ++
1 file changed, 318 insertions(+)
create mode 100644
This patchset adds support for the Amlogic based libretech cc v2.
Like the v1, this revised platform used the s905x SoC.
Jerome Brunet (2):
arm64: dts: import libretech-cc-v2 from linux v5.10-rc1
arm64: meson: add support for libretech-cc v2
arch/arm/dts/Makefile |
Add settings and enable the default sysinfo driver so that these can come
from the device tree.
Signed-off-by: Simon Glass
Reviewed-by: Bin Meng
---
(no changes since v1)
arch/arm/dts/meson-gxbb-odroidc2-u-boot.dtsi | 23
configs/odroid-c2_defconfig | 4
Hi Bin,
On Thu, 5 Nov 2020 at 01:43, Bin Meng wrote:
>
> Hi Simon,
>
> On Thu, Nov 5, 2020 at 2:56 PM Bin Meng wrote:
> >
> > On Thu, Nov 5, 2020 at 12:57 AM Simon Glass wrote:
> > >
> > > This series adds various minor features and tweaks to allow Coral to boot
> > > into Chrome OS from
Now that we can use devicetree to specify this information, drop the old
CONFIG options.
Signed-off-by: Simon Glass
---
(no changes since v5)
Changes in v5:
- Rename smbios_add_prop_default() to smbios_add_prop()
Changes in v3:
- Add onto the sysinfo binding
configs/clearfog_gt_8k_defconfig
Add a file containing defaults for these, using the existing CONFIG
options. This file must be included with #include since it needs to
are not passed through the C preprocessor.
Enable the driver for all x86 boards that generate SMBIOS tables. Disable
it for coral since it has its own driver.
This uclass is intended to provide a way to obtain information about a
U-Boot board. But the concept of a U-Boot 'board' is the whole system,
not just one circuit board, meaning that 'board' is something of a
misnomer for this uclass.
In addition, the name 'board' is a bit overused in U-Boot and
Add settings and enable the default sysinfo driver so that these can come
from the device tree.
Signed-off-by: Simon Glass
Reviewed-by: Bin Meng
---
(no changes since v1)
arch/arm/dts/armada-3720-uDPU-u-boot.dtsi | 20
configs/uDPU_defconfig| 3 ++-
Add settings and enable the default sysinfo driver so that these can come
from the device tree.
Signed-off-by: Simon Glass
Reviewed-by: Bin Meng
---
(no changes since v1)
.../dts/imx6ull-myir-mys-6ulx-eval-u-boot.dts | 25 +++
configs/myir_mys_6ulx_defconfig |
Add settings and enable the default sysinfo driver so that these can come
from the device tree.
Signed-off-by: Simon Glass
Reviewed-by: Bin Meng
---
(no changes since v1)
arch/arm/dts/rk3328-roc-cc-u-boot.dtsi| 21 +
arch/arm/dts/rk3328-rock-pi-e-u-boot.dtsi | 23
Add settings and enable the default sysinfo driver so that these can come
from the device tree.
Signed-off-by: Simon Glass
Reviewed-by: Bin Meng
---
(no changes since v5)
Changes in v5:
- Move the Kconfig comment into the devicetree
arch/x86/dts/galileo.dts| 28
Add a simple binding file for this, so that it is clear what this binding
directory is for.
Signed-off-by: Simon Glass
Reviewed-by: Bin Meng
---
(no changes since v5)
Changes in v5:
- Fix up the example for the binding
doc/device-tree-bindings/sysinfo/sysinfo.txt | 19 +++
1
Add information about how to set SMBIOS properties using the devicetree.
Signed-off-by: Simon Glass
Reviewed-by: Bin Meng
---
(no changes since v1)
doc/arch/x86.rst| 8 +++
doc/device-tree-bindings/sysinfo/smbios.txt | 77 +
2 files changed,
Some boards want to specify the manufacturer or product name but do not
need to have their own sysinfo driver.
Add a default driver which provides a way to specify this SMBIOS
information in the devicetree, without needing any board-specific
functionality.
Signed-off-by: Simon Glass
At present there are a few Kconfig options which allow SMBIOS fields to
be specified at build time.
Not all fields are supported. Also, defining these at build-time is
limiting since a factory system cannot insert values for particular boards
or models without rebuilding U-Boot.
This series adds
The current tables only support a subset of the available fields defined
by the SMBIOS spec. Add a few more.
We could use CONFIG_SYS_CPU or CONFIG_SYS_SOC as a default for family, but
the meaning of that value relates more to the whole system rather than
just the SoC.
Signed-off-by: Simon Glass
Support a way to put SMBIOS properties in the device tree. These can be
placed in a 'board' device in an 'smbios' subnode.
Signed-off-by: Simon Glass
Reviewed-by: Bin Meng
---
(no changes since v5)
Changes in v5:
- Fix "manufactuer" typo
- Fix "Informaiton" typo
Changes in v4:
- Fix build
As a first step to obtaining SMBIOS information from the devicetree, add
an ofnode parameter to the writing functions.
Signed-off-by: Simon Glass
Reviewed-by: Bin Meng
---
(no changes since v2)
Changes in v2:
- Move dm.h header file to avoid build error on qemu-arm
- Deal with boards that
This file needs to use the global data pointer. Add the required
declaration.
This is a fixup patch for the following:
09218442ca7 x86: Allow putting some tables in the bloblist
Signed-off-by: Simon Glass
---
arch/x86/lib/tables.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
Hi Bin,
On Wed, 4 Nov 2020 at 23:49, Bin Meng wrote:
>
> Hi Simon,
>
> On Wed, Nov 4, 2020 at 11:23 PM Simon Glass wrote:
> >
> > Now that we can use devicetree to specify this information, drop the old
> > CONFIG options.
> >
> > Signed-off-by: Simon Glass
> > ---
> >
> > Changes in v5:
> > -
On 05.11.20 10:28, Holger Brunck wrote:
This was used for a board which is not supproted anymore and can
therefore be dropped.
CC: Stefan Roese
Signed-off-by: Holger Brunck
Reviewed-by: Stefan Roese
Thanks,
Stefan
From: Biwen Li
Read PFE ESBC header flash with spi_flash_read API
- logs as follows,
Net: SF: Detected s25fs512s with page size 256 Bytes, erase size 256
KiB, total 64 MiB
"Synchronous Abort" handler, esr 0x96000210
elr: 8206db44 lr : 82004ea0 (reloc)
elr:
This series add a support of tracing for RISC-V arch.
This series is also available here [1] for testing.
[1] https://github.com/pragnesh26992/u-boot/tree/trace
How to test this patch:
1) Enable tracing in "configs/sifive_fu540_defconfig"
CONFIG_TRACE=y
CONFIG_TRACE_BUFFER_SIZE=0x0100
Add timer_get_us() which is useful for tracing.
For S-mode U-Boot, CSR_TIMEH and CSR_TIME will provide
a timer ticks and For M-mode U-Boot, mtime register will
provide the same.
Signed-off-by: Pragnesh Patel
---
drivers/timer/andes_plmt_timer.c | 16 +++-
This series add a support of tracing for RISC-V arch.
This series is also available here [1] for testing.
[1] https://github.com/pragnesh26992/u-boot/tree/trace
How to test this patch:
1) Enable tracing in "configs/sifive_fu540_defconfig"
CONFIG_TRACE=y
CONFIG_TRACE_BUFFER_SIZE=0x0100
Add timer_get_us() which is useful for tracing.
For S-mode U-Boot, CSR_TIMEH and CSR_TIME will provide
a timer ticks and For M-mode U-Boot, mtime register will
provide the same.
Signed-off-by: Pragnesh Patel
---
drivers/timer/andes_plmt_timer.c | 16 +++-
Hi Marek,
Thank you for the review.
On Wed, Nov 4, 2020 at 7:29 PM Marek Vasut wrote:
>
> On 11/4/20 6:27 PM, Lad Prabhakar wrote:
> > Update pin type after every successful call to sh_pfc_config_mux().
> >
> > This fixes pin functionality from being overwritten.
>
> Can you please provide more
Hi,
On 11/5/20 11:46 AM, AKASHI Takahiro wrote:
> Hi Oleksandr,
>
> On Thu, Nov 05, 2020 at 09:18:39AM +, Oleksandr Andrushchenko wrote:
>> Hello,
>>
>> On 11/4/20 7:24 AM, AKASHI Takahiro wrote:
>>> sbsa-uart is a virtual UART device with a sub-set of PL011 functionality
>>> which is
Hi Heinrich,
On Thu, Nov 5, 2020 at 4:55 PM Heinrich Schuchardt wrote:
>
> On 05.11.20 09:16, Bin Meng wrote:
> > From: Bin Meng
> >
> > SPL_RAM_SUPPORT and SPL_RAM_DEVICE are only visible in an SPL config.
>
> 'if SPL' would only be required if you would use 'select'. With 'imply'
> the
Hi Oleksandr,
On Thu, Nov 05, 2020 at 09:18:39AM +, Oleksandr Andrushchenko wrote:
> Hello,
>
> On 11/4/20 7:24 AM, AKASHI Takahiro wrote:
> > sbsa-uart is a virtual UART device with a sub-set of PL011 functionality
> > which is described in SBSA (Server Base System Architecture)[1].
> >
> >
This was used for a board which is not supproted anymore and can
therefore be dropped.
CC: Stefan Roese
Signed-off-by: Holger Brunck
---
include/configs/km/keymile-common.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/include/configs/km/keymile-common.h
Hello,
On 11/4/20 7:24 AM, AKASHI Takahiro wrote:
> sbsa-uart is a virtual UART device with a sub-set of PL011 functionality
> which is described in SBSA (Server Base System Architecture)[1].
>
> It mainly targets for server use, but sbsa-uart itself is useful in any
> para-virtualized use cases,
On 05.11.20 10:15, Holger Brunck wrote:
This option is obsolete since 2009 and can be removed globally.
CC: Stefan Roese
Signed-off-by: Holger Brunck
Reviewed-by: Stefan Roese
Thanks,
Stefan
---
include/configs/ethernut5.h | 1 -
include/configs/km/km-powerpc.h | 2 --
This option is obsolete since 2009 and can be removed globally.
CC: Stefan Roese
Signed-off-by: Holger Brunck
---
include/configs/ethernut5.h | 1 -
include/configs/km/km-powerpc.h | 2 --
include/configs/kmp204x.h | 3 ---
include/configs/pm9263.h| 1 -
spl_handoff should only be enabled when CONFIG_HANDOFF is set. Drop the
nested ifdefs and check for CONFIG_HANDOFF instead.
Signed-off-by: Ovidiu Panait
---
include/asm-generic/global_data.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Wed, 2020-11-04 at 17:18 +0100, Sebastian Reichel wrote:
> This updates the PPD MAINTAINERS file doing a couple of changes:
>
> * Replace Martyn with myself, since he no longer has the hardware
>available and add Ian Ray as maintainer
> * Fix the board directory path, which was still
Add a return value to bb_miiphy_init and use it directly in the
post-relocation init sequence, rather than using a wrapper stub.
Signed-off-by: Ovidiu Panait
---
common/board_r.c | 10 +-
drivers/net/phy/miiphybb.c | 4 +++-
include/miiphy.h | 2 +-
3 files
Add a return value to xen_init and use it directly in the
post-relocation init sequence, rather than using a wrapper stub.
Signed-off-by: Ovidiu Panait
---
common/board_r.c | 10 +-
drivers/xen/hypervisor.c | 4 +++-
include/xen.h| 2 +-
3 files changed, 5
In order to remove the arch-specific ifdefs around initr_trap, introduce
arch_initr_trap weak initcall. Implementations for ppc/m68k/mips have
been moved to arch//lib/traps.c
Default implementation is a nop stub.
Signed-off-by: Ovidiu Panait
---
arch/m68k/lib/traps.c | 7 +++
CONFIG_HANDOFF is used in u-boot proper to locate handoff info from SPL
during pre-relocation init (in setup_spl_handoff). Add explicit dependency
on CONFIG_SPL, to fix the following build error when CONFIG_HANDOFF &&
!CONFIG_SPL:
common/board_f.c: In function ‘setup_spl_handoff’:
Add a return value to api_init and use it directly in the
post-relocation init sequence, rather than using a wrapper stub.
Signed-off-by: Ovidiu Panait
---
api/api.c | 6 --
api/api_private.h | 2 +-
common/board_r.c | 11 +--
include/api.h | 2 +-
4 files changed, 7
Add a return value to noncached_init and use it directly in the
post-relocation init sequence, rather than using a wrapper stub.
Signed-off-by: Ovidiu Panait
---
arch/arm/include/asm/system.h | 2 +-
arch/arm/lib/cache.c | 4 +++-
common/board_r.c | 10 +-
3
Add a return value to jumptable_init and use it directly in the
post-relocation init sequence, rather than using a wrapper stub.
Signed-off-by: Ovidiu Panait
---
common/board_r.c | 8 +---
common/exports.c | 4 +++-
include/exports.h | 2 +-
3 files changed, 5 insertions(+), 9
1 - 100 of 121 matches
Mail list logo
