[linux-yocto][linux-yocto v6.1/standard/nxp-sdk-6.1/nxp-soc & v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc][PATCH 2/2] tty: serial: fsl_lpuart: use del_timer_sync() instead of lpuart_del_timer_sync()
Replace lpuart_del_timer_sync() with del_timer_sync() to avoid build
errors, which were introduced by commit b7f2b65538dd ("LF-9506-1 tty:
serial: fsl_lpuart: clean up EOP related code in lpuart driver")
Signed-off-by: Xiaolei Wang
---
drivers/tty/serial/fsl_lpuart.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/serial/fsl_lpuart.c b/drivers/tty/serial/fsl_lpuart.c
index 51112b27bb42..544bff231164 100644
--- a/drivers/tty/serial/fsl_lpuart.c
+++ b/drivers/tty/serial/fsl_lpuart.c
@@ -1964,7 +1964,7 @@ static void lpuart_dma_shutdown(struct lpuart_port *sport)
if (sport->dma_tx_chan)
dma_release_channel(sport->dma_tx_chan);
if (sport->dma_rx_chan) {
- lpuart_del_timer_sync(sport);
+ del_timer_sync(>lpuart_timer);
dma_release_channel(sport->dma_rx_chan);
}
}
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13807):
https://lists.yoctoproject.org/g/linux-yocto/message/13807
Mute This Topic: https://lists.yoctoproject.org/mt/105510456/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto][linux-yocto v6.1/standard/nxp-sdk-6.1/nxp-soc & v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc][PATCH 1/2] soc: imx: add character 't' for SOC_DEV_IMX9
commit 75e1b1be1109 ("LF-9535 soc: imx: split i.MX93 SoC device support
from soc-imx8m.c") is missing the character 't' during the backport
process, so add it.
Signed-off-by: Xiaolei Wang
---
drivers/soc/imx/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/soc/imx/Kconfig b/drivers/soc/imx/Kconfig
index 2445e0d0f419..4259381b8aa1 100644
--- a/drivers/soc/imx/Kconfig
+++ b/drivers/soc/imx/Kconfig
@@ -28,7 +28,7 @@ config IMX8M_PM_DOMAINS
select PM_GENERIC_DOMAINS
config SOC_DEV_IMX9
- ristate "i.MX9 SoC device support"
+ tristate "i.MX9 SoC device support"
depends on ARCH_MXC || COMPILE_TEST
depends on NVMEM_IMX_OCOTP_FSB_S400
default ARCH_MXC && ARM64
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13806):
https://lists.yoctoproject.org/g/linux-yocto/message/13806
Mute This Topic: https://lists.yoctoproject.org/mt/105510455/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] [PATCH] nxp-s32g: update to compatible with SDK BSP40
There are some new configs enabled in SDK BSP40 release, so update kernel cache to be compatible with SDK. Signed-off-by: Zhantao Tang --- bsp/nxp-s32g/nxp-s32g.cfg | 8 1 file changed, 8 insertions(+) diff --git a/bsp/nxp-s32g/nxp-s32g.cfg b/bsp/nxp-s32g/nxp-s32g.cfg index fd95c31a..b486b137 100644 --- a/bsp/nxp-s32g/nxp-s32g.cfg +++ b/bsp/nxp-s32g/nxp-s32g.cfg @@ -32,6 +32,9 @@ CONFIG_CPU_FREQ_GOV_POWERSAVE=y CONFIG_CPU_FREQ_GOV_USERSPACE=y CONFIG_CPU_FREQ_GOV_ONDEMAND=y CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y +CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y +CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y +CONFIG_ARM_SCMI_CPUFREQ=y CONFIG_ARM_SCMI_TRANSPORT_SMC_ATOMIC_ENABLE=y #To keep align with SDK, unset the ARM_SCMI_POWER_DOMAIN config @@ -53,6 +56,8 @@ CONFIG_BRIDGE=y CONFIG_NET_DSA=y CONFIG_NET_DSA_TAG_SJA1105=y CONFIG_NXP_TJA11XX_PHY=y +CONFIG_NXP_C45_TJA11XX_PHY=y +CONFIG_NXP_CBTX_PHY=y CONFIG_NET_DSA_SJA1105=y CONFIG_NET_DSA_SJA1105_PTP=y CONFIG_BRIDGE_VLAN_FILTERING=y @@ -66,6 +71,7 @@ CONFIG_SERIAL_FSL_LINFLEXUART_CONSOLE=y #SPI CONFIG_SPI=y CONFIG_SPI_FSL_DSPI=y +CONFIG_SPI_FSL_LPSPI=y CONFIG_SPI_SPIDEV=y CONFIG_GPIO_CDEV=y CONFIG_GPIO_S32CC=y @@ -126,6 +132,7 @@ CONFIG_INPUT_UINPUT=y # Thermal CONFIG_THERMAL=y CONFIG_QORIQ_THERMAL=y +CONFIG_CPU_THERMAL=y # ADC CONFIG_IIO=y @@ -163,6 +170,7 @@ CONFIG_BLK_DEV_NVME=y CONFIG_NVME_TARGET=y CONFIG_NVMEM_S32CC_SIUL2=y CONFIG_NVMEM_S32CC_OCOTP=y +CONFIG_NVMEM_S32CC_GPR=y # CONFIG_NVMEM_SCMI is not set #LLCE -- 2.25.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13804): https://lists.yoctoproject.org/g/linux-yocto/message/13804 Mute This Topic: https://lists.yoctoproject.org/mt/105509334/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] [yocto-kernel-cache kernel v6.1]: nxp-s32g: update to compatible with SDK BSP40
Hi Bruce, There is a patch to update v6.1 kernel cache for nxp-s32g bsp, would you please help to merge the following patch into yocto-6.1 branch? Thanks, Zhantao -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13805): https://lists.yoctoproject.org/g/linux-yocto/message/13805 Mute This Topic: https://lists.yoctoproject.org/mt/105509335/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Any recommendation to make software layer Yocto Compatible?
Hi Duy, The recipe in question was done by the Instrument Cluster EG, we can work on this with the group (main contact Yamaguchi-san). They do meet every other monday. See: https://lists.automotivelinux.org/g/agl-dev-community/calendar We do exacly what Paul describes all the time in meta-agl to pass the yocto- check-layer: e.g. https://git.automotivelinux.org/AGL/meta-agl/tree/meta-agl-core/recipes-core/ systemd/systemd_%25.bbappend and https://git.automotivelinux.org/AGL/meta-agl/tree/meta-agl-core/recipes-core/ systemd/systemd_aglcore.inc The condition can be on DISTRO_FEATURES or other variables. We try not to overload the usage of DISTRO_FEATURES as a change there will trigger a reparse in a lot of locations and hence possibly rebuilds. Thus the use of AGL_FEATURES in above example for anything that is directly related to AGL and is not a DISTRO_FEATURE in yocto already. For dlt-daemon in your example, we have these options and recommendations: a) use such a conditional include as shown above ... simple but it will not fix all the issues b) use :append: only in .bbappend files (name says it all ;) ) e.g. :append:aglcontainerguest or e.g. :append:aglcontainerhost The 2nd condition / override is important here to pass the check. A simple :append would triger c) distill the recipe down to just the required changes & if possible upstream these (e.g. PACKAGECONFIG options) ... config file changes can also be added in a "dlt-daemon-conf" package and replace or amend the original files. This helps most. a) will have immediate effect but only c) and b) will lower the workload mid- term. A path forward would then be: Upstream the PACKAGECONFIG bits . It might make sense to rework the package so there is a configuration sub-package that is replaceable by the user. Then most conf file changes are in a separate package and can be easily replaced by the user w/o even touching the main (binary) package. That is of importance for reproducible builds and binary feeds. Am Montag, 8. April 2024, 14:36:38 CEST schrieb Duy via lists.yoctoproject.org: > Hi Richard, > > Thanks for your response. > Here is one of the recipe bbappend files I'm working on: > meta-agl-ic-container/recipes-extended/dlt-daemon/dlt-daemon_%.bbappend · > master · Automotive Grade Linux / AGL / meta-agl-devel · GitLab ( > https://gitlab.com/automotivegradelinux/AGL/meta-agl-devel/-/blob/master/me > ta-agl-ic-container/recipes-extended/dlt-daemon/dlt-daemon_%25.bbappend?ref_ > type=heads ) > meta-agl-ic-container/recipes-extended/dlt-daemon/dlt-daemon_%.bbappend · > master · Automotive Grade Linux / AGL / meta-agl-devel · GitLab ( > https://gitlab.com/automotivegradelinux/AGL/meta-agl-devel/-/blob/master/me > ta-agl-ic-container/recipes-extended/dlt-daemon/dlt-daemon_%25.bbappend?ref_ > type=heads ) > > I think some configurations are better to be upstreaming, e.g: Adding new > PACKAGES, adding new PACKAGECONFIG. It avoids adding too much to bbappend. > If you have any idea, please share it. > > Best Regards, > Duy Dang -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62929): https://lists.yoctoproject.org/g/yocto/message/62929 Mute This Topic: https://lists.yoctoproject.org/mt/105397924/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Any recommendation to make software layer Yocto Compatible?
On Mon, 2024-04-08 at 05:36 -0700, Duy wrote: > Hi Richard, > > Thanks for your response. > Here is one of the recipe bbappend files I'm working on: > meta-agl-ic-container/recipes-extended/dlt-daemon/dlt- > daemon_%.bbappend · master · Automotive Grade Linux / AGL / meta-agl- > devel · GitLab > meta-agl-ic-container/recipes-extended/dlt-daemon/dlt- > daemon_%.bbappend · master · Automotive Grade Linux / AGL / meta-agl- > devel · GitLab > > I think some configurations are better to be upstreaming, e.g: Adding > new PACKAGES, adding new PACKAGECONFIG. It avoids adding too much to > bbappend. If you have any idea, please share it. Where possible please do share changes with upstream recipes, particularly for things like PACKAGECONFIG entries. There is no good reason to have them separate in most cases. Other parts of this look to be adding configuration files. Are these generally useful? That might help to know if they should be upstream. If not, should they be in a separate recipe? This isn't just a software layer, it has quite a bit of configuration/distro policy in there so the layer checks are right to flag it as problematic in my view. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62928): https://lists.yoctoproject.org/g/yocto/message/62928 Mute This Topic: https://lists.yoctoproject.org/mt/105397924/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Correct way for multiple recipes to install files in the same directory
As I have no prior experience with classes I'll have to read through the manual to learn and I'll have that in mind, cheers. Från: Markus Volk Skickat: den 13 april 2024 00:48 Till: yocto@lists.yoctoproject.org ; linusnils...@hotmail.com Ämne: Re: [yocto] Correct way for multiple recipes to install files in the same directory On Fri, Apr 12 2024 at 09:14:45 AM -07:00:00, Linus Nilsson wrote: I haven't worked with the classes yet but I can see how they can be used to make things a lot easier in my case. But don't use classen too invasively. They can be problematic, e.g. an :append may be ignored depending on the BBFILE_PRIORITY of a layer -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62927): https://lists.yoctoproject.org/g/yocto/message/62927 Mute This Topic: https://lists.yoctoproject.org/mt/105458437/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
