Re: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx8: add nxp-imx8 bsp kernel config
merged. Bruce In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx8: add nxp-imx8 bsp kernel config on 10/04/2023 Xiaolei Wang wrote: > Signed-off-by: Xiaolei Wang > --- > bsp/nxp-imx8/nxp-imx8-preempt-rt.cfg | 15 + > bsp/nxp-imx8/nxp-imx8-preempt-rt.scc | 10 + > bsp/nxp-imx8/nxp-imx8-standard.scc | 8 + > bsp/nxp-imx8/nxp-imx8.cfg| 537 +++ > bsp/nxp-imx8/nxp-imx8.scc| 11 + > 5 files changed, 581 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 ..677790ee > --- /dev/null > +++ b/bsp/nxp-imx8/nxp-imx8-preempt-rt.scc > @@ -0,0 +1,10 @@ > +define KMACHINE nxp-imx8 > +define KTYPE preempt-rt > +define KARCH arm64 > + > +include ktypes/preempt-rt > +branch nxp-imx8 > + > +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 ..222cbeac > --- /dev/null > +++ b/bsp/nxp-imx8/nxp-imx8-standard.scc > @@ -0,0 +1,8 @@ > +define KMACHINE nxp-imx8 > +define KTYPE standard > +define KARCH arm64 > + > +include ktypes/standard > +branch nxp-imx8 > + > +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 ..d90837d3 > --- /dev/null > +++ b/bsp/nxp-imx8/nxp-imx8.cfg > @@ -0,0 +1,537 @@ > +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_IMX_DSP=y > +CONFIG_IMX_SCU=y > +CONFIG_IMX_SCU_PD=y > +CONFIG_IMX_SECO_MU=y > +CONFIG_IMX_EL_ENCLAVE=m > +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 > + > +# > +# 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 > + > +# > +# Input device support > +# > +CONFIG_INPUT=y > +CONFIG_INPUT_KEYBOARD=y > +CONFIG_INPUT_EVDEV=y > +CONFIG_KEYBOARD_ADC=m > +CONFIG_KEYBOARD_GPIO=y > +CONFIG_KEYBOARD_SNVS_PWRKEY=y > +CONFIG_KEYBOARD_IMX_SC_KEY=y > +CONFIG_INPUT
Re: [linux-yocto][v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g][PATCH 0/3]
In message: [linux-yocto][v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g][PATCH 0/3] on 09/04/2023 quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > Hi Bruce, > Would you please help merge these 3 patches to the branches: > v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g > v5.15/standard/nxp-sdk-5.15/nxp-s32g merged. Bruce > Thanks, > Quanyang > > Quanyang Wang (3): > gpio: s32: force regmap use raw spinlock > gpio: s32: switch the spinlock of siul2_gpio_dev to raw spinlock > gpio: s32: don't run callbacks in some callbacks > > drivers/gpio/gpio-siul2-s32cc.c | 34 + > 1 file changed, 9 insertions(+), 25 deletions(-) > > -- > 2.36.1 > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12364): https://lists.yoctoproject.org/g/linux-yocto/message/12364 Mute This Topic: https://lists.yoctoproject.org/mt/98152526/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/leave/6687884/21656/624485779/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto] [linux-yocto v6.1/standard/base] fat: Replace prandom_u32() with get_random_u32()
In message: [linux-yocto v6.1/standard/base] fat: Replace prandom_u32() with
get_random_u32()
on 07/04/2023 Kevin Hao wrote:
> From: Kevin Hao
>
> The prandom_u32() is just wrapper of get_random_u32() and has been
> removed by commit de492c83cae0 ("prandom: remove unused functions").
> So use get_random_u32() directly.
merged (and staged for future kernel versions).
Bruce
>
> Signed-off-by: Kevin Hao
> ---
> fs/fat/namei_vfat.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/fat/namei_vfat.c b/fs/fat/namei_vfat.c
> index ef5cf74789ca..ef79a242751d 100644
> --- a/fs/fat/namei_vfat.c
> +++ b/fs/fat/namei_vfat.c
> @@ -616,7 +616,7 @@ static void vfat_build_dummy_83_buffer(struct inode *dir,
> char *msdos_name,
>0x1B, 0x1C, 0x1D, 0x1E, 0x1F, 0x22, 0x2a,
>0x3a, 0x3c, 0x3e, 0x3f, 0x5b, 0x5d, 0x7c };
> int i, tilde_pos, slash_pos;
> - u32 rand_num = prandom_u32();
> + u32 rand_num = get_random_u32();
>
> /* We need a '~' in the prefix to make Win98 happy. */
> tilde_pos = rand_num % 8;
> @@ -651,7 +651,7 @@ static void vfat_build_dummy_83_buffer(struct inode *dir,
> char *msdos_name,
> invalidchar[rand_num % sizeof(invalidchar)];
> rand_num /= sizeof(invalidchar);
> if (rand_num < sizeof(invalidchar))
> - rand_num = prandom_u32();
> + rand_num = get_random_u32();
> }
> }
> }
> --
> 2.39.2
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#12363):
https://lists.yoctoproject.org/g/linux-yocto/message/12363
Mute This Topic: https://lists.yoctoproject.org/mt/98123873/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe:
https://lists.yoctoproject.org/g/linux-yocto/leave/6687884/21656/624485779/xyzzy
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [linux-yocto][v5.15/standard/preempt-rt/sdkv5.15/xlnx-soc][PATCH] usb: dwc3: gadget: do cleanup for dwc3_stop_active_transfer
In message: [linux-yocto][v5.15/standard/preempt-rt/sdkv5.15/xlnx-soc][PATCH]
usb: dwc3: gadget: do cleanup for dwc3_stop_active_transfer
on 07/04/2023 quanyang.w...@windriver.com wrote:
> From: Quanyang Wang
>
> The cmd_endtransfer has been move to a new function
> __dwc3_stop_active_transfer in the commit 1536e51c30ada ("usb: dwc3:
> gadget: move cmd_endtransfer to extra function"), but it is brought back
> by merging. So delete it to fix compile error.
>
> Signed-off-by: Quanyang Wang
> ---
> Hi Bruce,
> Would you please help merge this patch to the branches:
> v5.15/standard/preempt-rt/sdkv5.15/xlnx-soc
> v5.15/standard/sdkv5.15/xlnx-soc
merged.
Bruce
> Thanks,
> Quanyang
> ---
> drivers/usb/dwc3/gadget.c | 38 +++---
> 1 file changed, 11 insertions(+), 27 deletions(-)
>
> diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
> index 9e9133ac9ab9b..79ea40f69db70 100644
> --- a/drivers/usb/dwc3/gadget.c
> +++ b/drivers/usb/dwc3/gadget.c
> @@ -3767,6 +3767,17 @@ void dwc3_stop_active_transfer(struct dwc3_ep *dep,
> bool force, bool interrupt)
> (dep->flags & DWC3_EP_END_TRANSFER_PENDING))
> return;
>
> + if (!interrupt)
> + dep->flags &= ~DWC3_EP_TRANSFER_STARTED;
> + else
> + dep->flags |= DWC3_EP_END_TRANSFER_PENDING;
> + /*
> + * when transfer is stopped with force rm bit false, it can be
> + * restarted by passing resource_index in params; don't loose it
> + */
> + if (force)
> + dep->resource_index = 0;
> +
> /*
>* NOTICE: We are violating what the Databook says about the
>* EndTransfer command. Ideally we would _always_ wait for the
> @@ -3797,33 +3808,6 @@ void dwc3_stop_active_transfer(struct dwc3_ep *dep,
> bool force, bool interrupt)
>* controller to handle the command completely before DWC3
>* remove requests attempts to unmap USB request buffers.
>*/
> -
> - cmd = DWC3_DEPCMD_ENDTRANSFER;
> - cmd |= force ? DWC3_DEPCMD_HIPRI_FORCERM : 0;
> - cmd |= interrupt ? DWC3_DEPCMD_CMDIOC : 0;
> - cmd |= DWC3_DEPCMD_PARAM(dep->resource_index);
> - memset(¶ms, 0, sizeof(params));
> - ret = dwc3_send_gadget_ep_cmd(dep, cmd, ¶ms);
> - WARN_ON_ONCE(ret);
> -
> - /*
> - * when transfer is stopped with force rm bit false, it can be
> - * restarted by passing resource_index in params; don't loose it
> - */
> - if (force)
> - dep->resource_index = 0;
> -
> - if (!interrupt)
> - dep->flags &= ~DWC3_EP_TRANSFER_STARTED;
> - else
> - dep->flags |= DWC3_EP_END_TRANSFER_PENDING;
> - /*
> - * when transfer is stopped with force rm bit false, it can be
> - * restarted by passing resource_index in params; don't loose it
> - */
> - if (force)
> - dep->resource_index = 0;
> -
> __dwc3_stop_active_transfer(dep, force, interrupt);
> }
>
> --
> 2.36.1
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#12362):
https://lists.yoctoproject.org/g/linux-yocto/message/12362
Mute This Topic: https://lists.yoctoproject.org/mt/98119766/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe:
https://lists.yoctoproject.org/g/linux-yocto/leave/6687884/21656/624485779/xyzzy
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] Reading file would overwrite reserved memory. Failed to load 'hello_world.bin - imx7d-pico - Uboot 2022.04
https://stackoverflow.com/questions/71073386/reading-file-would-overwrite-reserved-memory-failed-to-load-hello-world-bin Hi, I had this issue last year and I solved it via device tree. However, I used Yocto hardknott and uboot 2021.04 and Ubuntu 20.04. Now I use Yocto kirkstone and uboot 2022.04 and Ubuntu 22.04 I've been trying to resolve this issue for seven days now. I've already made several changes to the uboot and yocto/device tree configurations without success. Every help is welcome Note I tried: https://dantechrb.com/blog/how-to-build-and-debug-freertos-applications-for-cortexm4-on-mx6sx https://whycan.com/t_5474.html -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12361): https://lists.yoctoproject.org/g/linux-yocto/message/12361 Mute This Topic: https://lists.yoctoproject.org/mt/98149940/21656 Mute #address-cells:https://lists.yoctoproject.org/g/linux-yocto/mutehashtag/address-cells Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
