On 05.03.21 21:03, Phil Sutter wrote:
With the recent fixes in pci_mvebu and xhci-pci drivers, the two rear
USB3 ports are finally usable and accessing them no longer hangs the
system. Moreover, if Linux is booted without a prior call to 'pci enum'
and 'usb start', the HCD is detected but attache
* enable storing the environment in the SPI flash
* enable EXT4 and FAT file system
* enable hush shell
* run k210_bootcmd as default boot command
Signed-off-by: Heinrich Schuchardt
---
configs/sipeed_maix_smode_defconfig | 11 +++
1 file changed, 11 insertions(+)
diff --git a/configs/s
Dear Tom,
Please find my pull-request for u-boot-fsl-qoriq/master
https://github.com/u-boot/u-boot/pull/54/checks
Summary
Convert qemu-ppce500 to driver model and enable additional driver support
bug fixes/updates in net-dsa driver, vid driver, move configs to kconfig
Update Maintainers of some
On Fri, Mar 5, 2021 at 9:03 PM Adam Ford wrote:
>
> On Fri, Mar 5, 2021 at 11:10 AM Adam Ford wrote:
> >
> > On Fri, Mar 5, 2021 at 6:31 AM Stefan Roese wrote:
> > >
> > > On 05.03.21 12:25, Adam Ford wrote:
> > > > On Thu, Mar 4, 2021 at 4:33 PM Marek Behun wrote:
> > > >>
> > > >> On Thu, 4 M
On Sat, Mar 06, 2021 at 09:55:40AM +, Priyanka Jain wrote:
> Dear Tom,
>
>
> Please find my pull-request for u-boot-fsl-qoriq/master
> https://github.com/u-boot/u-boot/pull/54/checks
>
> Summary
> Convert qemu-ppce500 to driver model and enable additional driver support
> bug fixes/updates
Ping?
On Mon, Feb 22, 2021 at 10:15:34AM +0100, Roger Pau Monné wrote:
> On Wed, Feb 17, 2021 at 02:08:55PM +0100, Heiko Stuebner wrote:
> > Hi Tom,
> >
> > Am Mittwoch, 17. Februar 2021, 03:21:25 CET schrieb Tom Rini:
> > > I would say that yes, it's quite intentional that all boards for a given
On 3/6/21 2:18 AM, Heinrich Schuchardt wrote:
On 3/5/21 12:50 AM, Sean Anderson wrote:
On 3/4/21 12:00 PM, Heinrich Schuchardt wrote:
Provide sysreset driver using the SBI system reset extension.
Signed-off-by: Heinrich Schuchardt
---
MAINTAINERS | 1 +
arch/riscv/inc
On Sat, 6 Mar 2021 05:12:12 -0600
Adam Ford wrote:
> On Fri, Mar 5, 2021 at 9:03 PM Adam Ford wrote:
> >
> > On Fri, Mar 5, 2021 at 11:10 AM Adam Ford wrote:
> > >
> > > On Fri, Mar 5, 2021 at 6:31 AM Stefan Roese wrote:
> > > >
> > > > On 05.03.21 12:25, Adam Ford wrote:
> > > > > On Th
Dne četrtek, 04. marec 2021 ob 02:41:45 CET je Andre Przywara napisal(a):
> On Tue, 23 Feb 2021 21:46:16 +0100
>
> Jernej Skrabec wrote:
> > Code which searches for valid detailed timing entry will be used in more
> > places. Extract it.
> >
> > Signed-off-by: Jernej Skrabec
> > ---
> >
> > c
This series greatly reworks DE2 mixer and accompanying DW-HDMI platform
driver. Main goal was to use as many information from device tree as
possible and thus removing SoC speficic ifdefs from the code. This was
largely accomplished for mixer, HDMI and HDMI PHY driver.
Most of these changes are no
Currently sunxi Makefile manually specifies full path to dw-hdmi common
code. However, that is not needed because it can be selected in Kconfig
instead.
Select proper symbol in Kconfig and drop path from Makefile.
Reviewed-by: Andre Przywara
Signed-off-by: Jernej Skrabec
---
arch/arm/mach-sunx
Currently driver accepts all resolution which won't work on 4k screens.
Add validation callback which limits acceptable resolutions to 297 MHz.
Reviewed-by: Andre Przywara
Signed-off-by: Jernej Skrabec
---
drivers/video/sunxi/sunxi_dw_hdmi.c | 7 +++
1 file changed, 7 insertions(+)
diff --
When searching for detailed timing in EDID, check for digital display
earlier. There is no point parsing other parameters if this flag is not
present.
Reviewed-by: Andre Przywara
Signed-off-by: Jernej Skrabec
---
common/edid.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff
Code which searches for valid detailed timing entry will be used in more
places. Extract it.
No functional change is made. However, descriptors are casted to
edid_detailed_timing instead of edid_monitor_descriptor. Descriptor can
be of either type, but since we're interested only in DTD, it is mor
One of my monitors have only 4k@60 timing in base EDID block which is
out of range for devices with HDMI 1.4. It turns out that it has
additional detailed timings in CTA-861 Extension Block and two of them
are appropriate for HDMI 1.4.
Add additional search for valid detailed timing in extension b
It turns out that there are two ways how hot plug detection can be done.
One is standard way for DW HDMI controller - checking bit 2 in 0x3004
register. Another way is applicable only to Allwinner custom PHY - by
checking bit 19 in register 0x10038. Both method are equally good as far
as we know.
No Allwinner board with DW-HDMI controller use separate I2C bus for
EDID read. Remove that check.
Reviewed-by: Andre Przywara
Signed-off-by: Jernej Skrabec
---
drivers/video/sunxi/sunxi_dw_hdmi.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/video/sunxi/sunxi_dw_hdmi.c
b/driver
TV driver was never fully implemented. Remove search for it from DE2
driver.
Signed-off-by: Jernej Skrabec
---
drivers/video/sunxi/sunxi_de2.c | 15 +--
1 file changed, 1 insertion(+), 14 deletions(-)
diff --git a/drivers/video/sunxi/sunxi_de2.c b/drivers/video/sunxi/sunxi_de2.c
ind
Currently DE2 driver uses functions which are defined in internal
headers. They are not meant to be used outside of uclass framework.
Switch DE2 driver to public ones. This has additional benefit that
device_probe doesn't need to be called manually.
Signed-off-by: Jernej Skrabec
---
drivers/vide
Currently sunxi dw-hdmi driver is probed unconditionally, even if there
is no such device.
Switch driver to probing via compatible string. This brings many
benefits - driver can read DT node and allows driver to be always
enabled.
Signed-off-by: Jernej Skrabec
---
drivers/video/sunxi/sunxi_dw_h
Currently HDMI controller MMIO address is hardcoded. Change that so
address is read from DT node. That will make adding support for new
variants a bit easier.
Signed-off-by: Jernej Skrabec
---
drivers/video/sunxi/sunxi_dw_hdmi.c | 38 ++---
1 file changed, 24 insertions(+
Currently DE2 driver is probed via driver info. Switch probing to device
tree compatible string method.
Display is now searched via driver name which has same limitation as
previous method. This can be improved only when all drivers in chain are
probed via device tree compatible strings.
Signed-o
Currently DE2 uses hardcoded address based on SoC for which U-Boot is
built. Read it from DT instead so there is no need to specify it when
support for new SoC is added.
Signed-off-by: Jernej Skrabec
---
drivers/video/sunxi/sunxi_de2.c | 8
1 file changed, 4 insertions(+), 4 deletions(-
These clocks and resets are needed for video drivers.
Cc: Lukasz Majewski
Signed-off-by: Jernej Skrabec
---
drivers/clk/sunxi/clk_a64.c | 12
drivers/clk/sunxi/clk_h3.c | 12
2 files changed, 24 insertions(+)
diff --git a/drivers/clk/sunxi/clk_a64.c b/drivers/clk/sun
Video driver currently manages clocks and resets by directly writing to
registers. This is already a bit messy because each SoC has some
specifics. It's much better to implement proper clock and reset driver
which takes information from device tree file.
Note that this driver is not perfect yet. I
Now that proper DM clock and reset driver exists for Display Engine 2
and 3, remove all clock and reset related code and use appropriate
framework instead.
Signed-off-by: Jernej Skrabec
---
arch/arm/mach-sunxi/Kconfig | 1 +
drivers/video/sunxi/sunxi_de2.c | 67 +++--
Currently PHY init callback has only pixel clock as a parameter, but
other timing parameters may be needed for custom PHYs. Modify callback
signature to include full timings.
Cc: Neil Armstrong
Signed-off-by: Jernej Skrabec
---
drivers/video/dw_hdmi.c | 6 +++---
drivers/video/meson
This commit adds standalone driver for DW HDMI PHY. It deprecates code
which is included in sunxi dw-hdmi platform driver.
Signed-off-by: Jernej Skrabec
---
arch/arm/mach-sunxi/Kconfig | 1 +
drivers/video/sunxi/Makefile| 2 +-
drivers/video/sunxi/sunxi_dw_hdmi_phy.c
Remove direct PHY managing from dw-hdmi platform driver and use
dedicated driver instead. While at it, enable clocks and deassert reset
lines through clk and reset framework instead of manually configuring
bits.
Signed-off-by: Jernej Skrabec
---
drivers/video/sunxi/sunxi_dw_hdmi.c | 225 +---
On Sat, Mar 06, 2021 at 06:37:49PM +0100, Marek Behun wrote:
> On Sat, 6 Mar 2021 05:12:12 -0600
> Adam Ford wrote:
>
> > On Fri, Mar 5, 2021 at 9:03 PM Adam Ford wrote:
> > >
> > > On Fri, Mar 5, 2021 at 11:10 AM Adam Ford wrote:
> > > >
> > > > On Fri, Mar 5, 2021 at 6:31 AM Stefan Roese w
On Fri, Mar 05, 2021 at 07:35:24AM -0700, Simon Glass wrote:
> Hi,
>
> On Fri, 5 Mar 2021 at 07:33, Stefan Herbrechtsmeier
> wrote:
> >
> > Hi Eugeniu,
> >
> > Am 05.03.2021 um 12:52 schrieb Eugeniu Rosca:
> > > Hello Stefan,
> > >
> > > On Fri, Mar 05, 2021 at 07:39:04AM +, Stefan Herbrechts
On Saturday 06 March 2021 15:08:13 Tom Rini wrote:
> Perhaps we'll default to yes on some SoCs. The omap3 thing is a bit
> odd, but we'll see what happens on real N900 hardware.
Hello!
Could you send me a link to git repo / branch and tell me from which
commit should I do tests on real N900 hard
For systems where SPL loads fitImage, i.e. CONFIG_SPL_LOAD_FIT=y, use
u-boot.itb in the relevant documentation parts. Otherwise use u-boot.img.
Signed-off-by: Marek Vasut
Cc: Patrice Chotard
Cc: Patrick Delaunay
---
doc/board/st/stm32mp1.rst | 16 +++-
1 file changed, 11 insertions
On Sat, 6 Mar 2021 21:41:14 +0100
Pali Rohár wrote:
> On Saturday 06 March 2021 15:08:13 Tom Rini wrote:
> > Perhaps we'll default to yes on some SoCs. The omap3 thing is a bit
> > odd, but we'll see what happens on real N900 hardware.
>
> Hello!
>
> Could you send me a link to git repo / br
On Saturday 06 March 2021 21:54:00 Marek Behun wrote:
> On Sat, 6 Mar 2021 21:41:14 +0100
> Pali Rohár wrote:
>
> > On Saturday 06 March 2021 15:08:13 Tom Rini wrote:
> > > Perhaps we'll default to yes on some SoCs. The omap3 thing is a bit
> > > odd, but we'll see what happens on real N900 hard
On Sat, 6 Mar 2021 22:00:45 +0100
Pali Rohár wrote:
> On Saturday 06 March 2021 21:54:00 Marek Behun wrote:
> > On Sat, 6 Mar 2021 21:41:14 +0100
> > Pali Rohár wrote:
> >
> > > On Saturday 06 March 2021 15:08:13 Tom Rini wrote:
> > > > Perhaps we'll default to yes on some SoCs. The omap3
On Fri, 5 Mar 2021 08:37:28 -0500
Tom Rini wrote:
> On Fri, Mar 05, 2021 at 09:34:42PM +0800, Bin Meng wrote:
> > Hi Marek,
> >
> > On Fri, Mar 5, 2021 at 2:17 AM Marek Behun wrote:
> > >
> > > On Thu, 4 Mar 2021 18:57:11 +0800
> > > Bin Meng wrote:
> > >
> > > > Hi Marek,
> > > >
> > > >
On Saturday 06 March 2021 22:19:22 Marek Behun wrote:
> On Sat, 6 Mar 2021 22:00:45 +0100
> Pali Rohár wrote:
>
> > On Saturday 06 March 2021 21:54:00 Marek Behun wrote:
> > > On Sat, 6 Mar 2021 21:41:14 +0100
> > > Pali Rohár wrote:
> > >
> > > > On Saturday 06 March 2021 15:08:13 Tom Rini w
On 3/6/21 12:59 AM, Bin Meng wrote:
On Fri, Mar 5, 2021 at 1:02 AM Heinrich Schuchardt wrote:
Add the System Reset Extension and the Hart State Management Extension
definitions.
Add missing RFENCE Extension enum values.
The SBI 0.1 extension constants are needed for for the sbi command. Remo
On Sat, 6 Mar 2021 22:38:52 +0100
Pali Rohár wrote:
> On Saturday 06 March 2021 22:19:22 Marek Behun wrote:
> > On Sat, 6 Mar 2021 22:00:45 +0100
> > Pali Rohár wrote:
> >
> > > On Saturday 06 March 2021 21:54:00 Marek Behun wrote:
> > > > On Sat, 6 Mar 2021 21:41:14 +0100
> > > > Pali Rohá
On 3/6/21 3:20 AM, Heinrich Schuchardt wrote:
* enable storing the environment in the SPI flash
* enable EXT4 and FAT file system
* enable hush shell
* run k210_bootcmd as default boot command
Signed-off-by: Heinrich Schuchardt
---
configs/sipeed_maix_smode_defconfig | 11 +++
1 file
Signed-off-by: Pali Rohár
---
This patch increase u-boot.bin binary size above maximal limit. So this
patch cannot be applied yet. But it can be applied on top of the LTO
patches. So please put this patch into the queue and include it into
U-Boot after LTO patches are merged.
---
configs/nokia_rx
The api_public.h header file undefined macro CONFIG_SYS_64BIT_LBA.
But api/api_storage.c includes this header before including part.h,
causing the type of lbaint_t and subsequently the type signature of
blk_dread() and blk_dwrite() functions to change from the rest of U-Boot
(if CONFIG_SYS_64BIT_L
It seems like commit:
3f04db891a353f4b127ed57279279f851c6b4917 image: Check for unit addresses in FIT
Broke test/image/test-imagetools.sh.
I get the impression test-imagetools.sh is more-or-less unmaintained and
deprecated. Does test-imagetools.sh perform tests that are not covered
elsewhere? If
The arrays `pbs_dq_mapping`, `div_ratio1to1` and `div_ratio2to1` have
different bounds declared in header files where these variables are also
defined from the ones declared in source files.
This causes the compiler to complain (when building with LTO):
ddr3_sdram.c:24:12: warning: type of ‘pbs_
For some reason when building SPL for ARMv8 with LTO, the relocation
information is not discarded.
Discard it explicitly in the linker script.
This fixes LTO build for imx8mm_venice_defconfig.
Signed-off-by: Marek Behún
---
arch/arm/cpu/armv8/u-boot-spl.lds | 1 +
1 file changed, 1 insertion(+
Hello Tim,
you are listed as maintainer of i.MX8MM Venice board in U-Boot.
I am currently working on LTO support for U-Boot, and I have
encountered a problem with i.MX8MM Venice board:
when LTO is enabled, the linking process for SPL does not throw away
relocation information, making the resultin
Hello Tom,
I seem to run into an error on Azure's CI for U-Boot that I cannot
reproduce locally.
It concerns my LTO work https://github.com/u-boot/u-boot/pull/57
The test
u-boot.u-boot (test.py xilinx_zynq_virt)
is failing with this log
https://dev.azure.com/u-boot/a1096300-2999-4ec4-a21a-4c22
On Sat, 6 Mar 2021 20:54:22 +0100
Jernej Skrabec wrote:
> Code which searches for valid detailed timing entry will be used in more
> places. Extract it.
>
> No functional change is made. However, descriptors are casted to
> edid_detailed_timing instead of edid_monitor_descriptor. Descriptor can
On Sat, 6 Mar 2021 20:54:24 +0100
Jernej Skrabec wrote:
> It turns out that there are two ways how hot plug detection can be done.
> One is standard way for DW HDMI controller - checking bit 2 in 0x3004
> register. Another way is applicable only to Allwinner custom PHY - by
> checking bit 19 in
On Sat, 6 Mar 2021 20:54:26 +0100
Jernej Skrabec wrote:
> TV driver was never fully implemented. Remove search for it from DE2
> driver.
Correct, there is no driver in the tree which would match this string.
> Signed-off-by: Jernej Skrabec
Reviewed-by: Andre Przywara
Cheers,
Andre
> ---
>
On Sat, 6 Mar 2021 20:54:27 +0100
Jernej Skrabec wrote:
> Currently DE2 driver uses functions which are defined in internal
> headers. They are not meant to be used outside of uclass framework.
> Switch DE2 driver to public ones. This has additional benefit that
> device_probe doesn't need to be
On Sat, 6 Mar 2021 20:54:28 +0100
Jernej Skrabec wrote:
> Currently sunxi dw-hdmi driver is probed unconditionally, even if there
> is no such device.
>
> Switch driver to probing via compatible string. This brings many
> benefits - driver can read DT node and allows driver to be always
> enabl
Thanks a lot Sean!
I tried to enable logging by using the following CONFIG_:
```
CONFIG_LOG=y
CONFIG_SPL_LOG=y
CONFIG_TPL_LOG=y
CONFIG_LOG_MAX_LEVEL=5
CONFIG_SPL_LOG_MAX_LEVEL=3
CONFIG_TPL_LOG_MAX_LEVEL=3
CONFIG_LOG_DEFAULT_LEVEL=7
CONFIG_LOG_CONSOLE=y
CONFIG_SPL_LOG_CONSOLE=y
CONFIG_TPL_LOG_CONS
On 3/6/21 8:38 PM, Jonas Vautherin wrote:
Thanks a lot Sean!
I tried to enable logging by using the following CONFIG_:
```
CONFIG_LOG=y
CONFIG_SPL_LOG=y
CONFIG_TPL_LOG=y
CONFIG_LOG_MAX_LEVEL=5
You need to increase this. Log levels are only compiled-in if they are
less than the max log level.
[sorry for the spam, I accidentally sent this e-mail from my personal
address]
Hello Tim,
you are listed as maintainer of i.MX8MM Venice board in U-Boot.
I am currently working on LTO support for U-Boot, and I have
encountered a problem with i.MX8MM Venice board:
when LTO is enabled, the linking
On Sun, Mar 07, 2021 at 02:27:33AM +0100, Marek Behun wrote:
> Hello Tom,
>
> I seem to run into an error on Azure's CI for U-Boot that I cannot
> reproduce locally.
>
> It concerns my LTO work https://github.com/u-boot/u-boot/pull/57
>
> The test
> u-boot.u-boot (test.py xilinx_zynq_virt)
>
On Sat, 6 Mar 2021 21:11:34 -0500
Tom Rini wrote:
> On Sun, Mar 07, 2021 at 02:27:33AM +0100, Marek Behun wrote:
>
> > Hello Tom,
> >
> > I seem to run into an error on Azure's CI for U-Boot that I cannot
> > reproduce locally.
> >
> > It concerns my LTO work https://github.com/u-boot/u-boot/p
On Fri, 5 Mar 2021 18:21:51 +0100
Heinrich Schuchardt wrote:
> On 05.03.21 16:37, Marek Behun wrote:
> > On Fri, 5 Mar 2021 11:00:45 +0800
> > Bin Meng wrote:
> >
> >> On Wed, Mar 3, 2021 at 12:13 PM Marek Behún wrote:
> >>>
> >>> When building with LTO, the system libc's `errno` variable u
On Sat, Mar 6, 2021 at 3:49 PM Marek Behun wrote:
>
> On Sat, 6 Mar 2021 22:38:52 +0100
> Pali Rohár wrote:
>
> > On Saturday 06 March 2021 22:19:22 Marek Behun wrote:
> > > On Sat, 6 Mar 2021 22:00:45 +0100
> > > Pali Rohár wrote:
> > >
> > > > On Saturday 06 March 2021 21:54:00 Marek Behun wro
try_unlock_memory() is only used in one file, so make it static
in that file and remove it from the sys_proto header file. This
may help with some further optimization in the future.
Signed-off-by: Adam Ford
diff --git a/arch/arm/include/asm/arch-omap3/sys_proto.h
b/arch/arm/include/asm/arch-om
Hi Bin, Simon,
On 21/03/05 10:03:p, Bin Meng wrote:
> On Fri, Mar 5, 2021 at 10:31 PM Simon Glass wrote:
> > If I previously reviewed it you can add my tag.
I wasn't sure of the correct etiquette when a large rearrangement of the
patches had been done; I'll keep this in mind.
> > I think sandbo
This series moves the QFW driver into a uclass, UCLASS_QFW, and splits
the driver into qfw_pio and qfw_mmio. Each driver is selected on the
appropriate QEMU board. A sandbox driver is also added, and a DM unit
test against that driver. The qfw command is tested in QEMU, and
documentation added.
We move qfw into its own uclass and split the PIO functions into a
specific driver for that uclass. The PIO driver is selected in the
qemu-x86 board config (this covers x86 and x86_64).
include/qfw.h is cleaned up and documentation added.
Signed-off-by: Asherah Connor
---
Changes in v6:
* San
A sandbox driver and test are added for the qfw uclass, and a test in
QEMU added for qfw functionality to confirm it doesn't break in real
world use.
Signed-off-by: Asherah Connor
Reviewed-by: Simon Glass
---
(no changes since v1)
drivers/misc/Makefile | 1 +
drivers/misc/qfw_sandbox.c
Add MMIO driver for QFW.
Note that there is no consumer as of this patch.
Signed-off-by: Asherah Connor
---
(no changes since v5)
Changes in v5:
* Split MMIO driver into its own commit.
* Add CONFIG_QFW_MMIO for selection by arch/board.
drivers/misc/Kconfig| 7 +++
drivers/misc/Makefil
Select CMD_QFW and QFW_MMIO in the qemu-arm board (covers arm and
arm64).
Signed-off-by: Asherah Connor
---
(no changes since v5)
Changes in v5:
* Split adding MMIO driver to QEMU arm/64 into own commit.
* Use the generic qemu-arm board config rather than adding to multiple
defconfigs.
boa
secureworld_exit() is only used in one file, so make it static
to that file and remove it from sys_proto.h. This
may help with some further optimization in the future.
Signed-off-by: Adam Ford
diff --git a/arch/arm/include/asm/arch-omap3/sys_proto.h
b/arch/arm/include/asm/arch-omap3/sys_proto.h
secure_unlock_mem() is only used in one file, so make it static
in that file. This
may help with some further optimization in the future.
Signed-off-by: Adam Ford
diff --git a/arch/arm/mach-omap2/omap3/board.c
b/arch/arm/mach-omap2/omap3/board.c
index 879b0f..74b5a4b111 100644
--- a/arch/ar
On Sat, 6 Mar 2021 21:45:02 -0600
Adam Ford wrote:
> On Sat, Mar 6, 2021 at 3:49 PM Marek Behun wrote:
> >
> > On Sat, 6 Mar 2021 22:38:52 +0100
> > Pali Rohár wrote:
> >
> > > On Saturday 06 March 2021 22:19:22 Marek Behun wrote:
> > > > On Sat, 6 Mar 2021 22:00:45 +0100
> > > > Pali Rohár
In arch/arm/mach-mvebu/dram.c we always include axp's xor.h for common
XOR definitions, regardless whether we compile for axp or a38x.
But the declaration of this function has a different signature in axp's
xor.h from the one used in a38x' implementation - one parameter is u64
instead of u32. This
Hello,
so after the RFC I am now sending first version of patches adding
support for LTO to U-Boot.
This series was tested by Github/Azure CI at
https://github.com/u-boot/u-boot/pull/57
and also by Pali Rohar and Adam Ford for some boards.
There is one test that fails and one that did not comp
This is how Linux does this now, see Linux commit 339f29d91acf.
Signed-off-by: Marek Behún
---
scripts/checkpatch.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 755f4802a4..fd1e9c4d24 100755
--- a/scripts/checkpatch.pl
+
The api_public.h header file undefined macro CONFIG_SYS_64BIT_LBA.
But api/api_storage.c includes this header before including part.h,
causing the type of lbaint_t and subsequently the type signature of
blk_dread() and blk_dwrite() functions to change from the rest of U-Boot
(if CONFIG_SYS_64BIT_L
There is a serious bug in regmap_read() and regmap_write() functions
where an uint pointer is cast to (void *) which is then cast to (u8 *),
(u16 *), (u32 *) or (u64 *), depending on register width of the map.
For example given a regmap with 16-bit register width the code
int val = 0x12340
The arrays `pbs_dq_mapping`, `div_ratio1to1` and `div_ratio2to1` have
different bounds declared in header files where these variables are also
defined from the ones declared in source files.
This causes the compiler to complain (when building with LTO):
ddr3_sdram.c:24:12: warning: type of ‘pbs_
Use UNIQUE_ID in the __ADDRESSABLE macro.
Signed-off-by: Marek Behún
---
include/linux/compiler.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/compiler.h b/include/linux/compiler.h
index 82a8a4ede9..98dd3fc4cc 100644
--- a/include/linux/compiler.h
+++ b/inclu
Prepare private macros expanding to linker list entry symbol name and
declaration to avoid nasty code repetition in the next patch.
We also avoid some code repetition in current code with these macros.
Signed-off-by: Marek Behún
---
include/linker_lists.h | 46 --
Improve the regular expression that matches unittest symbols in
u-boot.sym.
Currently we do not enforce no prefix in symbol string, but with the
soon to come change in linker lists declaring lists and entries with the
__ADDRESSABLE macro (because of LTO), the symbol file will contain for
every sym
This commit does the same thing as Linux commit 33def8498fdd.
Use a more generic form for __section that requires quotes to avoid
complications with clang and gcc differences.
Remove the quote operator # from compiler_attributes.h __section macro.
Convert all unquoted __section(foo) uses to quot
Use the __ADDRESSABLE() macro to make entries and lists declared by
ll_entry_declare() and ll_entry_declare_list() addressable so that when
building with LTO the compiler does not optimize this data away.
Signed-off-by: Marek Behún
---
include/linker_lists.h | 8 ++--
1 file changed, 6 inser
Use the `externally_visible` attribute to declare binman symbols
externally visible, so that when building with LTO the compiler does not
optimize this data away.
Signed-off-by: Marek Behún
---
include/binman_sym.h | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/include/
It seems that sometimes (happening on ARM64, for example with
turris_mox_defconfig) GCC, when linking with LTO, changes the symbol
names of some functions, for example lib/string.c's memcpy() function to
memcpy.isra.0.
This is a problem however when GCC for a code such as this:
struct some
When linking with LTO, the compiler complains about type mismatch of
variables `__efi_runtime_start`, `__efi_runtime_stop`,
`__efi_runtime_rel_start` and `__efi_runtime_rel_stop`:
include/efi_loader.h:218:21: warning: type of ‘__efi_runtime_start’
does not m
Indent the linking commands so that they look cosmetically better.
Signed-off-by: Marek Behún
---
Makefile | 12 +++-
scripts/Makefile.spl | 15 +--
2 files changed, 16 insertions(+), 11 deletions(-)
diff --git a/Makefile b/Makefile
index 68ce5195b2..7b0ba9df9a 1
When compiling with LTO, the compiler fails with an error saying that
`crc_table` causes a section type conflict with `efi_var_buf`.
This is because both are declared to be in the same section (via macro
`__efi_runtime_data`), but one is const while the other is not.
Make this variable non-const
When building with LTO, move $(PLATFORM_LIBS) into the --start-group /
--end-group list.
Otherwise some functions declared in assembly may not be resolved and
linking may fail.
Signed-off-by: Marek Behún
---
Makefile | 3 ++-
scripts/Makefile.spl | 3 ++-
2 files changed, 4 insertion
Currently we use incremental linking (ld -r) to link several object
files from one directory into one built-in.o object file containing the
linked code from that directory (and its subdirectories).
Linux has, some time ago, moved to thin archives instead.
Thin archives are archives (.a) that do n
Add plumbing for building U-Boot with Link Time Optimizations.
Signed-off-by: Marek Behún
---
Kbuild | 2 ++
Kconfig | 19 +++
Makefile | 36
scripts/Makefile.lib | 3 +++
scripts/Makefile.spl | 14
When building with LTO, the system libc's `errno` variable used in
arch/sandbox/cpu/os.c conflicts with U-Boot's `errno` (defined in
lib/errno.c) with the following error:
.../ld: errno@@GLIBC_PRIVATE: TLS definition in /lib64/libc.so.6
section .tbss mismatches non-TLS reference in
Make LTO available for sandbox architecture.
Signed-off-by: Marek Behún
---
arch/Kconfig | 1 +
arch/sandbox/config.mk | 2 ++
2 files changed, 3 insertions(+)
diff --git a/arch/Kconfig b/arch/Kconfig
index 27843cd79c..a6dab3e56d 100644
--- a/arch/Kconfig
+++ b/arch/Kconfig
@@ -101,6
Build sandbox targets with LTO by default.
Signed-off-by: Marek Behún
---
arch/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/Kconfig b/arch/Kconfig
index a6dab3e56d..b884b7b248 100644
--- a/arch/Kconfig
+++ b/arch/Kconfig
@@ -123,6 +123,7 @@ config SANDBOX
select SYSRE
In style of linked lists, instead of declaring symbols for boundaries
of getopt options array in the linker script, declare corresponding
sections and retrieve the boundaries via static inline functions.
Without this clang's LTO produces binary without any getopt options,
because for some reason i
The Thumb instruction `ldr` is able to move high registers only from
armv7. For armv5 and armv6 we have to use `mov`.
Signed-off-by: Marek Behún
---
arch/arm/include/asm/global_data.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/arm/include/asm/global_data.h
b/arc
Fix LTO build for some thumb-interwork usecases (such as for
da850evm_defconfig), where inline assmebly such as
mrc p15,0,r2,c1,c0,0
causes the compiler to fail during LTO linking with
Error: selected processor does not support `mrc p15,0,r2,c1,c0,0'
in Thumb mode
Signed-off-by: Marek
When imx28_xea_defconfig is built with LTO, the compiler complains about
the two different declarations of _start:
include/asm-generic/sections.has extern void _start(void);
arch/arm/cpu/arm926ejs/mxs/mxs.c as extern uint32_t _start;
Fix this.
Signed-off-by: Marek Behún
---
arch/ar
On ARM, the gd pointer is stored in registers r9 / x18. For this the
-ffixed-r9 / -ffixed-x18 flag is used when compiling, but using global
register variables causes errors when building with LTO, and these
errors are very difficult to overcome.
Richard Biener says [1]:
Note that global register
When apf27_defconfig is built with LTO, linking complains about
undefined reference to `nand_boot`. This is because it is referenced
from inline assembly. Make it visible.
Signed-off-by: Marek Behún
---
drivers/mtd/nand/raw/mxc_nand_spl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
di
When building keystone with LTO the compiler complains:
Error: selected processor does not support `smc #0' in Thumb mode
Fix this by removing -flto for the file implementing these SMC calls.
Signed-off-by: Marek Behún
---
arch/arm/mach-keystone/Makefile | 1 +
1 file changed, 1 insertion(+)
When building with LTO, the compiler complains about type mismatch of
function clk_bsc_enable() in file:
arch/arm/cpu/armv7/kona-common/clk-stubs.c
vs other files that define or use this function:
warning: type of ‘clk_bsc_enable’ does not match original declaration.
Change the type of this fu
1 - 100 of 118 matches
Mail list logo
