Re: [linux-yocto][yocto-kernel-cache yocto-6.6][PATCH] nxp-imx6: Add scc and cfg files for nxp-imx6 platform
In message: [linux-yocto][yocto-kernel-cache yocto-6.6][PATCH] nxp-imx6: Add scc and cfg files for nxp-imx6 platform on 06/06/2024 Xiaolei Wang wrote: > new scc and cfg files for BSP nxp-imx6 on branch yocto-6.6. merged. Bruce > > 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| 7 + > 4 files changed, 247 insertions(+) > create mode 100644 bsp/nxp-imx6/nxp-imx6-preempt-rt.scc > create mode 100644 bsp/nxp-imx6/nxp-imx6-standard.scc > create mode 100644 bsp/nxp-imx6/nxp-imx6.cfg > create mode 100644 bsp/nxp-imx6/nxp-imx6.scc > > diff --git a/bsp/nxp-imx6/nxp-imx6-preempt-rt.scc > b/bsp/nxp-imx6/nxp-imx6-preempt-rt.scc > new file mode 100644 > index ..2d726c5f > --- /dev/null > +++ b/bsp/nxp-imx6/nxp-imx6-preempt-rt.scc > @@ -0,0 +1,7 @@ > +define KMACHINE nxp-imx6 > +define KTYPE preempt-rt > +define KARCH arm > + > +include ktypes/preempt-rt > + > +include nxp-imx6.scc > diff --git a/bsp/nxp-imx6/nxp-imx6-standard.scc > b/bsp/nxp-imx6/nxp-imx6-standard.scc > new file mode 100644 > index ..c7d7c920 > --- /dev/null > +++ b/bsp/nxp-imx6/nxp-imx6-standard.scc > @@ -0,0 +1,7 @@ > +define KMACHINE nxp-imx6 > +define KTYPE standard > +define KARCH arm > + > +include ktypes/standard > + > +include nxp-imx6.scc > diff --git a/bsp/nxp-imx6/nxp-imx6.cfg b/bsp/nxp-imx6/nxp-imx6.cfg > new file mode 100644 > index ..e43d5a92 > --- /dev/null > +++ b/bsp/nxp-imx6/nxp-imx6.cfg > @@ -0,0 +1,226 @@ > +CONFIG_ARCH_MXC=y > +CONFIG_SOC_IMX6UL=y > +CONFIG_SOC_IMX6Q=y > +CONFIG_SOC_IMX6SX=y > + > +CONFIG_FW_LOADER=y > +CONFIG_FW_LOADER_USER_HELPER=y > +CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y > + > +CONFIG_CPU_FREQ=y > +CONFIG_CPU_FREQ_GOV_POWERSAVE=y > +CONFIG_CPU_FREQ_GOV_USERSPACE=y > +CONFIG_CPU_FREQ_GOV_ONDEMAND=y > +CONFIG_ARM_IMX6Q_CPUFREQ=y > + > +CONFIG_SMP=y > +CONFIG_NR_CPUS=4 > + > +CONFIG_CPU_IDLE=y > +CONFIG_CPU_IDLE_GOV_MENU=y > + > +CONFIG_VFP=y > +CONFIG_NEON=y > + > +CONFIG_MXC_CLK=y > + > +CONFIG_DMADEVICES=y > +CONFIG_IMX_SDMA=m > +CONFIG_MXS_DMA=y > +CONFIG_DMA_OF=y > +CONFIG_MXC_PXP_V2=y > + > +CONFIG_CFG80211=y > +CONFIG_MAC80211=y > + > +CONFIG_AT803X_PHY=y > +CONFIG_MICREL_PHY=y > +CONFIG_CAN=y > +CONFIG_CAN_VCAN=y > +CONFIG_CAN_FLEXCAN=y > + > +CONFIG_CMA=y > +CONFIG_IMX_WEIM=y > + > +CONFIG_MTD=y > +CONFIG_MTD_CMDLINE_PARTS=y > +CONFIG_MTD_BLOCK=y > +CONFIG_MTD_CFI=y > +CONFIG_MTD_JEDECPROBE=y > +CONFIG_MTD_CFI_INTELEXT=y > +CONFIG_MTD_CFI_AMDSTD=y > +CONFIG_MTD_CFI_STAA=y > +CONFIG_MTD_PHYSMAP=y > +CONFIG_MTD_DATAFLASH=y > +CONFIG_MTD_SPI_NOR=y > +CONFIG_SPI_FSL_QUADSPI=y > +CONFIG_SPI_FSL_LPSPI=y > +CONFIG_MTD_SST25L=y > + > +CONFIG_MTD_RAW_NAND=y > +CONFIG_MTD_NAND_GPMI_NAND=y > +CONFIG_MTD_NAND_MXC=y > +CONFIG_MTD_UBI=y > + > +CONFIG_INPUT_EVDEV=y > +CONFIG_KEYBOARD_IMX=y > +CONFIG_KEYBOARD_GPIO=y > + > +CONFIG_INPUT_TOUCHSCREEN=y > +CONFIG_TOUCHSCREEN_EGALAX=y > +CONFIG_TOUCHSCREEN_MAX11801=y > +CONFIG_TOUCHSCREEN_IMX6UL_TSC=y > + > +CONFIG_INPUT_MISC=y > +CONFIG_INPUT_MMA8450=y > + > +CONFIG_SERIAL_IMX=y > +CONFIG_SERIAL_IMX_CONSOLE=y > +CONFIG_SERIAL_FSL_LPUART=y > +CONFIG_SERIAL_FSL_LPUART_CONSOLE=y > + > +CONFIG_NVMEM_IMX_OCOTP=y > + > +CONFIG_I2C_CHARDEV=y > +CONFIG_I2C_IMX=y > + > +CONFIG_SPI=y > +CONFIG_SPI_IMX=y > +CONFIG_SPI_GPIO=y > + > +CONFIG_POWER_SUPPLY=y > +CONFIG_WATCHDOG=y > +CONFIG_IMX2_WDT=y > + > +CONFIG_MFD_DA9052_I2C=y > +CONFIG_MFD_MC13XXX_SPI=y > +CONFIG_MFD_MC13XXX_I2C=y > +CONFIG_MFD_SI476X_CORE=y > + > +CONFIG_REGULATOR=y > +CONFIG_REGULATOR_FIXED_VOLTAGE=y > +CONFIG_REGULATOR_ANATOP=y > +CONFIG_REGULATOR_PFUZE100=y > + > +CONFIG_THERMAL=y > +CONFIG_DEVICE_THERMAL=y > +CONFIG_CPU_THERMAL=y > +CONFIG_IMX_THERMAL=y > + > +CONFIG_MEDIA_SUPPORT=y > +CONFIG_MEDIA_PLATFORM_SUPPORT=y > +CONFIG_MEDIA_CAMERA_SUPPORT=y > +CONFIG_V4L_MEM2MEM_DRIVERS=y > +CONFIG_VIDEO_CODA=y > +CONFIG_V4L_PLATFORM_DRIVERS=y > +CONFIG_STAGING=y > +CONFIG_STAGING_MEDIA=y > +CONFIG_VIDEO_MXC_CAPTURE=m > +CONFIG_VIDEO_MXC_OUTPUT=y > +CONFIG_VIDEO_MXC_CSI_CAMERA=m > +CONFIG_MXC_IPU_DEVICE_QUEUE_SDC=m > +CONFIG_MXC_CAMERA_OV5640=m > +CONFIG_MXC_CAMERA_OV5640_V2=m > +CONFIG_MXC_CAMERA_OV5640_MIPI=m > +CONFIG_MXC_CAMERA_OV5640_MIPI_V2=m > +CONFIG_MXC_MIPI_CSI=m > +CONFIG_MXC_MIPI_CSI2=y > +CONFIG_VIDEO_MXC_PXP_V4L2=y > +CONFIG_VIDEO_MUX=y > + > +CONFIG_DRM=y > +CONFIG_FB=y > +CONFIG_BACKLIGHT_CLASS_DEVICE=y > +CONFIG_LCD_CLASS_DEVICE=y > +CONFIG_LCD_L4F00242T03=y > +CONFIG_LCD_PLATFORM=y > +CONFIG_BACKLIGHT_PWM=y > +CONFIG_MXC_IPU=y > +CONFIG_FB_MXC_SYNC_PANEL=y > +CONFIG_FB_MXS=y > +CONFIG_FB_MXC_MIPI_DSI=y > +CONFIG_FB_MXC_LDB=y > +CONFIG_FB_MXC_HDMI=y > +CONFIG_MXC_GPU_VIV=y > + > +CONFIG_FRAMEBUFFER_CONSOLE=y > +CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y > + > +CONFIG_USB=y > +CONFIG_USB_OTG=y > +CONFIG_USB_CHIPIDEA=y > +CONFIG_USB_CHIPIDEA_UDC=y >
Re: [linux-yocto] [PATCH 00/14] Patches for nxp-soc
In message: [PATCH 00/14] Patches for nxp-soc on 06/06/2024 Xiaolei Wang wrote: > 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 > drm/bridge: it6263: fix a memory leak when application changeset fails > irqchip: imx-irqsteer: Block the runtime PM > ARM: imx: use raw_spin_lock instead of spin_lock > drm/bridge: adv7533: Limit supported clocks > video: fbdev: mxc: Release the previously allocated modedb before > parsing edid > video: sii902x: Fix panic caused by sii902x_read_edid > video: fbdev: mxc: hdmi: Fix a memory leak in mxc_hdmi_disp_init > arm: dts: imx6q-sabresd: Enable imx6q pcie > ARM: imx: use raw_spin_lock instead of spin_lock in gpc.c > ARM: imx: use raw_spin_lock instead of spin_lock in gpcv2.c > gpu: imx: dpu: Use raw_spin_lock instead of mutex_lock merged. Bruce > > Xiaolei Wang via lists.yoctoproject.org (1): > imx: dpu-blit: Remove GFP_DMA32 > > arch/arm/boot/dts/nxp/imx/imx6q-sabresd.dts | 4 + > arch/arm/mach-imx/Kconfig| 1 + > arch/arm/mach-imx/Makefile | 2 +- > arch/arm/mach-imx/gpc.c | 14 +-- > arch/arm/mach-imx/gpcv2.c| 30 +++ > arch/arm/mach-imx/src.c | 18 ++-- > drivers/gpu/drm/bridge/adv7511/adv7511_drv.c | 4 +- > drivers/gpu/drm/bridge/adv7511/adv7533.c | 31 +++ > drivers/gpu/drm/bridge/it6263.c | 4 +- > drivers/gpu/imx/dpu-blit/dpu-blit.c | 2 +- > drivers/gpu/imx/dpu/dpu-fetchdecode.c| 94 ++-- > drivers/gpu/imx/dpu/dpu-fetcheco.c | 56 ++-- > drivers/gpu/imx/dpu/dpu-fetchlayer.c | 48 +- > drivers/gpu/imx/dpu/dpu-fetchunit.c | 44 - > drivers/gpu/imx/dpu/dpu-fetchwarp.c | 48 +- > drivers/irqchip/irq-imx-irqsteer.c | 1 + > drivers/video/fbdev/mxc/mxc_edid.c | 2 + > drivers/video/fbdev/mxc/mxc_hdmi.c | 1 + > drivers/video/fbdev/mxc/mxsfb_sii902x.c | 2 +- > include/video/dpu.h | 2 +- > 20 files changed, 226 insertions(+), 182 deletions(-) > > -- > 2.25.1 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13996): https://lists.yoctoproject.org/g/linux-yocto/message/13996 Mute This Topic: https://lists.yoctoproject.org/mt/106517203/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][v6.6/standard/x86 and v6.6/standard/preempt-rt/x86][PATCH 0/3] Patches for Intel Grand Ridge and Snow Ridge
In message: [linux-yocto][v6.6/standard/x86 and v6.6/standard/preempt-rt/x86][PATCH 0/3] Patches for Intel Grand Ridge and Snow Ridge on 05/06/2024 yongxin@windriver.com wrote: > 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". merged. Bruce > > They are from Intel's repo > https://github.com/intel-collab/networking.wireless.transport.rdk.board-support.meta-intel-axxia.git > > 1) Patch "drivers/watchdog: Ignore 'No Reboot' Bit" will do nothing unless > 'iTCO_wdt.assume_noreboot_access=1' is added to the kernel command line. > > 2) Patch "clocksource: Add option to force acpi_pm as clocksource watchdog" > adds a kernel command line option to force the use of acpi_pm as the > watchdog clocksource. To use it add "ricardo_clocksource_wd=force_acpi_pm_wd" > to kernel command line. > > 3) Patch "iommu: Add support to change default domain of an iommu group" > only adds macros for GRR (8086:0dbd), GRR_QAT_PF (8086:578a) and and > GRR_QAT_VF (8086:578b). > > > John Jacques (2): > drivers/watchdog: Ignore 'No Reboot' Bit > clocksource: Add option to force acpi_pm as clocksource watchdog > > Sai Praneeth Prakhya (1): > iommu: Add support to change default domain of an iommu group > > drivers/iommu/intel/iommu.c | 14 +++ > drivers/watchdog/iTCO_wdt.c | 46 + > kernel/time/clocksource.c | 82 - > 3 files changed, 124 insertions(+), 18 deletions(-) > > Thanks, > Yongxin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13995): https://lists.yoctoproject.org/g/linux-yocto/message/13995 Mute This Topic: https://lists.yoctoproject.org/mt/106499071/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][linux-yocto v6.1] kernel code for marvell octeon
In message: [linux-yocto][linux-yocto v6.1] kernel code for marvell octeon on 03/06/2024 Ruiqiang Hao wrote: > Hi Bruce, > > Please help to merge this patch into our linux-yocto repo. > > repo: > linux-yocto > branch: > v6.1/standard/cn-sdkv5.15/octeon > v6.1/standard/preempt-rt/cn-sdkv5.15/octeon merged. Bruce > > Thanks, > Ruiqiang > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13972): https://lists.yoctoproject.org/g/linux-yocto/message/13972 Mute This Topic: https://lists.yoctoproject.org/mt/106458052/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto]: [kernel/kernel-rt]: nxp-ls1028: port kernel patches for nxp-ls1028
In message: [linux-yocto]: [kernel/kernel-rt]: nxp-ls1028: port kernel patches for nxp-ls1028 on 31/05/2024 Meng Li wrote: > From: Limeng > > Hi Bruce, > > The 7 patches are used to fix issues for NXP ls1028 BSP > So, could you please help merge these patches into linux-ycoto kernel, both > below 2 branchs? > v6.6/standard/nxp-sdk-6.6/nxp-soc > v6.6/standard/preempt-rt/nxp-sdk-6.6/nxp-soc > > diffstat info as below: > > b/drivers/i2c/busses/Kconfig |1 - > b/drivers/net/ethernet/freescale/enetc/enetc_pf.c | 67 > +++ > b/drivers/net/ethernet/freescale/enetc/enetc_tsn.c |4 > b/drivers/net/phy/Kconfig |1 + > b/net/tsn/genl_tsn.c |6 +++--- > drivers/net/ethernet/freescale/enetc/enetc_tsn.c | 11 +++ > 6 files changed, 86 insertions(+), 4 deletions(-) merged. Bruce > > > Pull request info as below: > > The following changes since commit 5422d57e79fa0c5b6a47fe18b5ea783224c18372: > > Merge branch 'v6.6/standard/base' into v6.6/standard/nxp-sdk-6.6/nxp-soc > (2024-05-28 13:31:22 -0400) > > are available in the Git repository at: > > https://github.com/limeng-linux/linux-yocto-bsp.git > v6.6/standard/nxp-sdk-6.6/nxp-soc > > for you to fetch changes up to 11ec379557d5960e98cb39faf787e587bc9d0ac9: > > net: phy: let PHYLINK select MII (2024-05-31 04:50:55 -0400) > > > Meng Li (6): > tsn: replace GFP_KERNEL with GFP_ATOMIC to avoid sleeping in atomic > context > enetc: add suspend/resume function to manage pm in ethernet driver > enetc: tsn: release resource before exiting enetc_qci_fmi_get() function > enetc: tsn: release resource before exiting > enetc_qci_sfi_counters_get() function > drivers: i2c: remove default y from I2C_IMX_FLEXIO config > drivers: enetc: tsn: free the CBS structure enetc_tsn_deinit() function > > Xulin Sun (1): > net: phy: let PHYLINK select MII > > drivers/i2c/busses/Kconfig | 1 - > drivers/net/ethernet/freescale/enetc/enetc_pf.c | 67 > +++ > drivers/net/ethernet/freescale/enetc/enetc_tsn.c | 15 +++ > drivers/net/phy/Kconfig | 1 + > net/tsn/genl_tsn.c | 6 +++--- > 5 files changed, 86 insertions(+), 4 deletions(-) > > > thanks, > Limeng -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13971): https://lists.yoctoproject.org/g/linux-yocto/message/13971 Mute This Topic: https://lists.yoctoproject.org/mt/106404616/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [PATCH] nxp-ls1028: add scc and cfg files for nxp-ls1028 platform
merged. Bruce In message: [PATCH] nxp-ls1028: add scc and cfg files for nxp-ls1028 platform on 31/05/2024 Meng Li wrote: > Refer to scc and cfg files on branch yocto-6.1, add new scc and cfg > files for BSP nxp-ls1028 on branch yocto-6.6. > > Signed-off-by: Meng Li > --- > bsp/nxp-ls1028/nxp-ls1028-preempt-rt.scc | 7 + > bsp/nxp-ls1028/nxp-ls1028-standard.scc | 8 + > bsp/nxp-ls1028/nxp-ls1028.cfg| 247 +++ > bsp/nxp-ls1028/nxp-ls1028.scc| 9 + > 4 files changed, 271 insertions(+) > create mode 100644 bsp/nxp-ls1028/nxp-ls1028-preempt-rt.scc > create mode 100644 bsp/nxp-ls1028/nxp-ls1028-standard.scc > create mode 100644 bsp/nxp-ls1028/nxp-ls1028.cfg > create mode 100644 bsp/nxp-ls1028/nxp-ls1028.scc > > diff --git a/bsp/nxp-ls1028/nxp-ls1028-preempt-rt.scc > b/bsp/nxp-ls1028/nxp-ls1028-preempt-rt.scc > new file mode 100644 > index ..6a8eb90d > --- /dev/null > +++ b/bsp/nxp-ls1028/nxp-ls1028-preempt-rt.scc > @@ -0,0 +1,7 @@ > +define KMACHINE nxp-ls1028 > +define KTYPE preempt-rt > +define KARCH arm64 > + > +include ktypes/preempt-rt > + > +include nxp-ls1028.scc > diff --git a/bsp/nxp-ls1028/nxp-ls1028-standard.scc > b/bsp/nxp-ls1028/nxp-ls1028-standard.scc > new file mode 100644 > index ..151e1661 > --- /dev/null > +++ b/bsp/nxp-ls1028/nxp-ls1028-standard.scc > @@ -0,0 +1,8 @@ > +# SPDX-License-Identifier: MIT > +define KMACHINE nxp-ls1028 > +define KTYPE standard > +define KARCH arm64 > + > +include ktypes/standard > + > +include nxp-ls1028.scc > diff --git a/bsp/nxp-ls1028/nxp-ls1028.cfg b/bsp/nxp-ls1028/nxp-ls1028.cfg > new file mode 100644 > index ..818431b7 > --- /dev/null > +++ b/bsp/nxp-ls1028/nxp-ls1028.cfg > @@ -0,0 +1,247 @@ > +CONFIG_ARM64=y > +CONFIG_64BIT=y > +CONFIG_ARCH_NXP=y > +CONFIG_ARCH_LAYERSCAPE=y > +CONFIG_MMU=y > +CONFIG_SMP=y > +CONFIG_NR_CPUS=2 > + > +CONFIG_SCHED_MC=y > +CONFIG_ARM64_VA_BITS_48=y > + > +CONFIG_PCI=y > +CONFIG_PCIEPORTBUS=y > +CONFIG_HOTPLUG_PCI_PCIE=y > +CONFIG_HOTPLUG_PCI=y > +CONFIG_PCI_LAYERSCAPE=y > +CONFIG_PCI_HOST_GENERIC=y > +CONFIG_PCI_IOV=y > +CONFIG_PCI_MSI=y > + > +CONFIG_CMA=y > + > +CONFIG_CPU_IDLE=y > +CONFIG_ARM_PSCI_CPUIDLE=y > +CONFIG_CPU_IDLE_GOV_MENU=y > +CONFIG_CPU_FREQ=y > +CONFIG_CPU_FREQ_GOV_USERSPACE=y > +CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y > +CONFIG_CPUFREQ_DT=y > +CONFIG_QORIQ_CPUFREQ=y > + > +CONFIG_SOC_BUS=y > +CONFIG_REGMAP=y > +CONFIG_REGMAP_I2C=y > +CONFIG_REGMAP_SPI=y > +CONFIG_REGMAP_MMIO=y > +CONFIG_DMA_SHARED_BUFFER=y > + > +CONFIG_DMA_CMA=y > +CONFIG_MTD=y > +CONFIG_MTD_BLOCK=y > +CONFIG_MTD_CFI=y > +CONFIG_MTD_CFI_ADV_OPTIONS=y > +CONFIG_MTD_CFI_INTELEXT=y > +CONFIG_MTD_CFI_AMDSTD=y > +CONFIG_MTD_PHYSMAP=y > +CONFIG_MTD_PHYSMAP_OF=y > +CONFIG_MTD_SST25L=y > +CONFIG_MTD_RAW_NAND=y > +CONFIG_MTD_SPI_NOR=y > +CONFIG_MTD_NAND_FSL_IFC=y > + > +CONFIG_COMMON_CLK=y > +CONFIG_CLK_QORIQ=y > +CONFIG_CLK_LS1028A_PLLDIG=y > + > +CONFIG_SRAM=y > +CONFIG_EEPROM_AT24=y > + > +CONFIG_ATA=y > +CONFIG_SATA_AHCI=y > +CONFIG_SATA_AHCI_PLATFORM=y > +CONFIG_AHCI_QORIQ=y > + > +CONFIG_NETDEVICES=y > + > +# enetc > +CONFIG_NET_DSA=y > +CONFIG_NET_DSA_TAG_OCELOT=y > +CONFIG_NET_DSA_MSCC_FELIX=y > +CONFIG_NET_SWITCHDEV=y > +CONFIG_FSL_ENETC=y > +CONFIG_FSL_ENETC_CORE=y > +CONFIG_FSL_ENETC_VF=y > +CONFIG_FSL_ENETC_IERB=y > +CONFIG_FSL_ENETC_MDIO=y > +CONFIG_FSL_ENETC_PTP_CLOCK=y > +CONFIG_FSL_ENETC_QOS=y > +CONFIG_PHY_FSL_LYNX_10G=y > + > +# tsn > +CONFIG_PTP_1588_CLOCK=y > +CONFIG_PTP_1588_CLOCK_QORIQ=y > +CONFIG_TSN=y > +CONFIG_NET_PKTGEN=y > +CONFIG_NET_VENDOR_MICROSEMI=y > +CONFIG_MSCC_OCELOT_SWITCH=y > +CONFIG_MSCC_OCELOT_SWITCH_LIB=y > +CONFIG_VITESSE_PHY=y > +CONFIG_NET_SCH_ETF=y > +CONFIG_NET_SCH_CBS=y > +CONFIG_NET_SCH_MQPRIO=y > +CONFIG_NET_SCH_TAPRIO=y > +CONFIG_VLAN_8021Q=y > + > +CONFIG_BRIDGE=y > +CONFIG_BRIDGE_VLAN_FILTERING=y > + > +# can > +CONFIG_CAN=y > +CONFIG_CAN_FLEXCAN=y > + > +CONFIG_INPUT_MATRIXKMAP=y > +CONFIG_INPUT_EVDEV=y > +CONFIG_INPUT_MISC=y > +CONFIG_KEYBOARD_ADC=m > +CONFIG_KEYBOARD_GPIO=y > +CONFIG_INPUT_MOUSEDEV=y > +CONFIG_MOUSE_PS2=y > + > +CONFIG_SERIAL_8250=y > +CONFIG_SERIAL_8250_CONSOLE=y > +CONFIG_SERIAL_OF_PLATFORM=y > + > +CONFIG_I2C=y > +CONFIG_I2C_CHARDEV=y > +CONFIG_I2C_MUX=y > +CONFIG_I2C_IMX=y > +CONFIG_I2C_COMPAT=y > +CONFIG_I2C_MUX_PCA954x=y > + > +CONFIG_SPI=y > +CONFIG_SPI_FSL_DSPI=y > +CONFIG_SPI_NXP_FLEXSPI=y > + > +CONFIG_GPIOLIB=y > +CONFIG_OF_GPIO=y > +CONFIG_GPIOLIB_IRQCHIP=y > +CONFIG_GPIO_PCA953X=y > +CONFIG_GPIO_PCA953X_IRQ=y > +CONFIG_GPIO_GENERIC=y > +CONFIG_GPIO_DWAPB=y > +CONFIG_GPIO_GENERIC_PLATFORM=y > +CONFIG_GPIO_MB86S7X=y > +CONFIG_GPIO_MPC8XXX=y > +CONFIG_GPIO_PL061=y > +CONFIG_GPIO_XGENE=y > + > +CONFIG_POWER_RESET_XGENE=y > +CONFIG_POWER_RESET_SYSCON=y > +CONFIG_ENERGY_MODEL=y > + > +CONFIG_SYSCON_REBOOT_MODE=y > +CONFIG_BATTERY_BQ27XXX=y > +CONFIG_SENSORS_LM90=m > +CONFIG_SENSORS_INA2XX=m > + > +CONFIG_CPU_THERMAL=y > + > +CONFIG_WATCHDOG=y > +CONFIG_IMX2_WDT=y >
Re: [linux-yocto][linux-yocto v5.15] kernel code for marvell octeon
In message: [linux-yocto][linux-yocto v5.15] kernel code for marvell octeon on 31/05/2024 Ruiqiang Hao wrote: > Hi Bruce, > > Please help to merge this patch into our linux-yocto repo. > > repo: > linux-yocto > branch: > v5.15/standard/cn-sdkv5.4/octeon > v5.15/standard/preempt-rt/cn-sdkv5.4/octeon > v5.15/standard/cn-sdkv5.15/octeon > v5.15/standard/preempt-rt/cn-sdkv5.15/octeon merged Bruce > > Thanks, > Ruiqiang > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13969): https://lists.yoctoproject.org/g/linux-yocto/message/13969 Mute This Topic: https://lists.yoctoproject.org/mt/106400510/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [PATCH linux-yocto] net: bcmgenet: Clean up unnecessary changes
In message: [PATCH linux-yocto] net: bcmgenet: Clean up unnecessary changes
on 29/05/2024 Kevin Hao wrote:
> From: Kevin Hao
>
> It seems that the changes introduced by following SDK commits on rpi
> branch sneak into s32g branch via merge 7dc7e308a5a8 ("Merge branch
> 'v6.1/standard/base' into v6.1/standard/nxp-sdk-5.15/nxp-s32g").
> 7cd65778c0c1 ("bcmgenet: Better coalescing parameter defaults")
> 722216493f90 ("net: bcmgenet: Add 'eee' module parameter")
> 97c843b196d3 ("net: bcmgenet: Workaround #2 for Pi4 Ethernet fail")
>
> Clean up all of them.
>
> Signed-off-by: Kevin Hao
> ---
> Hi Bruce,
>
> Please help me merge this patch into the following branch:
> v6.1/standard/nxp-sdk-5.15/nxp-s32g
merged.
Bruce
> ---
> drivers/net/ethernet/broadcom/genet/bcmgenet.c | 29
> ++
> 1 file changed, 2 insertions(+), 27 deletions(-)
>
> diff --git a/drivers/net/ethernet/broadcom/genet/bcmgenet.c
> b/drivers/net/ethernet/broadcom/genet/bcmgenet.c
> index 0a8bea6c4755..f087a9716409 100644
> --- a/drivers/net/ethernet/broadcom/genet/bcmgenet.c
> +++ b/drivers/net/ethernet/broadcom/genet/bcmgenet.c
> @@ -67,12 +67,6 @@
>
> /* Forward declarations */
> static void bcmgenet_set_rx_mode(struct net_device *dev);
> -static bool skip_umac_reset = false;
> -module_param(skip_umac_reset, bool, 0444);
> -MODULE_PARM_DESC(skip_umac_reset, "Skip UMAC reset step");
> -static bool eee = true;
> -module_param(eee, bool, 0444);
> -MODULE_PARM_DESC(eee, "Enable EEE (default Y)");
>
> static inline void bcmgenet_writel(u32 value, void __iomem *offset)
> {
> @@ -2500,11 +2494,6 @@ static void reset_umac(struct bcmgenet_priv *priv)
> bcmgenet_rbuf_ctrl_set(priv, 0);
> udelay(10);
>
> - if (skip_umac_reset) {
> - pr_warn("Skipping UMAC reset\n");
> - return;
> - }
> -
> /* issue soft reset and disable MAC while updating its registers */
> spin_lock_bh(>reg_lock);
> bcmgenet_umac_writel(priv, CMD_SW_RESET, UMAC_CMD);
> @@ -2676,7 +2665,7 @@ static void bcmgenet_init_tx_ring(struct bcmgenet_priv
> *priv,
>
> bcmgenet_tdma_ring_writel(priv, index, 0, TDMA_PROD_INDEX);
> bcmgenet_tdma_ring_writel(priv, index, 0, TDMA_CONS_INDEX);
> - bcmgenet_tdma_ring_writel(priv, index, 10, DMA_MBUF_DONE_THRESH);
> + bcmgenet_tdma_ring_writel(priv, index, 1, DMA_MBUF_DONE_THRESH);
> /* Disable rate control for now */
> bcmgenet_tdma_ring_writel(priv, index, flow_period_val,
> TDMA_FLOW_PERIOD);
> @@ -3451,17 +3440,6 @@ static int bcmgenet_open(struct net_device *dev)
>
> bcmgenet_phy_pause_set(dev, priv->rx_pause, priv->tx_pause);
>
> - if (!eee) {
> - struct ethtool_eee eee_data;
> -
> - ret = bcmgenet_get_eee(dev, _data);
> - if (ret == 0) {
> - eee_data.eee_enabled = 0;
> - bcmgenet_set_eee(dev, _data);
> - netdev_warn(dev, "EEE disabled\n");
> - }
> - }
> -
> bcmgenet_netif_start(dev);
>
> netif_tx_start_all_queues(dev);
> @@ -4182,12 +4160,9 @@ static int bcmgenet_probe(struct platform_device *pdev)
> netif_set_real_num_rx_queues(priv->dev, priv->hw_params->rx_queues + 1);
>
> /* Set default coalescing parameters */
> - for (i = 0; i < priv->hw_params->rx_queues; i++) {
> + for (i = 0; i < priv->hw_params->rx_queues; i++)
> priv->rx_rings[i].rx_max_coalesced_frames = 1;
> - priv->rx_rings[i].rx_coalesce_usecs = 50;
> - }
> priv->rx_rings[DESC_INDEX].rx_max_coalesced_frames = 1;
> - priv->rx_rings[DESC_INDEX].rx_coalesce_usecs = 50;
>
> /* libphy will determine the link state */
> netif_carrier_off(dev);
>
> ---
> base-commit: 7dc7e308a5a8cac4af482633cdefb514bfff8766
> change-id: 20240529-s32g-13fe3d379dfc
>
> Best regards,
> --
> Kevin Hao
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13961):
https://lists.yoctoproject.org/g/linux-yocto/message/13961
Mute This Topic: https://lists.yoctoproject.org/mt/106360767/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][yocto-kernel-cache][yocto-5.15/yocto-6.1/yocto-6.6/master][PATCH] features/kvm: enable CONFIG_VIRTUALIZATION
In message: [linux-yocto][yocto-kernel-cache][yocto-5.15/yocto-6.1/yocto-6.6/master][PATCH] features/kvm: enable CONFIG_VIRTUALIZATION on 21/05/2024 Liu Haitao wrote: > The CONFIG_VIRTUALIZATION is not enabled for ARM64, but it is > default for X86. And CONFIG_KVM depends on CONFIG_VIRTUALIZATION. > > The CONFIG_KVM is a bool type in ARM64, it could not be built as > a kernel module. But that does't mean we should build it in for x86 as well, since if it is still tristate there, we should keep the existing behaviour. You can check the KARCH in a .scc file, so we can adjust the option based on the architecture. Just split the conditional option out to a standalone .cfg file and include the one we want based on architecture. Bruce > > Signed-off-by: Liu Haitao > --- > features/kvm/qemu-kvm.cfg | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/features/kvm/qemu-kvm.cfg b/features/kvm/qemu-kvm.cfg > index aa0c29ff..6e1d1671 100644 > --- a/features/kvm/qemu-kvm.cfg > +++ b/features/kvm/qemu-kvm.cfg > @@ -1,5 +1,6 @@ > # SPDX-License-Identifier: MIT > -CONFIG_KVM=m > +CONFIG_VIRTUALIZATION=y > +CONFIG_KVM=y > CONFIG_KVM_INTEL=m > CONFIG_KVM_AMD=m > CONFIG_TUN=y > -- > 2.39.0 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13959): https://lists.yoctoproject.org/g/linux-yocto/message/13959 Mute This Topic: https://lists.yoctoproject.org/mt/106238645/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][v5.10/standard/x86 && v5.10/standard/preempt-rt/x86][PATCH] ixgbe: report link state for VF devices
merged. Bruce In message: [linux-yocto][v5.10/standard/x86 && v5.10/standard/preempt-rt/x86][PATCH] ixgbe: report link state for VF devices on 22/05/2024 Liu Haitao wrote: > From: Ovidiu Panait > > commit 738808ae82d908e5ef4bd025999d44510c0710a7 upstream > > The link state of VF devices can be controlled via "ip link set", but the > current state (auto/disabled) is not reported by "ip link show". > > Update ixgbe_ndo_get_vf_config() to make this info available to userspace. > > Reviewed-by: Przemek Kitszel > Signed-off-by: Ovidiu Panait > Tested-by: Rafal Romanowski > Signed-off-by: Tony Nguyen > Signed-off-by: Liu Haitao > --- > drivers/net/ethernet/intel/ixgbe/ixgbe_sriov.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_sriov.c > b/drivers/net/ethernet/intel/ixgbe/ixgbe_sriov.c > index 15f1eb1c94e4..6f59c937bb8b 100644 > --- a/drivers/net/ethernet/intel/ixgbe/ixgbe_sriov.c > +++ b/drivers/net/ethernet/intel/ixgbe/ixgbe_sriov.c > @@ -1851,5 +1851,6 @@ int ixgbe_ndo_get_vf_config(struct net_device *netdev, > ivi->spoofchk = adapter->vfinfo[vf].spoofchk_enabled; > ivi->rss_query_en = adapter->vfinfo[vf].rss_query_enabled; > ivi->trusted = adapter->vfinfo[vf].trusted; > + ivi->linkstate = adapter->vfinfo[vf].link_state; > return 0; > } > -- > 2.39.0 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13958): https://lists.yoctoproject.org/g/linux-yocto/message/13958 Mute This Topic: https://lists.yoctoproject.org/mt/106239654/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [kernel-cache][PATCH] features/intel-npu: introduce Intel NPU fragment
On Sun, May 26, 2024 at 9:30 PM Saini, Naveen Kumar wrote: > > Hi Bruce. I missed your reply. > > Pls merge it in both 6.6 and master. > merged. Bruce > Regards, > Naveen > > > -Original Message- > > From: linux-yocto@lists.yoctoproject.org > yo...@lists.yoctoproject.org> On Behalf Of Bruce Ashfield > > Sent: Thursday, May 16, 2024 10:23 PM > > To: Saini, Naveen Kumar > > Cc: linux-yocto@lists.yoctoproject.org > > Subject: Re: [linux-yocto] [kernel-cache][PATCH] features/intel-npu: > > introduce Intel NPU fragment > > > > Which branches were to looking at for this ? > > > > 6.6 and master ? > > > > just master ? > > > > Bruce > > > > In message: [kernel-cache][PATCH] features/intel-npu: introduce Intel NPU > > fragment on 15/05/2024 Naveen Saini wrote: > > > > > Add config fragment for the system with an 14th generation Intel CPU > > > (Meteor Lake) or newer. It will allow users to enable Intel NPU > > > (formerly called Intel VPU) which is a CPU-integrated inference > > > accelerator for Computer Vision and Deep Learning applications. > > > > > > Signed-off-by: Naveen Saini > > > --- > > > features/intel-npu/intel-npu.cfg | 3 +++ > > > features/intel-npu/intel-npu.scc | 4 > > > kern-features.rc | 1 + > > > 3 files changed, 8 insertions(+) > > > create mode 100644 features/intel-npu/intel-npu.cfg create mode > > > 100644 features/intel-npu/intel-npu.scc > > > > > > diff --git a/features/intel-npu/intel-npu.cfg > > > b/features/intel-npu/intel-npu.cfg > > > new file mode 100644 > > > index ..6b7ced30 > > > --- /dev/null > > > +++ b/features/intel-npu/intel-npu.cfg > > > @@ -0,0 +1,3 @@ > > > +# SPDX-License-Identifier: MIT > > > +CONFIG_DRM_ACCEL=y > > > +CONFIG_DRM_ACCEL_IVPU=m > > > diff --git a/features/intel-npu/intel-npu.scc > > > b/features/intel-npu/intel-npu.scc > > > new file mode 100644 > > > index ..782c8499 > > > --- /dev/null > > > +++ b/features/intel-npu/intel-npu.scc > > > @@ -0,0 +1,4 @@ > > > +# SPDX-License-Identifier: MIT > > > +define KFEATURE_DESCRIPTION "Enable Intel NPU for Computer Vision > > and Deep Learning applications" > > > + > > > +kconf hardware intel-npu.cfg > > > diff --git a/kern-features.rc b/kern-features.rc index > > > 0e83053c..14381cc8 100644 > > > --- a/kern-features.rc > > > +++ b/kern-features.rc > > > @@ -72,6 +72,7 @@ > > > config = features/lxc/lxc-enable.scc > > > config = features/inline/inline.scc > > > config = features/intel-tco/intel-tco.scc > > > + config = features/intel-npu/intel-npu.scc > > > config = features/ftrace/ftrace-function-tracer-disable.scc > > > config = features/ftrace/ftrace.scc > > > config = features/vxlan/vxlan-enable.scc > > > -- > > > 2.37.3 > > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13957): https://lists.yoctoproject.org/g/linux-yocto/message/13957 Mute This Topic: https://lists.yoctoproject.org/mt/106109710/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] Trial merge of v5.15.159 v5.15.160 v6.1.91 v6.1.92 v6.6.31 v6.6.32 for linux-yocto
Thanks Kevin! I've been on vacation, but will be back this coming Monday and will finish updates to all the kernels then! Bruce On Sat, May 25, 2024 at 9:58 PM Kevin Hao wrote: > > Hi Bruce, > > This is a trial merge of the stable kernel v5.15.159 v5.15.160 v6.1.91 > v6.1.92 v6.6.31 v6.6.32 for the following branches in the linux-yocto. > 71048115f6bc v5.15/standard/sdkv5.10/axxia > 72de38604da8 v5.15/standard/preempt-rt/sdkv5.10/axxia > 95258d7b1cd7 v5.15/standard/base > 85a09dd69abb v5.15/standard/preempt-rt/base > 144096b7e6bb v5.15/standard/cn-sdkv5.4/octeon > eeedd0ea8a41 v5.15/standard/preempt-rt/cn-sdkv5.4/octeon > 3de2af0f215a v5.15/standard/cn-sdkv5.15/octeon > 262aa7edc00b v5.15/standard/preempt-rt/cn-sdkv5.15/octeon > 48c64f5f90ee v5.15/standard/ti-sdk-5.10/ti-j72xx > 644f57dc080e v5.15/standard/preempt-rt/ti-sdk-5.10/ti-j72xx > 4e52ba5656ed v5.15/standard/nxp-sdk-5.15/nxp-soc > b5ca29527eb1 v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-soc > 4b38c86c9d72 v5.15/standard/bcm-2xxx-rpi > adf9cbba8eac v5.15/standard/preempt-rt/bcm-2xxx-rpi > 1800f16c4d25 v5.15/standard/nxp-sdk-5.15/nxp-s32g > 45320cac98da v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g > 9aafd46fde6b v5.15/standard/intel-sdk-5.15/intel-socfpga > b748eac10f46 v5.15/standard/preempt-rt/intel-sdk-5.15/intel-socfpga > 757fa6419b4f v5.15/standard/x86 > 39fffb16b6a8 v5.15/standard/preempt-rt/x86 > f4abc01b6b54 v5.15/standard/sdkv5.15/xlnx-soc > 718a476fc58a v5.15/standard/preempt-rt/sdkv5.15/xlnx-soc > 04fe20f000b3 v6.1/standard/sdkv5.10/axxia > f715330d4bdf v6.1/standard/preempt-rt/sdkv5.10/axxia > 3cc712e9b835 v6.1/standard/base > c6148615a795 v6.1/standard/preempt-rt/base > 2d6b57d03053 v6.1/standard/ti-sdk-6.1/ti-j7xxx > a620b934aa82 v6.1/standard/preempt-rt/ti-sdk-6.1/ti-j7xxx > a8e0db5b5960 v6.1/standard/nxp-sdk-6.1/nxp-soc > 5c3103ac22b8 v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc > 790028953b00 v6.1/standard/cn-sdkv5.15/octeon > 368d5d753ad7 v6.1/standard/preempt-rt/cn-sdkv5.15/octeon > efb8e517217a v6.1/standard/cn-sdkv6.1/octeon > 36a686b3d9ce v6.1/standard/preempt-rt/cn-sdkv6.1/octeon > d5407ed638ae v6.1/standard/microchip-polarfire-soc > c745402c3bc1 v6.1/standard/preempt-rt/microchip-polarfire-soc > ba2d9c0ba591 v6.1/standard/bcm-2xxx-rpi > 66e4ec9a762b v6.1/standard/preempt-rt/bcm-2xxx-rpi > baf4dab314d1 v6.1/standard/nxp-sdk-5.15/nxp-s32g > 6cdb1149cf75 v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g > 2f98d321aaf3 v6.1/standard/intel-sdk-6.1/intel-socfpga > e0067719fad7 v6.1/standard/preempt-rt/intel-sdk-6.1/intel-socfpga > 5f3a5048b548 v6.1/standard/x86 > 004b910cdbb0 v6.1/standard/preempt-rt/x86 > 2ee5f4c41819 v6.1/standard/sdkv6.1/xlnx-soc > 81e91feae76c v6.1/standard/preempt-rt/sdkv6.1/xlnx-soc > f1ae4da084b7 v6.6/standard/base > f15d3750043c v6.6/standard/preempt-rt/base > a076027897f0 v6.6/standard/nxp-sdk-6.6/nxp-soc > 6f9248487143 v6.6/standard/preempt-rt/nxp-sdk-6.6/nxp-soc > > - For v5.15.159 v6.1.91 v6.6.31 > Despite the extended stable release period and numerous patches, the merge > conflicts > were not particularly extensive. However, special attention is needed for a > semantic > conflict in the nxp branches (including v5.15, v6.1 and v6.6). To avoid a > compilation > error, we need to include "../host/xhci.h" in > drivers/usb/dwc3/dwc3-imx8mp.c. > > - For v5.15.160 v6.1.92 v6.6.32 > There is no any merge conflict or build error. > > All the branches have passed my build test. I have pushed all these branches > to: > https://github.com/haokexin/linux > > You can use this as a reference for the linux-yocto stable kernel bump. > > Thanks, > Kevin -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13955): https://lists.yoctoproject.org/g/linux-yocto/message/13955 Mute This Topic: https://lists.yoctoproject.org/mt/106308485/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto]: [kernel/kernel-rt v6.1]: driver: sdk_fman: move the irq free operation to the front of releasing register resource
In message: [linux-yocto]: [kernel/kernel-rt v6.1]: driver: sdk_fman: move the irq free operation to the front of releasing register resource on 22/05/2024 Meng Li wrote: > From: Limeng > > Hi Bruce, > > This patch is used to make sure that irq free operation is before releasing > register resource. > Could you please help merge this patch into linux-ycoto kernel? > Branch are v6.1/standard/nxp-sdk-6.1/nxp-soc and > v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc merged. Bruce > > > diffstat info as below: > > lnxwrp_fm.c | 11 ++- > 1 file changed, 6 insertions(+), 5 deletions(-) > > thanks, > Limeng -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13951): https://lists.yoctoproject.org/g/linux-yocto/message/13951 Mute This Topic: https://lists.yoctoproject.org/mt/106237502/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][v6.1/standard/nxp-sdk-6.1/nxp-soc & v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc][PATCH] net: Add judgment on fast_raw_socket_fd
merged.
Bruce
In message: [linux-yocto][v6.1/standard/nxp-sdk-6.1/nxp-soc &
v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc][PATCH] net: Add judgment on
fast_raw_socket_fd
on 20/05/2024 Xiaolei Wang wrote:
> A bug was introduced by commit 20932f1f83d3 ("fec_ecat: add fec native
> driver for raw packet proto"). When both fd and fast_raw_socket_fd are
> -1, the fast_raw_socket_dev would be null, then it will perform a null
> pointer operation and causes the following oops. The fast_raw_socket_dev
> is only set to a valid value when fast_raw_socket_fd is not -1. So add a
> check for fast_raw_socket_fd before invoking
> fast_raw_socket_dev->netdev_ops->ndo_fast_recv().
>
> Unable to handle kernel NULL pointer dereference at virtual address
> 00d8
> Mem abort info:
> ESR = 0x9605
> EC = 0x25: DABT (current EL), IL = 32 bits
> Mem abort info:
> ESR = 0x9605
> EC = 0x25: DABT (current EL), IL = 32 bits
> SET = 0, FnV = 0
> EA = 0, S1PTW = 0
> FSC = 0x05: level 1 translation fault
> SET = 0, FnV = 0
> EA = 0, S1PTW = 0
> FSC = 0x05: level 1 translation fault
> Data abort info:
> ISV = 0, ISS = 0x0005
> Data abort info:
> ISV = 0, ISS = 0x0005
> CM = 0, WnR = 0
> CM = 0, WnR = 0
> user pgtable: 4k pages, 39-bit VAs, pgdp=8aa5
> user pgtable: 4k pages, 39-bit VAs, pgdp=84314000
> [00d8] pgd=, p4d=,
> pud=
> [00d8] pgd=, p4d=,
> pud=
> Internal error: Oops: 9605 [#1] PREEMPT SMP
>
> Fixes: 20932f1f83d3("fec_ecat: add fec native driver for raw packet proto")
> Signed-off-by: Xiaolei Wang
> ---
> net/socket.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/socket.c b/net/socket.c
> index 4fc1e256d0f3..94ff9a5430aa 100644
> --- a/net/socket.c
> +++ b/net/socket.c
> @@ -2209,7 +2209,7 @@ int __sys_recvfrom(int fd, void __user *ubuf, size_t
> size, unsigned int flags,
> int err, err2;
> int fput_needed;
>
> - if (fd == fast_raw_socket_fd) {
> + if (fd == fast_raw_socket_fd && fast_raw_socket_fd != -1) {
> err =
> fast_raw_socket_dev->netdev_ops->ndo_fast_recv(fast_raw_socket_dev, ubuf,
> size, addr, addr_len);
> return err;
> }
> --
> 2.25.1
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13950):
https://lists.yoctoproject.org/g/linux-yocto/message/13950
Mute This Topic: https://lists.yoctoproject.org/mt/106199626/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][v5.10/standard/sdkv5.10/xlnx-soc & v5.10/standard/preempt-rt/sdkv5.10/xlnx-soc][PATCH] fix Revert 2 "spi: spi-zynqmp-gqspi: Fix runtime PM imbalance in zynqmp_qspi_probe"
merged.
Bruce
In message: [linux-yocto][v5.10/standard/sdkv5.10/xlnx-soc &
v5.10/standard/preempt-rt/sdkv5.10/xlnx-soc][PATCH] fix Revert 2 "spi:
spi-zynqmp-gqspi: Fix runtime PM imbalance in zynqmp_qspi_probe"
on 20/05/2024 Li Wang wrote:
> This reverts commit 2cdec9c13f81313dd9f41f09c7cdecbfa4bea91d.
>
> Reported issues with the backport, revert for now.
>
> Signed-off-by: Li Wang
> ---
> drivers/spi/spi-zynqmp-gqspi.c | 6 --
> 1 file changed, 6 deletions(-)
>
> diff --git a/drivers/spi/spi-zynqmp-gqspi.c b/drivers/spi/spi-zynqmp-gqspi.c
> index 29fd5a639811..462d64eb93e6 100644
> --- a/drivers/spi/spi-zynqmp-gqspi.c
> +++ b/drivers/spi/spi-zynqmp-gqspi.c
> @@ -1330,12 +1330,6 @@ static int zynqmp_qspi_probe(struct platform_device
> *pdev)
> pm_runtime_set_active(>dev);
> pm_runtime_enable(>dev);
>
> - ret = pm_runtime_get_sync(>dev);
> - if (ret < 0) {
> - dev_err(>dev, "Failed to pm_runtime_get_sync: %d\n", ret);
> - goto clk_dis_all;
> - }
> -
> if (of_property_read_bool(pdev->dev.of_node, "has-io-mode"))
> xqspi->io_mode = true;
>
> --
> 2.31.1
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13945):
https://lists.yoctoproject.org/g/linux-yocto/message/13945
Mute This Topic: https://lists.yoctoproject.org/mt/106197670/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][v6.1/standard/nxp-sdk-6.1/nxp-soc & v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc][PATCH] soc: imx8mp: place read register before clk_disable_unprepare()
merged.
Bruce
In message: [linux-yocto][v6.1/standard/nxp-sdk-6.1/nxp-soc &
v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc][PATCH] soc: imx8mp: place read
register before clk_disable_unprepare()
on 16/05/2024 Xiaolei Wang wrote:
> commit 328efccc7847 ("soc: imx8m: Enable OCOTP clock for imx8mm
> before reading registers") has re-enabled the clock, so reading
> the registers needs to be done before clk_disable_unprepare(),
> otherwise the kernel will hang.
>
> Fixes a3985483e7f1 ("LF-9486 soc: imx8mp: support 128 bits UID")
> Signed-off-by: Xiaolei Wang
> ---
> drivers/soc/imx/soc-imx8m.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/soc/imx/soc-imx8m.c b/drivers/soc/imx/soc-imx8m.c
> index 466b95242b3e..8217361ad232 100644
> --- a/drivers/soc/imx/soc-imx8m.c
> +++ b/drivers/soc/imx/soc-imx8m.c
> @@ -135,15 +135,15 @@ static void __init imx8mm_soc_uid(void)
> soc_uid <<= 32;
> soc_uid |= readl_relaxed(ocotp_base + OCOTP_UID_LOW + offset);
>
> - clk_disable_unprepare(clk);
> - clk_put(clk);
> -
> if (offset) {
> soc_uid_h = readl_relaxed(ocotp_base + IMX8MP_OCOTP_UID_HIGH +
> 0x10);
> soc_uid_h <<= 32;
> soc_uid_h |= readl_relaxed(ocotp_base + IMX8MP_OCOTP_UID_HIGH);
> }
>
> + clk_disable_unprepare(clk);
> + clk_put(clk);
> +
> iounmap(ocotp_base);
> of_node_put(np);
> }
> --
> 2.25.1
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13944):
https://lists.yoctoproject.org/g/linux-yocto/message/13944
Mute This Topic: https://lists.yoctoproject.org/mt/106136196/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [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] ethosu: Use GFP_ATOMIC instead of GFP_KERNEL
merged.
Bruce
In message: [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] ethosu: Use GFP_ATOMIC
instead of GFP_KERNEL
on 15/05/2024 Xiaolei Wang wrote:
> Atomic operations should be employed within rwlock, hence GFP_ATOMIC
> is utilized instead of GFP_KERNEL. This ensures the avoidance of the
> subsequent call trace and prevents potential misinterpretation of NPU
> performance degradation during testing.
>
> BUG: sleeping function called from invalid context at
> include/linux/sched/mm.h:274
> in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 529, name: python3
> preempt_count: 1, expected: 0
> RCU nest depth: 0, expected: 0
> Preemption disabled at:
> [] ethosu_rpmsg_register+0x24/0x64
> CPU: 1 PID: 529 Comm: python3 Tainted: G C
> 6.1.90-yocto-standard #1
> Hardware name: NXP i.MX93 11X11 EVK board (DT)
> Call trace:
> dump_backtrace.part.0+0xc8/0xd4
> show_stack+0x20/0x30
> dump_stack_lvl+0x6c/0x88
> dump_stack+0x18/0x34
> __might_resched+0x154/0x1c0
> __might_sleep+0x54/0xa4
> kmem_cache_alloc+0x458/0x630
> radix_tree_node_alloc.constprop.0+0x54/0x110
> idr_get_free+0x22c/0x2b0
> idr_alloc_u32+0x70/0x100
> idr_alloc_cyclic+0x6c/0xf0
> ethosu_rpmsg_register+0x3c/0x64
> ethosu_inference_create+0xc0/0x2a4
> ethosu_network_ioctl+0xd4/0x2a0
> __arm64_sys_ioctl+0xb4/0x100
>
> Signed-off-by: Xiaolei Wang
> ---
> drivers/staging/ethosu/ethosu_rpmsg.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/ethosu/ethosu_rpmsg.c
> b/drivers/staging/ethosu/ethosu_rpmsg.c
> index d3e597e82762..f2ab3b366de7 100644
> --- a/drivers/staging/ethosu/ethosu_rpmsg.c
> +++ b/drivers/staging/ethosu/ethosu_rpmsg.c
> @@ -36,7 +36,7 @@ int ethosu_rpmsg_register(struct ethosu_rpmsg *erp,
> struct ethosu_rpmsg_msg *msg)
> {
> write_lock(>lock);
> - msg->id = idr_alloc_cyclic(>msg_idr, msg, 0, INT_MAX, GFP_KERNEL);
> + msg->id = idr_alloc_cyclic(>msg_idr, msg, 0, INT_MAX, GFP_ATOMIC);
> write_unlock(>lock);
> if (msg->id < 0)
> return msg->id;
> --
> 2.25.1
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13941):
https://lists.yoctoproject.org/g/linux-yocto/message/13941
Mute This Topic: https://lists.yoctoproject.org/mt/106112654/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [kernel-cache][PATCH] features/intel-npu: introduce Intel NPU fragment
Which branches were to looking at for this ? 6.6 and master ? just master ? Bruce In message: [kernel-cache][PATCH] features/intel-npu: introduce Intel NPU fragment on 15/05/2024 Naveen Saini wrote: > Add config fragment for the system with an 14th generation > Intel CPU (Meteor Lake) or newer. It will allow users to > enable Intel NPU (formerly called Intel VPU) > which is a CPU-integrated inference accelerator for > Computer Vision and Deep Learning applications. > > Signed-off-by: Naveen Saini > --- > features/intel-npu/intel-npu.cfg | 3 +++ > features/intel-npu/intel-npu.scc | 4 > kern-features.rc | 1 + > 3 files changed, 8 insertions(+) > create mode 100644 features/intel-npu/intel-npu.cfg > create mode 100644 features/intel-npu/intel-npu.scc > > diff --git a/features/intel-npu/intel-npu.cfg > b/features/intel-npu/intel-npu.cfg > new file mode 100644 > index ..6b7ced30 > --- /dev/null > +++ b/features/intel-npu/intel-npu.cfg > @@ -0,0 +1,3 @@ > +# SPDX-License-Identifier: MIT > +CONFIG_DRM_ACCEL=y > +CONFIG_DRM_ACCEL_IVPU=m > diff --git a/features/intel-npu/intel-npu.scc > b/features/intel-npu/intel-npu.scc > new file mode 100644 > index ..782c8499 > --- /dev/null > +++ b/features/intel-npu/intel-npu.scc > @@ -0,0 +1,4 @@ > +# SPDX-License-Identifier: MIT > +define KFEATURE_DESCRIPTION "Enable Intel NPU for Computer Vision and Deep > Learning applications" > + > +kconf hardware intel-npu.cfg > diff --git a/kern-features.rc b/kern-features.rc > index 0e83053c..14381cc8 100644 > --- a/kern-features.rc > +++ b/kern-features.rc > @@ -72,6 +72,7 @@ > config = features/lxc/lxc-enable.scc > config = features/inline/inline.scc > config = features/intel-tco/intel-tco.scc > + config = features/intel-npu/intel-npu.scc > config = features/ftrace/ftrace-function-tracer-disable.scc > config = features/ftrace/ftrace.scc > config = features/vxlan/vxlan-enable.scc > -- > 2.37.3 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13940): https://lists.yoctoproject.org/g/linux-yocto/message/13940 Mute This Topic: https://lists.yoctoproject.org/mt/106109710/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] nxp-lx2xxx: add support NXP PCF2131 RTC
merged. Bruce In message: [linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] nxp-lx2xxx: add support NXP PCF2131 RTC on 15/05/2024 Xulin Sun wrote: > Add support NXP PCF2131 RTC for LX2160A-RDB Rev.D. > > Signed-off-by: Xulin Sun > --- > bsp/nxp-lx2xxx/nxp-lx2xxx.cfg | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/bsp/nxp-lx2xxx/nxp-lx2xxx.cfg b/bsp/nxp-lx2xxx/nxp-lx2xxx.cfg > index f8008cb7..c0321756 100644 > --- a/bsp/nxp-lx2xxx/nxp-lx2xxx.cfg > +++ b/bsp/nxp-lx2xxx/nxp-lx2xxx.cfg > @@ -138,6 +138,7 @@ CONFIG_I2C_MUX_PCA954x=y > CONFIG_RTC_CLASS=y > CONFIG_RTC_DRV_PCF2127=y > CONFIG_RTC_DRV_FSL_FTM_ALARM=y > +CONFIG_RTC_DRV_PCF2131=y > > CONFIG_DMADEVICES=y > CONFIG_FSL_EDMA=y > -- > 2.35.5 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13939): https://lists.yoctoproject.org/g/linux-yocto/message/13939 Mute This Topic: https://lists.yoctoproject.org/mt/106106960/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][linux-yocto v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc & v6.1/standard/nxp-sdk-6.1/nxp-soc][PATCH] arm64: dts: imx93-11x11-evk: Use "alloc-ranges" + "size" instead of "reg" for the
merged.
Bruce
In message: [linux-yocto][linux-yocto
v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc &
v6.1/standard/nxp-sdk-6.1/nxp-soc][PATCH] arm64: dts: imx93-11x11-evk: Use
"alloc-ranges" + "size" instead of "reg" for the ethosu_mem
on 12/05/2024 Xiaolei Wang via lists.yoctoproject.org wrote:
> Reserve memory defined through "reg" is unconditionally set as reserve
> memory, so these reserve memory regions can also be successfully set in
> the crash kernel. However, if they are also used as CMA memory and
> their starting addresses are not within the accessible range of the
> crash kernel, it will cause the following memory access exception.
> On the other hand, reserve memory defined through the combination of
> "alloc-ranges" and "size" will be allocated from the memory space
> accessible to the current kernel. If there is no memory that meets the
> corresponding restriction conditions, allocation will fail, thus
> avoiding the memory access exception mentioned earlier. For the crash
> kernel, it is acceptable for allocation of reserve memory to fail in
> such cases.
>
> At the same time, verify the npu working problem through python3
> label_image.py
> -d /usr/lib64/libethosu_delegate.so -i grace_hopper.bmp -l labels.txt. No
> exceptions have been found yet
>
> Unable to handle kernel paging request at virtual address fffe
> Mem abort info:
> ESR = 0x9606
> EC = 0x25: DABT (current EL), IL = 32 bits
> SET = 0, FnV = 0
> EA = 0, S1PTW = 0
> FSC = 0x06: level 2 translation fault
> Data abort info:
> ISV = 0, ISS = 0x0006
> CM = 0, WnR = 0
> swapper pgtable: 4k pages, 39-bit VAs, pgdp=defd8000
> [fffe] pgd=1000fd4a7003, p4d=1000fd4a7003,
> pud=1000fd4a7003, pmd=
> Internal error: Oops: 9606 [#1] PREEMPT SMP
> Modules linked in:
> CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW
> 6.1.83-yocto-standard #1
> Hardware name: NXP i.MX93 11X11 EVK board (DT)
> pstate: 0049 (nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> pc : cma_init_reserved_areas+0xb4/0x24c
> lr : cma_init_reserved_areas+0x88/0x24c
> sp : ffc00b32bd40
> x29: ffc00b32bd40 x28: 0680 x27: fffe
> x26: ffc009866078 x25: ffc00974e5e8 x24: ffc00b2b9d70
> x23: x22: ffc00b2b9dd8 x21: 000c
> x20: ffc0098f6008 x19: ffc00b2b9d70 x18: fffd
> x17: 20647261646e6174 x16: 732d6f74636f792d x15: ffc00b32b2e0
> x14: x13: 303278302f303178 x12: 302b6b726f665f6d
> x11: 656572665f74696e x10: 0004 x9 : ffc00919c8f4
> x8 : ff80214f8000 x7 : d6d64d8a x6 : d0855cef
> x5 : 00ff x4 : 0001 x3 : ffc0098f6008
> x2 : 0001 x1 : ffc00a125700 x0 :
> Call trace:
> cma_init_reserved_areas+0xb4/0x24c
> do_one_initcall+0xb0/0x33c
> kernel_init_freeable+0x2d4/0x344
> kernel_init+0x30/0x140
> ret_from_fork+0x10/0x20
>
> Signed-off-by: Xiaolei Wang
> ---
> arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts
> b/arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts
> index d58bce2a86e2..50822162bf9a 100644
> --- a/arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts
> +++ b/arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts
> @@ -36,7 +36,8 @@ linux,cma {
> ethosu_mem: ethosu_region@C000 {
> compatible = "shared-dma-pool";
> reusable;
> - reg = <0x0 0xC000 0x0 0x1000>;
> + alloc-ranges = <0 0xB000 0 0x2000>;
> + size = <0 0x1000>;
> };
>
> vdev0vring0: vdev0vring0@a400 {
> --
> 2.25.1
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13934):
https://lists.yoctoproject.org/g/linux-yocto/message/13934
Mute This Topic: https://lists.yoctoproject.org/mt/10600/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [yocto-kernel-cache kernel v6.1]: aptiv-s32g: update to compatible with SDK BSP40
merged! Bruce In message: [yocto-kernel-cache kernel v6.1]: aptiv-s32g: update to compatible with SDK BSP40 on 11/05/2024 Zhantao Tang wrote: > Hi Bruce, > > There is a patch to update v6.1 kernel cache for aptiv-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 (#13933): https://lists.yoctoproject.org/g/linux-yocto/message/13933 Mute This Topic: https://lists.yoctoproject.org/mt/106032784/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [kernel-cache][master][yocto-6.6][PATCH] bsp/intel-corei7-64: enable Intel IOMMU support
both patches are merged. I had to fixup the from field so I could push the patch, it is worth double checking your configuration (but gmail and groups.io have been mangling some patches regardless of configuration) Bruce In message: [linux-yocto] [kernel-cache][master][yocto-6.6][PATCH] bsp/intel-corei7-64: enable Intel IOMMU support on 09/05/2024 Naveen Saini via lists.yoctoproject.org wrote: > Enable Intel IOMMU driver for intel-corei7-64 machine. > > Signed-off-by: Naveen Saini > --- > bsp/intel-common/intel-corei7-64.scc | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/bsp/intel-common/intel-corei7-64.scc > b/bsp/intel-common/intel-corei7-64.scc > index ad9122c1..840c739f 100644 > --- a/bsp/intel-common/intel-corei7-64.scc > +++ b/bsp/intel-common/intel-corei7-64.scc > @@ -25,6 +25,8 @@ include features/x2apic/x2apic.scc > # CONFIG_INTEL_SPEED_SELECT_INTERFACE is 64-bit only > include features/intel-sst/intel-sst.scc > > +include features/iommu/iommu.scc > + > # This line comes last as it has the final word on > # CONFIG values. > kconf hardware intel-corei7-64.cfg > -- > 2.37.3 > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13932): https://lists.yoctoproject.org/g/linux-yocto/message/13932 Mute This Topic: https://lists.yoctoproject.org/mt/105996440/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx9: Enable RTC_DRV_BBNSM for nxp-imx9
merged. Bruce In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx9: Enable RTC_DRV_BBNSM for nxp-imx9 on 09/05/2024 Xiaolei Wang wrote: > Enable RTC_DRV_BBNSM for nxp-imx9. > > Signed-off-by: Xiaolei Wang > --- > bsp/nxp-imx9/nxp-imx9.cfg | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg > index d68b93be..4726803b 100644 > --- a/bsp/nxp-imx9/nxp-imx9.cfg > +++ b/bsp/nxp-imx9/nxp-imx9.cfg > @@ -487,6 +487,7 @@ CONFIG_RTC_CLASS=y > CONFIG_RTC_DRV_IMX_SC=y > CONFIG_RTC_DRV_IMX_RPMSG=y > CONFIG_RTC_DRV_SNVS=y > +CONFIG_RTC_DRV_BBNSM=y > > # > # DMA Devices > -- > 2.25.1 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13931): https://lists.yoctoproject.org/g/linux-yocto/message/13931 Mute This Topic: https://lists.yoctoproject.org/mt/105995051/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][linux-yocto v6.1] kernel code for marvell octeon
In message: [linux-yocto][linux-yocto v6.1] kernel code for marvell octeon on 09/05/2024 Ruiqiang Hao wrote: > Hi Bruce, > > Please help to merge code into our linux-yocto repo. > > repo: > linux-yocto > branch: > v6.1/standard/cn-sdkv6.1/octeon > v6.1/standard/preempt-rt/cn-sdkv6.1/octeon merged. Bruce > > Thanks, > Ruiqiang > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13930): https://lists.yoctoproject.org/g/linux-yocto/message/13930 Mute This Topic: https://lists.yoctoproject.org/mt/105994192/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [PATCH linux-yocto 0/8] nxp-soc: Fix misc build failures
In message: [PATCH linux-yocto 0/8] nxp-soc: Fix misc build failures on 08/05/2024 Kevin Hao wrote: > Hi Bruce, > > This patch series fixes misc build failures when enabling different > kernel option combos. Please help me merge them into the following two > branches: > v6.1/standard/nxp-sdk-6.1/nxp-soc > v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc merged. Bruce > > --- > Kevin Hao (8): > arm64: dts: Restore the mistakenly deleted imx8qxp.dtsi for > imx8qxp-mek.dts > arm64: dts: Fix a typo in imx8qxp-mek-dpu-lcdif-rpmsg.dtb name > arm64: dts: Delete the reference of nonexistent dtbs > ASoC: fsl: Fix implicit declaration of function 'fsl_easrc_m2m_init' > drm: rockchip: Fix the incorrect reference to audio_pdev > dmaengine: fsl-edma: export fsl_edma_get_realcnt() > PM: wakeup: export pm_system_irq_wakeup() > thermal: device_cooling: Rename devfreq_cooling_un/register() to > device_cooling_un/register() > > arch/arm64/boot/dts/freescale/Makefile| 10 +++--- > arch/arm64/boot/dts/freescale/imx8qxp-mek.dts | 1 + > drivers/base/power/wakeup.c | 1 + > drivers/dma/fsl-edma-common.c | 1 + > drivers/gpu/drm/rockchip/cdn-dp-core.c| 2 +- > drivers/thermal/device_cooling.c | 8 > drivers/thermal/imx8mm_thermal.c | 4 ++-- > drivers/thermal/imx_sc_thermal.c | 4 ++-- > drivers/thermal/imx_thermal.c | 4 ++-- > drivers/thermal/qoriq_thermal.c | 4 ++-- > include/linux/device_cooling.h| 8 > sound/soc/fsl/fsl_easrc.c | 4 ++-- > 12 files changed, 25 insertions(+), 26 deletions(-) > --- > base-commit: 303189dd5cf54be5a7a73e27b1cf95c961403281 > change-id: 20240508-nxp-misc-91bf137ef1c7 > > Best regards, > -- > Kevin Hao > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13920): https://lists.yoctoproject.org/g/linux-yocto/message/13920 Mute This Topic: https://lists.yoctoproject.org/mt/105978731/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH V2] bsp/intel-x86: enable PCIe Advanced Error Reporting driver
On Tue, May 7, 2024 at 9:31 PM Liu, Yongxin wrote: > > > -Original Message- > > From: Bruce Ashfield > > Sent: Wednesday, May 8, 2024 9:20 > > To: Liu, Yongxin > > Cc: Hao, Kexin ; linux- > > yo...@lists.yoctoproject.org > > Subject: Re: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto- > > 6.6/master][PATCH V2] bsp/intel-x86: enable PCIe Advanced Error Reporting > > driver > > > > CAUTION: This email comes from a non Wind River email account! > > Do not click links or open attachments unless you recognize the sender and > > know the content is safe. > > > > v2 worked perfectly. > > > > It is now merged. > > Thanks. But this patch is for yocto-6.1, yocto-6.6 and master. > I saw it only in yocto-6.1. > Please help to check. > Ooops. My mistake, it is on all the branches now. Bruce > Thanks, > Yongxin > > > > > > Bruce > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13910): https://lists.yoctoproject.org/g/linux-yocto/message/13910 Mute This Topic: https://lists.yoctoproject.org/mt/105971882/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH V2] bsp/intel-x86: enable PCIe Advanced Error Reporting driver
v2 worked perfectly. It is now merged. Bruce In message: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH V2] bsp/intel-x86: enable PCIe Advanced Error Reporting driver on 08/05/2024 yongxin@windriver.com wrote: > From: Yongxin Liu > > Signed-off-by: Yongxin Liu > --- > bsp/intel-x86/intel-x86.cfg | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/bsp/intel-x86/intel-x86.cfg b/bsp/intel-x86/intel-x86.cfg > index 8266bf8f..87e50c06 100644 > --- a/bsp/intel-x86/intel-x86.cfg > +++ b/bsp/intel-x86/intel-x86.cfg > @@ -95,6 +95,7 @@ CONFIG_HOTPLUG_PCI=y > CONFIG_HOTPLUG_PCI_ACPI=y > > CONFIG_PCIEPORTBUS=y > +CONFIG_PCIEAER=y > CONFIG_PCIEASPM=y > CONFIG_PCIEASPM_DEFAULT=y > > -- > 2.43.2 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13908): https://lists.yoctoproject.org/g/linux-yocto/message/13908 Mute This Topic: https://lists.yoctoproject.org/mt/105971882/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [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] soc: imx9: free buf in imx9_soc_device_register()
merged. Bruce In message: [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] soc: imx9: free buf in imx9_soc_device_register() on 07/05/2024 Xiaolei Wang wrote: > Free unused buffer to avoid memory leak in imx9_soc_device_register(). > > unreferenced object 0xff8009215180 (size 128): >comm "(udev-worker)", pid 309, jiffies 4294901878 (age 65.740s) >hex dump (first 32 bytes): > 6c d3 c9 a7 8d 1c 40 bb b4 b8 63 8a 4b 1d 3d cc l.@...c.K.=. > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >backtrace: > [] __kmem_cache_alloc_node+0x240/0x330 > [ ] __kmalloc+0x68/0x10c > [<66f93058>] nvmem_cell_read+0x40/0xe0 > [<4e1a073b>] imx9_init_soc_probe+0x184/0x2fc [soc_imx9] > [ ] platform_probe+0x70/0xcc > [ ] really_probe+0xc4/0x2e0 > [<043f6f98>] __driver_probe_device+0x80/0x120 > [<7de67432>] driver_probe_device+0x48/0x124 > [<85d153a6>] __driver_attach+0xa4/0x1bc > [<319009c3>] bus_for_each_dev+0x80/0xe0 > [<6c7d6c30>] driver_attach+0x2c/0x3c > [ ] bus_add_driver+0x15c/0x210 > [ ] driver_register+0x80/0x13c > [ ] __platform_driver_register+0x30/0x40 > [<095e0d10>] 0xffc0012d8028 > [<7dc559b3>] do_one_initcall+0xb0/0x33c > > Signed-off-by: Xiaolei Wang > --- > drivers/soc/imx/soc-imx9.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/soc/imx/soc-imx9.c b/drivers/soc/imx/soc-imx9.c > index 517e45923a1f..4d0cf15ad8bc 100644 > --- a/drivers/soc/imx/soc-imx9.c > +++ b/drivers/soc/imx/soc-imx9.c > @@ -76,6 +76,7 @@ static int imx9_soc_device_register(struct device *dev) > nvmem_cell_put(cell); > > memcpy(v, buf, min(len, sizeof(v))); > + kfree(buf); > attr->serial_number = kasprintf(GFP_KERNEL, "%08x%08x%08x%08x", v[0], > v[1], v[2], v[3]); > > if (DIGPROG_MAJOR_UPPER(device_id) == 0x9 && > DIGPROG_MAJOR_LOWER(device_id) == 0x2) { > -- > 2.25.1 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13904): https://lists.yoctoproject.org/g/linux-yocto/message/13904 Mute This Topic: https://lists.yoctoproject.org/mt/105956992/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][linux-yocto-6.1][v6.1/standard/intel-sdk-6.1/intel-socfpga && v6.1/standard/preempt-rt/intel-sdk-6.1/intel-socfpga][PATCH 1/1] usb: dwc2: Add support to get usb speed from dtb
merged.
Bruce
In message:
[linux-yocto][linux-yocto-6.1][v6.1/standard/intel-sdk-6.1/intel-socfpga &&
v6.1/standard/preempt-rt/intel-sdk-6.1/intel-socfpga][PATCH 1/1] usb: dwc2: Add
support to get usb speed from dtb
on 07/05/2024 Liwei Song wrote:
> This change will get "maximum-speed" from dtb if exist and set USB speed
> accordingly for Agilex and Stratix10 platform.
>
> Signed-off-by: Liwei Song
> ---
> drivers/usb/dwc2/params.c | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/usb/dwc2/params.c b/drivers/usb/dwc2/params.c
> index 8eab5f38b110..37e367154713 100644
> --- a/drivers/usb/dwc2/params.c
> +++ b/drivers/usb/dwc2/params.c
> @@ -96,9 +96,13 @@ static void dwc2_set_s3c6400_params(struct dwc2_hsotg
> *hsotg)
> static void dwc2_set_socfpga_agilex_params(struct dwc2_hsotg *hsotg)
> {
> struct dwc2_core_params *p = >params;
> + u32 max_speed;
>
> p->power_down = DWC2_POWER_DOWN_PARAM_NONE;
> p->no_clock_gating = true;
> + max_speed = usb_get_maximum_speed(hsotg->dev);
> + if (max_speed)
> + p->speed = max_speed;
> }
>
> static void dwc2_set_rk_params(struct dwc2_hsotg *hsotg)
> --
> 2.40.0
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13903):
https://lists.yoctoproject.org/g/linux-yocto/message/13903
Mute This Topic: https://lists.yoctoproject.org/mt/105956886/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][v6.6/standard/x86 and v6.6/standard/preempt-rt/x86][Pull Request ] cstate, uncore, i10nm_edac and igen6_edac update for some x86 platforms
In message: [linux-yocto][v6.6/standard/x86 and v6.6/standard/preempt-rt/x86][Pull Request ] cstate, uncore, i10nm_edac and igen6_edac update for some x86 platforms on 06/05/2024 Liu, Yongxin wrote: > Hi Bruce, > > Please help to review and merge this Pull Request for linux-yocto, branch > "v6.6/standard/x86" and "v6.6/standard/preempt-rt/x86". > > All patches are from mainline kernel. > > This patch series basically did the following changes. > > 1) Intel cstate performance events: add support for Grand Ridge and > Sierra Forest > 2) Intel uncore performance events: add support for Sierra Forest, Grand > Ridge and Granite Rapids > 3) EDAC/i10nm: add support for Intel Grand Ridge > 4) EDAC/igen6: add support for Intel Alder Lake N merged. Bruce > > > The following changes since commit 6655dc03f5de7bb734da3ec8eb97f9be281dfbdb: > > Merge tag 'v6.6.29' into v6.6/standard/base (2024-05-01 16:42:09 -0400) > > are available in the Git repository at: > > https://github.com/liux2085/linux-yocto.git v6.6_x86_pull > > for you to fetch changes up to 9a03c31e128c6be5e0427e54198f76f9b904fe4a: > > EDAC/i10nm: Add Intel Grand Ridge micro-server support (2024-05-06 20:14:41 > +0800) > > > Kan Liang (8): > perf/x86/intel/cstate: Cleanup duplicate attr_groups > perf/x86/intel/cstate: Add Sierra Forest support > perf/x86/intel/cstate: Add Grand Ridge support > perf/x86/intel/uncore: Generic uncore_get_uncores and MMIO format of SPR > perf/x86/uncore: Use u64 to replace unsigned for the uncore offsets > array > perf/x86/intel/uncore: Support Granite Rapids > perf/x86/intel/uncore: Support IIO free-running counters on GNR > perf/x86/intel/uncore: Support Sierra Forest and Grand Ridge > > Qiuxu Zhuo (3): > EDAC/igen6: Make get_mchbar() helper function > EDAC/igen6: Add Intel Alder Lake-N SoCs support > EDAC/i10nm: Add Intel Grand Ridge micro-server support > > arch/x86/events/intel/cstate.c | 158 > +- > arch/x86/events/intel/uncore.c | 12 > arch/x86/events/intel/uncore.h | 10 +++--- > arch/x86/events/intel/uncore_discovery.c | 5 +++-- > arch/x86/events/intel/uncore_discovery.h | 2 +- > arch/x86/events/intel/uncore_nhmex.c | 2 +- > arch/x86/events/intel/uncore_snbep.c | 137 > +++-- > drivers/edac/i10nm_base.c| 1 + > drivers/edac/igen6_edac.c| 81 > ++--- > 9 files changed, 339 insertions(+), 69 deletions(-) > > > Thanks, > Yongxin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13902): https://lists.yoctoproject.org/g/linux-yocto/message/13902 Mute This Topic: https://lists.yoctoproject.org/mt/105938064/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][yocto-kernel-cache][yocto-6.6][PATCH] nxp-imx8: add scc and cfg files for NXP IMX8 series platform
merged. Bruce In message: [linux-yocto][yocto-kernel-cache][yocto-6.6][PATCH] nxp-imx8: add scc and cfg files for NXP IMX8 series platform on 07/05/2024 Xulin Sun wrote: > Signed-off-by: Xulin Sun > --- > bsp/nxp-imx8/nxp-imx8-preempt-rt.cfg | 15 + > bsp/nxp-imx8/nxp-imx8-preempt-rt.scc | 9 + > bsp/nxp-imx8/nxp-imx8-standard.scc | 7 + > bsp/nxp-imx8/nxp-imx8.cfg| 623 +++ > bsp/nxp-imx8/nxp-imx8.scc| 11 + > 5 files changed, 665 insertions(+) > create mode 100644 bsp/nxp-imx8/nxp-imx8-preempt-rt.cfg > create mode 100644 bsp/nxp-imx8/nxp-imx8-preempt-rt.scc > create mode 100644 bsp/nxp-imx8/nxp-imx8-standard.scc > create mode 100644 bsp/nxp-imx8/nxp-imx8.cfg > create mode 100644 bsp/nxp-imx8/nxp-imx8.scc > > diff --git a/bsp/nxp-imx8/nxp-imx8-preempt-rt.cfg > b/bsp/nxp-imx8/nxp-imx8-preempt-rt.cfg > new file mode 100644 > index ..780e974a > --- /dev/null > +++ b/bsp/nxp-imx8/nxp-imx8-preempt-rt.cfg > @@ -0,0 +1,15 @@ > +.. > +.WARNING > +. > +. This file is a kernel configuration fragment, and not a full kernel > +. configuration file. The final kernel configuration is made up of > +. an assembly of processed fragments, each of which is designed to > +. capture a specific part of the final configuration (e.g. platform > +. configuration, feature configuration, and board specific hardware > +. configuration). For more information on kernel configuration, please > +. consult the product documentation. > +. > +.. > + > +# CONFIG_TRANSPARENT_HUGEPAGE is not set > +# CONFIG_LEDS_TRIGGER_CPU is not set > diff --git a/bsp/nxp-imx8/nxp-imx8-preempt-rt.scc > b/bsp/nxp-imx8/nxp-imx8-preempt-rt.scc > new file mode 100644 > index ..d900d656 > --- /dev/null > +++ b/bsp/nxp-imx8/nxp-imx8-preempt-rt.scc > @@ -0,0 +1,9 @@ > +define KMACHINE nxp-imx8 > +define KTYPE preempt-rt > +define KARCH arm64 > + > +include ktypes/preempt-rt > + > +include nxp-imx8.scc > + > +kconf hardware nxp-imx8-preempt-rt.cfg > diff --git a/bsp/nxp-imx8/nxp-imx8-standard.scc > b/bsp/nxp-imx8/nxp-imx8-standard.scc > new file mode 100644 > index ..d94f2dfd > --- /dev/null > +++ b/bsp/nxp-imx8/nxp-imx8-standard.scc > @@ -0,0 +1,7 @@ > +define KMACHINE nxp-imx8 > +define KTYPE standard > +define KARCH arm64 > + > +include ktypes/standard > + > +include nxp-imx8.scc > diff --git a/bsp/nxp-imx8/nxp-imx8.cfg b/bsp/nxp-imx8/nxp-imx8.cfg > new file mode 100644 > index ..642c1489 > --- /dev/null > +++ b/bsp/nxp-imx8/nxp-imx8.cfg > @@ -0,0 +1,623 @@ > +CONFIG_ARM64=y > +CONFIG_SMP=y > +CONFIG_ARCH_NXP=y > +CONFIG_ARCH_LAYERSCAPE=y > +CONFIG_ARCH_MXC=y > +CONFIG_HAVE_IMX_BUSFREQ=y > + > +CONFIG_PM=y > +CONFIG_CPU_PM=y > + > +# > +# CPU Idle > +# > +CONFIG_CPU_IDLE=y > +CONFIG_ARM_PSCI_CPUIDLE=y > +CONFIG_ARM_PSCI_CPUIDLE_DOMAIN=y > + > +# > +# CPU Frequency scaling > +# > +CONFIG_CPU_FREQ=y > +CONFIG_CPU_FREQ_GOV_ATTR_SET=y > +CONFIG_CPU_FREQ_GOV_COMMON=y > +CONFIG_CPU_FREQ_STAT=y > +CONFIG_CPU_FREQ_GOV_PERFORMANCE=y > +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_GOV_SCHEDUTIL=y > + > +# > +# CPU frequency scaling drivers > +# > +CONFIG_CPUFREQ_DT=y > +CONFIG_ARM_IMX_CPUFREQ_DT=y > + > +# > +# CAN > +# > +CONFIG_CAN=m > +CONFIG_CAN_FLEXCAN=m > + > +CONFIG_PCI=y > +CONFIG_PCI_MSI=y > +CONFIG_PCI_IMX6=y > +CONFIG_PCI_IMX6_HOST=y > +CONFIG_PHY_FSL_IMX8Q_PCIE=y > + > +CONFIG_IMX_DSP=y > +CONFIG_IMX_SCU=y > +CONFIG_IMX_SCU_PD=y > +CONFIG_IMX_SECO_MU=y > +CONFIG_IMX_ELE_TRNG=y > + > +# > +## MTD > +# > +CONFIG_MTD=y > +CONFIG_MTD_CMDLINE_PARTS=y > +CONFIG_MTD_BLOCK=y > +CONFIG_MTD_CFI=y > +CONFIG_MTD_CFI_ADV_OPTIONS=y > +CONFIG_MTD_CFI_INTELEXT=y > +CONFIG_MTD_CFI_AMDSTD=y > +CONFIG_MTD_CFI_STAA=y > +CONFIG_MTD_PHYSMAP=y > +CONFIG_MTD_PHYSMAP_OF=y > +CONFIG_MTD_DATAFLASH=y > +CONFIG_MTD_RAW_NAND=y > +CONFIG_MTD_NAND_DENALI_DT=y > +CONFIG_MTD_SPI_NOR=y > +CONFIG_MTD_SST25L=y > + > +# > +## Regulator Driver > +# > +CONFIG_PWM=y > +CONFIG_REGULATOR=y > +CONFIG_REGULATOR_FIXED_VOLTAGE=y > +CONFIG_REGULATOR_FAN53555=y > +CONFIG_REGULATOR_GPIO=y > +CONFIG_REGULATOR_MAX8973=y > +CONFIG_REGULATOR_PCA9450=y > +CONFIG_REGULATOR_PFUZE100=y > +CONFIG_REGULATOR_PWM=y > + > +# > +# MMC Driver > +# > +CONFIG_MMC=y > +CONFIG_MMC_SDHCI=y > +CONFIG_MMC_SDHCI_PLTFM=y > +CONFIG_MMC_SDHCI_ESDHC_IMX=y > + > +# > +# Controllers with non-SFF native interface > +# > +CONFIG_ATA=y > +CONFIG_MFD_SYSCON=y > +CONFIG_AHCI_IMX=y > +CONFIG_SATA_AHCI=y > +CONFIG_SATA_AHCI_PLATFORM=y > +CONFIG_LEDS_TRIGGERS=y > + > +# > +# Networking > +# > +CONFIG_FEC=y > +CONFIG_AT803X_PHY=y > +CONFIG_REALTEK_PHY=y > +CONFIG_STMMAC_ETH=y > + > +# > +# Input device support > +# > +CONFIG_INPUT=y > +CONFIG_INPUT_KEYBOARD=y
Re: [linux-yocto] [linux-yocto std/rt kernel v6.1]: nxp-s32g: gpio: fix pinctrl_gpio_get_mux_owner
In message: [linux-yocto] [linux-yocto std/rt kernel v6.1]: nxp-s32g: gpio: fix pinctrl_gpio_get_mux_owner on 07/05/2024 Zhantao Tang wrote: > Hi Bruce, > > There is a patch to fix pinctrl_gpio_get_mux_owner issue. > Would you please help to merge it into > v6.1/standard/nxp-sdk-5.15/nxp-s32g, > v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g > branches? merged. Bruce > > > Thanks, > Zhantao > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13900): https://lists.yoctoproject.org/g/linux-yocto/message/13900 Mute This Topic: https://lists.yoctoproject.org/mt/105953225/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH] bsp/intel-x86: enable PCIe Advanced Error Reporting driver
Make sure you are following the configuration advice here: https://docs.yoctoproject.org/contributor-guide/submit-changes.html#fixing-your-from-identity And if the issue persists, we'll have to get into some of the discussion here: https://lore.kernel.org/yocto-docs/20240502191839a351b43b@mail.local/T/#t I'll drop this while I wait for a v2 Bruce On Tue, May 7, 2024 at 3:28 PM Bruce Ashfield via lists.yoctoproject.org wrote: > > I spoke too soon, the mailing list mangled the author field. > > remote: ## > remote: Invalid author Yongxin Liu via lists.yoctoproject.org > remote: ## > > I'm looking for the latest advice on fixing your client so that the > list software doesn't do the mangling. > > So for now, I've dropped the patch. > > Bruce > > > On Tue, May 7, 2024 at 3:25 PM Bruce Ashfield via > lists.yoctoproject.org > wrote: > > > > merged. > > > > Bruce > > > > In message: > > [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH] > > bsp/intel-x86: enable PCIe Advanced Error Reporting driver > > on 06/05/2024 Yongxin Liu via lists.yoctoproject.org wrote: > > > > > Signed-off-by: Yongxin Liu > > > --- > > > bsp/intel-x86/intel-x86.cfg | 1 + > > > 1 file changed, 1 insertion(+) > > > > > > diff --git a/bsp/intel-x86/intel-x86.cfg b/bsp/intel-x86/intel-x86.cfg > > > index 8266bf8f..87e50c06 100644 > > > --- a/bsp/intel-x86/intel-x86.cfg > > > +++ b/bsp/intel-x86/intel-x86.cfg > > > @@ -95,6 +95,7 @@ CONFIG_HOTPLUG_PCI=y > > > CONFIG_HOTPLUG_PCI_ACPI=y > > > > > > CONFIG_PCIEPORTBUS=y > > > +CONFIG_PCIEAER=y > > > CONFIG_PCIEASPM=y > > > CONFIG_PCIEASPM_DEFAULT=y > > > > > > -- > > > 2.43.2 > > > > > > > > > > > > > > > > > > > > > > > > > -- > - Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end > - "Use the force Harry" - Gandalf, Star Trek II > > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13899): https://lists.yoctoproject.org/g/linux-yocto/message/13899 Mute This Topic: https://lists.yoctoproject.org/mt/105931613/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH] bsp/intel-x86: enable PCIe Advanced Error Reporting driver
I spoke too soon, the mailing list mangled the author field. remote: ## remote: Invalid author Yongxin Liu via lists.yoctoproject.org remote: ## I'm looking for the latest advice on fixing your client so that the list software doesn't do the mangling. So for now, I've dropped the patch. Bruce On Tue, May 7, 2024 at 3:25 PM Bruce Ashfield via lists.yoctoproject.org wrote: > > merged. > > Bruce > > In message: > [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH] > bsp/intel-x86: enable PCIe Advanced Error Reporting driver > on 06/05/2024 Yongxin Liu via lists.yoctoproject.org wrote: > > > Signed-off-by: Yongxin Liu > > --- > > bsp/intel-x86/intel-x86.cfg | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/bsp/intel-x86/intel-x86.cfg b/bsp/intel-x86/intel-x86.cfg > > index 8266bf8f..87e50c06 100644 > > --- a/bsp/intel-x86/intel-x86.cfg > > +++ b/bsp/intel-x86/intel-x86.cfg > > @@ -95,6 +95,7 @@ CONFIG_HOTPLUG_PCI=y > > CONFIG_HOTPLUG_PCI_ACPI=y > > > > CONFIG_PCIEPORTBUS=y > > +CONFIG_PCIEAER=y > > CONFIG_PCIEASPM=y > > CONFIG_PCIEASPM_DEFAULT=y > > > > -- > > 2.43.2 > > > > > > > > > > > > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13898): https://lists.yoctoproject.org/g/linux-yocto/message/13898 Mute This Topic: https://lists.yoctoproject.org/mt/105931613/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH] bsp/intel-x86: enable PCIe Advanced Error Reporting driver
merged. Bruce In message: [linux-yocto][yocto-kernel-cache][yocto-6.1/yocto-6.6/master][PATCH] bsp/intel-x86: enable PCIe Advanced Error Reporting driver on 06/05/2024 Yongxin Liu via lists.yoctoproject.org wrote: > Signed-off-by: Yongxin Liu > --- > bsp/intel-x86/intel-x86.cfg | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/bsp/intel-x86/intel-x86.cfg b/bsp/intel-x86/intel-x86.cfg > index 8266bf8f..87e50c06 100644 > --- a/bsp/intel-x86/intel-x86.cfg > +++ b/bsp/intel-x86/intel-x86.cfg > @@ -95,6 +95,7 @@ CONFIG_HOTPLUG_PCI=y > CONFIG_HOTPLUG_PCI_ACPI=y > > CONFIG_PCIEPORTBUS=y > +CONFIG_PCIEAER=y > CONFIG_PCIEASPM=y > CONFIG_PCIEASPM_DEFAULT=y > > -- > 2.43.2 > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13897): https://lists.yoctoproject.org/g/linux-yocto/message/13897 Mute This Topic: https://lists.yoctoproject.org/mt/105931613/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [PATCH 1/2] drm/i915: Drop some unrelated changes introduced during the merge of v6.6.29
On Thu, May 2, 2024 at 10:09 PM Bruce Ashfield via lists.yoctoproject.org
wrote:
>
>
> On Thu, May 2, 2024 at 9:38 PM Kevin Hao wrote:
>
>> From: Kevin Hao
>>
>> There are no these changes in the v6.6.29.
>>
>>
> I built and tested my changes. What issues are you seeing with them ?
>
>
Ah yes. I see the double unlock now.
I've applied the patch!
Bruce
> My resolution is based on the latest -rt kernel.
>
> Bruce
>
>
>
>> Signed-off-by: Kevin Hao
>> ---
>> drivers/gpu/drm/i915/display/intel_crtc.c | 7 ++-
>> 1 file changed, 2 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_crtc.c
>> b/drivers/gpu/drm/i915/display/intel_crtc.c
>> index 48300d05fffb..da2becfbc86c 100644
>> --- a/drivers/gpu/drm/i915/display/intel_crtc.c
>> +++ b/drivers/gpu/drm/i915/display/intel_crtc.c
>> @@ -684,7 +684,7 @@ void intel_pipe_update_end(struct intel_atomic_state
>> *state,
>> intel_psr_unlock(new_crtc_state);
>>
>> if (new_crtc_state->do_async_flip)
>> - goto out;
>> + return;
>>
>> trace_intel_pipe_update_end(crtc, end_vbl_count, scanline_end);
>>
>> @@ -736,7 +736,7 @@ void intel_pipe_update_end(struct intel_atomic_state
>> *state,
>> local_irq_enable();
>>
>> if (intel_vgpu_active(dev_priv))
>> - goto out;
>> + return;
>>
>> if (crtc->debug.start_vbl_count &&
>> crtc->debug.start_vbl_count != end_vbl_count) {
>> @@ -751,7 +751,4 @@ void intel_pipe_update_end(struct intel_atomic_state
>> *state,
>> }
>>
>> dbg_vblank_evade(crtc, end_vbl_time);
>> -
>> -out:
>> - intel_psr_unlock(new_crtc_state);
>> }
>> --
>> 2.44.0
>>
>>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>
>
>
>
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13888):
https://lists.yoctoproject.org/g/linux-yocto/message/13888
Mute This Topic: https://lists.yoctoproject.org/mt/105880611/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [PATCH 2/2] serial: core: Use port lock wrappers in serial_port_runtime_resume()
On Thu, May 2, 2024 at 9:38 PM Kevin Hao wrote:
> From: Kevin Hao
>
> The rt commit 3e8aef19aa6f ("serial: core: Use port lock wrappers") has
> changed to use the port lock wrappers in function
> serial_port_runtime_resume(). But that was mangled when merging v6.6.29.
> Restore it back.
>
I already have this fixed locally, but thanks for the patch!
Bruce
>
> Signed-off-by: Kevin Hao
> ---
> drivers/tty/serial/serial_port.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/tty/serial/serial_port.c
> b/drivers/tty/serial/serial_port.c
> index a8faed70ddbb..7d51e66ec88b 100644
> --- a/drivers/tty/serial/serial_port.c
> +++ b/drivers/tty/serial/serial_port.c
> @@ -42,7 +42,7 @@ static int serial_port_runtime_resume(struct device *dev)
> port->ops->start_tx(port);
>
> unlock:
> - spin_unlock_irqrestore(>lock, flags);
> + uart_port_unlock_irqrestore(port, flags);
>
> out:
> pm_runtime_mark_last_busy(dev);
> --
> 2.44.0
>
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13887):
https://lists.yoctoproject.org/g/linux-yocto/message/13887
Mute This Topic: https://lists.yoctoproject.org/mt/105880612/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [PATCH 1/2] drm/i915: Drop some unrelated changes introduced during the merge of v6.6.29
On Thu, May 2, 2024 at 9:38 PM Kevin Hao wrote:
> From: Kevin Hao
>
> There are no these changes in the v6.6.29.
>
>
I built and tested my changes. What issues are you seeing with them ?
My resolution is based on the latest -rt kernel.
Bruce
> Signed-off-by: Kevin Hao
> ---
> drivers/gpu/drm/i915/display/intel_crtc.c | 7 ++-
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_crtc.c
> b/drivers/gpu/drm/i915/display/intel_crtc.c
> index 48300d05fffb..da2becfbc86c 100644
> --- a/drivers/gpu/drm/i915/display/intel_crtc.c
> +++ b/drivers/gpu/drm/i915/display/intel_crtc.c
> @@ -684,7 +684,7 @@ void intel_pipe_update_end(struct intel_atomic_state
> *state,
> intel_psr_unlock(new_crtc_state);
>
> if (new_crtc_state->do_async_flip)
> - goto out;
> + return;
>
> trace_intel_pipe_update_end(crtc, end_vbl_count, scanline_end);
>
> @@ -736,7 +736,7 @@ void intel_pipe_update_end(struct intel_atomic_state
> *state,
> local_irq_enable();
>
> if (intel_vgpu_active(dev_priv))
> - goto out;
> + return;
>
> if (crtc->debug.start_vbl_count &&
> crtc->debug.start_vbl_count != end_vbl_count) {
> @@ -751,7 +751,4 @@ void intel_pipe_update_end(struct intel_atomic_state
> *state,
> }
>
> dbg_vblank_evade(crtc, end_vbl_time);
> -
> -out:
> - intel_psr_unlock(new_crtc_state);
> }
> --
> 2.44.0
>
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13886):
https://lists.yoctoproject.org/g/linux-yocto/message/13886
Mute This Topic: https://lists.yoctoproject.org/mt/105880611/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] drm/bridge: adv7511: Fix incorrect merge conflict resolutions in adv7511_probe()
In message: [linux-yocto] drm/bridge: adv7511: Fix incorrect merge conflict
resolutions in adv7511_probe()
on 28/04/2024 Kevin Hao wrote:
> From: Kevin Hao
>
> When merging b140d9d4515f ("drm/bridge: adv7511: fix crash on irq during
> probe") into nxp branches, it conflicts with the SDK commit ad93dd09fbbe
> ("Revert "drm/bridge: adv7511: Register and attach our DSI device at
> probe""). The current merge resolutions introduced two issues:
> - Part of codes deleted by SDK commit was restored mistakenly.
> - Reference of the label deleted by SDK commit.
>
> Resolve them to fix the build errors.
>
> Signed-off-by: Kevin Hao
> ---
> Hi Bruce,
>
> Please help me merge this into the following two branches:
> v6.1/standard/nxp-sdk-6.1/nxp-soc
> v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc
merged.
Bruce
>
> drivers/gpu/drm/bridge/adv7511/adv7511_drv.c | 8 +---
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c
> b/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c
> index 6e90871267f1..aba1fea6c22c 100644
> --- a/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c
> +++ b/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c
> @@ -1422,13 +1422,7 @@ static int adv7511_probe(struct i2c_client *i2c, const
> struct i2c_device_id *id)
> IRQF_ONESHOT, dev_name(dev),
> adv7511);
> if (ret)
> - goto err_unregister_audio;
> - }
> -
> - if (adv7511->type == ADV7533 || adv7511->type == ADV7535) {
> - ret = adv7533_attach_dsi(adv7511);
> - if (ret)
> - goto err_unregister_audio;
> + goto err_unregister_cec;
> }
>
> return 0;
> --
> 2.44.0
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13881):
https://lists.yoctoproject.org/g/linux-yocto/message/13881
Mute This Topic: https://lists.yoctoproject.org/mt/105779474/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [PATCH v6.6/v6.1 0/1] backport of drm/bridge/adv7511 for CVE-2024-26876
In message: [PATCH v6.6/v6.1 0/1] backport of drm/bridge/adv7511 for CVE-2024-26876 on 25/04/2024 pa...@kernel.org wrote: > From: Paul Gortmaker > > It would seem that a trivial change in surrounding context prevented the > linux-stable team from backporting this change to v6.6 and v6.1. The > same commit with updated context applies to both v6.6 and v6.1 cleanly. > > The "Fixes:" line indicates that it could also be relevant to v5.15 but > after a quick look/test there, I decided the unwind code in the probe > was sufficiently different that it is best we just leave it alone. merged. Bruce > > Build tested on v6.6 baseline. > > Paul. > -- > > Mads Bligaard Nielsen (1): > drm/bridge: adv7511: fix crash on irq during probe > > drivers/gpu/drm/bridge/adv7511/adv7511_drv.c | 22 ++-- > 1 file changed, 11 insertions(+), 11 deletions(-) > > -- > 2.25.1 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13876): https://lists.yoctoproject.org/g/linux-yocto/message/13876 Mute This Topic: https://lists.yoctoproject.org/mt/105732451/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [PATCH v5.15/v6.1 0/1] reiserfs namei.c backport for CVE-2023-52591
In message: [PATCH v5.15/v6.1 0/1] reiserfs namei.c backport for CVE-2023-52591 on 24/04/2024 pa...@kernel.org wrote: > From: Paul Gortmaker > > I was ready to put this CVE in the ignore pile, since IMHO the reiserfs > only continues to exist as a curiousity and possibly as a back > compatibility test for the VFS layer. Pretty sure nobody has used it in > earnest in the last 15-ish years? > > However, the "conflict" was a trivial one in the variable declaration > block (from addition of struct timespec64 ctime) and the same "fixed up" > commit applies to both v5.15 and v6.1 kernels. So we might as well take > the easy ones, I guess. Nothing for v6.6.x as it already has a backport. Looks good to. Since it isn't risky or challenging, I don't see any issues or risk in merging this either. merged to 5.15 and 6.1 Bruce > > Build tested only. Obviously zero rush to merge this, given the subject > matter and essentially zero user base. It can sit for a month+ if there > are other things going on, and nobody will care (including me). > > Paul. > -- > > Jan Kara (1): > reiserfs: Avoid touching renamed directory if parent does not change > > fs/reiserfs/namei.c | 54 - > 1 file changed, 29 insertions(+), 25 deletions(-) > > -- > 2.25.1 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13875): https://lists.yoctoproject.org/g/linux-yocto/message/13875 Mute This Topic: https://lists.yoctoproject.org/mt/105724660/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [PATCH v5.15 0/2] Backports for IPv6 CVE-2022-3567
In message: [PATCH v5.15 0/2] Backports for IPv6 CVE-2022-3567 on 24/04/2024 pa...@kernel.org wrote: > From: Paul Gortmaker > > The commit log of "the fix" identifies an earlier commit as "part 1" of > of the fix. But when we go back as far as v5.15, we find neither are > there. So this CVE has two commits. > > Built and boot tested on top of CVE-2022-3566 fix sent yesterday: > > https://lists.yoctoproject.org/g/linux-yocto/message/13856 > > Once again, v6.1+ kernels have both commits by default, so nothing > for us to do there. > > No rush for integration of these - they have been lingering since 2022. merged. Bruce > > Paul. > -- > > Eric Dumazet (1): > ipv6: annotate some data-races around sk->sk_prot > > Kuniyuki Iwashima (1): > ipv6: Fix data races around sk->sk_prot. > > net/core/sock.c | 6 -- > net/ipv4/af_inet.c | 23 --- > net/ipv6/af_inet6.c | 24 ++-- > net/ipv6/ipv6_sockglue.c | 6 -- > 4 files changed, 42 insertions(+), 17 deletions(-) > > -- > 2.25.1 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13874): https://lists.yoctoproject.org/g/linux-yocto/message/13874 Mute This Topic: https://lists.yoctoproject.org/mt/105709263/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][v6.1/standard/x86 and v6.1/standard/preempt-rt/x86][PATCH] EDAC/i10nm: Add Intel Grand Ridge micro-server support
merged.
Bruce
In message: [linux-yocto][v6.1/standard/x86 and
v6.1/standard/preempt-rt/x86][PATCH] EDAC/i10nm: Add Intel Grand Ridge
micro-server support
on 24/04/2024 Yongxin Liu wrote:
> From: Qiuxu Zhuo
>
> commit e77086c3750834553cf6fd2255c5f3ee04843ed8 upstream.
>
> The Grand Ridge CPU model uses similar memory controller registers with
> Granite Rapids server. Add Grand Ridge CPU model ID for EDAC support.
>
> Tested-by: Ricardo Neri
> Signed-off-by: Qiuxu Zhuo
> Signed-off-by: Tony Luck
> Link: https://lore.kernel.org/r/20240129062040.60809-3-qiuxu.z...@intel.com
> Signed-off-by: Yongxin Liu
> ---
> drivers/edac/i10nm_base.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/edac/i10nm_base.c b/drivers/edac/i10nm_base.c
> index 04ca336b879f..2f2f24f829de 100644
> --- a/drivers/edac/i10nm_base.c
> +++ b/drivers/edac/i10nm_base.c
> @@ -907,6 +907,7 @@ static const struct x86_cpu_id i10nm_cpuids[] = {
> X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(EMERALDRAPIDS_X,
> X86_STEPPINGS(0x0, 0xf), _cfg),
> X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(GRANITERAPIDS_X,
> X86_STEPPINGS(0x0, 0xf), _cfg),
> X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ATOM_CRESTMONT_X,
> X86_STEPPINGS(0x0, 0xf), _cfg),
> + X86_MATCH_INTEL_FAM6_MODEL_STEPPINGS(ATOM_CRESTMONT,
> X86_STEPPINGS(0x0, 0xf), _cfg),
> {}
> };
> MODULE_DEVICE_TABLE(x86cpu, i10nm_cpuids);
> --
> 2.43.2
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13873):
https://lists.yoctoproject.org/g/linux-yocto/message/13873
Mute This Topic: https://lists.yoctoproject.org/mt/105705247/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][v6.1/standard/x86 and v6.1/standard/preempt-rt/x86][PATCH 0/1] Fix Intel Grand Ridge cannot boot issue
In message: [linux-yocto][v6.1/standard/x86 and
v6.1/standard/preempt-rt/x86][PATCH 0/1] Fix Intel Grand Ridge cannot boot issue
on 24/04/2024 Yongxin Liu wrote:
>
> Hi Bruce,
>
> Intel Grand Ridge cannot boot after the backport of commit a6a5006dad57
> ("iommu/vt-d: Retrieve IOMMU perfmon capability information"), in v6.1.83.
>
> This patch is the second patch of the following patch series in mainline.
>
> d8a7c0cf05a2 2023-02-03 11:06 Kan Liangiommu/vt-d: Enable IOMMU
> perfmon support
> 4a0d4265659b 2023-02-03 11:06 Kan Liangiommu/vt-d: Add IOMMU perfmon
> overflow handler support
> 46284c6ceb5e 2023-02-03 11:06 Kan Liangiommu/vt-d: Support cpumask
> for IOMMU perfmon
> 7232ab8b89e9 2023-02-03 11:06 Kan Liangiommu/vt-d: Add IOMMU perfmon
> support
> dc57875866ab 2023-02-03 11:06 Kan Liangiommu/vt-d: Support Enhanced
> Command Interface
> a6a5006dad57 2023-02-03 11:06 Kan Liangiommu/vt-d: Retrieve IOMMU
> perfmon capability information
> 4db96bfe9d77 2023-02-03 11:06 Kan Liangiommu/vt-d: Support size of
> the register set in DRHD
>
> It is strange only one patch was backported in linux-stable v6.1.
> Because in order to eable IOMMU perfmon, all patches should be backported.
>
> Anyway, we need to back port the first patch to boot kernel on newer
> hardware, such as Intel GrandRidge.
>
> So please help to merge this patch to v6.1/standard/x86 and
> v6.1/standard/preempt-rt/x86.
merged.
Bruce
>
>
> Thanks,
> Yongxin
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13872):
https://lists.yoctoproject.org/g/linux-yocto/message/13872
Mute This Topic: https://lists.yoctoproject.org/mt/105704897/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [PATCH v5.15 0/1] backport of TCP fix for CVE-2022-3566
In message: [PATCH v5.15 0/1] backport of TCP fix for CVE-2022-3566 on 23/04/2024 pa...@kernel.org wrote: > From: Paul Gortmaker > > Mainline commit f49cd2f4d6 is listed as the fix for CVE-2022-3566. > I guess the linux-stable team skipped over it since it didn't apply? > > Maybe enough other stuff has since been backported such that it does > apply now - hands free with "wiggle" (the original AI if you ask me). > > Build and boot tested on v5.15/standard/base - ssh'd in and nothing > to see in dmesg - nice and clean. > > It is already present in v6.1+ so nothing for us to do there. No > rush on this - it has been hanging around since 2022! Thanks Paul! This is now merged. Bruce > > Paul. > -- > > Kuniyuki Iwashima (1): > tcp: Fix data races around icsk->icsk_af_ops. > > net/ipv4/tcp.c | 10 ++ > net/ipv6/ipv6_sockglue.c | 3 ++- > net/ipv6/tcp_ipv6.c | 6 -- > 3 files changed, 12 insertions(+), 7 deletions(-) > > -- > 2.25.1 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13871): https://lists.yoctoproject.org/g/linux-yocto/message/13871 Mute This Topic: https://lists.yoctoproject.org/mt/105689820/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] Seeking information on use of linux-yocto-dev
On Tue, Apr 23, 2024 at 12:34 PM Sourabh Banerjee (QUIC) <
quic_sbane...@quicinc.com> wrote:
>
>
> > -Original Message-----
> > From: Bruce Ashfield
> > Sent: Tuesday, April 23, 2024 7:22 AM
> > To: Sourabh Banerjee (QUIC)
> > Cc: linux-yocto@lists.yoctoproject.org
> > Subject: Re: [linux-yocto] Seeking information on use of linux-yocto-dev
> >
> >
> > On Mon, Apr 22, 2024 at 4:29 PM quic_sbanerje via
> http://lists.yoctoproject.org
> > mailto:quicinc@lists.yoctoproject.org> wrote:
> > From a previous discussion with Richard, I understand, that the
> linux-yocto-dev
> > recipe exists for anyone needing more recent kernels. Bruce is
> maintaining is
> > as a rolling update, and version upgrades are quite frequent.
> >
> > I am seeking information on following to understand use of
> linux-yocto-dev
> > better:
> > 1. When there's a version bump for linux-yocto-dev is there a test suite
> that is
> > run?
> >
> > I have some simple scripts and manual tests that I run against each bump
> of -
> > dev.
> >
> > In particular core-image-kernel-dev and the tightly coupled tools (lttng,
> > systemtap, etc).
> >
> > A boot of systemd based images tends to shake out most of the major
> issues, so
> > that
> > is what I do.
>
> Thank you for pointing to core-image-kernel-dev.
> When building this image do you generally use poky-altcfg, as it includes
> systemd?
>
>
I have my own distro and configuration that I use. But I also do test with
poky and poky-altcfg.
> How is the decision made to create a linux-yocto_${version} recipe from
> linux-yocto-dev recipe? Is it guided by a set cadence?
>
It follows guidance we put together about 10 years ago now, it is somewhere
on the project wiki. I've also covered it in several presentations over the
past
few years as well.
But generally speaking on our non-LTS releases, it is three kernel versions
the latest lts, the latest released kernel around the -m3 timeframe and the
-dev kernel. For our LTS releases, we drop the "latest released" kernel, and
just do lts + dev.
>
> >
> > 2. Is linux-yocto-dev tested by the autobuilder or a similar CI?
> >
> > We've had adding it to the autobuilder CI on the wishlist for quite a
> while. I
> > thought
> > Ross added something a few months ago, but I can't recall the details.
> We do
> > need
> > to decide on exactly what to test, making sure it is lighter than what
> is run
> > against
> > the release kernels that I generate.
> >
> > If it was in CI there might be some breakage due to the bleeding edge
> nature of
> > the updates. We just wouldn't want it to block any project milestones if
> run as
> > part of CI.
> >
>
> Added Ross to get a bit more clarity on autobuilder setup to
> linux-yocto-dev.
>
> >
> > 3. Do BSP layer maintainers generally use linux-yocto-dev to verify the
> BSP layer
> > against kernel upstream?
> >
> > There are some developers that do that, yes. Others use it for the
> AUTOREV
> > and rolling nature of it, etc. Now that even linux-yocto-dev uses
> versioned
> > branches, we could in theory just use linux-yocto for all of those
> purposes, but
> > I still strongly prefer that only our supported versions appear in
> linux-yocto.
> >
> If a BSP maintainer chooses to use linux-yocto-dev and expands the test
> scope
> to frameworks such as Weston, pulseaudio etc., let's say while testing
> detects
> bugs what should be the next step?
>
If the bug is in the kernel, hopefully they'll take it to lkml, since
that's why we
have the -dev kernel tracking the latest. It makes upstream discussions
easier
and more relevant. If it is an issue with the -dev kernel and the rest of OE
core interacting in an unexpected way, then the linux-yocto or oe-core
mailing
lists are used to discuss.
Since -dev kernels are highlighting issues that we will eventually have in a
release, the issues are valid and treat them as such
Bruce
> I am trying to understand can a BSP maintainer use this as a reference to
> test
> and plan ahead.
>
> > Bruce
> >
> >
> >
> >
> >
> >
> >
> > --
> > - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at
> > its end
> > - "Use the force Harry" - Gandalf, Star Trek II
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13859):
https://lists.yoctoproject.org/g/linux-yocto/message/13859
Mute This Topic: https://lists.yoctoproject.org/mt/105677861/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] Seeking information on use of linux-yocto-dev
On Mon, Apr 22, 2024 at 4:29 PM quic_sbanerje via lists.yoctoproject.org wrote: > From a previous discussion with Richard, I understand, that the > linux-yocto-dev > recipe exists for anyone needing more recent kernels. Bruce is maintaining > is > as a rolling update, and version upgrades are quite frequent. > > I am seeking information on following to understand use of linux-yocto-dev > better: > 1. When there's a version bump for linux-yocto-dev is there a test suite > that is run? > I have some simple scripts and manual tests that I run against each bump of -dev. In particular core-image-kernel-dev and the tightly coupled tools (lttng, systemtap, etc). A boot of systemd based images tends to shake out most of the major issues, so that is what I do. > 2. Is linux-yocto-dev tested by the autobuilder or a similar CI? > We've had adding it to the autobuilder CI on the wishlist for quite a while. I thought Ross added something a few months ago, but I can't recall the details. We do need to decide on exactly what to test, making sure it is lighter than what is run against the release kernels that I generate. If it was in CI there might be some breakage due to the bleeding edge nature of the updates. We just wouldn't want it to block any project milestones if run as part of CI. > 3. Do BSP layer maintainers generally use linux-yocto-dev to verify the > BSP layer > against kernel upstream? > There are some developers that do that, yes. Others use it for the AUTOREV and rolling nature of it, etc. Now that even linux-yocto-dev uses versioned branches, we could in theory just use linux-yocto for all of those purposes, but I still strongly prefer that only our supported versions appear in linux-yocto. Bruce > > > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13855): https://lists.yoctoproject.org/g/linux-yocto/message/13855 Mute This Topic: https://lists.yoctoproject.org/mt/105677861/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [PATCH v6.6/standard/base 0/5] Fix intermittent qemu-x86 boot hangs
On Mon, Apr 22, 2024 at 1:38 PM Bruce Ashfield via lists.yoctoproject.org wrote: > In message: [PATCH v6.6/standard/base 0/5] Fix intermittent qemu-x86 boot > hangs > on 19/04/2024 pa...@kernel.org wrote: > > > From: Paul Gortmaker > > > > Pretty much everything is documented here: > > > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=15463 > > > > ...other than I have since put the reverts onto the v6.6/standard/base > > (v6.6.23-118-g2d01bc1d4eea) and ran boot tests on that for 150 > > iterations w/o issue. > > > > We'll still need to let the linux-stable people know there is an issue, > > and checking if mainline has the issue (vs. just being related to > > backports) remains to be determined as well. > > > > But if there is a desire to move forward, and this is blocking, well > > then at least there is an option. > > Thanks for the detailed explanation paul! > > I'm in favour of applying these to 6.6 and I'll deal with > any -stable fallout later. > > That being said, when I apply these on top of v6.6/standard/base > patch 2/5 is failing. I'm looking at resolving it now, but it does > imply that I have a different baseline than you do! > > Aha. My baseline is now 6.6.27, so there have been some more stacked commits onto the common x86 entry point file. I've been sitting on those -stable updates to let the release settle. You can see all my queued changes at: https://git.yoctoproject.org/poky-contrib/log/?h=zedd/kernel Bruce > Bruce > > > > > Note that I did all the testing on qemux86 w/o KVM. I figure everyone > > else tests qemux86-64 with KVM, right? > > --- > > > > Paul Gortmaker (5): > > Revert "x86/tdx: Allow 32-bit emulation by default" > > Revert "x86/entry: Do not allow external 0x80 interrupts" > > Revert "x86/entry: Convert INT 0x80 emulation to IDTENTRY" > > Revert "x86/coco: Disable 32-bit emulation by default on TDX and SEV" > > Revert "x86: Introduce ia32_enabled()" > > > > arch/x86/coco/tdx/tdx.c | 1 - > > arch/x86/entry/common.c | 97 +--- > > arch/x86/entry/entry_64_compat.S | 77 + > > arch/x86/include/asm/ia32.h | 23 +--- > > arch/x86/include/asm/idtentry.h | 4 -- > > arch/x86/include/asm/proto.h | 4 ++ > > arch/x86/kernel/idt.c| 2 +- > > arch/x86/mm/mem_encrypt_amd.c| 11 > > arch/x86/xen/enlighten_pv.c | 2 +- > > arch/x86/xen/xen-asm.S | 2 +- > > 10 files changed, 86 insertions(+), 137 deletions(-) > > > > -- > > 2.44.0 > > > > > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13852): https://lists.yoctoproject.org/g/linux-yocto/message/13852 Mute This Topic: https://lists.yoctoproject.org/mt/105625698/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [yocto-kernel-cache kernel v6.1]: nxp-s32g: update to compatible with SDK BSP40
In message: [yocto-kernel-cache kernel v6.1]: nxp-s32g: update to compatible with SDK BSP40 on 22/04/2024 Zhantao Tang wrote: > 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 merged. Bruce > branch? > > Thanks, > Zhantao > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13851): https://lists.yoctoproject.org/g/linux-yocto/message/13851 Mute This Topic: https://lists.yoctoproject.org/mt/105665221/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx9: Enable VIDEO_AP1302
merged. Bruce In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx9: Enable VIDEO_AP1302 on 21/04/2024 Xiaolei Wang wrote: > Enable VIDEO_AP1302 for imx93, since > ap1302_60fps_ar0144_27M_2Lane_awb_tuning.bin > firmware needs to be loaded, build it as a module > > Signed-off-by: Xiaolei Wang > --- > bsp/nxp-imx9/nxp-imx9.cfg | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg > index 5e4cd6dc..d68b93be 100644 > --- a/bsp/nxp-imx9/nxp-imx9.cfg > +++ b/bsp/nxp-imx9/nxp-imx9.cfg > @@ -251,6 +251,7 @@ CONFIG_MXC_CAMERA_OV5640_MIPI_V2=y > # > CONFIG_VIDEO_IMX8_JPEG=m > CONFIG_VIDEO_OV5640=y > +CONFIG_VIDEO_AP1302=m > > # > # Graphics support > -- > 2.25.1 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13850): https://lists.yoctoproject.org/g/linux-yocto/message/13850 Mute This Topic: https://lists.yoctoproject.org/mt/105646492/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] media: mxc: mxc_v4l2_capture: Fix an error in checking if the name string is NULL
In message: [linux-yocto] media: mxc: mxc_v4l2_capture: Fix an error in
checking if the name string is NULL
on 20/04/2024 Kevin Hao wrote:
> From: Kevin Hao
>
> The struct v4l2_input::name is an array, so the checking of
> (mxc_capture_inputs[cam->current_input].name != NULL) always return
> true. The issue was introduced by commit 5b1aeb69cf15 ("media: capture:
> add mxc v4l2 capture driver").
>
> Signed-off-by: Kevin Hao
> ---
> Hi Bruce,
>
> Please help me merge this into the following two branches:
> v5.15/standard/nxp-sdk-5.15/nxp-soc
> v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-soc
merged.
Bruce
>
> drivers/media/platform/mxc/capture/mxc_v4l2_capture.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/platform/mxc/capture/mxc_v4l2_capture.c
> b/drivers/media/platform/mxc/capture/mxc_v4l2_capture.c
> index e768cd443e7e..b836027fe12c 100644
> --- a/drivers/media/platform/mxc/capture/mxc_v4l2_capture.c
> +++ b/drivers/media/platform/mxc/capture/mxc_v4l2_capture.c
> @@ -495,7 +495,7 @@ static int mxc_streamoff(cam_data *cam)
>* 3. disable idmac
>* 4. disable smfc (CSI--MEM channel)
>*/
> - if (mxc_capture_inputs[cam->current_input].name != NULL) {
> + if (mxc_capture_inputs[cam->current_input].name[0]) {
> if (cam->enc_disable_csi) {
> err = cam->enc_disable_csi(cam);
> if (err != 0)
> --
> 2.44.0
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13849):
https://lists.yoctoproject.org/g/linux-yocto/message/13849
Mute This Topic: https://lists.yoctoproject.org/mt/105631195/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [PATCH v6.6/standard/base 0/5] Fix intermittent qemu-x86 boot hangs
In message: [PATCH v6.6/standard/base 0/5] Fix intermittent qemu-x86 boot hangs on 19/04/2024 pa...@kernel.org wrote: > From: Paul Gortmaker > > Pretty much everything is documented here: > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=15463 > > ...other than I have since put the reverts onto the v6.6/standard/base > (v6.6.23-118-g2d01bc1d4eea) and ran boot tests on that for 150 > iterations w/o issue. > > We'll still need to let the linux-stable people know there is an issue, > and checking if mainline has the issue (vs. just being related to > backports) remains to be determined as well. > > But if there is a desire to move forward, and this is blocking, well > then at least there is an option. Thanks for the detailed explanation paul! I'm in favour of applying these to 6.6 and I'll deal with any -stable fallout later. That being said, when I apply these on top of v6.6/standard/base patch 2/5 is failing. I'm looking at resolving it now, but it does imply that I have a different baseline than you do! Bruce > > Note that I did all the testing on qemux86 w/o KVM. I figure everyone > else tests qemux86-64 with KVM, right? > --- > > Paul Gortmaker (5): > Revert "x86/tdx: Allow 32-bit emulation by default" > Revert "x86/entry: Do not allow external 0x80 interrupts" > Revert "x86/entry: Convert INT 0x80 emulation to IDTENTRY" > Revert "x86/coco: Disable 32-bit emulation by default on TDX and SEV" > Revert "x86: Introduce ia32_enabled()" > > arch/x86/coco/tdx/tdx.c | 1 - > arch/x86/entry/common.c | 97 +--- > arch/x86/entry/entry_64_compat.S | 77 + > arch/x86/include/asm/ia32.h | 23 +--- > arch/x86/include/asm/idtentry.h | 4 -- > arch/x86/include/asm/proto.h | 4 ++ > arch/x86/kernel/idt.c| 2 +- > arch/x86/mm/mem_encrypt_amd.c| 11 > arch/x86/xen/enlighten_pv.c | 2 +- > arch/x86/xen/xen-asm.S | 2 +- > 10 files changed, 86 insertions(+), 137 deletions(-) > > -- > 2.44.0 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13848): https://lists.yoctoproject.org/g/linux-yocto/message/13848 Mute This Topic: https://lists.yoctoproject.org/mt/105625698/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][linux-yocto v5.15/standard/ti-sdk-5.10/ti-j72xx][PATCH] media: platform: vxe-vxd: Remove the redundant function umin()
merged
Bruce
In message: [linux-yocto][linux-yocto
v5.15/standard/ti-sdk-5.10/ti-j72xx][PATCH] media: platform: vxe-vxd: Remove
the redundant function umin()
on 18/04/2024 Xulin Sun wrote:
> commit cf716d5a0dd86f6 (minmax: add umin(a, b) and umax(a, b)) introduces
> the definition umin() in include/linux/minmax.h, remove the redundant
> function umin() in the file h264_secure_parser.c to fix below building issue:
> drivers/media/platform/vxe-vxd/decoder/h264_secure_parser.c:174:28: note: in
> expansion of macro 'umin'
> | 174 | static inline unsigned int umin(unsigned int a, unsigned int b)
> | |^~~~
>
> Signed-off-by: Xulin Sun
> ---
> .../media/platform/vxe-vxd/decoder/h264_secure_parser.c | 8
> 1 file changed, 8 deletions(-)
>
> diff --git a/drivers/media/platform/vxe-vxd/decoder/h264_secure_parser.c
> b/drivers/media/platform/vxe-vxd/decoder/h264_secure_parser.c
> index 90f5197b17bc..9887db1067e3 100644
> --- a/drivers/media/platform/vxe-vxd/decoder/h264_secure_parser.c
> +++ b/drivers/media/platform/vxe-vxd/decoder/h264_secure_parser.c
> @@ -168,14 +168,6 @@ static const int bspp_subheightc[] = { -1, 2, 1, 1 };
> */
> static const int bspp_subwidthc[] = { -1, 2, 2, 1 };
>
> -/*
> - * inline functions for Minimum and Maximum value
> - */
> -static inline unsigned int umin(unsigned int a, unsigned int b)
> -{
> - return (((a) < (b)) ? (a) : (b));
> -}
> -
> static inline int smin(int a, int b)
> {
> return (((a) < (b)) ? (a) : (b));
> --
> 2.34.1
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13847):
https://lists.yoctoproject.org/g/linux-yocto/message/13847
Mute This Topic: https://lists.yoctoproject.org/mt/105594237/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [PATCH yocto-kc v6.1/v6.6/master] full_nohz: remove RCU_FAST_NO_HZ gone from upstream
merged.
Bruce
In message: [PATCH yocto-kc v6.1/v6.6/master] full_nohz: remove RCU_FAST_NO_HZ
gone from upstream
on 16/04/2024 pa...@kernel.org wrote:
> From: Paul Gortmaker
>
> In commit e2c73a6860bd ("rcu: Remove the RCU_FAST_NO_HZ Kconfig option")
> the so named option was removed from the v5.17 kernel.
>
> We should get it out of our active branches to prevent a warning.
>
> Signed-off-by: Paul Gortmaker
> ---
> features/full_nohz/full_nohz.cfg | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/features/full_nohz/full_nohz.cfg
> b/features/full_nohz/full_nohz.cfg
> index 2fba92379a94..16db20044c35 100644
> --- a/features/full_nohz/full_nohz.cfg
> +++ b/features/full_nohz/full_nohz.cfg
> @@ -1,4 +1,3 @@
> # SPDX-License-Identifier: MIT
> CONFIG_NO_HZ_FULL=y
> CONFIG_RCU_EXPERT=y
> -CONFIG_RCU_FAST_NO_HZ=y
> --
> 2.25.1
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13833):
https://lists.yoctoproject.org/g/linux-yocto/message/13833
Mute This Topic: https://lists.yoctoproject.org/mt/105563197/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [PATCH yocto-kc v6.6/master] cgl: drop SELINUX_DISABLE option
merged.
Bruce
In message: [PATCH yocto-kc v6.6/master] cgl: drop SELINUX_DISABLE option
on 16/04/2024 pa...@kernel.org wrote:
> From: Paul Gortmaker
>
> It was removed from mainline in v6.4 in commit f22f9aaf6c3d ("selinux:
> remove the runtime disable functionality").
>
> Signed-off-by: Paul Gortmaker
> ---
> cgl/features/selinux/selinux.cfg | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/cgl/features/selinux/selinux.cfg
> b/cgl/features/selinux/selinux.cfg
> index 9e5cac69c313..a73ad995caca 100644
> --- a/cgl/features/selinux/selinux.cfg
> +++ b/cgl/features/selinux/selinux.cfg
> @@ -7,5 +7,4 @@ CONFIG_JFS_SECURITY=y
> CONFIG_JFFS2_FS_SECURITY=y
> CONFIG_SECURITY_NETWORK=y
> CONFIG_SECURITY_SELINUX=y
> -CONFIG_SECURITY_SELINUX_DISABLE=y
> CONFIG_SECURITY_SELINUX_AVC_STATS=y
> --
> 2.25.1
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13832):
https://lists.yoctoproject.org/g/linux-yocto/message/13832
Mute This Topic: https://lists.yoctoproject.org/mt/105560235/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx9: Enable GPIO_VF610 for nxp-imx9
merged. Bruce In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx9: Enable GPIO_VF610 for nxp-imx9 on 16/04/2024 Xiaolei Wang wrote: > Enable GPIO_VF610 for nxp-imx9. > > Signed-off-by: Xiaolei Wang > --- > bsp/nxp-imx9/nxp-imx9.cfg | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg > index 8654f93c..5e4cd6dc 100644 > --- a/bsp/nxp-imx9/nxp-imx9.cfg > +++ b/bsp/nxp-imx9/nxp-imx9.cfg > @@ -86,6 +86,7 @@ CONFIG_REGULATOR_PCA9450=y > CONFIG_REGULATOR_PFUZE100=y > CONFIG_REGULATOR_PWM=y > CONFIG_PWM_ADP5585=y > +CONFIG_GPIO_VF610=y > > # > # MMC Driver > -- > 2.25.1 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13831): https://lists.yoctoproject.org/g/linux-yocto/message/13831 Mute This Topic: https://lists.yoctoproject.org/mt/105553457/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][v6.1/standard/nxp-sdk-6.1/nxp-soc & v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc][PATCH 1/3] phy: lynx-28g: truly power the lanes up or down
merged.
Bruce
In message: [linux-yocto][v6.1/standard/nxp-sdk-6.1/nxp-soc &
v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc][PATCH 1/3] phy: lynx-28g: truly
power the lanes up or down
on 16/04/2024 Xulin Sun wrote:
> From: Vladimir Oltean
>
> commit f73df580c2379a90c9269dace6dc3084fdf85ccc from
> https://github.com/nxp-imx/linux-imx lf-6.1.y
>
> The current procedure for power_off() and power_on() is the same as the
> one used for major lane reconfiguration, aka halting. But one can
> observe that a halted lane does not cause, for example, the CDR of the
> link partner to lose lock.
>
> Implement the procedure mentioned in the block guide for powering down
> a lane, and then back on.
>
> Signed-off-by: Vladimir Oltean
> [Xulin: add functions lynx_28g_lane_halt() & lynx_28g_lane_reset()
> directly, since they were mistakenly removed by the previous merge.]
> Signed-off-by: Xulin Sun
> ---
> drivers/phy/freescale/phy-fsl-lynx-28g.c | 99 +++-
> 1 file changed, 96 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/phy/freescale/phy-fsl-lynx-28g.c
> b/drivers/phy/freescale/phy-fsl-lynx-28g.c
> index ccfdd36a89b7..5cb34312d593 100644
> --- a/drivers/phy/freescale/phy-fsl-lynx-28g.c
> +++ b/drivers/phy/freescale/phy-fsl-lynx-28g.c
> @@ -87,6 +87,8 @@
>
> /* Lane a Tx Reset Control Register */
> #define LYNX_28G_LNaTRSTCTL(lane)(0x800 + (lane) * 0x100 + 0x20)
> +#define LYNX_28G_LNaTRSTCTL_DIS BIT(24)
> +#define LYNX_28G_LNaTRSTCTL_STP_REQ BIT(26)
> #define LYNX_28G_LNaTRSTCTL_HLT_REQ BIT(27)
> #define LYNX_28G_LNaTRSTCTL_RST_DONE BIT(30)
> #define LYNX_28G_LNaTRSTCTL_RST_REQ BIT(31)
> @@ -143,6 +145,8 @@
>
> /* Lane a Rx Reset Control Register */
> #define LYNX_28G_LNaRRSTCTL(lane)(0x800 + (lane) * 0x100 + 0x40)
> +#define LYNX_28G_LNaRRSTCTL_DIS BIT(24)
> +#define LYNX_28G_LNaRRSTCTL_STP_REQ BIT(26)
> #define LYNX_28G_LNaRRSTCTL_HLT_REQ BIT(27)
> #define LYNX_28G_LNaRRSTCTL_RST_DONE BIT(30)
> #define LYNX_28G_LNaRRSTCTL_RST_REQ BIT(31)
> @@ -948,6 +952,95 @@ static void lynx_28g_lane_set_25g(struct lynx_28g_lane
> *lane,
> LYNX_28G_LNaTTLCR0_CDR_MIN_SMP_ON(1));
> }
>
> +/* Halting puts the lane in a mode in which it can be reconfigured */
> +static void lynx_28g_lane_halt(struct phy *phy)
> +{
> + struct lynx_28g_lane *lane = phy_get_drvdata(phy);
> + u32 trstctl, rrstctl;
> +
> + /* Issue a halt request */
> + lynx_28g_lane_rmw(lane, LNaTRSTCTL, LYNX_28G_LNaTRSTCTL_HLT_REQ,
> + LYNX_28G_LNaTRSTCTL_HLT_REQ);
> + lynx_28g_lane_rmw(lane, LNaRRSTCTL, LYNX_28G_LNaRRSTCTL_HLT_REQ,
> + LYNX_28G_LNaRRSTCTL_HLT_REQ);
> +
> + /* Wait until the halting process is complete */
> + do {
> + trstctl = lynx_28g_lane_read(lane, LNaTRSTCTL);
> + rrstctl = lynx_28g_lane_read(lane, LNaRRSTCTL);
> + } while ((trstctl & LYNX_28G_LNaTRSTCTL_HLT_REQ) ||
> + (rrstctl & LYNX_28G_LNaRRSTCTL_HLT_REQ));
> +}
> +
> +static void lynx_28g_lane_reset(struct phy *phy)
> +{
> + struct lynx_28g_lane *lane = phy_get_drvdata(phy);
> + u32 trstctl, rrstctl;
> +
> + /* Issue a reset request on the lane */
> + lynx_28g_lane_rmw(lane, LNaTRSTCTL, LYNX_28G_LNaTRSTCTL_RST_REQ,
> + LYNX_28G_LNaTRSTCTL_RST_REQ);
> + lynx_28g_lane_rmw(lane, LNaRRSTCTL, LYNX_28G_LNaRRSTCTL_RST_REQ,
> + LYNX_28G_LNaRRSTCTL_RST_REQ);
> +
> + /* Wait until the reset sequence is completed */
> + do {
> + trstctl = lynx_28g_lane_read(lane, LNaTRSTCTL);
> + rrstctl = lynx_28g_lane_read(lane, LNaRRSTCTL);
> + } while (!(trstctl & LYNX_28G_LNaTRSTCTL_RST_DONE) ||
> + !(rrstctl & LYNX_28G_LNaRRSTCTL_RST_DONE));
> +}
> +
> +static int lynx_28g_power_off(struct phy *phy)
> +{
> + struct lynx_28g_lane *lane = phy_get_drvdata(phy);
> + u32 trstctl, rrstctl;
> +
> + if (!lane->powered_up)
> + return 0;
> +
> + /* Issue a stop request */
> + lynx_28g_lane_rmw(lane, LNaTRSTCTL, LYNX_28G_LNaTRSTCTL_STP_REQ,
> + LYNX_28G_LNaTRSTCTL_STP_REQ);
> + lynx_28g_lane_rmw(lane, LNaRRSTCTL, LYNX_28G_LNaRRSTCTL_STP_REQ,
> + LYNX_28G_LNaRRSTCTL_STP_REQ);
> +
> + /* Wait until the stop process is complete */
> + do {
> + trstctl = lynx_28g_lane_read(lane, LNaTRSTCTL);
> + rrstctl = lynx_28g_lane_read(lane, LNaRRSTCTL);
> + } while ((trstctl & LYNX_28G_LNaTRSTCTL_STP_REQ) ||
> + (rrstctl & LYNX_28G_LNaRRSTCTL_STP_REQ));
> +
> + /* Power down the RX and TX portions of the lane */
> + lynx_28g_lane_rmw(lane, LNaRRSTCTL, LYNX_28G_LNaRRSTCTL_DIS,
> + LYNX_28G_LNaRRSTCTL_DIS);
> + lynx_28g_lane_rmw(lane,
Re: [linux-yocto] Overlapped upstream patch in yocto-kernel-cache
On Tue, Apr 16, 2024 at 1:52 PM Robert D Kocisko wrote: > On Tue, Apr 16, 2024 at 9:50 AM Bruce Ashfield via > lists.yoctoproject.org > wrote: > > > > Your issue is something different. > > > > The linux-yocto branches are generated from the kernel-cache, so you'll > always see a patch in the kernel-cache and in the linux-yocto kernel > branches. > > Ah ok. I had a sneaking suspicion that perhaps this was the case but > it wasn't obvious to me even after five read-throughs of the > documentation :) > > > > > What you are seeing likely stems from your BSP definition. How have to > defined it for your board ? > > This is where my confusion lies. I defined my BSP as follows, trying > to follow the 'beaglebone' examples from the documentation. > I don't want to include ktypes/preempt-rt because it enables a bunch > of *_DEBUG kernel configuration options as well as other stuff that I > find bloat-y. > Without including the ktypes/preempt-rt/preempt-rt.scc, you won't actually have the preempt-rt patches applied, as that's where the branches are created and the features/rt is included (and that feature is the actual -rt patches). Any debug options are typically controlled by KERNEL_FEATURES in the kernel recipes, so I wouldn't expect too much to be one. Generally speaking, we are middle of the road for functionality versus minimal. You also can always turn off options you don't want in your BSP, since the last fragment that is processed will "win". > > --- > define KMACHINE rk3588-firefly-itx > define KTYPE preempt-rt > define KARCH arm64 > > include ktypes/tiny > branch firefly-preempt-rt > > kconf non-hardware firefly-preempt-rt.cfg > > include remove-non-rockchip-arch-arm64.ssc > --- > > Then in my machine .conf I add this line (without this I'm not sure > how to tell yocto to use the bsp definition I created): > KERNEL_FEATURES += " bsp/rockchip/firefly-preempt-rt.scc" > > That would do exactly what you are seeing, it would start processing the fragment and applying the patches. Which is where you ended up with the duplicate patches being applied. This is the section that you are looking for: https://docs.yoctoproject.org/dev/kernel-dev/advanced.html#recipe-space-metadata That's how the tools will locate the BSP and process it accordingly. There could of course be bugs, but I have tested this in the past 6 months. Bruce > > > > The tools know that with a proper BSP definition that they don't need to > re-apply patches, since they are already in the trees and only the kernel > type configuration will be used. > > > > In this case, everything in the standard kernel and preempt-rt kernel > are already on the v6.6/standard/preempt-rt/base branch, so they'll be > skipped. Only your BSP patches and configuration will be added. > > > > But that functionality needs a proper BSP definition to work. > > > > If you find the section "recipe space BSPs" in the project > documentation, it has more details. > > > > Bruce > > > > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13828): https://lists.yoctoproject.org/g/linux-yocto/message/13828 Mute This Topic: https://lists.yoctoproject.org/mt/105548012/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] Overlapped upstream patch in yocto-kernel-cache
On Mon, Apr 15, 2024 at 8:02 PM Robert D Kocisko via lists.yoctoproject.org wrote: > Hello! My name is Bob Kocisko (engineer at St Joseph Missions, in the > broadcast industry) and we are using Yocto to build a preempt-rt > distribution for a rockchip-based arm board. > > I have been trying to append " ktypes/preempt-rt" or " ktypes/tiny" to > the KERNEL_FEATURES variable in my machine .conf, and I keep getting > the following error: > > | (5/277) ARM-LPAE-Invalidate-the-TLB-for-module-addresses-dur.patch > | [INFO]: check of > > .kernel-meta//patches//arch/arm/v7-A15/ARM-LPAE-Invalidate-the-TLB-for-module-addresses-dur.patch > with "git am" did not > pass, trying reduced context. > | [INFO]: Context reduced git-am of > > .kernel-meta//patches//arch/arm/v7-A15/ARM-LPAE-Invalidate-the-TLB-for-module-addresses-dur.patch > with > "git am" did not work, trying "apply". > | error: patch failed: arch/arm/mm/fault.c:448 > | error: arch/arm/mm/fault.c: patch does not apply > > Upon further inspection, it seems to me that there is an overlap in > the patches, because in yocto-kernel-cache we have the patch in [1], > but in linux-yocto, that patch appears to be already applied at [2]. > > 1: > https://git.yoctoproject.org/yocto-kernel-cache/tree/arch/arm/v7-A15/ARM-LPAE-Invalidate-the-TLB-for-module-addresses-dur.patch?h=yocto-6.6 > 2: > https://git.yoctoproject.org/linux-yocto/commit/arch/arm/mm/fault.c?h=v6.6/standard/preempt-rt/base=75e31a2b70fd3d94a4af563ab8b3bea75e089469 > > Have I diagnosed this correctly? If so, please confirm and I can > Your issue is something different. The linux-yocto branches are generated from the kernel-cache, so you'll always see a patch in the kernel-cache and in the linux-yocto kernel branches. What you are seeing likely stems from your BSP definition. How have to defined it for your board ? The tools know that with a proper BSP definition that they don't need to re-apply patches, since they are already in the trees and only the kernel type configuration will be used. In this case, everything in the standard kernel and preempt-rt kernel are already on the v6.6/standard/preempt-rt/base branch, so they'll be skipped. Only your BSP patches and configuration will be added. But that functionality needs a proper BSP definition to work. If you find the section "recipe space BSPs" in the project documentation, it has more details. Bruce > submit a patch to update yocto-kernel-cache. > > > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13825): https://lists.yoctoproject.org/g/linux-yocto/message/13825 Mute This Topic: https://lists.yoctoproject.org/mt/105548012/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g][PATCH] dts: Aptiv-FL: Update 'Slew-Rates' from MSCR registers
In message:
[linux-yocto][v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g][PATCH] dts:
Aptiv-FL: Update 'Slew-Rates' from MSCR registers
on 15/04/2024 quanyang.w...@windriver.com wrote:
> From: Quanyang Wang
>
> In SDK commit 3bf1e1fe0321 ("s32cc: Update 'Slew-Rates' from MSCR
> registers", "Slew-Rates" is updated.
>
> Signed-off-by: Quanyang Wang
> ---
> Hi Bruce,
> Would you please help merge this patch to the branches:
> v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g
> v6.1/standard/nxp-sdk-5.15/nxp-s32g
merged.
Bruce
> Thanks,
> Quanyang
> ---
> .../boot/dts/freescale/s32gxxxa-cvc-fl.dtsi | 86 +--
> 1 file changed, 43 insertions(+), 43 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/freescale/s32gxxxa-cvc-fl.dtsi
> b/arch/arm64/boot/dts/freescale/s32gxxxa-cvc-fl.dtsi
> index 537eda907e80d..9ca0424e49fdb 100644
> --- a/arch/arm64/boot/dts/freescale/s32gxxxa-cvc-fl.dtsi
> +++ b/arch/arm64/boot/dts/freescale/s32gxxxa-cvc-fl.dtsi
> @@ -255,13 +255,13 @@ can0_pins: can0 {
> can0_grp0 {
> pinmux = ;
> output-enable;
> - slew-rate = ;
> + slew-rate = ;
> };
>
> can0_grp1 {
> pinmux = ;
> input-enable;
> - slew-rate = ;
> + slew-rate = ;
> };
>
> can0_grp2 {
> @@ -273,13 +273,13 @@ can1_pins: can1 {
> can1_grp0 {
> pinmux = ;
> output-enable;
> - slew-rate = ;
> + slew-rate = ;
> };
>
> can1_grp1 {
> pinmux = ;
> input-enable;
> - slew-rate = ;
> + slew-rate = ;
> };
>
> can1_grp2 {
> @@ -292,13 +292,13 @@ can2_pins: can2 {
> can2_grp0 {
> pinmux = ;
> output-enable;
> - slew-rate = ;
> + slew-rate = ;
> };
>
> can2_grp1 {
> pinmux = ;
> input-enable;
> - slew-rate = ;
> + slew-rate = ;
> };
>
> can2_grp2 {
> @@ -311,13 +311,13 @@ can3_pins: can3 {
> can3_grp0 {
> pinmux = ;
> output-enable;
> - slew-rate = ;
> + slew-rate = ;
> };
>
> can3_grp1 {
> pinmux = ;
> input-enable;
> - slew-rate = ;
> + slew-rate = ;
> };
>
> can3_grp2 {
> @@ -330,26 +330,26 @@ dspi1_pins: dspi1 {
> dspi1_grp0 {
> pinmux = ;
> output-enable;
> - slew-rate = ;
> + slew-rate = ;
> bias-pull-up;
> };
>
> dspi1_grp1 {
> pinmux = ;
> output-enable;
> - slew-rate = ;
> + slew-rate = ;
> };
>
> dspi1_grp2 {
> pinmux = ;
> output-enable;
> - slew-rate = ;
> + slew-rate = ;
> };
>
> dspi1_grp3 {
> pinmux = ;
> input-enable;
> - slew-rate = ;
> + slew-rate = ;
> bias-pull-up;
> };
>
> @@ -363,13 +363,13 @@ dspi1slave_pins: dspi1slave {
> dspi1slave_grp0 {
> pinmux = ;
> output-enable;
> - slew-rate = ;
> + slew-rate = ;
> };
>
> dspi1slave_grp1 {
> pinmux = ;
> input-enable;
> - slew-rate = ;
> + slew-rate = ;
> };
>
> dspi1slave_grp2 {
> @@ -381,13 +381,13 @@ dspi1slave_grp2 {
> dspi1slave_grp3 {
> pinmux = ;
> input-enable;
> - slew-rate = ;
> + slew-rate = ;
> };
>
> dspi1slave_grp4 {
> pinmux = ;
> input-enable;
> - slew-rate = ;
> + slew-rate = ;
> bias-pull-up;
> };
>
> @@ -400,7 +400,7 @@ i2c0_grp0 {
> drive-open-drain;
> output-enable;
> input-enable;
> - slew-rate = ;
> +
Re: [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
merged.
Bruce
In message: [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
on 14/04/2024 Xiaolei Wang wrote:
> 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
>
In message: [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()
on 14/04/2024 Xiaolei Wang wrote:
> 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 (#13816):
https://lists.yoctoproject.org/g/linux-yocto/message/13816
Mute This Topic: https://lists.yoctoproject.org/mt/105544894/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] Trial merge of v5.15.154 v5.15.155 v6.1.85 v6.1.86 v6.6.26 v6.6.27 for linux-yocto
In message: Trial merge of v5.15.154 v5.15.155 v6.1.85 v6.1.86 v6.6.26 v6.6.27
for linux-yocto
on 14/04/2024 Kevin Hao wrote:
> Hi Bruce,
>
> This is a trial merge of the stable kernel v5.15.154 v5.15.155 v6.1.85
> v6.1.86 v6.6.26 v6.6.27 for the following branches in the linux-yocto.
> e9abb220b483 v5.15/standard/sdkv5.10/axxia
> 45ea7fd6deb3 v5.15/standard/preempt-rt/sdkv5.10/axxia
>#Have textual conflicts
> 338e45bb3c72 v5.15/standard/base
> 560114e1157c v5.15/standard/preempt-rt/base
>#Have textual conflicts
> 15bfd383b4fe v5.15/standard/cn-sdkv5.4/octeon
>#Have textual conflicts
> fe537f5c00aa v5.15/standard/preempt-rt/cn-sdkv5.4/octeon
>#Have textual conflicts
> 42d51dfcf742 v5.15/standard/cn-sdkv5.15/octeon
>#Have textual conflicts
> a360a277d8c5 v5.15/standard/preempt-rt/cn-sdkv5.15/octeon
>#Have textual conflicts
> 94f8d18051bc v5.15/standard/ti-sdk-5.10/ti-j72xx
>#Have semantic conflicts
> 28a567a954bb v5.15/standard/preempt-rt/ti-sdk-5.10/ti-j72xx
>#Have textual and semantic conflicts
> 9b10d67f9133 v5.15/standard/nxp-sdk-5.15/nxp-soc
> 000ea032ce7e v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-soc
>#Have textual conflicts
> 7275aca4cfdf v5.15/standard/bcm-2xxx-rpi
>#Have textual conflicts
> 78c69a0f908a v5.15/standard/preempt-rt/bcm-2xxx-rpi
>#Have textual conflicts
> 6787a55d698c v5.15/standard/nxp-sdk-5.15/nxp-s32g
> 93d7d914ca7f v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g
>#Have textual conflicts
> 637311038753 v5.15/standard/intel-sdk-5.15/intel-socfpga
> a06b22b7d58e v5.15/standard/preempt-rt/intel-sdk-5.15/intel-socfpga
>#Have textual conflicts
> 4d50b8c5189a v5.15/standard/x86
> 276dfc4331d5 v5.15/standard/preempt-rt/x86
>#Have textual conflicts
> 98a0d48f8b36 v5.15/standard/sdkv5.15/xlnx-soc
> 7792c8cb904e v5.15/standard/preempt-rt/sdkv5.15/xlnx-soc
>#Have textual conflicts
> 9ceb112cb342 v6.1/standard/sdkv5.10/axxia
> 7cf4993427e1 v6.1/standard/preempt-rt/sdkv5.10/axxia
> 4dabed7fb978 v6.1/standard/base
> 9e90f437b653 v6.1/standard/preempt-rt/base
> 5a46b2f8deb1 v6.1/standard/ti-sdk-6.1/ti-j7xxx
> 9a28a49e61f2 v6.1/standard/preempt-rt/ti-sdk-6.1/ti-j7xxx
> 470cf58c8b0a v6.1/standard/nxp-sdk-6.1/nxp-soc
>#Have textual conflicts
> 1a3c9deae571 v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc
>#Have textual conflicts
> e5e11cf46c8b v6.1/standard/cn-sdkv5.15/octeon
> 6f429f01fa65 v6.1/standard/preempt-rt/cn-sdkv5.15/octeon
> db049b49dff8 v6.1/standard/cn-sdkv6.1/octeon
> cc34d22ea6ec v6.1/standard/preempt-rt/cn-sdkv6.1/octeon
> a3d86213ad68 v6.1/standard/microchip-polarfire-soc
> 3ceee345c596 v6.1/standard/preempt-rt/microchip-polarfire-soc
> 2251f3484861 v6.1/standard/bcm-2xxx-rpi
> 1d41d5af914d v6.1/standard/preempt-rt/bcm-2xxx-rpi
> 25c63255a081 v6.1/standard/nxp-sdk-5.15/nxp-s32g
> 806851c530cf v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g
> 912f6a8d9b46 v6.1/standard/intel-sdk-6.1/intel-socfpga
> 80ad7c379462 v6.1/standard/preempt-rt/intel-sdk-6.1/intel-socfpga
> aa513c5e1706 v6.1/standard/x86
> 61d456afb1a9 v6.1/standard/preempt-rt/x86
> 4219fee1b3b0 v6.1/standard/sdkv6.1/xlnx-soc
> f28253069109 v6.1/standard/preempt-rt/sdkv6.1/xlnx-soc
> 94cc25c90d4b v6.6/standard/base
> 66e58fb721a8 v6.6/standard/preempt-rt/base
>#Have textual conflicts
> 8c366355c6f8 v6.6/standard/nxp-sdk-6.6/nxp-soc
>#Have textual and semantic conflicts
> 4c8afd018000 v6.6/standard/preempt-rt/nxp-sdk-6.6/nxp-soc
>#Have textual and semantic conflicts
>
> Most of the merge conflicts come from v5.15 kernel.
>
> - There is a merge conflict on the v5.15 rt kernel. It is caused by
> stable commit 9bd2f11ac9ef ("printk: Update @console_may_schedule in
> console_trylock_spinning()")
> rt commit 2d440f3f2ee5 ("printk: move console printing to kthreads")
>
> We just need to drop the changes introduced by stable commit 9bd2f11ac9ef
> because the original
> console_trylock_spinning() function was already delete by rt commit
> 2d440f3f2ee5.
>
> - There is a semantic conflict on v5.15 j72xx branches. We need to drop the
> umin() function
> in drivers/media/platform/vxe-vxd/decoder/h264_secure_parser.c because an
> umin() macro
> was introduce by stable commit cf716d5a0dd8 ("minmax: add umin(a, b) and
> umax(a, b)")
>
> - There is also a semantic conflict on v6.6 nxp branches. We need adjust the
> change of
>
Re: [linux-yocto] [yocto-kernel-cache kernel v6.1]: nxp-s32g: update to compatible with SDK BSP40
Thanks for the heads up. I've dropped it from my queue. Bruce On Mon, Apr 15, 2024 at 4:46 AM Tang, Zhantao wrote: > Hi Bruce, > > Please ignore this request, I will send a new one later. > > Thanks, > Zhantao > > -- > *From:* linux-yocto@lists.yoctoproject.org < > linux-yocto@lists.yoctoproject.org> on behalf of Zhantao Tang via > lists.yoctoproject.org > *Sent:* Sunday, April 14, 2024 7:24:58 AM > *To:* bruce.ashfi...@gmail.com > *Cc:* linux-yocto@lists.yoctoproject.org < > linux-yocto@lists.yoctoproject.org> > *Subject:* [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 > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13814): https://lists.yoctoproject.org/g/linux-yocto/message/13814 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: [linux-yocto] [linux-yocto std kernel]: update std kernel for nxp-imx9
both are merged. Bruce In message: [linux-yocto] [linux-yocto std kernel]: update std kernel for nxp-imx9 on 12/04/2024 Xiaolei Wang wrote: > Hi bruce > > Would you please help to merge the following patch into branch: > > v6.1/standard/nxp-sdk-6.1/nxp-soc > > for nxp-imx9 bsp? > > The following changes since commit 93c514e7433e49536a23abaca358935674922bad: > > arm64: dts: fix ecspi2 dts node (2024-03-22 11:48:47 +0800) > > are available in the Git repository at: > > https://github.com/wangxiaolei12/linux-yocto-6.1.git > v6.1/standard/nxp-sdk-6.1/nxp-soc > > for you to fetch changes up to 02fe605dcc348f36559b8ce4833cece1f1f65224: > > LF-10611 arm64: dts: imx8mq-evk-rpmsg: fix CMA memory reservation fail > (2024-04-12 09:07:33 +0800) > > > Alexander Sverdlin (1): > LF-9506-2 tty: serial: fsl_lpuart: fix race on RX DMA shutdown > > Alice Guo (7): > LF-9535 soc: imx: split i.MX93 SoC device support from soc-imx8m.c > LF-9476-1 ele_base_msg: handle common fuse with special id > LF-9476-2 nvmem: imx: update read_common_fuse with special ID > LF-9476-3 nvmem: imx: update i.MX93 fuse read driver > LF-9646-1: soc: imx: remove the part related to i.MX9 from soc-imx8m.c > LF-9646-2 soc: imx9: i.MX91P reuses i.MX93 SoC driver > LF-10365 nvmem: imx: i.MX8ULP: update fsb_bank_reg of > imx8ulp_fsb_s400_hw > > Alice Yuan (4): > LF-9127-1: arm64: dtsi: imx8ulp: Support suspend/resume when camera is > running > LF-9127-2: media: csi: Support suspend/resume when camera is running > LF-9127-3: media: isi: support suspend/resume when camera is running > LF-9638 media: isi: Fix the isi-m2m play hang if convert format > > Andrew Lunn (1): > net: mdio: Add dedicated C45 API to MDIO bus drivers > > Andy Shevchenko (1): > device property: Introduce fwnode_device_is_compatible() helper > > Apeksha Gupta (1): > net/fec-uio: Fixed error handling > > Camelia Groza (16): > net: phy: aquantia: Add support for AQR115 > net: sdk_fman: macsec: check the return value of FM_MAC_GetId > net: sdk_fman: macsec: free locks on error paths > net: sdk_fman: fm_cc: free resources on MatchTableSet error path > net: sdk_fman: fm_manip: initialize prsArrayOffset > net: sdk_fman: fm_manip: release the p_Manip spinlock on error > net: sdk_fman: wrapper: check the return value of FM_CtrlMonGetCounters > fsl_qbman: check qman_ccsrmempeek's return value > net: sdk_fman: cleanup memory on fm_port_probe error paths > net: sdk_fman: cleanup memory on fm_probe error paths > net: sdk_fman: initialize variables before use > net: sdk_fman: cleanup SP memory on FM_Config errors > net: sdk_fman: cleanup resources if HashTableSet fails > soc: fsl: qbman: check kzalloc return value > net: fman: fix variable type > net: sdk_fman: avoid division by zero > > Carlos Song (4): > MLK-26127-1 arm64: dts: imx91p-9x9-qsb: add lpspi master support > MLK-26127-2 arm64: dts: imx91p-9x9-qsb: add lpspi slave support > LF-9490 arm64: dts: imx93: enable eDMA for lpspi devices > LF-9692 arm64: dts: imx91p-11x11-evk: Add lpspi support > > Chancel Liu (18): > LF-9256: arm64: dts: imx93-11x11-evk-rpmsg: Disable unavailable devices > MLK-26119: arm64: dts: imx91p-9x9-qsb-aud-hat: Add a new DT to support > AUD-HAT board > LF-9645-1: arm64: dts: imx91p-11x11-evk-mqs: Add a new DT to support MQS > LF-9645-2: arm64: dts: imx91p-11x11-evk-aud-hat: Add a new DT to > support AUD-HAT board > LF-9688-1: arm64: dts: imx93-9x9-qsb-rpmsg: Add a DT to support LPA > LF-9688-2: arm64: dts: imx93-9x9-qsb-rpmsg-lpv: Add a DT to support LPV > LF-9708: arm64: dts: imx93-9x9-qsb-aud-hat: Use RPI 3v3 and 5v regulator > ASoC: fsl_micfil: Add new registers and new bit definition > ASoC: fsl_micfil: Add fsl_micfil_use_verid function > ASoC: fsl_micfil: Use SET_SYSTEM_SLEEP_PM_OPS to simplify PM > LF-9333: ASoC: fsl_rpmsg: Move MCLK control to runtime suspend/resume > phase > Revert "LF-9333: ASoC: fsl_rpmsg: Move MCLK control to runtime > suspend/resume phase" > LF-9368: arm64: dts: imx93-11x11-evk-rpmsg: Enable dynamic buffer size > for i2c-rpmsg > LF-9910-1: arm64: dts: imx8m: Let WM8524 driver constrain supported rate > LF-9910-2: Revert "LF-6278-2: ASoC: fsl_rpmsg: Constrain rates of > wm8524 codec" > ASoC: soc-pcm.c: Clear DAIs parameters after stream_active is updated > ASoC: soc-pcm.c: Make sure DAI parameters cleared if the DAI becomes > inactive > LF-9973-7: arm64: dts: imx93: add fsl,sai-mclk-direction-output > > Clark Wang (6): > MLK-26126 arm64: dts: imx91p-9x9-qsb: add i3c support > LF-9574-1 nvmem: imx: change the unit of offset > LF-9574-2 arm64: dts:
Re: [linux-yocto] net/can: llce: Drop unused label in register_devlink_params()
In message: [linux-yocto] net/can: llce: Drop unused label in
register_devlink_params()
on 11/04/2024 Kevin Hao wrote:
> From: Kevin Hao
>
> This unused label was introduced by sdk commit 6f13f0d7b7a7 ("net/can:
> llce: Add self-recv devlink parameter").
>
> Signed-off-by: Kevin Hao
> ---
> Hi Bruce,
>
> Please help me merge this into the following two branches:
> v6.1/standard/nxp-sdk-5.15/nxp-s32g
> v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g
merged.
Bruce
>
> drivers/net/can/llce/llce_can.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/net/can/llce/llce_can.c b/drivers/net/can/llce/llce_can.c
> index 8d059ae6626f..57336d06d369 100644
> --- a/drivers/net/can/llce/llce_can.c
> +++ b/drivers/net/can/llce/llce_can.c
> @@ -816,7 +816,6 @@ static int register_devlink_params(struct llce_can *llce,
> struct device *dev)
> unreg_devlink:
> if (ret)
> devlink_unregister(devlink);
> -free_devlink:
> if (ret)
> devlink_free(devlink);
>
> --
> 2.44.0
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13802):
https://lists.yoctoproject.org/g/linux-yocto/message/13802
Mute This Topic: https://lists.yoctoproject.org/mt/105460526/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [linux-yocto 0/2] Fix two build warnings on v5.15 j72xx branches
In message: [linux-yocto 0/2] Fix two build warnings on v5.15 j72xx branches on 11/04/2024 Kevin Hao wrote: > From: Kevin Hao > > Hi Bruce, > > These two patches fix several build warnings on v5.15 j72xx branches. > Please help me merge them into the following two branches: > v5.15/standard/ti-sdk-5.10/ti-j72xx > v5.15/standard/preempt-rt/ti-sdk-5.10/ti-j72xx merged. Bruce > > Kevin Hao (2): > media: vxe-vxd: Drop unused variable and function in vxd_v4l2.c > media: vxe-vxd: Fix the incorrect indentation in > topaz_video_destroy_context() > > .../media/platform/vxe-vxd/decoder/vxd_v4l2.c| 16 > .../media/platform/vxe-vxd/encoder/topaz_api.c | 4 ++-- > 2 files changed, 2 insertions(+), 18 deletions(-) > > -- > 2.44.0 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13801): https://lists.yoctoproject.org/g/linux-yocto/message/13801 Mute This Topic: https://lists.yoctoproject.org/mt/105459977/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [linux-yocto preempt-rt kernel v6.1]: nxp-s32g: update to compatible with SDK BSP40 release
In message: [linux-yocto] [linux-yocto preempt-rt kernel v6.1]: nxp-s32g: update to compatible with SDK BSP40 release on 11/04/2024 Zhantao Tang wrote: > Hi Bruce, > > There are 211 patches to update to compatible with SDK BSP40 release. > Would you please help to merge the following patches into > v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g merged. Bruce > > branch? > > The following changes since commit acda2a279d8f9e5f60c19e47d6ae70e207e751e1: > > Merge branch 'v6.1/standard/preempt-rt/base' into > v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g (2024-04-09 12:37:43 -0400) > > are available in the Git repository at: > > https://github.com/zhantaotang/linux-yocto-std > v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g > > for you to fetch changes up to d49e6f8ff7060fa5478362aee50fa5b81566fc45: > > thermal: qoriq: Fix deadlock between irq and tmu_get_temp (2024-04-10 > 21:43:22 +0800) > > > Thanks, > Zhantao > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13800): https://lists.yoctoproject.org/g/linux-yocto/message/13800 Mute This Topic: https://lists.yoctoproject.org/mt/105454685/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [linux-yocto std kernel v6.1]: nxp-s32g: update to compatible with SDK BSP40 release
In message: [linux-yocto] [linux-yocto std kernel v6.1]: nxp-s32g: update to compatible with SDK BSP40 release on 11/04/2024 Zhantao Tang wrote: > Hi Bruce, > > There are 211 patches to update to compatible with SDK BSP39 release. > Would you please help to merge the patches to: > v6.1/standard/nxp-sdk-5.15/nxp-s32g > branch? > merged. Bruce > > The following changes since commit c35789c18149bed4d149a893a16ba61f589a3d20: > > Merge branch 'v6.1/standard/base' into v6.1/standard/nxp-sdk-5.15/nxp-s32g > (2024-04-09 12:30:40 -0400) > > are available in the Git repository at: > > https://github.com/zhantaotang/linux-yocto-std > v6.1/standard/nxp-sdk-5.15/nxp-s32g > > for you to fetch changes up to e3c1d80279e6fe930a99bcec75fb3179ab0f1adf: > > thermal: qoriq: Fix deadlock between irq and tmu_get_temp (2024-04-10 > 21:15:51 +0800) > > > Thanks, > Zhantao > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13799): https://lists.yoctoproject.org/g/linux-yocto/message/13799 Mute This Topic: https://lists.yoctoproject.org/mt/105454683/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [kernel-cache][PATCH] nft_test.cfg: Enable CONFIG_VETH
merged. SRCREV bumps will follow in a bit. Bruce In message: [linux-yocto] [kernel-cache][PATCH] nft_test.cfg: Enable CONFIG_VETH on 10/04/2024 Khem Raj wrote: > nftable ptests do create interfaces of veth type and this > feature would be needed to enable those tests > > e.g. from tests/shell/testcases/packetpath/vlan_8021ad_tag > > ip link add veth0 netns $ns1 type veth peer name veth0 netns $ns2 > > Signed-off-by: Khem Raj > --- > features/nf_tables/nft_test.cfg | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/features/nf_tables/nft_test.cfg b/features/nf_tables/nft_test.cfg > index 45ca8e5d..0a959d0e 100644 > --- a/features/nf_tables/nft_test.cfg > +++ b/features/nf_tables/nft_test.cfg > @@ -10,3 +10,4 @@ CONFIG_NFT_OSF=m > CONFIG_NFT_QUOTA=m > CONFIG_NFT_SYNPROXY=m > CONFIG_NFT_XFRM=m > +CONFIG_VETH=y > -- > 2.44.0 > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13798): https://lists.yoctoproject.org/g/linux-yocto/message/13798 Mute This Topic: https://lists.yoctoproject.org/mt/105453035/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] media: img: vxd: Drop the unneeded umin() function
In message: [linux-yocto] media: img: vxd: Drop the unneeded umin() function
on 10/04/2024 Kevin Hao wrote:
> From: Kevin Hao
>
> The stable commit 8d8be62a7d53 ("minmax: add umin(a, b) and umax(a, b)")
> introduced an umin() macro. This conflicts with the umin() inline
> function in vxe-vxd driver. So drop this inline function to fix the
> build error.
>
> Signed-off-by: Kevin Hao
> ---
> Hi Bruce,
>
> Could you help me merge this into the following two branches?
> v6.1/standard/ti-sdk-6.1/ti-j7xxx
> v6.1/standard/preempt-rt/ti-sdk-6.1/ti-j7xxx
merged.
Bruce
>
> .../platform/img/vxe-vxd/decoder/h264_secure_parser.c | 8
> 1 file changed, 8 deletions(-)
>
> diff --git a/drivers/media/platform/img/vxe-vxd/decoder/h264_secure_parser.c
> b/drivers/media/platform/img/vxe-vxd/decoder/h264_secure_parser.c
> index 6c098a6fddf4..da43bf6a7a03 100644
> --- a/drivers/media/platform/img/vxe-vxd/decoder/h264_secure_parser.c
> +++ b/drivers/media/platform/img/vxe-vxd/decoder/h264_secure_parser.c
> @@ -168,14 +168,6 @@ static const int bspp_subheightc[] = { -1, 2, 1, 1 };
> */
> static const int bspp_subwidthc[] = { -1, 2, 2, 1 };
>
> -/*
> - * inline functions for Minimum and Maximum value
> - */
> -static inline unsigned int umin(unsigned int a, unsigned int b)
> -{
> - return (((a) < (b)) ? (a) : (b));
> -}
> -
> static inline int smin(int a, int b)
> {
> return (((a) < (b)) ? (a) : (b));
> --
> 2.44.0
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13787):
https://lists.yoctoproject.org/g/linux-yocto/message/13787
Mute This Topic: https://lists.yoctoproject.org/mt/105437816/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto]: [kernel/kernel-rt v6.1]: dmaengine: imx-sdma: move memory copy operation before dma map
merged. Bruce In message: [linux-yocto]: [kernel/kernel-rt v6.1]: dmaengine: imx-sdma: move memory copy operation before dma map on 08/04/2024 Meng Li wrote: > From: Limeng > > Hi Bruce, > > This patch is used to move memory copy operation before dma map > Could you please help merge this patch into linux-ycoto kernel? > Branch are v6.1/standard/nxp-sdk-6.1/nxp-soc and > v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc > > > diffstat info as below: > > imx-sdma.c |4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > thanks, > Limeng -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13783): https://lists.yoctoproject.org/g/linux-yocto/message/13783 Mute This Topic: https://lists.yoctoproject.org/mt/105397624/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] Trial merge of v6.1.84 for linux-yocto
In message: [linux-yocto] Trial merge of v6.1.84 for linux-yocto
on 05/04/2024 Kevin Hao wrote:
> Hi Bruce,
>
> This is a trial merge of the stable kernel v6.1.84 for the following branches
> in the linux-yocto.
> 7e8aba41d616 v6.1/standard/sdkv5.10/axxia
> 20b864b63270 v6.1/standard/preempt-rt/sdkv5.10/axxia
>#Have textual conflicts
> 6e7505a77dab v6.1/standard/base
> a0836e0ed8b0 v6.1/standard/preempt-rt/base
>#Have textual conflicts
> c8a6a6ede39b v6.1/standard/ti-sdk-6.1/ti-j7xxx
>#Have textual and semantic conflicts
> 6b0bd6c88b2b v6.1/standard/preempt-rt/ti-sdk-6.1/ti-j7xxx
>#Have textual and semantic conflicts
> 39ae0de6c0d0 v6.1/standard/nxp-sdk-6.1/nxp-soc
> fb59778024f1 v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc
>#Have textual conflicts
> e3971ab030ed v6.1/standard/cn-sdkv5.15/octeon
> 459b44937628 v6.1/standard/preempt-rt/cn-sdkv5.15/octeon
>#Have textual conflicts
> cd0f526a7e68 v6.1/standard/cn-sdkv6.1/octeon
> af294cdc7744 v6.1/standard/preempt-rt/cn-sdkv6.1/octeon
>#Have textual conflicts
> 33d58f391255 v6.1/standard/microchip-polarfire-soc
> 7a324d693ac0 v6.1/standard/preempt-rt/microchip-polarfire-soc
>#Have textual conflicts
> fa81a6f5ee82 v6.1/standard/bcm-2xxx-rpi
> 7d18665d29dc v6.1/standard/preempt-rt/bcm-2xxx-rpi
>#Have textual conflicts
> 88714ab2b982 v6.1/standard/nxp-sdk-5.15/nxp-s32g
> f7261b4f1704 v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g
>#Have textual conflicts
> b3001ad2c0f0 v6.1/standard/intel-sdk-6.1/intel-socfpga
>#Have textual conflicts
> 23a0b1e792c8 v6.1/standard/preempt-rt/intel-sdk-6.1/intel-socfpga
>#Have textual conflicts
> 158fbc5639bd v6.1/standard/x86
> 6657024d2663 v6.1/standard/preempt-rt/x86
>#Have textual conflicts
> 64960db058fe v6.1/standard/sdkv6.1/xlnx-soc
> 6d72a43f8f44 v6.1/standard/preempt-rt/sdkv6.1/xlnx-soc
>#Have textual conflicts
>
> - There is a conflict on the RT kernel, it was caused by following two
> commits:
> stable commit b8073c069a84 ("serial: Lock console when calling into
> driver before registration")
> RT commit 9c5c63877973 ("serial: 8250: implement write_atomic").
> This merge conflict is not too difficult to resolve.
>
> - There are many ugly merge conflicts in dwc3-am62 driver on j7xx branches
> due to the private data rename.
> aa1d1ce1ad6b ("usb: dwc3-am62: Rename private data")
> I believe I have resolved all of them.
>
> All the branches have passed my build test. I have pushed all these branches
> to:
> https://github.com/haokexin/linux
>
> You can use this as a reference for the linux-yocto stable kernel bump.
Thanks Kevin,
I did a smilar merge and grabbed your resolutions .. the ti-jxxx BSPs certainly
caused some issues :)
IF anything is still broken, ssend follow up patches.
Bruce
>
> Thanks,
> Kevin
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13782):
https://lists.yoctoproject.org/g/linux-yocto/message/13782
Mute This Topic: https://lists.yoctoproject.org/mt/105346373/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][linux-yocto-5.15][PATCH 0/2] revert two patches to avoid import new issue
In message: [linux-yocto][linux-yocto-5.15][PATCH 0/2] revert two patches to avoid import new issue on 03/04/2024 Liwei Song wrote: > Hi Bruce, > > Could you help merge these two patches to below branches? > Revert them is because SDK already have better fix, and > is already applied to linux-yocto. > > v5.15/standard/intel-sdk-5.15/intel-socfpga > v5.15/standard/preempt-rt/intel-sdk-5.15/intel-socfpga merged. Bruce > > Thanks, > Liwei. > > Liwei Song (2): > Revert "firmware: stratix10-svc: release mutex sdm_lock after > processing command" > Revert "intel: fcs: release mutex lock in failing path" > > drivers/crypto/intel_fcs_main.c | 4 +--- > drivers/firmware/stratix10-svc.c | 2 -- > 2 files changed, 1 insertion(+), 5 deletions(-) > > -- > 2.40.0 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13778): https://lists.yoctoproject.org/g/linux-yocto/message/13778 Mute This Topic: https://lists.yoctoproject.org/mt/105302921/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][linux-yocto v6.1] update socfpga to SDK version socfpga-6.1.55-lts
In message: [linux-yocto][linux-yocto v6.1] update socfpga to SDK version socfpga-6.1.55-lts on 03/04/2024 Liwei Song wrote: > Hi Bruce, > > This pull is uesed to update socfpga to SDK version socfpga-6.1.55-lts, > Could you help merge these patches to below branches: > > v6.1/standard/intel-sdk-6.1/intel-socfpga > v6.1/standard/preempt-rt/intel-sdk-6.1/intel-socfpga Done! Bruce > > Thanks, > Liwei. > > > The following changes since commit db7fc7d08272a50cbae490c0bd6e890dbd23c45c: > > Merge branch 'v6.1/standard/base' into > v6.1/standard/intel-sdk-6.1/intel-socfpga (2024-03-28 13:29:29 -0400) > > are available in the Git repository at: > > https://github.com/2005songliwei/linux-yocto-pull.git pull-socfpga-240304 > > for you to fetch changes up to 02cda76a83f2a3e30f77e039e3ce63d57090a16f: > > arm64: dts: socfpga_agilex.dtsi: remove disable status from fcs for Agilex > board (2024-04-03 10:10:53 +0800) > > > Adrian Ng Ho Yin (20): > HSD #15013623051: crypto: intel_fcs: Fix Unused Variable Issue > HSD #15013665788: hwmon: fix integer overflow > HSD #18030428333:dts: Update USB31 max speed > HSD #15013743257:dts: Update USB31 to comply to dt bindings > HSD #15013743257: dt-bindings: usb: add binding for Intel agilex5 > controller > HSD #15013743257:dt-bindings: usb:rename agilex5 dwc3 binding > HSD #18031811919: arm64: dts: Add otg-rev property > HSD #14015549956: dt-bindings: mmc: sdhci: Add Intel Agilex5 compatible > string > HSD #14015549956: mmc: sdhci-cadence: Add compatible string and quirk > for Agilex5 > HSD #14015549956: mmc: sdhci: Add 40-bit DMA mask quirk > HSD #14015549956 dt-bindings: usb: snps,dwc3: Add > 'snps,dma_set_40_bit_mask_quirk' quirk > HSD #14015549956: USB: dwc3: Add 40 bit dma bit-mask quirk > HSD #14015549956: dt-bindings: dma:dw-axi-dmac: Add 40bits dma bit-mask > quirk > HSD #14015549956: dmaengine: dw-axi-dmac: Add dma-40-bit-mask quirk to > support SMMU on Agilex5 > HSD #14015549956: arm64: dts: agilex5: Add SMMU node > HSD #14015549956: arm64: dts: agilex5: Add SMMU node and quirks for > peripherals to support SMMU > HSD #18031811979: usb: dwc2: Add handling for SetFeature b_hnp_enable > HSD#15014517890: firmware: stratix10-svc: Fix segmentation fault during > rmmod operation > HSD#14015549956: firmware: stratix10-svc: Enable usage of SMMU for SVC > driver > HSD#15014543910: firmware:stratix10-svc: Fix Coverity warnings > > Ang Tien Sung (1): > HSD #15014165241: fpga: altera-cvp: agilex5 support > > Austin Zhang (4): > Revert "HSD #18022323310: spi: cadence-quadspi: Disable irqs during > indirect reads" > HSD #14018622405: crypto: intel_fcs: Add notification of HWRNG support > on Agilex devices > HSD #22017943621: crypto: intel_fcs: Add matched mutex release > HSD #15014339624: crypto: intel_fcs: Matched missed mutex release and > resource release > > Boon Khai Ng (1): > HSD #15014196997: arm64: dts: Add xgmac support for Agilex5. > > Dinh Nguyen (6): > HSD #15013542017: fix build for intel_fpga_qse_ll_main > HSD #14018622405-1: add "intel,n5x-soc-fcs" dts binding for N5X > HSD #14018622405-2: add platform specific data for different platforms > HSD 14019646348-1: add the correct dts binding for Stratix10 FCS > HSD 14019646348-2: add error checking when getting "platform" > HSD 14019646348-3: add the proper cleanup for errors during probe > > Durga Surya Rajesh Aki (2): > HSD #15013287484 crypto:intel_fcs: Register the HWRNG device after SMMU > is initialized. > HSD-15012124940: Enhanced return codes of > INTEL_FCS_DEV_SEND_CERTIFICATE to differentiate between non-provisioned > device and authentication fail > > G Thomas, Rohan (3): > HSD #16020791023: net: stmmac: Set MII_XGMAC_C22P_MASK bitmask end bit > position as 31 > HSD #16020988342: net: stmmac: xgmac: Add FPE link partner hand-shaking > support > HSD #16020988342: net: stmmac: xgmac: Configure FPE preempt settings > > Joyce Ooi (1): > HSD#1509832443: net: eth: altera: fix build errors for QSE drivers > > Kah Jing Lee (6): > HSD #15013345463: arch: arm64: dts: Added the rsu-handle for Uboot to > retrieve qspi_boot > HSD #15013667680: drivers: firmware: stratix10-rsu: Fix max_retry > counter value > HSD# 18022969776: firmware: stratix10-rsu: prevent io block when > sending RSU messages > HSD #16019264140: mmc: sdhci-cadence: agilex5: Remove the debug log > HSD#14017166971: arch: arm64: boot: dts: agilex5: Updated QSPI Flash > layout for UBIFS > HSD #14020037621: arm64: dts: n5x: Add missing rsu-handle for N5X > > LCSwee (5): > HSD #15013478346: arm: configs: enable clocksource for a10 (#73) > HSD #15013478346: arch: arm:
Re: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/1] nxp-imx9: Enable Arm ETHOS NPU
merged. Bruce In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/1] nxp-imx9: Enable Arm ETHOS NPU on 03/04/2024 Xiaolei Wang wrote: > Enable Arm ETHOS NPU. > > Signed-off-by: Xiaolei Wang > --- > bsp/nxp-imx9/nxp-imx9.cfg | 5 + > 1 file changed, 5 insertions(+) > > diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg > index 8ad37abb..8654f93c 100644 > --- a/bsp/nxp-imx9/nxp-imx9.cfg > +++ b/bsp/nxp-imx9/nxp-imx9.cfg > @@ -284,6 +284,11 @@ CONFIG_DRM_ITE_IT6263=y > # > CONFIG_MXC_GPU_VIV=y > > +# > +# Arm Ethos-U NPU > +# > +CONFIG_ETHOSU=y > + > # > # I2C encoder or helper chips > # > -- > 2.25.1 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13776): https://lists.yoctoproject.org/g/linux-yocto/message/13776 Mute This Topic: https://lists.yoctoproject.org/mt/105302004/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [yocto-kernel-cache yocto-6.1][PATCH] Revert "features/nf_tables: nft_objref is now builtin"
merged. Bruce In message: [linux-yocto] [yocto-kernel-cache yocto-6.1][PATCH] Revert "features/nf_tables: nft_objref is now builtin" on 02/04/2024 Lyu, William via lists.yoctoproject.org wrote: > From: William Lyu > > This reverts commit dbe1767f364cdbf7dcc75433635678bd39c71e1f. > > The reverted commit removes kernel configuration CONFIG_NFT_OBJREF which > became builtin starting from kernel v6.2 [1]. However, this kernel > configuration is still available in kernel v6.1. So, this kernel > configuration option should NOT be removed from "yocto-kernel-cache" on > branch "yocto-6.1". > > References > [1] > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d037abc2414b4539401e0e6aa278bedc4628ad69 > > Signed-off-by: William Lyu > --- > features/nf_tables/nf_tables.cfg | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/features/nf_tables/nf_tables.cfg > b/features/nf_tables/nf_tables.cfg > index 5b0f28df..4debc628 100644 > --- a/features/nf_tables/nf_tables.cfg > +++ b/features/nf_tables/nf_tables.cfg > @@ -11,6 +11,7 @@ CONFIG_NFT_LIMIT=m > CONFIG_NFT_CONNLIMIT=m > CONFIG_NFT_TUNNEL=m > CONFIG_NFT_NAT=m > +CONFIG_NFT_OBJREF=m > CONFIG_NFT_QUEUE=m > CONFIG_NFT_REJECT=m > CONFIG_NFT_REJECT_INET=m > -- > 2.43.0 > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13775): https://lists.yoctoproject.org/g/linux-yocto/message/13775 Mute This Topic: https://lists.yoctoproject.org/mt/105291813/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [yocto-kernel-cache yocto-6.4][PATCH 1/2] features/nf_tables: nft_objref is now builtin
merged. Bruce In message: [linux-yocto] [yocto-kernel-cache yocto-6.4][PATCH 1/2] features/nf_tables: nft_objref is now builtin on 02/04/2024 Lyu, William via lists.yoctoproject.org wrote: > From: William Lyu > > Backported from commit on branch "yocto-6.6": > 40ecdcc5e4f5053536cec6e3f74334aa418f07cc > > Starting from kernel v6.2 (including all rc versions), > CONFIG_NFT_OBJREF has become builtin and cannot be disabled [1]. So, > this configure option is removed from nf_tables.cfg. > > References > [1] > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d037abc2414b4539401e0e6aa278bedc4628ad69 > > Signed-off-by: William Lyu > --- > features/nf_tables/nf_tables.cfg | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/features/nf_tables/nf_tables.cfg > b/features/nf_tables/nf_tables.cfg > index 4debc628..5b0f28df 100644 > --- a/features/nf_tables/nf_tables.cfg > +++ b/features/nf_tables/nf_tables.cfg > @@ -11,7 +11,6 @@ CONFIG_NFT_LIMIT=m > CONFIG_NFT_CONNLIMIT=m > CONFIG_NFT_TUNNEL=m > CONFIG_NFT_NAT=m > -CONFIG_NFT_OBJREF=m > CONFIG_NFT_QUEUE=m > CONFIG_NFT_REJECT=m > CONFIG_NFT_REJECT_INET=m > -- > 2.43.0 > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13774): https://lists.yoctoproject.org/g/linux-yocto/message/13774 Mute This Topic: https://lists.yoctoproject.org/mt/105350943/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [yocto-kernel-cache yocto-6.5][PATCH 1/2] features/nf_tables: nft_objref is now builtin
merged. Bruce In message: [linux-yocto] [yocto-kernel-cache yocto-6.5][PATCH 1/2] features/nf_tables: nft_objref is now builtin on 02/04/2024 Lyu, William via lists.yoctoproject.org wrote: > From: William Lyu > > Backported from commit on branch "yocto-6.6": > 40ecdcc5e4f5053536cec6e3f74334aa418f07cc > > Starting from kernel v6.2 (including all rc versions), > CONFIG_NFT_OBJREF has become builtin and cannot be disabled [1]. So, > this configure option is removed from nf_tables.cfg. > > References > [1] > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d037abc2414b4539401e0e6aa278bedc4628ad69 > > Signed-off-by: William Lyu > --- > features/nf_tables/nf_tables.cfg | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/features/nf_tables/nf_tables.cfg > b/features/nf_tables/nf_tables.cfg > index 4debc628..5b0f28df 100644 > --- a/features/nf_tables/nf_tables.cfg > +++ b/features/nf_tables/nf_tables.cfg > @@ -11,7 +11,6 @@ CONFIG_NFT_LIMIT=m > CONFIG_NFT_CONNLIMIT=m > CONFIG_NFT_TUNNEL=m > CONFIG_NFT_NAT=m > -CONFIG_NFT_OBJREF=m > CONFIG_NFT_QUEUE=m > CONFIG_NFT_REJECT=m > CONFIG_NFT_REJECT_INET=m > -- > 2.43.0 > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13773): https://lists.yoctoproject.org/g/linux-yocto/message/13773 Mute This Topic: https://lists.yoctoproject.org/mt/105350876/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] Merge v6.1.83 into v6.1/standard/cn-sdkv6.1/octeon branch
fix ALC285 issues on HP Envy x360 laptops
>
> Attila Tőkés (1):
> ASoC: amd: yc: Fix non-functional mic on Lenovo 82UU
>
> Baochen Qiang (1):
> wifi: ath11k: initialize rx_mcs_80 and rx_mcs_160 before use
>
> Baokun Li (1):
> quota: simplify drop_dquot_ref()
>
> Bart Van Assche (1):
> fs: Fix rw_hint validation
>
> Bartosz Golaszewski (1):
> Bluetooth: hci_qca: don't use IS_ERR_OR_NULL() with gpiod_get_optional()
>
> Baruch Siach (1):
> mtd: maps: physmap-core: fix flash size larger than 32-bit
>
> Basavaraj Natikar (2):
> HID: amd_sfh: Update HPD sensor structure elements
> HID: amd_sfh: Avoid disabling the interrupt
>
> Ben Wolsieffer (1):
> watchdog: stm32_iwdg: initialize default timeout
>
> Bert Karwatzki (1):
> iommu: Fix compilation without CONFIG_IOMMU_INTEL
>
> Bitterblue Smith (2):
> wifi: rtw88: 8821c: Fix beacon loss and disconnect
> wifi: rtw88: 8821c: Fix false alarm count
>
> Bjorn Andersson (1):
> pmdomain: qcom: rpmhpd: Drop SA8540P gfx.lvl
>
> Breno Leitao (1):
> net: blackhole_dev: fix build warning for ethh set but not used
>
> Bruce Ashfield (1):
> Merge tag 'v6.1.83' into v6.1/standard/base
>
> Bryan O'Donoghue (1):
> clk: Fix clk_core_get NULL dereference
>
> Cai Huoqing (1):
> drm/tegra: dsi: Make use of the helper function dev_err_probe()
>
> Changbin Du (1):
> modules: wait do_free_init correctly
>
> Chao Yu (13):
> f2fs: reduce stack memory cost by using bitfield in struct f2fs_io_info
> f2fs: compress: fix to guarantee persisting compressed blocks by CP
> f2fs: compress: fix to cover normal cluster write with cp_rwsem
> f2fs: delete obsolete FI_FIRST_BLOCK_WRITTEN
> f2fs: delete obsolete FI_DROP_CACHE
> f2fs: introduce get_dnode_addr() to clean up codes
> f2fs: update blkaddr in __set_data_blkaddr() for cleanup
> f2fs: compress: fix to avoid inconsistence bewteen i_blocks and dnode
> f2fs: compress: fix to cover f2fs_disable_compressed_file() w/ i_sem
> f2fs: fix to avoid potential panic during recovery
> f2fs: compress: fix to check zstd compress level correctly in mount
> option
> f2fs: compress: fix to check compress flag w/ .i_sem lock
> f2fs: ro: compress: fix to avoid caching unaligned extent
>
> Chen Ni (2):
> sr9800: Add check for usbnet_get_endpoints
> drm/tegra: dsi: Add missing check for of_find_device_by_node
>
> Chen-Yu Tsai (3):
> arm64: dts: allwinner: h6: Add RX DMA channel for SPDIF
> pinctrl: mediatek: Drop bogus slew rate register range for MT8186
> pinctrl: mediatek: Drop bogus slew rate register range for MT8192
>
> Christoph Hellwig (3):
> f2fs: simplify __allocate_data_block
> nvme: only set reserved_tags in nvme_alloc_io_tag_set for fabrics
> controllers
> nvme: add the Apple shared tag workaround to nvme_alloc_io_tag_set
>
> Christophe JAILLET (12):
> mmc: wmt-sdmmc: remove an incorrect release_mem_region() call in the
> .remove function
> drm/tegra: dsi: Fix some error handling paths in tegra_dsi_probe()
> drm/tegra: dsi: Fix missing pm_runtime_disable() in the error handling
> path of tegra_dsi_probe()
> drm/tegra: hdmi: Fix some error handling paths in tegra_hdmi_probe()
> drm/tegra: rgb: Fix some error handling paths in tegra_dc_rgb_probe()
> drm/tegra: rgb: Fix missing clk_put() in the error handling paths of
> tegra_dc_rgb_probe()
> drm/tegra: output: Fix missing i2c_put_adapter() in the error handling
> paths of tegra_output_probe()
> PCI: switchtec: Fix an error handling path in switchtec_pci_probe()
> clk: hisilicon: hi3519: Release the correct number of gates in
> hi3519_clk_unregister()
> clk: hisilicon: hi3559a: Fix an erroneous devm_kfree()
> net: sunrpc: Fix an off by one in rpc_sockaddr2uaddr()
> NFS: Fix an off by one in root_nfs_cat()
>
> Christophe Leroy (1):
> powerpc: Force inlining of arch_vmap_p{u/m}d_supported()
>
> Chuck Lever (2):
> NFSD: Convert filecache to rhltable
> NFSD: Add an nfsd4_encode_nfstime4() helper
>
> Chun-Yi Lee (1):
> aoe: fix the potential use-after-free problem in aoecmd_cfg_pkts
>
> Chunguang Xu (1):
> nvme: fix reconnection fail due to reserved tag allocation
>
> Colin Ian King (1):
> usb: gadget: net2272: Use irqflags in the call to net2272_probe_fin
>
> Conor Dooley (1):
> riscv: dts: sifive: add missing #interrupt-cells to pmic
>
> Craig Tatlor (1):
> ARM: dts: qcom: msm89
Re: [linux-yocto] Merge v6.1.83 into v6.1/standard/preempt-rt/cn-sdkv6.1/octeon branch
iansyah (1):
> ALSA: hda/realtek: fix ALC285 issues on HP Envy x360 laptops
>
> Attila Tőkés (1):
> ASoC: amd: yc: Fix non-functional mic on Lenovo 82UU
>
> Baochen Qiang (1):
> wifi: ath11k: initialize rx_mcs_80 and rx_mcs_160 before use
>
> Baokun Li (1):
> quota: simplify drop_dquot_ref()
>
> Bart Van Assche (1):
> fs: Fix rw_hint validation
>
> Bartosz Golaszewski (1):
> Bluetooth: hci_qca: don't use IS_ERR_OR_NULL() with gpiod_get_optional()
>
> Baruch Siach (1):
> mtd: maps: physmap-core: fix flash size larger than 32-bit
>
> Basavaraj Natikar (2):
> HID: amd_sfh: Update HPD sensor structure elements
> HID: amd_sfh: Avoid disabling the interrupt
>
> Ben Wolsieffer (1):
> watchdog: stm32_iwdg: initialize default timeout
>
> Bert Karwatzki (1):
> iommu: Fix compilation without CONFIG_IOMMU_INTEL
>
> Bitterblue Smith (2):
> wifi: rtw88: 8821c: Fix beacon loss and disconnect
> wifi: rtw88: 8821c: Fix false alarm count
>
> Bjorn Andersson (1):
> pmdomain: qcom: rpmhpd: Drop SA8540P gfx.lvl
>
> Breno Leitao (1):
> net: blackhole_dev: fix build warning for ethh set but not used
>
> Bruce Ashfield (1):
> Merge tag 'v6.1.83' into v6.1/standard/base
>
> Bryan O'Donoghue (1):
> clk: Fix clk_core_get NULL dereference
>
> Cai Huoqing (1):
> drm/tegra: dsi: Make use of the helper function dev_err_probe()
>
> Changbin Du (1):
> modules: wait do_free_init correctly
>
> Chao Yu (13):
> f2fs: reduce stack memory cost by using bitfield in struct f2fs_io_info
> f2fs: compress: fix to guarantee persisting compressed blocks by CP
> f2fs: compress: fix to cover normal cluster write with cp_rwsem
> f2fs: delete obsolete FI_FIRST_BLOCK_WRITTEN
> f2fs: delete obsolete FI_DROP_CACHE
> f2fs: introduce get_dnode_addr() to clean up codes
> f2fs: update blkaddr in __set_data_blkaddr() for cleanup
> f2fs: compress: fix to avoid inconsistence bewteen i_blocks and dnode
> f2fs: compress: fix to cover f2fs_disable_compressed_file() w/ i_sem
> f2fs: fix to avoid potential panic during recovery
> f2fs: compress: fix to check zstd compress level correctly in mount
> option
> f2fs: compress: fix to check compress flag w/ .i_sem lock
> f2fs: ro: compress: fix to avoid caching unaligned extent
>
> Chen Ni (2):
> sr9800: Add check for usbnet_get_endpoints
> drm/tegra: dsi: Add missing check for of_find_device_by_node
>
> Chen-Yu Tsai (3):
> arm64: dts: allwinner: h6: Add RX DMA channel for SPDIF
> pinctrl: mediatek: Drop bogus slew rate register range for MT8186
> pinctrl: mediatek: Drop bogus slew rate register range for MT8192
>
> Christoph Hellwig (3):
> f2fs: simplify __allocate_data_block
> nvme: only set reserved_tags in nvme_alloc_io_tag_set for fabrics
> controllers
> nvme: add the Apple shared tag workaround to nvme_alloc_io_tag_set
>
> Christophe JAILLET (12):
> mmc: wmt-sdmmc: remove an incorrect release_mem_region() call in the
> .remove function
> drm/tegra: dsi: Fix some error handling paths in tegra_dsi_probe()
> drm/tegra: dsi: Fix missing pm_runtime_disable() in the error handling
> path of tegra_dsi_probe()
> drm/tegra: hdmi: Fix some error handling paths in tegra_hdmi_probe()
> drm/tegra: rgb: Fix some error handling paths in tegra_dc_rgb_probe()
> drm/tegra: rgb: Fix missing clk_put() in the error handling paths of
> tegra_dc_rgb_probe()
> drm/tegra: output: Fix missing i2c_put_adapter() in the error handling
> paths of tegra_output_probe()
> PCI: switchtec: Fix an error handling path in switchtec_pci_probe()
> clk: hisilicon: hi3519: Release the correct number of gates in
> hi3519_clk_unregister()
> clk: hisilicon: hi3559a: Fix an erroneous devm_kfree()
> net: sunrpc: Fix an off by one in rpc_sockaddr2uaddr()
> NFS: Fix an off by one in root_nfs_cat()
>
> Christophe Leroy (1):
> powerpc: Force inlining of arch_vmap_p{u/m}d_supported()
>
> Chuck Lever (2):
> NFSD: Convert filecache to rhltable
> NFSD: Add an nfsd4_encode_nfstime4() helper
>
> Chun-Yi Lee (1):
> aoe: fix the potential use-after-free problem in aoecmd_cfg_pkts
>
> Chunguang Xu (1):
> nvme: fix reconnection fail due to reserved tag allocation
>
> Colin Ian King (1):
> usb: gadget: net2272: Use irqflags in the call to net2272_probe_fin
>
> Conor Dooley (1):
> riscv: dts: sifive: add missing #interrupt-cells to pmic
>
> C
Re: [linux-yocto] Trial merge of v5.15.153 v6.1.83 for linux-yocto
In message: Trial merge of v5.15.153 v6.1.83 for linux-yocto on 27/03/2024 Kevin Hao wrote: > Hi Bruce, > > This is a trial merge of the stable kernel v5.15.153 v6.1.83 for the > following branches in the linux-yocto. > 205fb9414e6e v5.15/standard/sdkv5.10/axxia > 979be40c2ae5 v5.15/standard/preempt-rt/sdkv5.10/axxia > 74734259970f v5.15/standard/base > bb72fca17f4f v5.15/standard/preempt-rt/base > a9974f629f77 v5.15/standard/cn-sdkv5.4/octeon > 035c7daab2b7 v5.15/standard/preempt-rt/cn-sdkv5.4/octeon > b74aa0a8024d v5.15/standard/cn-sdkv5.15/octeon > 74297e0728f6 v5.15/standard/preempt-rt/cn-sdkv5.15/octeon > 29b806be96ce v5.15/standard/ti-sdk-5.10/ti-j72xx > f01334cdb2af v5.15/standard/preempt-rt/ti-sdk-5.10/ti-j72xx > 9e053973d336 v5.15/standard/nxp-sdk-5.15/nxp-soc > 4a93d86880fd v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-soc > e03d5d89e932 v5.15/standard/bcm-2xxx-rpi > b37087646460 v5.15/standard/preempt-rt/bcm-2xxx-rpi > ab3c32d818b9 v5.15/standard/nxp-sdk-5.15/nxp-s32g > edc5f2992f04 v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g > a36ecee67619 v5.15/standard/intel-sdk-5.15/intel-socfpga > eda03308ec1b v5.15/standard/preempt-rt/intel-sdk-5.15/intel-socfpga > e4660c0705bd v5.15/standard/x86 > 4580de5a9dda v5.15/standard/preempt-rt/x86 > ea5b0ec91334 v5.15/standard/sdkv5.15/xlnx-soc > 61f2756657c7 v5.15/standard/preempt-rt/sdkv5.15/xlnx-soc > 2510a62351e0 v6.1/standard/sdkv5.10/axxia > 78197ec0c0cd v6.1/standard/preempt-rt/sdkv5.10/axxia > d32dd2590616 v6.1/standard/base > 2890500e8e88 v6.1/standard/preempt-rt/base > 1c83c7f6dfd4 v6.1/standard/ti-sdk-6.1/ti-j7xxx >#Have textual and semantic conflicts > 546a458e9c00 v6.1/standard/preempt-rt/ti-sdk-6.1/ti-j7xxx >#Have textual and semantic conflicts > 0007023c27e7 v6.1/standard/nxp-sdk-6.1/nxp-soc > c94ce1a29154 v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc > 24dd25d562cc v6.1/standard/cn-sdkv5.15/octeon >#Have textual and semantic conflicts > 953e77082395 v6.1/standard/preempt-rt/cn-sdkv5.15/octeon >#Have textual and semantic conflicts > f4affd3d699a v6.1/standard/microchip-polarfire-soc > d36420705bfe v6.1/standard/preempt-rt/microchip-polarfire-soc > 2402072fe574 v6.1/standard/bcm-2xxx-rpi > 8cbeb6bb9bd3 v6.1/standard/preempt-rt/bcm-2xxx-rpi > d920a160b2cd v6.1/standard/nxp-sdk-5.15/nxp-s32g > ed009ed30a24 v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g > ee963980bc2a v6.1/standard/intel-sdk-6.1/intel-socfpga > 40d48601784d v6.1/standard/preempt-rt/intel-sdk-6.1/intel-socfpga > 3361bb9de599 v6.1/standard/x86 > 83245bce963e v6.1/standard/preempt-rt/x86 > 7cab8e94e5a9 v6.1/standard/sdkv6.1/xlnx-soc > 38579581e000 v6.1/standard/preempt-rt/sdkv6.1/xlnx-soc > > I am surprised that there are no merge conflicts on v5.15 branches, despite > having over > 300 patches in v5.15.153. All the merge conflicts come from v6.1.83. > > - The merge conflict on j7xx looks trivial, but we should note that there is > semantic > conflict here. We need to adjust the change in stable according to the change > in the SDK. > > - The merge conflicts on octeon branch are quite ugly, part of the reason is > that we > moved the resctrl from arch/x86/kernel/cpu to fs/, and another part is the > significant > changes to the octeontx2 Ethernet driver caused by v6.1.83. Thanks Kevin, I had a few challenges during the merge, but I did end up doing a force merge of your resolution to ensure that the octone branches match (at least that is what my git diff is telling me) I did just create add a new BSP, and it has issues: v6.1/standard/cn-sdkv6.1/octeon v6.1/standard/preempt-rt/cn-sdkv6.1/octeon For now, I've excluded them from the update, so they'll need to be resolved and sent separately. Bruce > > All the branches have passed my build test. I have pushed all these branches > to: > https://github.com/haokexin/linux > > You can use this as a reference for the linux-yocto stable kernel bump. > > Thanks, > Kevin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13756): https://lists.yoctoproject.org/g/linux-yocto/message/13756 Mute This Topic: https://lists.yoctoproject.org/mt/105175729/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [linux-yocto v6.1] nxp-soc: Fix two build warnings
In message: [linux-yocto v6.1] nxp-soc: Fix two build warnings
on 27/03/2024 Kevin Hao wrote:
> From: Kevin Hao
>
> Hi Bruce,
>
> This patch series fixes two build warnings introduced by SDK commit
> 20932f1f83d3 ("fec_ecat: add fec native driver for raw packet proto").
>
> Please help me merge them onto the following two branches:
> v6.1/standard/nxp-sdk-6.1/nxp-soc
> v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc
merged.
Bruce
>
> Kevin Hao (2):
> af_packet: Delete the unused variable 'sk'
> net: Delete the unused variable in __sys_recvfrom()
>
> net/packet/af_packet.c | 2 --
> net/socket.c | 2 +-
> 2 files changed, 1 insertion(+), 3 deletions(-)
>
> --
> 2.44.0
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13755):
https://lists.yoctoproject.org/g/linux-yocto/message/13755
Mute This Topic: https://lists.yoctoproject.org/mt/105175660/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [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] fec_ecat: Fix build warning in fec_ecat.c
merged.
Bruce
In message: [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] fec_ecat: Fix build
warning in fec_ecat.c
on 28/03/2024 Xiaolei Wang wrote:
> commit ("fec_ecat: add fec native driver for raw packet prot"),
> introduced many warnings, which comes from the SDK, Since too
> many warnings are introduced by this file, this patch fixes all
> warnings.
>
> Signed-off-by: Xiaolei Wang
> ---
> drivers/net/ethernet/freescale/fec_ecat.c | 131 ++
> 1 file changed, 7 insertions(+), 124 deletions(-)
>
> diff --git a/drivers/net/ethernet/freescale/fec_ecat.c
> b/drivers/net/ethernet/freescale/fec_ecat.c
> index 86eb3341105b..06e0b22e710d 100644
> --- a/drivers/net/ethernet/freescale/fec_ecat.c
> +++ b/drivers/net/ethernet/freescale/fec_ecat.c
> @@ -316,15 +316,6 @@ static int fec_enet_get_bd_index(struct bufdesc *bdp,
> return ((const char *)bdp - (const char *)bd->base) >> bd->dsize_log2;
> }
>
> -static void swap_buffer(void *bufaddr, int len)
> -{
> - int i;
> - unsigned int *buf = bufaddr;
> -
> - for (i = 0; i < len; i += 4, buf++)
> - swab32s(buf);
> -}
> -
> static void swap_buffer2(void *dst_buf, void *src_buf, int len)
> {
> int i;
> @@ -383,7 +374,8 @@ static int fec_ecat_txq_submit_buff(struct
> fec_enet_priv_tx_q *txq,
> skb = txq->tx_skbuff[index];
> bufaddr = skb->data;
> buflen = len;
> - copy_from_user(skb->data, buff, len);
> + if(copy_from_user(skb->data, buff, len))
> + return -EFAULT;
> bdp->cbd_datlen = cpu_to_fec16(buflen);
> /* Push the data cache so the CPM does not get stale memory data. */
> dma_sync_single_for_device(>pdev->dev,
> @@ -424,7 +416,6 @@ static void fec_ecat_tx_queue(struct net_device *ndev)
> struct bufdesc *bdp;
> unsigned short status;
> struct fec_enet_priv_tx_q *txq = fep->tx_queue;
> - int index = 0;
>
> /* get next bdp of dirty_tx */
> bdp = txq->dirty_tx;
> @@ -487,7 +478,6 @@ static void fec_enet_bd_init(struct net_device *dev)
> struct fec_enet_priv_rx_q *rxq = fep->rx_queue;
> struct bufdesc *bdp;
> int i;
> - struct sk_buff *skb;
>
> /* Initialize the receive buffer descriptors. */
> bdp = rxq->bd.base;
> @@ -713,44 +703,6 @@ static int fec_enet_ipc_handle_init(struct
> fec_enet_private *fep)
> return imx_scu_get_handle(>ipc_handle);
> }
>
> -static void fec_enet_ipg_stop_set(struct fec_enet_private *fep, bool enabled)
> -{
> - struct device_node *np = fep->pdev->dev.of_node;
> - u32 rsrc_id, val;
> - int idx;
> -
> - if (!np || !fep->ipc_handle)
> - return;
> -
> - idx = of_alias_get_id(np, "ethernet");
> - if (idx < 0)
> - idx = 0;
> - rsrc_id = idx ? IMX_SC_R_ENET_1 : IMX_SC_R_ENET_0;
> -
> - val = enabled ? 1 : 0;
> - imx_sc_misc_set_control(fep->ipc_handle, rsrc_id, IMX_SC_C_IPG_STOP,
> val);
> -}
> -
> -static void fec_enet_stop_mode(struct fec_enet_private *fep, bool enabled)
> -{
> - struct fec_platform_data *pdata = fep->pdev->dev.platform_data;
> - struct fec_stop_mode_gpr *stop_gpr = >stop_gpr;
> -
> - if (stop_gpr->gpr) {
> - if (enabled)
> - regmap_update_bits(stop_gpr->gpr, stop_gpr->reg,
> -BIT(stop_gpr->bit),
> -BIT(stop_gpr->bit));
> - else
> - regmap_update_bits(stop_gpr->gpr, stop_gpr->reg,
> -BIT(stop_gpr->bit), 0);
> - } else if (pdata && pdata->sleep_mode_enable) {
> - pdata->sleep_mode_enable(enabled);
> - } else {
> - fec_enet_ipg_stop_set(fep, enabled);
> - }
> -}
> -
> static inline void fec_irqs_disable(struct net_device *ndev)
> {
> struct fec_enet_private *fep = netdev_priv(ndev);
> @@ -762,7 +714,6 @@ static void
> fec_stop(struct net_device *ndev)
> {
> struct fec_enet_private *fep = netdev_priv(ndev);
> - u32 rmii_mode = readl(fep->hwp + FEC_R_CNTRL) & (1 << 8);
>
> /* We cannot expect a graceful transmit stop without link !!! */
> if (fep->link) {
> @@ -821,7 +772,6 @@ static int fec_ecat_recv_from_queue(struct net_device
> *ndev, void __user *buff,
> int recv_len = 0;
> int index = 0;
> boolneed_swap = fep->quirks & FEC_QUIRK_SWAP_FRAME;
> - int ret = 0;
>
> #ifdef CONFIG_M532x
> flush_cache_all();
> @@ -885,7 +835,8 @@ static int fec_ecat_recv_from_queue(struct net_device
> *ndev, void __user *buff,
> if (data[12] ==0x88 && data[13] ==0xa4) {
> len = len < pkt_len? len : pkt_len;
> if (!need_swap) {
> - copy_to_user(buff, data, len);
> + if(copy_to_user(buff, data, len))
Re: [linux-yocto] [kernel-cache][PATCH 1/3] bsp/genericarm64: enable support for Xilinx KV260
merged. SRCREV bumps will follow shortly. Bruce In message: [linux-yocto] [kernel-cache][PATCH 1/3] bsp/genericarm64: enable support for Xilinx KV260 on 27/03/2024 Ross Burton wrote: > From: Ross Burton > > Add more config options so that the Xilinx KV260 is fully supported. > > This work was done by Bill Mills , I simply > integrated it. > > Signed-off-by: Ross Burton > --- > bsp/genericarm64/genericarm64-gpio.cfg | 13 +- > bsp/genericarm64/genericarm64-i2c.cfg | 6 +- > bsp/genericarm64/genericarm64.cfg | 161 - > 3 files changed, 170 insertions(+), 10 deletions(-) > > diff --git a/bsp/genericarm64/genericarm64-gpio.cfg > b/bsp/genericarm64/genericarm64-gpio.cfg > index b7a94890..126b193f 100644 > --- a/bsp/genericarm64/genericarm64-gpio.cfg > +++ b/bsp/genericarm64/genericarm64-gpio.cfg > @@ -1,6 +1,9 @@ > +# GPIO Support > # Memory mapped GPIO drivers > # Altera GPIO > CONFIG_GPIO_ALTERA=m > +# Cadence GPIO support > +CONFIG_GPIO_CADENCE=m > # TI Davinci/Keystone GPIO support > CONFIG_GPIO_DAVINCI=m > # Synopsys DesignWare APB GPIO driver > @@ -17,6 +20,8 @@ CONFIG_GPIO_PL061=m > CONFIG_GPIO_RCAR=m > # GPIO based on SYSCON > CONFIG_GPIO_SYSCON=m > +# Cavium ThunderX/OCTEON-TX GPIO > +CONFIG_GPIO_THUNDERX=m > # UniPhier GPIO support > CONFIG_GPIO_UNIPHIER=m > # Toshiba Visconti GPIO support > @@ -25,6 +30,10 @@ CONFIG_GPIO_VISCONTI=m > CONFIG_GPIO_XGENE=y > # APM X-Gene GPIO standby controller support > CONFIG_GPIO_XGENE_SB=m > +# Xilinx GPIO support > +CONFIG_GPIO_XILINX=m > +# Xilinx Zynq GPIO support > +CONFIG_GPIO_ZYNQ=m > > # I2C GPIO expanders > # MAX7319, MAX7320-7327 I2C Port Expanders > @@ -41,5 +50,5 @@ CONFIG_GPIO_BD9571MWV=m > CONFIG_GPIO_MAX77620=m > # Kontron sl28cpld GPIO support > CONFIG_GPIO_SL28CPLD=m > -# Cavium ThunderX/OCTEON-TX GPIO > -CONFIG_GPIO_THUNDERX=m > +# TI TPS65086 GPO > +CONFIG_GPIO_TPS65086=m > diff --git a/bsp/genericarm64/genericarm64-i2c.cfg > b/bsp/genericarm64/genericarm64-i2c.cfg > index 6294579c..46777402 100644 > --- a/bsp/genericarm64/genericarm64-i2c.cfg > +++ b/bsp/genericarm64/genericarm64-i2c.cfg > @@ -53,9 +53,11 @@ CONFIG_I2C_S3C2410=m > CONFIG_I2C_SH_MOBILE=m > # NVIDIA Tegra internal I2C controller > CONFIG_I2C_TEGRA=m > -# Cavium ThunderX I2C bus support > -CONFIG_I2C_THUNDERX=m > # UniPhier FIFO-builtin I2C controller > CONFIG_I2C_UNIPHIER_F=m > +# Cavium ThunderX I2C bus support > +CONFIG_I2C_THUNDERX=m > +# Xilinx I2C Controller > +CONFIG_I2C_XILINX=m > # Renesas R-Car I2C Controller > CONFIG_I2C_RCAR=m > diff --git a/bsp/genericarm64/genericarm64.cfg > b/bsp/genericarm64/genericarm64.cfg > index 773ba6db..9cda73c8 100644 > --- a/bsp/genericarm64/genericarm64.cfg > +++ b/bsp/genericarm64/genericarm64.cfg > @@ -87,15 +87,27 @@ CONFIG_QORIQ_CPUFREQ=m > # ACPI (Advanced Configuration and Power Interface) Support > CONFIG_ACPI=y > > +# Memory Management options > +# Contiguous Memory Allocator > +CONFIG_CMA=y > + > +# Networking support > +# CAN bus subsystem support > +CONFIG_CAN=m > + > # Device Drivers > # PCI support > # PCI controller drivers > -# Generic PCI host controller > -CONFIG_PCI_HOST_GENERIC=m > # Cavium Thunder PCIe controller to off-chip devices > CONFIG_PCI_HOST_THUNDER_PEM=y > # Cavium Thunder ECAM controller to on-chip devices on pass-1.x silicon > CONFIG_PCI_HOST_THUNDER_ECAM=y > +# Generic PCI host controller > +CONFIG_PCI_HOST_GENERIC=m > +# Xilinx AXI PCIe controller > +CONFIG_PCIE_XILINX=y > +# Xilinx NWL PCIe controller > +CONFIG_PCIE_XILINX_NWL=y > > # DesignWare-based PCIe controllers > # Freescale i.MX6/7/8 PCIe controller (host mode) > @@ -104,6 +116,9 @@ CONFIG_PCI_IMX6_HOST=y > CONFIG_PCI_LAYERSCAPE=y > > # Bus devices > + > +CONFIG_ARM_CCI=y > +CONFIG_ARM_CCI400_COMMON=y > # TI sysc interconnect target module driver > CONFIG_TI_SYSC=y > # QorIQ DPAA2 fsl-mc bus driver > @@ -123,6 +138,10 @@ CONFIG_IMX_SCU=y > CONFIG_IMX_SCU_PD=y > > # Memory Technology Device (MTD) support > +# RAM/ROM/Flash chip drivers > +# Detect flash chips by Common Flash Interface (CFI) probe > +CONFIG_MTD_CFI=m > + > # NAND > # Raw/Parallel NAND Device Support > CONFIG_MTD_RAW_NAND=y > @@ -159,22 +178,32 @@ CONFIG_SATA_AHCI_PLATFORM=m > > # Network device support > # Ethernet driver support > +# Cadence MACB/GEM support > +CONFIG_MACB=m > +# Use IEEE 1588 hwstamp > +CONFIG_MACB_USE_HWSTAMP=y > # FEC ethernet controller (of ColdFire and some i.MX CPUs) > CONFIG_FEC=m > # ENETC PF driver > CONFIG_FSL_ENETC=m > # ENETC VF driver > CONFIG_FSL_ENETC_VF=m > -# STMicroelectronics Multi-Gigabit Ethernet driver > -CONFIG_STMMAC_ETH=m > -# TI K3 AM654x/J721E CPSW Ethernet driver > -CONFIG_TI_K3_AM65_CPSW_NUSS=m > # Marvell OcteonTX2 RVU Admin Function driver > CONFIG_OCTEONTX2_AF=m > # Marvell OcteonTX2 NIC Physical Function driver > CONFIG_OCTEONTX2_PF=m > # Marvell OcteonTX2 NIC Virtual Function driver > CONFIG_OCTEONTX2_VF=m > +#
Re: [linux-yocto] [yocto-kernel-cache yocto-6.6][PATCH 1/2] features/nf_tables: nft_objref is now builtin
merged to 6.6 and master. Bruce In message: [linux-yocto] [yocto-kernel-cache yocto-6.6][PATCH 1/2] features/nf_tables: nft_objref is now builtin on 27/03/2024 Lyu, William via lists.yoctoproject.org wrote: > From: William Lyu > > Starting from kernel v6.2 (including all rc versions), > CONFIG_NFT_OBJREF has become builtin and cannot be disabled [1]. So, > this configure option is removed from nf_tables.cfg. > > References > [1] > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d037abc2414b4539401e0e6aa278bedc4628ad69 > > Signed-off-by: William Lyu > --- > features/nf_tables/nf_tables.cfg | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/features/nf_tables/nf_tables.cfg > b/features/nf_tables/nf_tables.cfg > index 4debc628..5b0f28df 100644 > --- a/features/nf_tables/nf_tables.cfg > +++ b/features/nf_tables/nf_tables.cfg > @@ -11,7 +11,6 @@ CONFIG_NFT_LIMIT=m > CONFIG_NFT_CONNLIMIT=m > CONFIG_NFT_TUNNEL=m > CONFIG_NFT_NAT=m > -CONFIG_NFT_OBJREF=m > CONFIG_NFT_QUEUE=m > CONFIG_NFT_REJECT=m > CONFIG_NFT_REJECT_INET=m > -- > 2.43.0 > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13752): https://lists.yoctoproject.org/g/linux-yocto/message/13752 Mute This Topic: https://lists.yoctoproject.org/mt/105198030/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [v2][linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] ti-am62: add TSN feature related kernel configs
I had a minor merge conflict with this change: - commit 8de3d1d2825a5d6fb30279acb583f9778c1da164 Author: Meng Li Date: Thu Feb 22 22:44:26 2024 +0800 ti-am62: enable optee related kernel configs Add optee feature and enable it in ti-am62 BSP. Signed-off-by: Meng Li Signed-off-by: Bruce Ashfield - but of course it was easy to resolve and this is now merged. Bruce In message: [v2][linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] ti-am62: add TSN feature related kernel configs on 27/03/2024 Xulin Sun wrote: > Add TSN feature related kernel configs, and drop the duplicated > kernel config CONFIG_NET_SCH_TAPRIO with tsn.cfg. > > Signed-off-by: Xulin Sun > --- > bsp/ti-am62/ti-am62.cfg | 1 - > bsp/ti-am62/ti-am62.scc | 1 + > 2 files changed, 1 insertion(+), 1 deletion(-) > > diff --git a/bsp/ti-am62/ti-am62.cfg b/bsp/ti-am62/ti-am62.cfg > index fdef5c2b..2dab2c45 100755 > --- a/bsp/ti-am62/ti-am62.cfg > +++ b/bsp/ti-am62/ti-am62.cfg > @@ -251,7 +251,6 @@ CONFIG_TI_K3_AM65_CPSW_SWITCHDEV=y > CONFIG_NET_SWITCHDEV=y > CONFIG_TI_K3_AM65_CPTS=y > CONFIG_TI_AM65_CPSW_TAS=y > -CONFIG_NET_SCH_TAPRIO=y > CONFIG_BRIDGE_VLAN_FILTERING=y > > # > diff --git a/bsp/ti-am62/ti-am62.scc b/bsp/ti-am62/ti-am62.scc > index 9a0dda7f..d8d41953 100644 > --- a/bsp/ti-am62/ti-am62.scc > +++ b/bsp/ti-am62/ti-am62.scc > @@ -4,5 +4,6 @@ include cfg/fs/flash_fs.cfg > include features/hugetlb/hugetlb.scc > # Enable the ability to run 32 bit apps > include arch/arm/32bit-compat.scc > +include features/tsn/tsn.scc > > kconf hardware ti-am62.cfg > -- > 2.34.1 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13751): https://lists.yoctoproject.org/g/linux-yocto/message/13751 Mute This Topic: https://lists.yoctoproject.org/mt/105173754/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] ti-am62: add kernel configs NET_SCH_CBS & NET_SCH_MQPRIO & NET_SCH_ETF
In message: Re: [linux-yocto][yocto-kernel-cache][yocto-6.1][PATCH] ti-am62: add kernel configs NET_SCH_CBS & NET_SCH_MQPRIO & NET_SCH_ETF on 27/03/2024 Kevin Hao wrote: > On Wed, Mar 27, 2024 at 03:30:35PM +0800, Xulin Sun via > lists.yoctoproject.org wrote: > > Add kernel configs NET_SCH_CBS & NET_SCH_MQPRIO & NET_SCH_ETF to support > > AM62AX TSN feature. > > > > Signed-off-by: Xulin Sun > > --- > > bsp/ti-am62/ti-am62.cfg | 3 +++ > > 1 file changed, 3 insertions(+) > > > > diff --git a/bsp/ti-am62/ti-am62.cfg b/bsp/ti-am62/ti-am62.cfg > > index fdef5c2b..537f4120 100755 > > --- a/bsp/ti-am62/ti-am62.cfg > > +++ b/bsp/ti-am62/ti-am62.cfg > > @@ -252,6 +252,9 @@ CONFIG_NET_SWITCHDEV=y > > CONFIG_TI_K3_AM65_CPTS=y > > CONFIG_TI_AM65_CPSW_TAS=y > > CONFIG_NET_SCH_TAPRIO=y > > +CONFIG_NET_SCH_ETF=y > > +CONFIG_NET_SCH_CBS=y > > +CONFIG_NET_SCH_MQPRIO=y > > We can use the feature/tsn. Thanks for the review Kevin! I'm grabbing the v2. Bruce > > Thanks, > Kevin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13750): https://lists.yoctoproject.org/g/linux-yocto/message/13750 Mute This Topic: https://lists.yoctoproject.org/mt/105173259/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/3] nxp-imx9: Delete IMX_SCU since imx93 does not need this driver
merged. Bruce In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/3] nxp-imx9: Delete IMX_SCU since imx93 does not need this driver on 26/03/2024 Xiaolei Wang wrote: > IMX_SCU is specific on imx8, so remove it to avoid warnings > > [NOTE]: 'CONFIG_PINCTRL_IMX_SCU' last val (y) and .config val (n) do not match > [INFO]: CONFIG_PINCTRL_IMX_SCU : n > [INFO]: raw config text: > > config PINCTRL_IMX_SCU > tristate > select PINCTRL_IMX > depends on IMX_SCU && PINCTRL > > Config 'PINCTRL_IMX_SCU' has the following Direct dependencies > (PINCTRL_IMX_SCU=y): > IMX_SCU(=y) && PINCTRL(=y) > Parent dependencies are: > PINCTRL [y] IMX_SCU [y] > [INFO]: config 'CONFIG_PINCTRL_IMX_SCU' was set, but it wasn't > assignable, check (parent) dependencies > > [INFO]: selection details for 'CONFIG_PINCTRL_IMX_SCU': > Symbols currently n-selecting this symbol (no effect): > - PINCTRL_IMX8QM > - PINCTRL_IMX8QXP > - PINCTRL_IMX8DXL > > Signed-off-by: Xiaolei Wang > --- > bsp/nxp-imx9/nxp-imx9.cfg | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg > index 41964ea5..29c3b8e3 100644 > --- a/bsp/nxp-imx9/nxp-imx9.cfg > +++ b/bsp/nxp-imx9/nxp-imx9.cfg > @@ -164,7 +164,6 @@ CONFIG_SPI_SLAVE=y > CONFIG_PINCTRL=y > CONFIG_GPIOLIB=y > CONFIG_PINCTRL_IMX=y > -CONFIG_PINCTRL_IMX_SCU=y > CONFIG_PINCTRL_IMX93=y > CONFIG_GPIO_MAX732X=y > CONFIG_GPIO_PCA953X=y > -- > 2.25.1 > In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 3/3] nxp-imx9: Delete MXC_CLK_SCU since imx93 does not need this driver on 26/03/2024 Xiaolei Wang wrote: > MXC_CLK_SCU is specific on imx8, so remove it to avoid warnings > > [NOTE]: 'CONFIG_MXC_CLK_SCU' last val (y) and .config val (n) do not match > [INFO]: CONFIG_MXC_CLK_SCU : n > [INFO]: raw config text: > > config MXC_CLK_SCU > tristate > depends on COMMON_CLK > > Config 'MXC_CLK_SCU' has the following Direct dependencies > (MXC_CLK_SCU=y): > COMMON_CLK(=y) > Parent dependencies are: > COMMON_CLK [y] > [INFO]: config 'CONFIG_MXC_CLK_SCU' was set, but it wasn't assignable, > check (parent) dependencies > > [INFO]: selection details for 'CONFIG_MXC_CLK_SCU': > Symbols currently n-selecting this symbol (no effect): > - CLK_IMX8QXP > > Signed-off-by: Xiaolei Wang > --- > bsp/nxp-imx9/nxp-imx9.cfg | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg > index c034cb5c..8ad37abb 100644 > --- a/bsp/nxp-imx9/nxp-imx9.cfg > +++ b/bsp/nxp-imx9/nxp-imx9.cfg > @@ -511,7 +511,6 @@ CONFIG_DMABUF_HEAPS_DSP=y > # Clock driver for ARM Reference designs > # > CONFIG_MXC_CLK=y > -CONFIG_MXC_CLK_SCU=y > CONFIG_CLK_IMX93=y > > # > -- > 2.25.1 > In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 2/3] nxp-imx9: Enable NET_DSA for nxp-imx9 on 26/03/2024 Xiaolei Wang wrote: > Enable NET_DSA for nxp-imx9. > > Signed-off-by: Xiaolei Wang > --- > bsp/nxp-imx9/nxp-imx9.cfg | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg > index 29c3b8e3..c034cb5c 100644 > --- a/bsp/nxp-imx9/nxp-imx9.cfg > +++ b/bsp/nxp-imx9/nxp-imx9.cfg > @@ -113,6 +113,7 @@ CONFIG_AT803X_PHY=y > CONFIG_REALTEK_PHY=y > CONFIG_STMMAC_ETH=y > CONFIG_FEC_ECAT=y > +CONFIG_NET_DSA=m > CONFIG_NET_DSA_NETC=m > CONFIG_NET_DSA_SJA1105=m > CONFIG_NET_DSA_SJA1105_PTP=y > -- > 2.25.1 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13749): https://lists.yoctoproject.org/g/linux-yocto/message/13749 Mute This Topic: https://lists.yoctoproject.org/mt/105197672/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][branch v6.1/standard/nxp-sdk-6.1/nxp-soc & v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc][PATCH 1/2] net: stmmac: Fix build error fpe_cfg undeclared
merged.
Bruce
In message: [linux-yocto][branch v6.1/standard/nxp-sdk-6.1/nxp-soc &
v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc][PATCH 1/2] net: stmmac: Fix build
error fpe_cfg undeclared
on 23/03/2024 Xiaolei Wang wrote:
> Use priv->plat->fpe_cfg instead of fpe_cfg to avoid fpe_cfg undeclared
>
> Fixes: b102a918b11cb ("net: stmmac: add ethtool preempt support")
> Signed-off-by: Xiaolei Wang
> ---
> drivers/net/ethernet/stmicro/stmmac/stmmac_ethtool.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_ethtool.c
> b/drivers/net/ethernet/stmicro/stmmac/stmmac_ethtool.c
> index e483caafbdda..7e396b6976e6 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_ethtool.c
> +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_ethtool.c
> @@ -1221,7 +1221,7 @@ static int stmmac_set_preempt(struct net_device *dev,
> struct ethtool_fp *fpcmd)
> priv->plat->fpe_cfg->enable = 1;
> priv->fp_enabled_admin = 1;
> }
> - stmmac_fpe_configure(priv, priv->ioaddr, fpe_cfg,
> + stmmac_fpe_configure(priv, priv->ioaddr, priv->plat->fpe_cfg,
>priv->plat->tx_queues_to_use,
>priv->plat->rx_queues_to_use, fpe.enable, );
>
> --
> 2.25.1
>
In message: [linux-yocto][branch v6.1/standard/nxp-sdk-6.1/nxp-soc &
v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc][PATCH 2/2] net: stmmac: Fix build
error too few parameters
on 23/03/2024 Xiaolei Wang wrote:
> Since commit ed7e211b6786 ("net: stmmac: fix FPE events losing")
> adds the fpe_cfg parameter, add it to avoid build errors.
>
> error: too few arguments to function 'priv->hw->mac->fpe_send_mpacket'
>
> Signed-off-by: Xiaolei Wang
> ---
> drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> index 034ae1dc65ec..859af9117a0f 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> @@ -958,7 +958,7 @@ static void stmmac_fpe_link_state_handle(struct
> stmmac_priv *priv, bool is_up)
>
> if (is_up) {
> if (*hs_enable)
> - stmmac_fpe_send_mpacket(priv, priv->ioaddr,
> MPACKET_VERIFY);
> + stmmac_fpe_send_mpacket(priv, priv->ioaddr, fpe_cfg,
> MPACKET_VERIFY);
> } else {
> *lo_state = FPE_STATE_OFF;
> *lp_state = FPE_STATE_OFF;
> --
> 2.25.1
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13747):
https://lists.yoctoproject.org/g/linux-yocto/message/13747
Mute This Topic: https://lists.yoctoproject.org/mt/105197595/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [linux-yocto std kernel]: Add TSN support for imx9
merged! Bruce In message: [linux-yocto] [linux-yocto std kernel]: Add TSN support for imx9 on 22/03/2024 Xiaolei Wang wrote: > Hi Bruce > > Would you please help to merge the following patch into branch: > > v6.1/standard/nxp-sdk-6.1/nxp-soc > > for nxp-imx9 bsp? > > The following changes since commit b9f1e20c17376d047aa8d6a9f1a06e970da2d1f9: > > Merge branch 'v6.1/standard/base' into v6.1/standard/nxp-sdk-6.1/nxp-soc > (2024-03-10 23:19:33 -0400) > > are available in the Git repository at: > > https://github.com/wangxiaolei12/linux-yocto-6.1.git > v6.1/standard/nxp-sdk-6.1/nxp-soc > > for you to fetch changes up to 93c514e7433e49536a23abaca358935674922bad: > > arm64: dts: fix ecspi2 dts node (2024-03-22 11:48:47 +0800) > > > Alexandre Howard (8): > firmware: imx: scu-pd: add power domains for gpt instances in ADMA > subsystem > arm64: dts: add node for gpt instance from audio ss for imx8dxl > arm64: dts: add imx8dxl evk device tree for avb support > arm64: dts: add tja1100 with avb support device tree for imx8dxl > net: dsa: sja1105: make hostprio configurable through the dtb > net: dsa: sja1105: round up tc-cbs idleslope to prevent bandwidth > under-allocation > net: sched: sch_cbs: prevent the offloading of erroneous value to tc-cbs > net: dsa: sja1105: use mqprio mapping to configure port egress pcp > mapping > > Alison Wang (1): > ARM: LS1021A: Add platform support for LS1021AIOT in Makefile > > Biwen Li (3): > drivers: tty: support i.MX SRTM protocol(for uart) > dt-bindings: tty: add rpmsg_tty > arm64: dts: imx8mm-evk-rpmsg: add uart rpmsg bus > > Changming Huang (1): > ARM: LS1021AIOT: Enable SDHC > > Chunguang Li (1): > rpmsg: add 8M buffer support switch > > Colin Ian King (1): > net: dsa: sja1105: make read-only const arrays static > > Cosmin Chenaru (4): > net: fec: enable RX flushing for Best Effort queue > net: fec: apply workaround for ERR007885 for normal path too > net: fec: avb: set RCMR to only match two AVB priority classes > net: fec: avb: export function to dynamically set the Idle Slope > > Hou Zhiqiang (17): > arm64: dts: imx8mm: Add RPMsg 8M buffer support DTS > RTC: imx-rpmsg: Add dependency of RPMSG > mailbox: Fix potential crash caused by channel receive function > dt-binding: Add binding file for generic software mailbox > rpmsg: imx_rpmsg: Updated the dependent items in Kconfig > arm64: dts: imx8mm: Add DTS for RPMSG examples between A cores > dma-mapping: Respect to device 'dma-coherent' property > rpmsg: imx: add remove() callback function > arm64: dts: imx8mm: fix rsc table name > arm64: dts: imx8mm: fix address unit format of M4 reserved-memory node > arm64: dts: imx8mp: add dtsi for RPMsg running on CA53 > arm64: dts: imx8mp: add dtsi for the second generic mailbox > arm64: dts: imx8mp: add dtsi for the second rpmsg slave on CA53 > mailbox: Add generic software mailbox driver > drivers: rpmsg: add rpmsg_perf driver > arm64: dts: imx8m: add dtsi for the second generic mailbox > arm64: dts: imx8m: add dtsi for the second rpmsg slave > > Jiafei Pan (3): > mailbox: gen-sw-mailbox: fix handle sequence > mailbox: gen-sw-mailbox: add ack option > drivers: tty: rpmsg_tty: add hello command > > Jianchao Wang (4): > ARM: LS1021AIOT: Add flexcan nodes in ls1021a-iot.dts > LS1028ARDB: NFC Click: Add pn7120 node in fsl-ls1028a-rdb.dts file. > LS1028ARDB: NFC Click: Add NFC click driver. > arm64: dts: fsl-ls1028a: add dspi2 support > > Liu Gang (1): > ARM: LS1021A: Enable baremetal support > > Marouen Ghodhbane (30): > net: fec: add device tree property for Tx/Rx timestamps latency > adjustment > net: fec: fix default rx phy-mac delay compensation > clk: imx8mq: fix the wrong gpt1 clock mux definition > net: fec: avb: enable clocks once at probe and disable the pm runtime > for avb usage > net: fec: avb: Improve CPU load under heavy AVB network load > net: fec: avb: read buffer descriptor once to avoid multiple reads to > non cacheable memory > clk: imx: add imx pll api for media clock recovery > clk: imx: clk-pllv3: add imx pll api support > clk: imx: clk-frac-pll: add imx pll api support > clk: imx: clk-pll14xx: add imx pll api support > arm64: dts: imx8mm: add gpt1 node > clk: refine the fractional part of the audio pll > clk: imx: fracn-gppll: add imx pll api support > net: fec: avb: increase tx/rx ring sizes and tune default coalescing > setting in avb configuration > net: phy: increase phy status update rate > net: fec: avb: check if fec_enet_avb_get_device() call is related to > fec device or not > arm64:
Re: [linux-yocto] [kernel-cache][PATCH 08/12] bsp/genericarm64: enable USB On-The-Go and Gadget
On Fri, Mar 22, 2024 at 6:27 AM Ross Burton wrote: > > On 21 Mar 2024, at 23:26, Bruce Ashfield wrote: > >> # USB support > >> +# OTG support > >> +CONFIG_USB_OTG=y > > > > We've got more than a few BSPs that are setting this, and > > really we should just add a features/usb/usb-otg.scc to > > go along with the other usb features. > > > > I wouldn't cleanup all the other badly bhaving BSPs > > immediately, but making a otg feature available is the > > first step. > > Absolutely agreed. There’s a number of pieces that are replicated across > BSPs, and also some pieces that genericarm64 is replicating that are already > fragments because those fragments are x86-specific. > > Can we do the rationalisation post-release though? Fair enough. I'll raise a bug against myself to have a look at it for the fall release. Bruce > > Ross -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13724): https://lists.yoctoproject.org/g/linux-yocto/message/13724 Mute This Topic: https://lists.yoctoproject.org/mt/105052013/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [kernel-cache][PATCH 08/12] bsp/genericarm64: enable USB On-The-Go and Gadget
In message: [linux-yocto] [kernel-cache][PATCH 08/12] bsp/genericarm64: enable USB On-The-Go and Gadget on 20/03/2024 Ross Burton wrote: > From: Ross Burton > > Signed-off-by: Ross Burton > --- > bsp/genericarm64/genericarm64.cfg | 5 + > 1 file changed, 5 insertions(+) > > diff --git a/bsp/genericarm64/genericarm64.cfg > b/bsp/genericarm64/genericarm64.cfg > index 92a1daee..25dc4c4b 100644 > --- a/bsp/genericarm64/genericarm64.cfg > +++ b/bsp/genericarm64/genericarm64.cfg > @@ -395,11 +395,16 @@ CONFIG_SND_SOC_DAVINCI_MCASP=m > CONFIG_SND_SOC_DA7213=m > > # USB support > +# OTG support > +CONFIG_USB_OTG=y We've got more than a few BSPs that are setting this, and really we should just add a features/usb/usb-otg.scc to go along with the other usb features. I wouldn't cleanup all the other badly bhaving BSPs immediately, but making a otg feature available is the first step. Thoughts ? Bruce > # DesignWare USB3 DRD Core Support > CONFIG_USB_DWC3=m > # Texas Instruments AM62 Platforms > CONFIG_USB_DWC3_AM62=m > > +# USB Gadget Support > +CONFIG_USB_GADGET=m > + > # USB Type-C Support > CONFIG_TYPEC=m > # USB Type-C Port Controller Manager > -- > 2.34.1 > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13720): https://lists.yoctoproject.org/g/linux-yocto/message/13720 Mute This Topic: https://lists.yoctoproject.org/mt/105052013/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/3] features/net: Add xdp feature config
All three are merged to yocto-6.1, the net features are also on 6.6 and master. Bruce In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 1/3] features/net: Add xdp feature config on 21/03/2024 Xiaolei Wang wrote: > Add xdp feature config. > > Signed-off-by: Xiaolei Wang > --- > features/net/xdp/xdp.cfg | 1 + > features/net/xdp/xdp.scc | 1 + > 2 files changed, 2 insertions(+) > create mode 100644 features/net/xdp/xdp.cfg > create mode 100644 features/net/xdp/xdp.scc > > diff --git a/features/net/xdp/xdp.cfg b/features/net/xdp/xdp.cfg > new file mode 100644 > index ..061b65a4 > --- /dev/null > +++ b/features/net/xdp/xdp.cfg > @@ -0,0 +1 @@ > +CONFIG_XDP_SOCKETS=y > diff --git a/features/net/xdp/xdp.scc b/features/net/xdp/xdp.scc > new file mode 100644 > index ..e4df6d09 > --- /dev/null > +++ b/features/net/xdp/xdp.scc > @@ -0,0 +1 @@ > +kconf hardware xdp.cfg > -- > 2.25.1 > In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 2/3] features/net_sched: Add MULTIQ and NET_EMATCH config on 21/03/2024 Xiaolei Wang wrote: > Add MULTIQ and NET_EMATCH config. > > Signed-off-by: Xiaolei Wang > --- > features/net_sched/net_sched.cfg | 5 + > 1 file changed, 5 insertions(+) > > diff --git a/features/net_sched/net_sched.cfg > b/features/net_sched/net_sched.cfg > index d0473170..137ca752 100644 > --- a/features/net_sched/net_sched.cfg > +++ b/features/net_sched/net_sched.cfg > @@ -20,6 +20,8 @@ CONFIG_NET_SCH_INGRESS=m > CONFIG_NET_SCH_CODEL=m > CONFIG_NET_SCH_FQ_CODEL=m > > +CONFIG_NET_SCH_MULTIQ=m > + > # > # Classification > # > @@ -31,3 +33,6 @@ CONFIG_NET_CLS_U32=y > CONFIG_NET_ACT_MIRRED=m > CONFIG_NET_ACT_SKBEDIT=m > CONFIG_NET_EMATCH=y > + > +CONFIG_NET_EMATCH_U32=y > +CONFIG_NET_EMATCH_META=y > -- > 2.25.1 > In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH 3/3] nxp-imx9: Add some related net config required by tsn on 21/03/2024 Xiaolei Wang wrote: > Add some related net config required by tsn. > > Signed-off-by: Xiaolei Wang > --- > bsp/nxp-imx9/nxp-imx9-preempt-rt.scc | 2 ++ > bsp/nxp-imx9/nxp-imx9-standard.scc | 2 ++ > bsp/nxp-imx9/nxp-imx9.cfg| 6 ++ > 3 files changed, 10 insertions(+) > > diff --git a/bsp/nxp-imx9/nxp-imx9-preempt-rt.scc > b/bsp/nxp-imx9/nxp-imx9-preempt-rt.scc > index 57ce73f9..737fdeab 100644 > --- a/bsp/nxp-imx9/nxp-imx9-preempt-rt.scc > +++ b/bsp/nxp-imx9/nxp-imx9-preempt-rt.scc > @@ -3,6 +3,8 @@ define KTYPE preempt-rt > define KARCH arm64 > > include ktypes/preempt-rt > +include features/tsn/tsn.scc > +include features/net/xdp/xdp.scc > > include nxp-imx9.scc > > diff --git a/bsp/nxp-imx9/nxp-imx9-standard.scc > b/bsp/nxp-imx9/nxp-imx9-standard.scc > index 4483215c..1e6e9eea 100644 > --- a/bsp/nxp-imx9/nxp-imx9-standard.scc > +++ b/bsp/nxp-imx9/nxp-imx9-standard.scc > @@ -3,5 +3,7 @@ define KTYPE standard > define KARCH arm64 > > include ktypes/standard > +include features/tsn/tsn.scc > +include features/net/xdp/xdp.scc > > include nxp-imx9.scc > diff --git a/bsp/nxp-imx9/nxp-imx9.cfg b/bsp/nxp-imx9/nxp-imx9.cfg > index 499b0750..41964ea5 100644 > --- a/bsp/nxp-imx9/nxp-imx9.cfg > +++ b/bsp/nxp-imx9/nxp-imx9.cfg > @@ -112,6 +112,12 @@ CONFIG_FEC=y > CONFIG_AT803X_PHY=y > CONFIG_REALTEK_PHY=y > CONFIG_STMMAC_ETH=y > +CONFIG_FEC_ECAT=y > +CONFIG_NET_DSA_NETC=m > +CONFIG_NET_DSA_SJA1105=m > +CONFIG_NET_DSA_SJA1105_PTP=y > +CONFIG_NET_DSA_SJA1105_TAS=y > +CONFIG_NET_DSA_SJA1105_VL=y > > # > # Input device support > -- > 2.25.1 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13719): https://lists.yoctoproject.org/g/linux-yocto/message/13719 Mute This Topic: https://lists.yoctoproject.org/mt/105076207/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] Trial merge of v5.15.152 v6.1.82 for linux-yocto
In message: Trial merge of v5.15.152 v6.1.82 for linux-yocto on 16/03/2024 Kevin Hao wrote: > Hi Bruce, > > This is a trial merge of the stable kernel v5.15.152 v6.1.82 for the > following branches in the linux-yocto. > 8441795c5d6f v5.15/standard/sdkv5.10/axxia > 8242dc07ca33 v5.15/standard/preempt-rt/sdkv5.10/axxia > c83b73b48974 v5.15/standard/base > 0d992354aa32 v5.15/standard/preempt-rt/base > de1bc32baa54 v5.15/standard/cn-sdkv5.4/octeon > cd0719b53bf9 v5.15/standard/preempt-rt/cn-sdkv5.4/octeon > 1fa974505ba2 v5.15/standard/cn-sdkv5.15/octeon > c799c504eac8 v5.15/standard/preempt-rt/cn-sdkv5.15/octeon > f173c9f889fa v5.15/standard/ti-sdk-5.10/ti-j72xx > c80f38dd2543 v5.15/standard/preempt-rt/ti-sdk-5.10/ti-j72xx > 448957b6 v5.15/standard/nxp-sdk-5.15/nxp-soc > 7939302b17e9 v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-soc > 8638c9a65ea1 v5.15/standard/bcm-2xxx-rpi >#Have textual conflicts > cfcea09b8b9c v5.15/standard/preempt-rt/bcm-2xxx-rpi > 59c473545504 v5.15/standard/nxp-sdk-5.15/nxp-s32g > d035368ec01a v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g > c62b5d909bd4 v5.15/standard/intel-sdk-5.15/intel-socfpga > 074c73c8fb65 v5.15/standard/preempt-rt/intel-sdk-5.15/intel-socfpga > 6f68051affde v5.15/standard/x86 > 8ea8d2415faa v5.15/standard/preempt-rt/x86 > 62f89ced13cc v5.15/standard/sdkv5.15/xlnx-soc > 007a7d0f7e8b v5.15/standard/preempt-rt/sdkv5.15/xlnx-soc > 13f46c11e84d v6.1/standard/sdkv5.10/axxia > 6b719d4ebd91 v6.1/standard/preempt-rt/sdkv5.10/axxia > 77cfcdc0f431 v6.1/standard/base > fb102a5fe10b v6.1/standard/preempt-rt/base > 76d8795a2614 v6.1/standard/ti-sdk-6.1/ti-j7xxx > caceb206db05 v6.1/standard/preempt-rt/ti-sdk-6.1/ti-j7xxx > b6068c48e578 v6.1/standard/nxp-sdk-6.1/nxp-soc > eb93150e3db3 v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc > 8e19ca547fe3 v6.1/standard/cn-sdkv5.15/octeon > a9cb178d96a2 v6.1/standard/preempt-rt/cn-sdkv5.15/octeon > 3c2229b42119 v6.1/standard/microchip-polarfire-soc > 9a714e926528 v6.1/standard/preempt-rt/microchip-polarfire-soc > b4f069b2407d v6.1/standard/bcm-2xxx-rpi > 91b2f7e6d9a7 v6.1/standard/preempt-rt/bcm-2xxx-rpi > 227df9926302 v6.1/standard/nxp-sdk-5.15/nxp-s32g > ebb4201875ea v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g > 5896799d54f7 v6.1/standard/intel-sdk-6.1/intel-socfpga > 09509f3893f0 v6.1/standard/preempt-rt/intel-sdk-6.1/intel-socfpga > 007392942561 v6.1/standard/x86 > 22e449f4568d v6.1/standard/preempt-rt/x86 > 087fdda55e45 v6.1/standard/sdkv6.1/xlnx-soc > 35048bcb1b5e v6.1/standard/preempt-rt/sdkv6.1/xlnx-soc > > There is only minor merge conflict on v5.15 rpi branch due to re-sort the usb > audio quirk tables. Please note we also need to re-sort the entries added by > SDK patches. Thanks Kevin, I just grabbed your resolution for the rpi branch. Bruce > > All the branches have passed my build test. I have pushed all these branches > to: > https://github.com/haokexin/linux > > You can use this as a reference for the linux-yocto stable kernel bump. > > Thanks, > Kevin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13703): https://lists.yoctoproject.org/g/linux-yocto/message/13703 Mute This Topic: https://lists.yoctoproject.org/mt/104963163/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][linux-yocto v6.1] kernel code for marvell octeon
both branches are merged. Bruce In message: [linux-yocto][linux-yocto v6.1] kernel code for marvell octeon on 19/03/2024 Ruiqiang Hao wrote: > Hi Bruce, > > Please help to merge code into our linux-yocto repo. > > repo: > linux-yocto > branch: > v6.1/standard/cn-sdkv5.15/octeon > > Thanks, > Ruiqiang > > The following changes since commit 34d48a6c6406fbb97861ff8b55c50cecabadb8c0: > > Merge branch 'v6.1/standard/base' into v6.1/standard/cn-sdkv5.15/octeon > (2024-03-10 23:16:49 -0400) > > are available in the Git repository at: > > g...@github.com:cythe/linux.git linux-yocto/v6.1/standard/cn-sdkv5.15/octeon > > for you to fetch changes up to 755d0e9afe53c6c4a99790263350128a352a9769: > > arm_mpam: replace acpi_table_mpam_msc with acpi_mpam_msc_node (2024-03-19 > 09:26:44 +0800) > > > Ankur Dwivedi (1): > octeontx2-af: fix mcam hit counter > > Baha Mesleh (3): > octeontx2-bphy-netdev: ignore MCS bypass errors > octeontx2-bphy-netdev: release psm queues on exit > octeontx2-bphy-netdev: disable rx on RFOEs on exit > > Bharat Bhushan (2): > crypto/octeontx2: By default allocate one CPT LF per CPT VF > crypto: octeontx2: Honor irqaffinity passed via bootargs > > Damian Eppel (2): > firmware: octeontx2: sysfs interface for PORTM boot cfg > firmware: octeontx2: minor fixes for PORTM boot cfg > > George Cherian (1): > octeontx2-af: Fix Support of FDSA tag > > Hariprasad Kelam (3): > octeontx2-af: configure 802.3 pause frames in SGMII/QSGMII mode > octeontx2-af: map management port always to first PF > octeontx2-af: Fix default entries mcam entry action > > James Morse (1): > ACPI/MPAM: update MPAM ACPI headers > > Kiran Kumar K (2): > octeontx2-af: Fix capture PPPOE ltype > octeontx2-af: Add KPU parsing support for GRE ERSPAN > > Mikko Suni (1): > FWLOG: Correct read length with ppos > > Naveen Mamindlapalli (1): > octeontx2-bphy-netdev: Add cpri busrt packet limiter > > Nithin Dabilpuram (1): > octeontx2-af: fix CN10KB FIFO length for RPM2 > > Paul Way (1): > MMC: Fix for SD card support in cadence driver > > Piyush Malgujar (1): > soc: marvell: otx2: Add dependency in Kconfig for GHES BERT > > Ratheesh Kannoth (2): > Revert "octeontx2-pf: Set maximum queue size to 16K" > octeontx2-af: Initialize bitmap arrays. > > Ruiqiang Hao (1): > arm_mpam: replace acpi_table_mpam_msc with acpi_mpam_msc_node > > Sai Krishna (2): > octeontx2-pf: Reorder tearing down of PTP RX info work queue, mailbox > octeontx2-pf: Add ucast filter count configurability via devlink. > > Scott Rowberry (1): > firmware: octeontx2: sysfs interface for led blink rate > > Shijith Thotton (1): > octeontx2-af: reveal only TIM params that are available > > Subbaraya Sundeep (4): > octeontx2-pf: Send UP messages to VF only when VF is up. > octeontx2-pf: Reschedule up message if message data is non zero > octeontx2-af: Use separate handlers for interrupts > octeontx2-cpt: Wake up waiting process as last step > > Suman Ghosh (1): > octeontx2-af: Fix multicast/mirror group lock/unlock issue > > Sunil Goutham (1): > octeontx2-pf: Fix module compilation failure > > Witold Sadowski (1): > swup: Remove smc_update_obj_info > > drivers/acpi/arm64/mpam.c | 45 +- > drivers/crypto/marvell/octeontx2/otx2_cptlf.c | 14 +- > drivers/crypto/marvell/octeontx2/otx2_cptpf_main.c | 1 + > drivers/crypto/marvell/octeontx2/otx2_cptpf_mbox.c | 3 +- > drivers/crypto/marvell/octeontx2/otx2_cptvf_main.c | 3 +- > drivers/firmware/octeontx2/Kconfig | 22 + > drivers/firmware/octeontx2/Makefile| 2 + > drivers/firmware/octeontx2/led-blink-rate.c| 113 + > drivers/firmware/octeontx2/portm-boot-cfg.c| 511 > + > drivers/mmc/host/sdhci-cadence.c | 3 +- > drivers/net/ethernet/marvell/octeontx2/af/cgx.c| 5 + > drivers/net/ethernet/marvell/octeontx2/af/mbox.h | 13 +- > .../ethernet/marvell/octeontx2/af/npc_profile.h| 141 +- > drivers/net/ethernet/marvell/octeontx2/af/rpm.c| 7 +- > drivers/net/ethernet/marvell/octeontx2/af/rvu.c| 17 +- > .../net/ethernet/marvell/octeontx2/af/rvu_cgx.c| 60 ++- > .../ethernet/marvell/octeontx2/af/rvu_devlink.c| 41 +- > .../net/ethernet/marvell/octeontx2/af/rvu_nix.c| 125 +++-- > .../net/ethernet/marvell/octeontx2/af/rvu_npc.c| 95 ++-- > .../net/ethernet/marvell/octeontx2/af/rvu_npc_fs.c | 10 +- > .../ethernet/marvell/octeontx2/bphy/bphy_common.h | 31 ++ > .../marvell/octeontx2/bphy/bphy_netdev_comm_if.h | 5 + > .../marvell/octeontx2/bphy/cnf10k_bphy_hw.h| 16 + > .../ethernet/marvell/octeontx2/bphy/cnf10k_rfoe.c |
Re: [linux-yocto] drm/tilcdc: Set preferred depth
In message: [linux-yocto] drm/tilcdc: Set preferred depth
on 19/03/2024 Kevin Hao wrote:
> The commit c91acda3a380 ("drm/gem: Check for valid formats") adds a
> check for valid pixel formats on drm_gem_fb_create(), but this breaks
> the X server on the beaglebone black board.
>
> We have set 'DefaultDepth' to 16 in our xorg.conf. In the X modesetting
> driver, the drmmode_get_default_bpp() is used to guess the default
> depth/bpp. First it tries to get them via DRM_CAP_DUMB_PREFERRED_DEPTH
> ioctl, and if it fail, then try to create a FB with 'depth = 24' and
> 'bpp = 32' to check whether this depth/dpp is a valid combo. Before the
> kernel commit c91acda3a380, the FB always can be created successfully.
> This will avoid the bpp to be set to 24 forcibly. But after kernel
> commit c91acda3a380, the FB will not be created successfully due to the
> check of the valid pixel format. Then the bpp is set to 24, but the
> 'depth = 16' and 'bpp = 24' combo is not a valid pixel format.
>
> Fix this issue by explicitly setting the preferred_depth in this driver.
> With this change, the modesetting driver would choose the correct
> depth/bpp combo based on our setting in xorg.conf.
>
> Fixes: c91acda3a380 ("drm/gem: Check for valid formats")
> Cc: sta...@vger.kernel.org
> Signed-off-by: Kevin Hao
> Link: https://lore.kernel.org/r/20240317033918.535716-1-haoke...@gmail.com/
> ---
> Hi Bruce,
>
> Please merge this onto v6.6/standard/base branch.
>
> This patch is still in review, but it fixes the X malfunction on the
> beaglebone black, so I want it to be merged as soon as possible. There is
> also another patch [1] on the mail list to fix the same issue, but I
> like mine and think it is more suitable for a stable kernel fix. There
> is also no semantic conflict between these two patches.
The direction sounds fine to me.
I've merged this and will send the SRCREV bump by the end
of the day (I have a bit more testing on unrelated commits)
Bruce
>
> [1]
> https://lore.kernel.org/dri-devel/e7ef6d422365986f49746b596735f7a0b939574d.1710698387.git.frej.drejham...@gmail.com/T/#mf85946113936134f54807095b92d7c45428f6004
>
> drivers/gpu/drm/tilcdc/tilcdc_drv.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/tilcdc/tilcdc_drv.c
> b/drivers/gpu/drm/tilcdc/tilcdc_drv.c
> index 2f6eaac7f659..daff3926ab89 100644
> --- a/drivers/gpu/drm/tilcdc/tilcdc_drv.c
> +++ b/drivers/gpu/drm/tilcdc/tilcdc_drv.c
> @@ -269,6 +269,7 @@ static int tilcdc_init(const struct drm_driver *ddrv,
> struct device *dev)
>
> pm_runtime_put_sync(dev);
>
> + ddev->mode_config.preferred_depth = 16;
> if (priv->rev == 1) {
> DBG("Revision 1 LCDC supports only RGB565 format");
> priv->pixelformats = tilcdc_rev1_formats;
> @@ -284,6 +285,7 @@ static int tilcdc_init(const struct drm_driver *ddrv,
> struct device *dev)
> priv->num_pixelformats =
> ARRAY_SIZE(tilcdc_crossed_formats);
> bpp = 32; /* Choose bpp with RGB support for fbdef */
> + ddev->mode_config.preferred_depth = 24;
> } else if (0 == strcmp(str, "straight")) {
> DBG("Configured for straight blue and red wires");
> priv->pixelformats = tilcdc_straight_formats;
> --
> 2.44.0
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13701):
https://lists.yoctoproject.org/g/linux-yocto/message/13701
Mute This Topic: https://lists.yoctoproject.org/mt/105016038/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][yocto-kernel-cache][master/yocto-6.6][PATCH 1/3] features/vfio: remove CONFIG_VFIO_VIRQFD
All three are applied.
Bruce
In message: [linux-yocto][yocto-kernel-cache][master/yocto-6.6][PATCH 1/3]
features/vfio: remove CONFIG_VFIO_VIRQFD
on 18/03/2024 Yongxin Liu wrote:
> CONFIG_VFIO_VIRQFD was changed to bool in kernel commit
> e2d55709398e ("vfio: Fold vfio_virqfd.ko into vfio.ko") and
> it is not user selectable.
>
> Signed-off-by: Yongxin Liu
> ---
> features/vfio/vfio.cfg | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/features/vfio/vfio.cfg b/features/vfio/vfio.cfg
> index 96c9208e..2a38f6d9 100644
> --- a/features/vfio/vfio.cfg
> +++ b/features/vfio/vfio.cfg
> @@ -1,6 +1,5 @@
> # SPDX-License-Identifier: MIT
> CONFIG_VFIO_IOMMU_TYPE1=m
> -CONFIG_VFIO_VIRQFD=m
> CONFIG_VFIO=m
> CONFIG_VFIO_PCI=m
> CONFIG_VFIO_PCI_VGA=y
> --
> 2.43.2
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13700):
https://lists.yoctoproject.org/g/linux-yocto/message/13700
Mute This Topic: https://lists.yoctoproject.org/mt/105000432/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][yocto-kernel-cache][master/yocto-6.6][PATCH] bsp/intel-x86: remove intel-x86-64-preempt-rt.cfg in scc file
merged.
Bruce
In message: [linux-yocto][yocto-kernel-cache][master/yocto-6.6][PATCH]
bsp/intel-x86: remove intel-x86-64-preempt-rt.cfg in scc file
on 18/03/2024 Yongxin Liu wrote:
> intel-x86-64-preempt-rt.cfg was removed in commit bd20a636b044
> ("config: remove mis-located configuration fragment").
>
> Signed-off-by: Yongxin Liu
> ---
> bsp/intel-x86/intel-x86-64-preempt-rt.scc | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/bsp/intel-x86/intel-x86-64-preempt-rt.scc
> b/bsp/intel-x86/intel-x86-64-preempt-rt.scc
> index 63d517ec..e776cfa9 100644
> --- a/bsp/intel-x86/intel-x86-64-preempt-rt.scc
> +++ b/bsp/intel-x86/intel-x86-64-preempt-rt.scc
> @@ -8,4 +8,3 @@ include ktypes/preempt-rt
> include intel-x86-64.scc
> include features/tsn/tsn.scc
> kconf hardware cfs-bandwidth.cfg
> -kconf hardware intel-x86-64-preempt-rt.cfg
> --
> 2.43.2
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13699):
https://lists.yoctoproject.org/g/linux-yocto/message/13699
Mute This Topic: https://lists.yoctoproject.org/mt/104997867/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][v5.15/standard/preempt-rt/sdkv5.15/xlnx-soc][PATCH 0/2]
In message: [linux-yocto][v5.15/standard/preempt-rt/sdkv5.15/xlnx-soc][PATCH 0/2] on 15/03/2024 quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > Hi Bruce, > Would you please help merge these 2 patches to the branches: > v5.15/standard/preempt-rt/sdkv5.15/xlnx-soc > v5.15/standard/sdkv5.15/xlnx-soc merged. Bruce > Thanks, > Quanyang > > > Manikanta Guntupalli (1): > gpio: zynq: fix zynqmp_gpio not an immutable chip warning > > Marc Zyngier (1): > gpio: Don't fiddle with irqchips marked as immutable > > drivers/gpio/gpio-zynq.c | 12 +--- > drivers/gpio/gpiolib.c | 7 ++- > include/linux/irq.h | 2 ++ > kernel/irq/debugfs.c | 1 + > 4 files changed, 18 insertions(+), 4 deletions(-) > > -- > 2.36.1 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13698): https://lists.yoctoproject.org/g/linux-yocto/message/13698 Mute This Topic: https://lists.yoctoproject.org/mt/104942021/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][v5.10/standard/ti-sdk-5.10/ti-j72xx & v5.10/standard/preempt-rt/ti-sdk-5.10/ti-j72xx][PATCH] dwc: fix compile error
merged. Bruce In message: [linux-yocto][v5.10/standard/ti-sdk-5.10/ti-j72xx & v5.10/standard/preempt-rt/ti-sdk-5.10/ti-j72xx][PATCH] dwc: fix compile error on 13/03/2024 Li Wang wrote: > ti-j72xx/kernel-source/drivers/pci/controller/dwc/pcie-designware-ep.c:598 > error: too few arguments to function 'dw_pcie_ep_map_addr' > > Signed-off-by: Li Wang > --- > drivers/pci/controller/dwc/pcie-designware-ep.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/pci/controller/dwc/pcie-designware-ep.c > b/drivers/pci/controller/dwc/pcie-designware-ep.c > index b84e2ce3d714..fb53240150d2 100644 > --- a/drivers/pci/controller/dwc/pcie-designware-ep.c > +++ b/drivers/pci/controller/dwc/pcie-designware-ep.c > @@ -595,7 +595,7 @@ int dw_pcie_ep_raise_msix_irq(struct dw_pcie_ep *ep, u8 > func_no, > > aligned_offset = msg_addr & (epc->mem->window.page_size - 1); > msg_addr = ALIGN_DOWN(msg_addr, epc->mem->window.page_size); > - ret = dw_pcie_ep_map_addr(epc, func_no, ep->msi_mem_phys, msg_addr, > + ret = dw_pcie_ep_map_addr(epc, func_no, 0, ep->msi_mem_phys, msg_addr, > epc->mem->window.page_size); > if (ret) > return ret; > -- > 2.25.1 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13686): https://lists.yoctoproject.org/g/linux-yocto/message/13686 Mute This Topic: https://lists.yoctoproject.org/mt/104907828/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
