Re: [linux-yocto] [kernel-cache yocto-5.2] nxp-ls20xx: add kernel-cache configuration files for BSP nxp-ls20xx
merged. Bruce In message: [linux-yocto] [kernel-cache yocto-5.2] nxp-ls20xx: add kernel-cache configuration files for BSP nxp-ls20xx on 04/09/2019 Xulin Sun wrote: > This adds the cfg & scc files to support the LS2088A-RDB. > > Signed-off-by: Xulin Sun > --- > bsp/nxp-ls20xx/nxp-ls20xx-standard.scc | 8 ++ > bsp/nxp-ls20xx/nxp-ls20xx.cfg | 162 + > bsp/nxp-ls20xx/nxp-ls20xx.scc | 7 ++ > 3 files changed, 177 insertions(+) > create mode 100755 bsp/nxp-ls20xx/nxp-ls20xx-standard.scc > create mode 100755 bsp/nxp-ls20xx/nxp-ls20xx.cfg > create mode 100755 bsp/nxp-ls20xx/nxp-ls20xx.scc > > diff --git a/bsp/nxp-ls20xx/nxp-ls20xx-standard.scc > b/bsp/nxp-ls20xx/nxp-ls20xx-standard.scc > new file mode 100755 > index ..e0d9b2b7 > --- /dev/null > +++ b/bsp/nxp-ls20xx/nxp-ls20xx-standard.scc > @@ -0,0 +1,8 @@ > +define KMACHINE nxp-ls20xx > +define KTYPE standard > +define KARCH arm64 > + > +include ktypes/standard/standard.scc > +branch nxp-ls20xx > + > +include nxp-ls20xx.scc > diff --git a/bsp/nxp-ls20xx/nxp-ls20xx.cfg b/bsp/nxp-ls20xx/nxp-ls20xx.cfg > new file mode 100755 > index ..f554c916 > --- /dev/null > +++ b/bsp/nxp-ls20xx/nxp-ls20xx.cfg > @@ -0,0 +1,162 @@ > +.. > +.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_ARM64=y > +CONFIG_ARM64_VA_BITS_48=y > +CONFIG_ARCH_LAYERSCAPE=y > +CONFIG_SCHED_MC=y > +CONFIG_ARM_SMMU=y > +CONFIG_ARM_SMMU_V3=y > + > +CONFIG_PCI=y > +CONFIG_PCI_LAYERSCAPE=y > +CONFIG_PCI_HOST_GENERIC=y > +CONFIG_PCI_XGENE=y > +CONFIG_PCI_MSI=y > + > +CONFIG_CPU_FREQ=y > +CONFIG_CPU_FREQ_STAT=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_CPUFREQ_DT=y > +CONFIG_QORIQ_CPUFREQ=y > + > +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_DATAFLASH=y > +CONFIG_MTD_M25P80=y > +CONFIG_MTD_SST25L=y > +CONFIG_MTD_SPI_NOR=y > +CONFIG_MTD_RAW_NAND=y > +CONFIG_MTD_NAND_FSL_IFC=y > +CONFIG_SPI_FSL_QUADSPI=y > +CONFIG_SCSI_SAS_ATA=y > +CONFIG_SCSI_HISI_SAS=y > +CONFIG_ATA=y > +CONFIG_SATA_AHCI=y > +CONFIG_SATA_AHCI_PLATFORM=y > +CONFIG_AHCI_CEVA=y > +CONFIG_AHCI_XGENE=y > +CONFIG_AHCI_QORIQ=y > +CONFIG_SATA_SIL24=y > + > +CONFIG_FSL_XGMAC_MDIO=y > +CONFIG_HNS_DSAF=y > +CONFIG_HNS_ENET=y > +CONFIG_E1000=y > +CONFIG_E1000E=y > + > +CONFIG_SERIAL_8250=y > +CONFIG_SERIAL_8250_CONSOLE=y > +CONFIG_SERIAL_8250_DW=y > +CONFIG_SERIAL_OF_PLATFORM=y > +CONFIG_SERIAL_FSL_LPUART=y > +CONFIG_SERIAL_FSL_LPUART_CONSOLE=y > + > +CONFIG_SPI=y > +CONFIG_SPI_FSL_DSPI=y > +CONFIG_SPI_PL022=y > +CONFIG_SPI_NXP_FLEXSPI=y > + > +CONFIG_POWER_RESET_XGENE=y > +CONFIG_POWER_RESET_SYSCON=y > +CONFIG_THERMAL_GOV_POWER_ALLOCATOR=y > + > +CONFIG_THERMAL=y > +CONFIG_THERMAL_OF=y > +CONFIG_CPU_THERMAL=y > +CONFIG_THERMAL_EMULATION=y > +CONFIG_WATCHDOG=y > +CONFIG_ARM_SP805_WATCHDOG=y > + > +CONFIG_USB=y > +CONFIG_USB_OTG=y > +CONFIG_USB_XHCI_HCD=y > +CONFIG_USB_STORAGE=y > +CONFIG_USB_DWC3=y > +CONFIG_USB_DWC2=y > +CONFIG_USB_GADGET=y > + > +CONFIG_MMC=y > +CONFIG_MMC_ARMMMCI=y > +CONFIG_MMC_SDHCI=y > +CONFIG_MMC_SDHCI_PLTFM=y > +CONFIG_MMC_SDHCI_OF_ARASAN=y > +CONFIG_MMC_SDHCI_OF_ESDHC=y > +CONFIG_MMC_SDHCI_CADENCE=y > +CONFIG_MMC_SPI=y > +CONFIG_MMC_DW=y > + > +CONFIG_GPIOLIB=y > +CONFIG_OF_GPIO=y > + > +CONFIG_MDIO_DEVICE=y > +CONFIG_MDIO_BITBANG=y > +CONFIG_PHYLIB=y > +CONFIG_AQUANTIA_PHY=y > +CONFIG_CORTINA_PHY=y > + > +# > +# I2C support > +# > +CONFIG_I2C=y > +CONFIG_I2C_MUX=y > +CONFIG_I2C_IMX=y > +CONFIG_I2C_MUX_PCA954x=y > + > +CONFIG_RTC_CLASS=y > +CONFIG_RTC_DRV_DS3232=y > +CONFIG_RTC_DRV_PL031=y > +CONFIG_RTC_DRV_PCF2127=y > + > +CONFIG_DMADEVICES=y > +CONFIG_FSL_EDMA=y > +CONFIG_CMA=y > +CONFIG_DMA_CMA=y > + > +CONFIG_VFIO=y > +CONFIG_VFIO_PCI=y > + > +CONFIG_STAGING=y > +CONFIG_FSL_MC_BUS=y > +CONFIG_FSL_MC_DPIO=y > + > +CONFIG_CLK_QORIQ=y > + > +CONFIG_PHY_XGENE=y > + > +CONFIG_CRYPTO_DEV_FSL_CAAM=y > +CONFIG_CRYPTO_DEV_FSL_DPAA2_CAAM=y > +CONFIG_ARM64_CRYPTO=y > +CONFIG_CRYPTO_SHA1_ARM64_CE=y > +CONFIG_CRYPTO_SHA2_ARM64_CE=y > +CONFIG_CRYPTO_GHASH_ARM64_CE=y > +CONFIG_CRYPTO_AES_ARM64_CE_CCM=y > +CONFIG_CRYPTO_AES_ARM64_CE_BLK=y > +#
Re: [linux-yocto] [kernel-cache v5.2] ti-am335x: add base support
In message: [linux-yocto][kernel-cache v5.2] ti-am335x: add base support on 04/09/2019 Jun Miao wrote: > Hi Bruce, > > I am working ti boards(AM335x evm/sk/BBB) with am335x soc. > > Could you help me add scc/cfg to yocto-kernel-cache v5.2 branch. Looks good to me. This is now merged. Bruce > > > Jun Miao (1): > ti-am335x: add the basic scc/cfg enablement > > bsp/ti-am335x/ti-am335x-standard.scc | 7 + > bsp/ti-am335x/ti-am335x.cfg | 230 +++ > bsp/ti-am335x/ti-am335x.scc | 7 + > 3 files changed, 244 insertions(+) > create mode 100644 bsp/ti-am335x/ti-am335x-standard.scc > create mode 100644 bsp/ti-am335x/ti-am335x.cfg > create mode 100644 bsp/ti-am335x/ti-am335x.scc > > -- > 2.22.0 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [kernel-cache yocto-5.2][PATCH 0/1] xilinx-zynq: add kernel-cache support for zc702 and zc706 boards
In message: [linux-yocto][kernel-cache yocto-5.2][PATCH 0/1] xilinx-zynq: add kernel-cache support for zc702 and zc706 boards on 05/09/2019 quanyang.w...@windriver.com wrote: > From: Quanyang Wang > > Hi Bruce, > > The patch as below includes scc and cfg files for xilinx zc702/zc706 boards. > > Could you please merge this patch into yocto-kernel-cache, branch is > yocto-5.2? merged. Bruce > > Quanyang Wang (1): > xilinx-zynq: add the support for xlinx-zynq bsp > > bsp/xilinx-zynq/xilinx-zynq-standard.scc | 7 + > bsp/xilinx-zynq/xilinx-zynq.cfg | 199 +++ > bsp/xilinx-zynq/xilinx-zynq.scc | 8 + > 3 files changed, 214 insertions(+) > create mode 100644 bsp/xilinx-zynq/xilinx-zynq-standard.scc > create mode 100644 bsp/xilinx-zynq/xilinx-zynq.cfg > create mode 100644 bsp/xilinx-zynq/xilinx-zynq.scc > > -- > 2.17.1 > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH] spp: optimize strip_common_prefix function
I have this queued for testing now.
Bruce
On Fri, Aug 30, 2019 at 1:09 AM Zhaolong Zhang wrote:
>
> strip_common_prefix() is the hot path that executes on every input file.
> This patch sorts and uniqs the $include_paths by length descreasingly.
> And with the sorted $include_paths, the for-loop inside strip_common_prefix
> can break earlier, thus kernel_metadata task can be sped up by multiple times.
>
> Signed-off-by: Zhaolong Zhang
> ---
> tools/spp | 12
> 1 file changed, 12 insertions(+)
>
> diff --git a/tools/spp b/tools/spp
> index 1150ff3..cba52bb 100755
> --- a/tools/spp
> +++ b/tools/spp
> @@ -125,6 +125,7 @@ strip_common_prefix()
> if [ $this_len -lt $out_len ]; then
> relocated_name=$t
> out_len=$this_len
> + break
> fi
> # add a trailing slash to get corner cases where one may
> # have been added or not dropped
> @@ -133,6 +134,7 @@ strip_common_prefix()
> if [ $this_len -lt $out_len ]; then
> relocated_name=$t
> out_len=$this_len
> + break
> fi
> done
>
> @@ -297,6 +299,16 @@ infiles=$@
>
> processed_files=""
>
> +# this function also removes duplicated lines by `sort -u`
> +sort_by_len_dec()
> +{
> +for i in $@; do
> +echo $i
> +done | sort -u | awk '{ print length($0) " " $0; }' | sort -nr | cut
> -d ' ' -f 2-
> +}
> +
> +include_paths=$(sort_by_len_dec $include_paths)
> +
> ##
> ## create variables for use in scripts
> ##
> --
> 1.9.1
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH] [for all x86 branches] x86/boot: Save fields explicitly, zero out everything else
Since this is destined for -stable, I'm not going to merge the individual patch.
I'm holding nearly all 5.2 updates until the last introduction issues
are fixed. By that time, I'll have the next round of -stable updates
ready to go as well.
Cheers,
Bruce
On Thu, Sep 5, 2019 at 6:02 AM wrote:
>
> From: John Hubbard
>
> commit a90118c445cc7f07781de26a9684d4ec58bfcfd1 upstream.
>
> Recent gcc compilers (gcc 9.1) generate warnings about an out of bounds
> memset, if the memset goes accross several fields of a struct. This
> generated a couple of warnings on x86_64 builds in sanitize_boot_params().
>
> Fix this by explicitly saving the fields in struct boot_params
> that are intended to be preserved, and zeroing all the rest.
>
> [ tglx: Tagged for stable as it breaks the warning free build there as well ]
>
> Suggested-by: Thomas Gleixner
> Suggested-by: H. Peter Anvin
> Signed-off-by: John Hubbard
> Signed-off-by: Thomas Gleixner
> Cc: sta...@vger.kernel.org
> Link: https://lkml.kernel.org/r/20190731054627.5627-2-jhubb...@nvidia.com
> Signed-off-by: Greg Kroah-Hartman
> ---
> Fix the following build warning. It has been merge to 5.2.11.
> Please consider merging if it's worth.
>
> ./arch/x86/include/asm/bootparam_utils.h:40:3: warning: ‘memset’ offset [197,
> 448] from the object at ‘boot_params’ is out of the bounds of referenced
> subobject ‘ext_ramdisk_image’ with type
> ‘unsigned int’ at offset 192 [-Warray-bounds]
>
> ./arch/x86/include/asm/bootparam_utils.h:43:3: warning: ‘memset’ offset [493,
> 497] from the object at ‘boot_params’ is out of the bounds of referenced
> subobject ‘kbd_status’ with type ‘unsig
> ned char’ at offset 491 [-Warray-bounds]
>
> arch/x86/include/asm/bootparam_utils.h | 63
> ++
> 1 file changed, 48 insertions(+), 15 deletions(-)
>
> diff --git a/arch/x86/include/asm/bootparam_utils.h
> b/arch/x86/include/asm/bootparam_utils.h
> index f6f6ef4..7fed0fc 100644
> --- a/arch/x86/include/asm/bootparam_utils.h
> +++ b/arch/x86/include/asm/bootparam_utils.h
> @@ -18,6 +18,20 @@
> * Note: efi_info is commonly left uninitialized, but that field has a
> * private magic, so it is better to leave it unchanged.
> */
> +
> +#define sizeof_mbr(type, member) ({ sizeof(((type *)0)->member); })
> +
> +#define BOOT_PARAM_PRESERVE(struct_member) \
> + { \
> + .start = offsetof(struct boot_params, struct_member), \
> + .len = sizeof_mbr(struct boot_params, struct_member), \
> + }
> +
> +struct boot_params_to_save {
> + unsigned int start;
> + unsigned int len;
> +};
> +
> static void sanitize_boot_params(struct boot_params *boot_params)
> {
> /*
> @@ -35,21 +49,40 @@ static void sanitize_boot_params(struct boot_params
> *boot_params)
> * problems again.
> */
> if (boot_params->sentinel) {
> - /* fields in boot_params are left uninitialized, clear them */
> - boot_params->acpi_rsdp_addr = 0;
> - memset(_params->ext_ramdisk_image, 0,
> - (char *)_params->efi_info -
> - (char *)_params->ext_ramdisk_image);
> - memset(_params->kbd_status, 0,
> - (char *)_params->hdr -
> - (char *)_params->kbd_status);
> - memset(_params->_pad7[0], 0,
> - (char *)_params->edd_mbr_sig_buffer[0] -
> - (char *)_params->_pad7[0]);
> - memset(_params->_pad8[0], 0,
> - (char *)_params->eddbuf[0] -
> - (char *)_params->_pad8[0]);
> - memset(_params->_pad9[0], 0, sizeof(boot_params->_pad9));
> + static struct boot_params scratch;
> + char *bp_base = (char *)boot_params;
> + char *save_base = (char *)
> + int i;
> +
> + const struct boot_params_to_save to_save[] = {
> + BOOT_PARAM_PRESERVE(screen_info),
> + BOOT_PARAM_PRESERVE(apm_bios_info),
> + BOOT_PARAM_PRESERVE(tboot_addr),
> + BOOT_PARAM_PRESERVE(ist_info),
> + BOOT_PARAM_PRESERVE(acpi_rsdp_addr),
> + BOOT_PARAM_PRESERVE(hd0_info),
> + BOOT_PARAM_PRESERVE(hd1_info),
> + BOOT_PARAM_PRESERVE(sys_desc_table),
> + BOOT_PARAM_PRESERVE(olpc_ofw_header),
> + BOOT_PARAM_PRESERVE(efi_info),
> + BOOT_PARAM_PRESERVE(alt_mem_k),
> + BOOT_PARAM_PRESERVE(scratch),
> + BOOT_PARAM_PRESERVE(e820_entries),
> + BOOT_PARAM_PRESERVE(eddbuf_entries),
> + BOOT_PARAM_PRESERVE(edd_mbr_sig_buf_entries),
> +
[linux-yocto] [PATCH] [for all x86 branches] x86/boot: Save fields explicitly, zero out everything else
From: John Hubbard
commit a90118c445cc7f07781de26a9684d4ec58bfcfd1 upstream.
Recent gcc compilers (gcc 9.1) generate warnings about an out of bounds
memset, if the memset goes accross several fields of a struct. This
generated a couple of warnings on x86_64 builds in sanitize_boot_params().
Fix this by explicitly saving the fields in struct boot_params
that are intended to be preserved, and zeroing all the rest.
[ tglx: Tagged for stable as it breaks the warning free build there as well ]
Suggested-by: Thomas Gleixner
Suggested-by: H. Peter Anvin
Signed-off-by: John Hubbard
Signed-off-by: Thomas Gleixner
Cc: sta...@vger.kernel.org
Link: https://lkml.kernel.org/r/20190731054627.5627-2-jhubb...@nvidia.com
Signed-off-by: Greg Kroah-Hartman
---
Fix the following build warning. It has been merge to 5.2.11.
Please consider merging if it's worth.
./arch/x86/include/asm/bootparam_utils.h:40:3: warning: ‘memset’ offset [197,
448] from the object at ‘boot_params’ is out of the bounds of referenced
subobject ‘ext_ramdisk_image’ with type
‘unsigned int’ at offset 192 [-Warray-bounds]
./arch/x86/include/asm/bootparam_utils.h:43:3: warning: ‘memset’ offset [493,
497] from the object at ‘boot_params’ is out of the bounds of referenced
subobject ‘kbd_status’ with type ‘unsig
ned char’ at offset 491 [-Warray-bounds]
arch/x86/include/asm/bootparam_utils.h | 63 ++
1 file changed, 48 insertions(+), 15 deletions(-)
diff --git a/arch/x86/include/asm/bootparam_utils.h
b/arch/x86/include/asm/bootparam_utils.h
index f6f6ef4..7fed0fc 100644
--- a/arch/x86/include/asm/bootparam_utils.h
+++ b/arch/x86/include/asm/bootparam_utils.h
@@ -18,6 +18,20 @@
* Note: efi_info is commonly left uninitialized, but that field has a
* private magic, so it is better to leave it unchanged.
*/
+
+#define sizeof_mbr(type, member) ({ sizeof(((type *)0)->member); })
+
+#define BOOT_PARAM_PRESERVE(struct_member) \
+ { \
+ .start = offsetof(struct boot_params, struct_member), \
+ .len = sizeof_mbr(struct boot_params, struct_member), \
+ }
+
+struct boot_params_to_save {
+ unsigned int start;
+ unsigned int len;
+};
+
static void sanitize_boot_params(struct boot_params *boot_params)
{
/*
@@ -35,21 +49,40 @@ static void sanitize_boot_params(struct boot_params
*boot_params)
* problems again.
*/
if (boot_params->sentinel) {
- /* fields in boot_params are left uninitialized, clear them */
- boot_params->acpi_rsdp_addr = 0;
- memset(_params->ext_ramdisk_image, 0,
- (char *)_params->efi_info -
- (char *)_params->ext_ramdisk_image);
- memset(_params->kbd_status, 0,
- (char *)_params->hdr -
- (char *)_params->kbd_status);
- memset(_params->_pad7[0], 0,
- (char *)_params->edd_mbr_sig_buffer[0] -
- (char *)_params->_pad7[0]);
- memset(_params->_pad8[0], 0,
- (char *)_params->eddbuf[0] -
- (char *)_params->_pad8[0]);
- memset(_params->_pad9[0], 0, sizeof(boot_params->_pad9));
+ static struct boot_params scratch;
+ char *bp_base = (char *)boot_params;
+ char *save_base = (char *)
+ int i;
+
+ const struct boot_params_to_save to_save[] = {
+ BOOT_PARAM_PRESERVE(screen_info),
+ BOOT_PARAM_PRESERVE(apm_bios_info),
+ BOOT_PARAM_PRESERVE(tboot_addr),
+ BOOT_PARAM_PRESERVE(ist_info),
+ BOOT_PARAM_PRESERVE(acpi_rsdp_addr),
+ BOOT_PARAM_PRESERVE(hd0_info),
+ BOOT_PARAM_PRESERVE(hd1_info),
+ BOOT_PARAM_PRESERVE(sys_desc_table),
+ BOOT_PARAM_PRESERVE(olpc_ofw_header),
+ BOOT_PARAM_PRESERVE(efi_info),
+ BOOT_PARAM_PRESERVE(alt_mem_k),
+ BOOT_PARAM_PRESERVE(scratch),
+ BOOT_PARAM_PRESERVE(e820_entries),
+ BOOT_PARAM_PRESERVE(eddbuf_entries),
+ BOOT_PARAM_PRESERVE(edd_mbr_sig_buf_entries),
+ BOOT_PARAM_PRESERVE(edd_mbr_sig_buffer),
+ BOOT_PARAM_PRESERVE(e820_table),
+ BOOT_PARAM_PRESERVE(eddbuf),
+ };
+
+ memset(, 0, sizeof(scratch));
+
+ for (i = 0; i < ARRAY_SIZE(to_save); i++) {
+ memcpy(save_base + to_save[i].start,
+ bp_base + to_save[i].start, to_save[i].len);
+ }
+
+ memcpy(boot_params,
[linux-yocto] [kernel-cache yocto-5.2][PATCH 1/1] xilinx-zynq: add the support for xlinx-zynq bsp
From: Quanyang Wang This add cfg files to support xilinx zc702 and zc706 boards. Signed-off-by: Quanyang Wang --- bsp/xilinx-zynq/xilinx-zynq-standard.scc | 7 + bsp/xilinx-zynq/xilinx-zynq.cfg | 199 +++ bsp/xilinx-zynq/xilinx-zynq.scc | 8 + 3 files changed, 214 insertions(+) create mode 100644 bsp/xilinx-zynq/xilinx-zynq-standard.scc create mode 100644 bsp/xilinx-zynq/xilinx-zynq.cfg create mode 100644 bsp/xilinx-zynq/xilinx-zynq.scc diff --git a/bsp/xilinx-zynq/xilinx-zynq-standard.scc b/bsp/xilinx-zynq/xilinx-zynq-standard.scc new file mode 100644 index ..34856f90 --- /dev/null +++ b/bsp/xilinx-zynq/xilinx-zynq-standard.scc @@ -0,0 +1,7 @@ +define KMACHINE xilinx-zynq +define KTYPE standard +define KARCH arm + +include ktypes/standard + +include xilinx-zynq.scc diff --git a/bsp/xilinx-zynq/xilinx-zynq.cfg b/bsp/xilinx-zynq/xilinx-zynq.cfg new file mode 100644 index ..3b4cc64d --- /dev/null +++ b/bsp/xilinx-zynq/xilinx-zynq.cfg @@ -0,0 +1,199 @@ +CONFIG_ARCH_ZYNQ=y +CONFIG_SMP=y +CONFIG_NR_CPUS=4 +CONFIG_HOTPLUG_CPU=y +CONFIG_VMSPLIT_2G=y + +# +# Xilinx Specific Options +# +CONFIG_XILINX_PREFETCH=y + +# ERRATA +CONFIG_PL310_ERRATA_588369=y +CONFIG_ARM_ERRATA_720789=y +CONFIG_PL310_ERRATA_727915=y +CONFIG_PL310_ERRATA_753970=y +CONFIG_ARM_ERRATA_754322=y +CONFIG_PL310_ERRATA_769419=y +CONFIG_ARM_ERRATA_775420=y + +CONFIG_VFP=y +CONFIG_NEON=y + +# DMA +CONFIG_XILINX_DMA_ENGINES=y +CONFIG_AXI_DMAC=y +CONFIG_DMADEVICES=y +CONFIG_DMA_ENGINE=y +CONFIG_PL330_DMA=y +CONFIG_XILINX_DMA=y + +# Power Management +CONFIG_PMBUS=y +CONFIG_SENSORS_UCD9000=y + +# Watchdog +CONFIG_WATCHDOG=y +CONFIG_WATCHDOG_NOWAYOUT=y +CONFIG_CADENCE_WATCHDOG=y + +# GPIO +CONFIG_GPIOLIB=y +CONFIG_GPIO_SYSFS=y +CONFIG_GPIO_XILINX=y +CONFIG_GPIO_ZYNQ=y +CONFIG_GPIO_PCA953X=y + +CONFIG_KEYBOARD_GPIO=y +CONFIG_LEDS_GPIO=y +CONFIG_NEW_LEDS=y +CONFIG_LEDS_CLASS=y + +# UART +CONFIG_SERIAL_XILINX_PS_UART=y +CONFIG_SERIAL_XILINX_PS_UART_CONSOLE=y + +# PTP clock support +CONFIG_PTP_1588_CLOCK=y + +# AXI Ethernet +CONFIG_NET_VENDOR_XILINX=y +CONFIG_XILINX_AXI_EMAC=y +CONFIG_XILINX_AXI_EMAC_HWTSTAMP=y + +# Cadence Ethernet +CONFIG_MACB=y +CONFIG_MACB_USE_HWSTAMP=y + +# PHY +CONFIG_MARVELL_PHY=y +CONFIG_VITESSE_PHY=y + +# I2C +CONFIG_I2C=y +CONFIG_I2C_MUX=y +CONFIG_I2C_CHARDEV=y +CONFIG_I2C_MUX_PCA954x=y +CONFIG_I2C_CADENCE=y +CONFIG_I2C_XILINX=y + +# RTC +CONFIG_RTC_CLASS=y +CONFIG_RTC_DRV_PCF8563=y +CONFIG_RTC_DRV_DS1307=y + +CONFIG_COMMON_CLK_AXI_CLKGEN=y + +# SPI +CONFIG_SPI_CADENCE=y +CONFIG_SPI_ZYNQ_QSPI=y + +# MTD +CONFIG_MTD=y +CONFIG_MTD_OF_PARTS=y +CONFIG_MTD_BLOCK=y +CONFIG_MTD_M25P80=y +CONFIG_MTD_SPI_NOR=y +CONFIG_MTD_CFI=y +CONFIG_MTD_GEN_PROBE=y +CONFIG_MTD_PHYSMAP=y +CONFIG_MTD_PHYSMAP_OF=y + +CONFIG_SCSI=y +CONFIG_BLK_DEV_SD=y + +# MMC +CONFIG_MMC=y +CONFIG_MMC_SDHCI=y +CONFIG_MMC_SDHCI_PLTFM=y +CONFIG_MMC_SDHCI_OF_ARASAN=y + +# USB +CONFIG_USB_OTG=y +CONFIG_USB_CHIPIDEA=y +CONFIG_USB_CHIPIDEA_OF=y +CONFIG_USB_CHIPIDEA_PCI=y +CONFIG_USB_CHIPIDEA_UDC=y +CONFIG_USB_CHIPIDEA_HOST=y + +CONFIG_USB_GADGET=y +CONFIG_USB_GADGET_XILINX=y + +CONFIG_USB_PHY=y +CONFIG_USB_ULPI=y +CONFIG_NOP_USB_XCEIV=y + +# PCIe +CONFIG_PCI=y +CONFIG_PCI_MSI=y +CONFIG_PCIE_XILINX=y + +# Graphic +CONFIG_FB=y +CONFIG_FRAMEBUFFER_CONSOLE=y + +CONFIG_DRM=y +CONFIG_DRM_KMS_HELPER=y +CONFIG_DRM_XILINX=y +CONFIG_FB_XILINX=y + +CONFIG_DRM_I2C_ADV7511=y +CONFIG_DRM_I2C_ADV7511_AUDIO=y +CONFIG_DRM_I2C_ADV7533=y +CONFIG_DRM_I2C_ADV7511_CEC=y + +# FPGA +CONFIG_FPGA=y +CONFIG_FPGA_MGR_ZYNQ_FPGA=y +CONFIG_FPGA_BRIDGE=y +CONFIG_FPGA_REGION=y +CONFIG_OF_FPGA_REGION=y + +# Misc +CONFIG_INPUT=y +CONFIG_INPUT_MOUSEDEV=y +CONFIG_INPUT_EVDEV=y +CONFIG_CMA=y +CONFIG_DMA_CMA=y +CONFIG_UIO=y +CONFIG_UIO_PDRV_GENIRQ=y +CONFIG_UIO_XILINX_APM=y + +CONFIG_COMMON_CLK_SI570=y + +CONFIG_CPU_IDLE=y +CONFIG_ARM_CPUIDLE=y +CONFIG_ARM_ZYNQ_CPUIDLE=y +CONFIG_CPU_IDLE_GOV_LADDER=y +CONFIG_CPU_IDLE_GOV_MENU=y + +CONFIG_EEPROM_AT24=y + +CONFIG_MEDIA_SUPPORT=y +CONFIG_MEDIA_CAMERA_SUPPORT=y +CONFIG_MEDIA_CONTROLLER=y +CONFIG_VIDEO_V4L2_SUBDEV_API=y +CONFIG_V4L_PLATFORM_DRIVERS=y +CONFIG_MEDIA_SUBDRV_AUTOSELECT=y +CONFIG_MEDIA_USB_SUPPORT=y + +CONFIG_SOUND=y +CONFIG_SND=y +CONFIG_SND_SOC=y +CONFIG_SND_SOC_ADI=y +CONFIG_SND_SOC_ADI_AXI_I2S=y +CONFIG_SND_SOC_ADI_AXI_SPDIF=y +CONFIG_SND_SIMPLE_CARD=y + +CONFIG_DEBUG_LL=y +CONFIG_DEBUG_ZYNQ_UART1=y +CONFIG_EARLY_PRINTK=y + +CONFIG_IIO=y +CONFIG_XILINX_TRAFGEN=y +CONFIG_IIO_CONFIGFS=y +CONFIG_IIO_SW_DEVICE=y +CONFIG_IIO_SW_TRIGGER=y +CONFIG_OF_OVERLAY=y +CONFIG_OF_CONFIGFS=y diff --git a/bsp/xilinx-zynq/xilinx-zynq.scc b/bsp/xilinx-zynq/xilinx-zynq.scc new file mode 100644 index ..621f6954 --- /dev/null +++ b/bsp/xilinx-zynq/xilinx-zynq.scc @@ -0,0 +1,8 @@ +include arch/arm/arm.scc nopatch +include cfg/usb-mass-storage.scc +include features/spi/spi.scc +include features/spi/spidev.scc +include features/usb/ehci-hcd.scc +include features/debug/debug-kernel.scc + +kconf hardware
[linux-yocto] [kernel-cache yocto-5.2][PATCH 0/1] xilinx-zynq: add kernel-cache support for zc702 and zc706 boards
From: Quanyang Wang Hi Bruce, The patch as below includes scc and cfg files for xilinx zc702/zc706 boards. Could you please merge this patch into yocto-kernel-cache, branch is yocto-5.2? Quanyang Wang (1): xilinx-zynq: add the support for xlinx-zynq bsp bsp/xilinx-zynq/xilinx-zynq-standard.scc | 7 + bsp/xilinx-zynq/xilinx-zynq.cfg | 199 +++ bsp/xilinx-zynq/xilinx-zynq.scc | 8 + 3 files changed, 214 insertions(+) create mode 100644 bsp/xilinx-zynq/xilinx-zynq-standard.scc create mode 100644 bsp/xilinx-zynq/xilinx-zynq.cfg create mode 100644 bsp/xilinx-zynq/xilinx-zynq.scc -- 2.17.1 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
