new scc and cfg files for BSP nxp-imx6 on branch yocto-6.6.
Signed-off-by: Xiaolei Wang
---
bsp/nxp-imx6/nxp-imx6-preempt-rt.scc | 7 +
bsp/nxp-imx6/nxp-imx6-standard.scc | 7 +
bsp/nxp-imx6/nxp-imx6.cfg| 226 +++
bsp/nxp-imx6/nxp-imx6.scc|
From: "Xiaolei Wang via lists.yoctoproject.org"
The DMA32 zone on imx8qm is empty, and GFP_DMA32 and
GFP_DMA are a bad combination.
Signed-off-by: Xiaolei Wang
Signed-off-by: Bruce Ashfield
---
drivers/gpu/imx/dpu-blit/dpu-blit.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
For Atomic Mode Setting, it is safer to use raw spin lock.
Mutex may cause scheduling, which avoids the following warning.
BUG: sleeping function called from invalid context at kernel/locking/mutex.c:283
in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 191, name: kworker/5:13
Use raw_spin_lock instead of spin_lock,
this patch fixes the following warning:
BUG: sleeping function called from invalid context at
kernel/locking/spinlock_rt.c:46
in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 506, name: sh
preempt_count: 2, expected: 0
RCU nest depth: 0, expected:
Use raw_spin_lock instead of spin_lock,
this patch fixes the following warning:
Hardware name: Freescale i.MX7 Dual (Device Tree)
unwind_backtrace from show_stack+0x18/0x1c
show_stack from dump_stack_lvl+0x40/0x4c
dump_stack_lvl from __might_resched+0x140/0x1b4
__might_resched from
The data structure edid_fbi needs to be initialized, otherwise
edid_fbi->monspecs.modedb and fbi->monspecs.modedb_len are not
initial values, which will cause illegal free to be detected
by KASAN, and the following panic will appear:
Unable to handle kernel paging request at virtual address
Enable pcie for imx6q-sabresd.
Signed-off-by: Xiaolei Wang
Signed-off-by: Bruce Ashfield
---
arch/arm/boot/dts/nxp/imx/imx6q-sabresd.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/nxp/imx/imx6q-sabresd.dts
b/arch/arm/boot/dts/nxp/imx/imx6q-sabresd.dts
index
When mxc_hdmi_disp_init returns failure, hdmi->fbi->modelist needs
to be released in mxc_hdmi_disp_deinit(), this patch solves the
following memory leaks:
unreferenced object 0xc52a45c0 (size 64):
comm "swapper/0", pid 1, jiffies 4294937844 (age 159.630s)
hex dump (first 32 bytes):
80 45
When we don`t set "video=mxcfb0:dev=hdmi" in bootargs,
but connect hdmi to imx6q, it will trigger a periodically
hdmi interrupt in a few seconds. These repeated interruptions
will read edid and alloc modedb, so we need to release the
modedb before the next allocation.
Fix following memory
CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW
5.15.78-rt48-yocto-preempt-rt #1
Hardware name: Freescale i.MX7 Dual (Device Tree)
[<80110f4c>] (unwind_backtrace) from [<8010aef8>] (show_stack+0x18/0x1c)
[<8010aef8>] (show_stack) from [<80be4998>] (dump_stack_lvl+0x40/0x4c)
[<80be4998>]
Refer to commit 323751dadfbe("MLK-21958-13: drm/bridge: adv7511: Limit
supported clocks")
Add Limit supported clocks for adv7533, Some modes are not working with this
converter.
This will cause hdmi link down, so add this workround patch to solve this
problem.
Signed-off-by: Xiaolei Wang
The irqsteer's runtime PM has to be enabled otherwise the probe of
some devices (such as dpu) will fail because of the failure of
irq_chip_pm_get().
But we can't allow the irqsteer to really enter the suspend state
because it will break the kdump with a call trace like below.
Internal error:
Changeset application failure should be destroyed
unreferenced object 0x0008f249a980 (size 128):
comm "kworker/2:1", pid 83, jiffies 4294893542 (age 70.832s) hex dump
(first 32 bytes):
e0 b6 db 11 00 80 ff ff e0 b6 db 11 00 80 ff ff
05 00 00 00 00 00 00 00 20 de 44 ff 08
Hi Bruce
Please help merge the following 14 patches to linux-yocto
branch v6.6/standard/preempt-rt/nxp-sdk-6.6/nxp-soc &
v6.6/standard/nxp-sdk-6.6/nxp-soc
Xiaolei Wang (13):
arm: imx: Enable lpddr3_freq_imx for imx6
drm/bridge: adv7511: fix a memory leak when application changeset
fails
For imx6 bsp, the SDK actually integrates imx6 config
and imx7 config, so lpddr3_freq_imx is needed when we
use imx6, otherwise it will cause a series of problems,
such as blurred graphics displayed by the display system,
etc., so in order to avoid turning on the CONFIG_SOC_IMX7D and
Changeset application failure should be destroyed
unreferenced object 0x0008f2656480 (size 128):
comm "kworker/2:1", pid 83, jiffies 4294893570 (age 70.724s)
hex dump (first 32 bytes):
c0 b6 db 11 00 80 ff ff c0 b6 db 11 00 80 ff ff
02 00 00 00 00 00 00 00 28 9e
Thanks for the explanation Alexander.
Thanks & Regards
Saswati
On Wed, Jun 5, 2024 at 4:23 PM Alexander Kanavin
wrote:
> TEMPLATECONF needs to be set only when you execute oe-init-build-env
> to initialize the build. You don't need to permanently export it to
> the environment, and can simply
TEMPLATECONF needs to be set only when you execute oe-init-build-env
to initialize the build. You don't need to permanently export it to
the environment, and can simply put it as a prefix to the command:
TEMPLATECONF=/path/to/config/template/in/some/meta-layer/ .
/path/to/oe-init-build-env
Hello Paul,
Many Thanks (not entirely politically correct English language), I
guess it was one of the errors:
PREFERRED_VERSION_linux-torvalds ?= "6.10.%"
I swapped "torvalds" with "mainline", as U did.
But the one I've bumped to is the one I just noticed at the end of
writing the original
Hello Alexander,
Can you help me with the example?
As I am using the Kirkstone version of yocto, I am not able to get a proper
idea how to set.
Do we need to export the TEMPLATECONF?
Thanks & Regards
Saswati
On Tue, Jun 4, 2024 at 3:54 PM Alexander Kanavin
wrote:
> If your yocto version is
A build flagged for QA (yocto-5.1_M1.rc2) was completed on the autobuilder
and is available at:
https://autobuilder.yocto.io/pub/releases/yocto-5.1_M1.rc2
Build URL:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/7008
Build hash information:
From: Sai Praneeth Prakhya
Presently, the default domain of an iommu group is allocated during boot
time and it cannot be changed later. So, the device would typically be
either in identity (also known as pass_through) mode or the device would be
in DMA mode as long as the machine is up and
From: Yongxin Liu
Hi Bruce,
Please help to merge the following 3 patches to linux-yocto, branch
"v6.6/standard/x86" and "v6.6/standard/preempt-rt/x86".
They are from Intel's repo
https://github.com/intel-collab/networking.wireless.transport.rdk.board-support.meta-intel-axxia.git
1) Patch
From: John Jacques
Add a kernel command line option to force the use of acpi_pm as the
watchdog clocksource. To use it, add the following to the
kernel command line:
ricardo_clocksource_wd=force_acpi_pm_wd
and in dmesg look for:
RICARDO: Force acpi_pm as watchdog
Also, add a
From: John Jacques
Early versions of the SNR chip do not allow the "no reboot"
bit to be accessed. This commit simply assumes that it is
writeable without checking in order to allow the watchdog to
but used in Linux. This will be fixed in later versions of
the chip.
Signed-off-by: John
25 matches
Mail list logo
