The driver provides regulator set/get voltage enable/disable
functions for TI TPS5911 PMIC.
Signed-off-by: Svyatoslav Ryhel
Reviewed-by: Simon Glass
---
drivers/power/regulator/Kconfig | 11 +
drivers/power/regulator/Makefile | 1 +
drivers/power/regulator/tps65911_r
Add support to bind the regulators/child nodes with the pmic.
Also adds the pmic i2c based read/write functions to access pmic
registers.
Signed-off-by: Svyatoslav Ryhel
Reviewed-by: Simon Glass
---
doc/device-tree-bindings/pmic/tps65911.txt | 78 ++
drivers/power/pmic/pmic_
The driver provides regulator set/get voltage enable/disable
functions for TI TPS80031/TPS80032 PMICs.
Signed-off-by: Svyatoslav Ryhel
Reviewed-by: Simon Glass
---
drivers/power/regulator/Kconfig | 8 +
drivers/power/regulator/Makefile | 1 +
drivers/power/regulator
Add support to bind the regulators/child nodes with the pmic.
Also adds the pmic i2c based read/write functions to access pmic
registers.
Signed-off-by: Svyatoslav Ryhel
Reviewed-by: Simon Glass
---
doc/device-tree-bindings/pmic/tps80031.txt | 76 +++
drivers/power/pmic/Kconfig
The driver provides regulator set/get voltage
enable/disable functions for MAXIM MAX77663 PMICs.
Signed-off-by: Svyatoslav Ryhel
Reviewed-by: Simon Glass
---
drivers/power/regulator/Kconfig | 9 +
drivers/power/regulator/Makefile | 1 +
drivers/power/regulator/max77
Add support to bind the regulators/child nodes with the pmic.
Also adds the pmic i2c based read/write functions to access pmic
registers.
Signed-off-by: Svyatoslav Ryhel
Reviewed-by: Simon Glass
---
doc/device-tree-bindings/pmic/max77663.txt | 84 +
drivers/power/pmic/Kconfi
dev->driver_data will carry the tail of ldo if there is a number and
if there is no number it will be an error code, anyway it will not be
zero. This results in a wrong ldo regulator detection.
To avoid this check for non-numerical ldo first and then manipulate
dev->driver_data.
Signed-off-by: Sv
Existing PALMAS PMIC driver is fully compatible with TI TPS65913
PMIC found in many Tegra 4 devices, like Tegra Note 7 and ASUS
TF701T. TPS65913 shares same structure of regulators like TPS659038
so data can be reused.
Tested-by: Svyatoslav Ryhel # NVIDIA Tegratab
Signed-off-by: Svyatoslav Ryhel
Patch set adds basic support for PMICs used in many Tegra 3 devices.
All PMIC drivers are based on datasheets provided by vendors.
Implemented API include regulator set/get voltage enable/disable and
basic PMIC r/w capabilities.
Drivers were tested by me on LG P895 (max77663), HTC One X (TPS80032)
18 серпня 2023 р. 20:04:47 GMT+03:00, Tom Rini
написав(-ла):
>On Fri, Aug 18, 2023 at 08:02:30PM +0300, Svyatoslav Ryhel wrote:
>>
>>
>> 18 серпня 2023 р. 19:49:43 GMT+03:00, Tom Rini
>> написав(-ла):
>> >On Fri, Aug 18, 2023 at 03:39:22PM +0200, Thierry Reding wrote:
>> >
>> >> From: Thie
On 8/16/23 8:35 PM, Marek Vasut wrote:
Add function to flush and invalidate cache over request and response
queue entries, and perform flush and optional invalidate over block
layer data that are passed into the UFS layer. This makes it possible
to use UFS with caches enabled.
Signed-off-by: Mar
On 8/16/23 8:35 PM, Marek Vasut wrote:
Use utp_transfer_req_desc pointer to reference to utrdl queue
instead of referencing the queue directly. This makes the code
more consistent. No functional change.
Signed-off-by: Marek Vasut
---
Cc: Bhupesh Sharma
Cc: Faiz Abbas
---
V2: No change
---
On 8/16/23 8:35 PM, Marek Vasut wrote:
Pass the hba pointer itself to ufshcd_prepare_req_desc_hdr()
instead of duplicating utp_transfer_req_desc access at each
call site. No functional change.
Signed-off-by: Marek Vasut
---
Cc: Bhupesh Sharma
Cc: Faiz Abbas
---
V2: No change
---
drivers/
On 8/16/23 8:35 PM, Marek Vasut wrote:
Extend the version check to handle UFS 3.0 controllers as well.
Tested on R-Car S4 UFS 3.0 controller.
Signed-off-by: Marek Vasut
---
Cc: Bhupesh Sharma
Cc: Faiz Abbas
---
V2: No change
---
drivers/ufs/ufs.c | 3 ++-
drivers/ufs/ufs.h | 1 +
2 fil
On 8/16/23 8:35 PM, Marek Vasut wrote:
Add UFSHCD_QUIRK_HIBERN_FASTAUTO quirk for host controllers which supports
auto-hibernate the capability but only FASTAUTO mode.
Ported from Linux kernel commit
2f11bbc2c7f3 ("scsi: ufs: core: Add UFSHCD_QUIRK_HIBERN_FASTAUTO")
Signed-off-by: Marek Vasu
On 8/16/23 8:35 PM, Marek Vasut wrote:
Add UFSHCD_QUIRK_BROKEN_64BIT_ADDRESS for host controllers which do not
support 64-bit addressing.
Ported from Linux kernel commit
6554400d6f66 ("scsi: ufs: core: Add UFSHCD_QUIRK_BROKEN_64BIT_ADDRESS")
with ufs_scsi_buffer_aligned() based on U-Boot gene
On 8/16/23 8:35 PM, Marek Vasut wrote:
Use BIT() macro for quirks, no functional change.
Signed-off-by: Marek Vasut
---
Cc: Bhupesh Sharma
Cc: Faiz Abbas
---
V2: New patch
---
drivers/ufs/ufs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/ufs/ufs.h b/drivers/
Tested on visionfive2, it works.
On 18.08.23 07:11, Chanho Park wrote:
Since the Patch 55171aedda88, VisionFive2 booting has been broken [1].
VisionFive2 board requires to enable CONFIG_TIMER_EARLY but booting went
to panic from initr_dm_devices due to lack of a timer device.
- Error logs
initc
Tested on visionfive2 board, it works. Thanks for taking a look into this.
On 18.08.23 07:11, Chanho Park wrote:
This patch introduces EVT_DM_POST_INIT_R event type for handling hooks
after relocation.
Fixes: 55171aedda88 ("dm: Emit the arch_cpu_init_dm() even only before
relocation")
Suggeste
Hi AKASHI,
On Mon, 21 Aug 2023 at 20:46, AKASHI Takahiro
wrote:
>
> The output from "dm tree" or "dm uclass" is a bit annoying
> if the number of devices available on the system is huge.
> (This is especially true on sandbox when I debug some DM code.)
>
> With this patch, we can specify the ucla
Add a new event which handles this function. Convert existing use of
the function to use the new event instead.
Make sure that EVENT is enabled by affected boards, by selecting it from
the LAST_STAGE_INIT option. For x86, enable it by default since all boards
need it.
For controlcenterdc, inline
Use the misc_init_f event instead, which is designed for this purpose.
All boards with CONFIG_VID already enable CONFIG_EVENT.
Signed-off-by: Simon Glass
---
arch/arm/cpu/armv8/fsl-layerscape/spl.c | 5 +
board/freescale/ls1088a/ls1088a.c | 3 ++-
board/freescale/lx2160a/lx2160a.c
Convert this to use events instead of calling a function directly in the
init sequence.
Rename it to arch_fsp_init_f() to distinguish it from the one that happens
after relocation.
For FSPv2 nothing needs to be done here, so drop the empty function.
Signed-off-by: Simon Glass
---
arch/x86/lib
Now that we have two types of spy, mention this in the documentation. Put
the simple spy first, since it seems to be the common case.
Signed-off-by: Simon Glass
---
doc/develop/event.rst | 23 +--
1 file changed, 21 insertions(+), 2 deletions(-)
diff --git a/doc/develop/eve
The new name makes it clearer that this is for a full spy, with access to
the context and the event data.
Signed-off-by: Simon Glass
---
boot/vbe_request.c | 2 +-
boot/vbe_simple_os.c | 2 +-
include/event.h | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/boot/vbe
Very few of the existing event-spy records use the arguments they are
passed. Update them to use a simple spy instead, to simplify the code.
Where an adaptor function is currently used, remove it where possible.
Signed-off-by: Simon Glass
---
arch/arm/mach-imx/imx8/cpu.c | 4
Move the manual-relocation code to the initcall file. Make sure to avoid
manually relocating event types. Only true function pointers should be
relocated.
Signed-off-by: Simon Glass
---
common/board_r.c | 6 ++
include/initcall.h | 7 +++
lib/initcall.c | 10 ++
3 files
At present the initcall list consists of a list of function pointers. Over
time the initcall lists will likely change to mostly emitting events,
since most of the calls are board- or arch-specific.
As a first step, allow an initcall to be an event type instead of a
function pointer. Add the requir
Export this function so it can be used with initcall debugging.
Signed-off-by: Simon Glass
---
common/event.c | 2 +-
include/event.h | 8
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/common/event.c b/common/event.c
index 7e2590eb0400..55f6932ef62c 100644
--- a/common
Move the failure message outside the loop, so it is easier to follow the
code. Avoid swallowing the error code - just pass it along.
Drop the initcall-list address from the output. This is confusing since
we show two addresses. Really it is only the function address which is
useful, since it can b
Use a variable to hold the function, so we don't need to repeat the
pointer access each time. Rename the init pointer to 'ptr' since we only
refer to it in the for() statement now.
Signed-off-by: Simon Glass
---
lib/initcall.c | 24
1 file changed, 12 insertions(+), 12
The current event spy is always passed the event context and the event.
The context is always NULL for a static spy. The event is not often used.
Introduce a 'simple' spy which takes no arguments. This allows us to drop
the adaptation code that many of these spy records use.
Update the event scri
Somehow I do not see any inlining with initcalls now. I was sure I saw
it when this commit went in, but now it seems to make things worse.
This reverts commit 47870afab92fca6e672c03d0dea802a55e200675.
Signed-off-by: Simon Glass
---
common/board_r.c | 5 -
include/initcall.h | 46 +--
Move this into a function and do it once, not each time around the loop.
Signed-off-by: Simon Glass
---
lib/initcall.c | 25 +++--
1 file changed, 15 insertions(+), 10 deletions(-)
diff --git a/lib/initcall.c b/lib/initcall.c
index eedb0fbf1d5c..89a68b2444fe 100644
--- a/li
This series replaces some more of the init hooks in board_f.c and
board_r.c with events. Notably it converts last_state_init() over.
It also provides a 'simple' event spy, which takes no arguments. It turns
out that this is quite a common case, so it is worth optimising for this,
to reduce code
The output from "dm tree" or "dm uclass" is a bit annoying
if the number of devices available on the system is huge.
(This is especially true on sandbox when I debug some DM code.)
With this patch, we can specify the uclass or the device
that we are interested in in order to limit the output.
For
Hi Rogan,
On Fri, Aug 18, 2023 at 10:45 AM Rogan Dawes wrote:
>
> Circling back to this, I wanted to get a modern u-boot running on the
> Wink Hub v1 as well. Since it is possible to invoke SDP over USB
> (having soldered on a suitable microUSB connector), I have no concern
> about bricking it no
Enable UFS controller driver and matching UFS and SCSI commands. The
former is used to initialize the device, the later is used to perform
low level access to the SCSI interface of the UFS device.
Enable R8A779F0 S4 Spider specific dependencies, the PCA953x driver
and GPIO clock gate driver. This
Add support for Renesas R-Car UFS controller which needs vendor-specific
initialization.
Ported from Linux kernel as of commit
c2ab666072bc ("scsi: ufs: Explicitly include correct DT includes")
Signed-off-by: Marek Vasut
---
Cc: Faiz Abbas
---
drivers/ufs/Kconfig | 9 +
drivers/ufs/Mak
On 8/21/23 16:06, Svyatoslav Ryhel wrote:
21 серпня 2023 р. 16:41:51 GMT+03:00, Marek Vasut написав(-ла):
On 8/21/23 13:19, Svyatoslav Ryhel wrote:
Some devices (like ASUS TF201) may not use fuse based xcvr setup
which will result in not working USB line. To fix this situation
allow xcvr setup
Hi Alex,
On Mon, 21 Aug 2023 at 16:40, Alexander Graf wrote:
>
>
> On 22.08.23 00:10, Simon Glass wrote:
> > Hi Alex,
> >
> > On Mon, 21 Aug 2023 at 14:20, Alexander Graf wrote:
> >>
> >> On 21.08.23 21:57, Simon Glass wrote:
> >>> Hi Alex,
> >>>
> >>> On Mon, 21 Aug 2023 at 13:33, Alexander Gra
Hi Alex,
On Mon, 21 Aug 2023 at 16:44, Alexander Graf wrote:
>
>
> On 22.08.23 00:10, Simon Glass wrote:
> > Hi Alex,
> >
> > On Mon, 21 Aug 2023 at 13:59, Alexander Graf wrote:
> >>
> >> On 21.08.23 21:11, Simon Glass wrote:
> >>> Hi Alper,
> >>>
> >>> On Mon, 21 Aug 2023 at 07:51, Alper Nebi Y
On 22.08.23 00:10, Simon Glass wrote:
Hi Alex,
On Mon, 21 Aug 2023 at 13:59, Alexander Graf wrote:
On 21.08.23 21:11, Simon Glass wrote:
Hi Alper,
On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak wrote:
From: Alexander Graf
Now that we have a damage area tells us which parts of the fram
On 22.08.23 00:10, Simon Glass wrote:
Hi Alex,
On Mon, 21 Aug 2023 at 14:20, Alexander Graf wrote:
On 21.08.23 21:57, Simon Glass wrote:
Hi Alex,
On Mon, 21 Aug 2023 at 13:33, Alexander Graf wrote:
On 21.08.23 21:11, Simon Glass wrote:
Hi Alper,
On Mon, 21 Aug 2023 at 07:51, Alper Neb
Add a minimal generic RK3566/RK3568 board that only have eMMC and SDMMC
enabled. This defconfig can be used to boot from eMMC or SD-card on most
RK3566/RK3568 boards that follow reference board design.
Signed-off-by: Jonas Karlman
---
v2:
- New patch
arch/arm/dts/rk3568-generic-u-boot.dtsi | 14
Port the Rockchip IO-domain driver for RK3568 from linux.
The driver auto probe after bind to configure IO-domain based on the
regulator voltage. Compared to the linux driver this driver is not
notified about regulator voltage changes and only configure IO-domain
based on the initial voltage autos
From: Joseph Chen
Information from the first range group is always used to calculate the
voltage returned for buck converters. This may result in wrong voltage
reported back to the regulator_get_value caller.
Traverse all the possible BUCK ranges to fix this issue.
Fixes: addd062beacc ("power:
From: shengfei Xu
The voltage value for switchout converters is always reported as 0 uV.
When the switch is enabled, it's voltage is same as input supply.
Fix this by implementing get_value for switchout converters.
Fixes: ee30068fa574 ("power: pmic: rk809: support rk809 pmic")
Signed-off-by: s
With the commit 4fcba5d556b4 ("regulator: implement basic reference
counter"), keeping regulator enablement in balance become more important.
Calling regulator_autoset multiple times on a fixed regulator increase
the enable count for each call, resulting in an unbalanced enable count.
Introduce a
This series port the IO-domain driver for RK3568 from linux. It is
necessary for the IO-domain setting of the SoC to match the voltage
supplied by the regulators.
The driver auto probe after bind and configures IO-domain based on the
voltage reported by the regulators. This fixes issues observed w
Hi Alex,
On Mon, 21 Aug 2023 at 13:59, Alexander Graf wrote:
>
>
> On 21.08.23 21:11, Simon Glass wrote:
> > Hi Alper,
> >
> > On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak
> > wrote:
> >> From: Alexander Graf
> >>
> >> Now that we have a damage area tells us which parts of the frame buffer
>
On Mon, 21 Aug 2023 at 12:13, Alper Nebi Yasak wrote:
>
> Now that we have video damage tracking, try to reduce the SDL display
> work by copying only the updated regions onto the SDL texture instead of
> the entire framebuffer. We still have to do RenderClear and RenderCopy
> the whole texture on
On Mon, 21 Aug 2023 at 12:13, Alper Nebi Yasak wrote:
>
> The sandbox SDL video sync is handled in the uclass because there has
> been a sync rate limiter and a way to bypass that. Previous patches
> move the rate limit code into SDL-specific files, and provide a generic
> way to defer and force v
Hi Alper,
On Mon, 21 Aug 2023 at 12:13, Alper Nebi Yasak wrote:
>
> The sandbox SDL driver has some code in the video uclass to rate limit
> video syncs by postponing them, and forcing a sync nonetheless with a
> "force" argument.
>
> Add infrastructure for doing this through driver ops, where th
On Mon, 21 Aug 2023 at 12:13, Alper Nebi Yasak wrote:
>
> When VIDEO_COPY is enabled, the "main" framebuffer is a cached work area
> in U-Boot allocated memory and the "copy" framebuffer is the hardware
> frame buffer displayed on the screen. The sandbox SDL video driver sets
> copy_base to indica
Hi Alex,
On Mon, 21 Aug 2023 at 14:20, Alexander Graf wrote:
>
>
> On 21.08.23 21:57, Simon Glass wrote:
> > Hi Alex,
> >
> > On Mon, 21 Aug 2023 at 13:33, Alexander Graf wrote:
> >>
> >> On 21.08.23 21:11, Simon Glass wrote:
> >>> Hi Alper,
> >>>
> >>> On Mon, 21 Aug 2023 at 07:51, Alper Nebi Y
Here's the latest report
-- Forwarded message -
From:
Date: Mon, Aug 21, 2023 at 4:30 PM
Subject: New Defects reported by Coverity Scan for Das U-Boot
To:
Hi,
Please find the latest report on new defect(s) introduced to Das
U-Boot found with Coverity Scan.
4 new defect(s) int
Hey all,
It's release day and I've tagged and pushed -rc3, and will merge that to
next as well shortly. Things should really stay stable now until
release, so I'd really like to start seeing PRs for -next at this point.
In terms of a changelog,
git log --merges v2023.10-rc2..v2023.10-rc3
contain
On 21.08.23 21:57, Simon Glass wrote:
Hi Alex,
On Mon, 21 Aug 2023 at 13:33, Alexander Graf wrote:
On 21.08.23 21:11, Simon Glass wrote:
Hi Alper,
On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak wrote:
This is a rebase of Alexander Graf's video damage tracking series, with
some tests and
On Mon, Aug 21, 2023 at 01:11:38PM -0600, Simon Glass wrote:
> Hi Tom,
>
> https://source.denx.de/u-boot/custodians/u-boot-dm/-/pipelines/17449
> https://dev.azure.com/simon0972/u-boot/_build/results?buildId=47&view=results
>
>
> The following changes since commit 17aad803551500e1a3d87339a6559e
On 21.08.23 21:11, Simon Glass wrote:
Hi Alper,
On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak wrote:
From: Alexander Graf
CONFIG_VIDEO_COPY implemented a range-based copying mechanism: If we
print a single character, it will always copy the full range of bytes
from the top left corner of
On 21.08.23 21:11, Simon Glass wrote:
Hi Alper,
On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak wrote:
From: Alexander Graf
Now that we have a damage area tells us which parts of the frame buffer
actually need updating, let's only dcache flush those on video_sync()
calls. With this optimiza
Hi Alex,
On Mon, 21 Aug 2023 at 13:33, Alexander Graf wrote:
>
>
> On 21.08.23 21:11, Simon Glass wrote:
> > Hi Alper,
> >
> > On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak
> > wrote:
> >> This is a rebase of Alexander Graf's video damage tracking series, with
> >> some tests and other changes
The Devicespec specification skips over handling of a logical view of
the memory map, pointing users to the UEFI specification.
It is common to split firmware into 'Platform Init', which does the
initial hardware setup and a "Payload" which selects the OS to be booted.
Thus an handover interface i
On 18.08.23 16:59, Simon Glass wrote:
Hi Heinrich,
On Thu, 17 Aug 2023 at 10:36, Heinrich Schuchardt wrote:
On 16.08.23 19:47, Simon Glass wrote:
Hi Jonathan,
On Wed, 16 Aug 2023 at 11:15, Jonathan Corbet wrote:
Simon Glass writes:
Hi Jonathan,
I would like to do something like this:
Similar to MT7981 and MT7986 also MT7988 can have a high number of
reserved-memory regions used by the various hardware offloading
subsystems.
Raise CONFIG_LMB_MAX_REGIONS to 64 to avoid errors when trying to boot
Linux with more then 6 reserved regions:
ERROR: reserving fdt memory region failed
From: Igor Opaniuk
Move an OEM closing logic to ahab_close() function to be able to use
it directly without calling a u-boot command.
Signed-off-by: Igor Opaniuk
Co-developed-by: Oleksandr Suvorov
Signed-off-by: Oleksandr Suvorov
---
arch/arm/include/asm/arch-imx8/sys_proto.h | 1 +
arch/a
On 21.08.23 21:11, Simon Glass wrote:
Hi Alper,
On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak wrote:
This is a rebase of Alexander Graf's video damage tracking series, with
some tests and other changes. The original cover letter is as follows:
This patch set speeds up graphics output on A
On Sun, 20 Aug 2023 at 11:31, Tom Rini wrote:
>
> These jobs are to confirm specific build targets, on a Linux host. We
> can safely combine these two build tests, with a make mrproper in
> between.
>
> Signed-off-by: Tom Rini
> ---
> .azure-pipelines.yml | 13 ++---
> .gitlab-ci.yml
On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak wrote:
>
> From: Alexander Graf
>
> Now that we have a damage tracking API, let's populate damage done by
> UEFI payloads when they BLT data onto the screen.
>
> Signed-off-by: Alexander Graf
> Reported-by: Da Xue
> Reviewed-by: Heinrich Schuchardt
Hi Alper,
On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak wrote:
>
> This is a rebase of Alexander Graf's video damage tracking series, with
> some tests and other changes. The original cover letter is as follows:
>
> > This patch set speeds up graphics output on ARM by a factor of 60x.
> >
> > On
Hi Neil,
On Mon, 21 Aug 2023 at 03:16, neil.armstr...@linaro.org
wrote:
>
> Hi,
>
> On 16/07/2023 01:40, Simon Glass wrote:
> > Hi,
> >
> > On Thu, 13 Jul 2023 at 23:30, AKASHI Takahiro
> > wrote:
> >>
> >> On Tue, Jul 11, 2023 at 01:13:29PM -0600, Simon Glass wrote:
> >>> +AKASHI Takahiro
> >>
On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak wrote:
>
> From: Alexander Graf
>
> We are going to introduce image damage tracking to fasten up screen
> refresh on large displays. This patch adds damage tracking for up to
> one rectangle of the screen which is typically enough to hold blt or
> te
Hi Alper,
On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak wrote:
>
> From: Alexander Graf
>
> CONFIG_VIDEO_COPY implemented a range-based copying mechanism: If we
> print a single character, it will always copy the full range of bytes
> from the top left corner of the character to the lower right
On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak wrote:
>
> With VIDEO_DAMAGE, the video uclass tracks updated regions of the frame
> buffer in order to avoid unnecessary work during a video sync. Enable
> the config in sandbox and add a test for it, by printing strings at a
> few locations and chec
On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak wrote:
>
> From: Alexander Graf
>
> Now that we have a damage tracking API, let's populate damage done by
> vidconsole drivers. We try to declare as little memory as damaged as
> possible.
>
> Signed-off-by: Alexander Graf
> Reported-by: Da Xue
> [
On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak wrote:
>
> From: Alexander Graf
>
> Some drivers call video_set_flush_dcache() to indicate that they want to
> have the dcache flushed for the frame buffer. These drivers benefit from
> our new video damage control, because we can reduce the amount o
Hi Alper,
On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak wrote:
>
> From: Alexander Graf
>
> Now that we have a damage area tells us which parts of the frame buffer
> actually need updating, let's only dcache flush those on video_sync()
> calls. With this optimization in place, frame buffer upda
On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak wrote:
>
> From: Alexander Graf
>
> Let's report the video damage when we fill parts of the screen. This
> way we can later lazily flush only relevant regions to hardware.
>
> Signed-off-by: Alexander Graf
> Reported-by: Da Xue
> [Alper: Call video
On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak wrote:
>
> With VIDEO_COPY enabled, only the modified parts of the frame buffer are
> intended to be copied to the hardware. Add a test that checks this, by
> overwriting contents we prepared without telling the video uclass and
> then checking if the
On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak wrote:
>
> While checking frame buffer contents, the video tests also check if the
> copy frame buffer contents match the main frame buffer. To test if only
> the modified regions are updated after a sync, we will need to create
> situations where the
Hi Peter,
On Sat, 19 Aug 2023 at 07:53, Peter Robinson wrote:
>
> On Wed, Aug 16, 2023 at 4:08 PM Simon Glass wrote:
> >
> > Hi Matthias, Peter,
> >
> > On Thu, 27 Jul 2023 at 15:54, Simon Glass wrote:
> > >
> > > This series moves Raspberry Pi boards over to use standard boot.
> > >
> > > It a
On Mon, 21 Aug 2023 at 07:51, Alper Nebi Yasak wrote:
>
> The video tests have a helper function to generate a pseudo-digest of
> frame buffer contents, but it only does so for the main one. There is
> another check that the copy frame buffer is the same as that. But
> neither is enough to test if
Hi Joao,
On Sun, 20 Aug 2023 at 13:04, Joao Marcos Costa wrote:
>
> Hello U-Boot community,
>
> I'm submitting a patch series that ports the gen_compile_commands.py
> script from the Linux kernel's sources to U-Boot. This script, originally
> located in scripts/clang-tools/gen_compile_commands.py
On Mon, 21 Aug 2023 at 08:53, Tom Rini wrote:
>
> On Mon, Aug 21, 2023 at 08:59:10AM -0500, Andrew Davis wrote:
>
> > This should have already been enabled but was missed when converting the
> > base platform defconfig, fix this here.
> >
> > Fixes: 3c5aa6caccab ("configs: Enable CONFIG_BLK in am5
On Sun, 20 Aug 2023 at 11:32, Tom Rini wrote:
>
> - We have added more TODO/etc comments since this task was created and
> never focused on removing them.
> - The output of sloccount isn't preserved or looked at, and if desired
> should be in the release stats pages instead somehow.
> - The re
On Sun, 20 Aug 2023 at 11:31, Tom Rini wrote:
>
> Now that we have 3600 minutes per build job, condense and rework things
> such that our overall time largely doesn't change, but we can also
> largely avoid having to re-tweak this job to avoid timeouts. Given that
> we have 10 threads, we also mo
On Sun, 20 Aug 2023 at 11:31, Tom Rini wrote:
>
> As per current Azure Pipelines documentation we qualify for 3600 minutes
> per job, if specified, as the timeout. The default unspecified timeout
> is 60 minutes. Rework things to specify 0 as the timeout (and so maximum
> allowed) so that we don't
Hi Tom,
https://source.denx.de/u-boot/custodians/u-boot-dm/-/pipelines/17449
https://dev.azure.com/simon0972/u-boot/_build/results?buildId=47&view=results
The following changes since commit 17aad803551500e1a3d87339a6559e99b7fad479:
Merge branch 'master' of
https://source.denx.de/u-boot/custod
On Mon, Aug 21, 2023 at 04:13:32PM +, Marcel Ziswiler wrote:
> Hi Sjoerd
>
> On Thu, 2023-06-01 at 08:37 +0200, Sjoerd Simons wrote:
> > On Wed, 2023-05-31 at 17:14 -0400, Tom Rini wrote:
> > > On Thu, Apr 06, 2023 at 08:55:34PM +0200, Sjoerd Simons wrote:
> > >
> > > > This series adds more
Now that we have video damage tracking, try to reduce the SDL display
work by copying only the updated regions onto the SDL texture instead of
the entire framebuffer. We still have to do RenderClear and RenderCopy
the whole texture onto the renderer, but that allegedly happens in the
GPU.
Signed-o
The sandbox SDL video sync is handled in the uclass because there has
been a sync rate limiter and a way to bypass that. Previous patches
move the rate limit code into SDL-specific files, and provide a generic
way to defer and force video syncs.
Sandbox code shouldn't be in the uclasses if possibl
As a first step of removing sandbox-specific code from the video uclass,
move the sync rate limiter into the SDL code. We lose the ability to
immediately force a screen refresh, but can retry until it does.
Signed-off-by: Alper Nebi Yasak
---
arch/sandbox/cpu/sdl.c | 9 +
arch/s
The sandbox SDL driver has some code in the video uclass to rate limit
video syncs by postponing them, and forcing a sync nonetheless with a
"force" argument.
Add infrastructure for doing this through driver ops, where the driver
can request to defer a sync with -EAGAIN, and the uclass can force i
When VIDEO_COPY is enabled, the "main" framebuffer is a cached work area
in U-Boot allocated memory and the "copy" framebuffer is the hardware
frame buffer displayed on the screen. The sandbox SDL video driver sets
copy_base to indicate support for this, but it displays the work area
instead. Chang
While working on the video damage tracking series [1], I noticed the
10Hz limitation on the sandbox screen refresh rate, and thought maybe
applying the damage tracking idea to SDL would make it reasonable to
increase the rate or even remove the limit completely.
Experimenting on that idea resulted
Tested on visionfive2, it works.
On 18.08.23 07:11, Chanho Park wrote:
Since the Patch 55171aedda88, VisionFive2 booting has been broken [1].
VisionFive2 board requires to enable CONFIG_TIMER_EARLY but booting went
to panic from initr_dm_devices due to lack of a timer device.
- Error logs
initc
Tested on visionfive2 board, it works. Thanks for taking a look into this.
On 18.08.23 07:11, Chanho Park wrote:
This patch introduces EVT_DM_POST_INIT_R event type for handling hooks
after relocation.
Fixes: 55171aedda88 ("dm: Emit the arch_cpu_init_dm() even only before
relocation")
Suggest
With this version I have done with a generic name, in this case 'data',
as suggested by Alper Nebi Yasak. This may be controversial, but we may
as well have the dicussion now. I assume that there are no other
ongoing attempts to define the layout of firmware in devicetree.
Signed-off-by: Simon Gla
Add a motivation and purpose for this new proposed node.
Signed-off-by: Simon Glass
---
(no changes since v1)
dtschema/schemas/firmware.yaml | 83 ++
1 file changed, 83 insertions(+)
create mode 100644 dtschema/schemas/firmware.yaml
diff --git a/dtschema/schem
1 - 100 of 145 matches
Mail list logo
