Date   

Re: [isar-cip-core PATCH 0/4] Add rzg2m support

Chris Paterson
 

Hello,

From: Gylstorff Quirin <quirin.gylstorff@...>
Sent: 06 November 2019 14:37



On 11/6/19 3:12 PM, Jan Kiszka wrote:
Nice! Beyond building and actually deploying this, what else would be
missing to hook up the result with a board in the lab?
We would need to change the configuration of the LAVA jobs in [1] to
use the tarballs generated by the build.
Yes, at the moment they are painfully hardcoded. I plan to at least have them point to the 'latest' CIP Core.
However for your use case, you'll want to test the binaries you just created.

I guess we should decide on whether we want to re-use linux-cip-ci for CIP Core testing, or just end up creating a separate version for CIP Core.
Linux-cip-ci could easily be modified to support both CIP Linux & Core testing (we could just add another version of submit_tests.sh for CIP Core), and I think this would be easier to maintain down the line.

Is this something you'd like to have a go at?
I'm happy to do it, but I may struggle to find time in the next few weeks.

Kind regards, Chris


[1]:
https://gitlab.com/cip-project/cip-testing/linux-cip-
ci/blob/next/lava_templates/

From what I see the actions use a hardcoded rootfs url to boot via nfs.
We could use the same template mechanism from Chris for dtb and Kernel
for the rootfs.

Kind regards,

Quirin


Re: [isar-cip-core PATCH 3/4] hihope-rzg2m: Add board support

Quirin Gylstorff
 

On 11/6/19 4:38 PM, Chris Paterson wrote:
Hello Quirin,
Thank you for the patch.

From: cip-dev-bounces@... <cip-dev-bounces@...
project.org> On Behalf Of Q. Gylstorff
Sent: 06 November 2019 12:45

From: Quirin Gylstorff <quirin.gylstorff@...>

The hihope-rzg2m is a ARM64 reference platform for the CIP project.

Signed-off-by: Quirin Gylstorff <quirin.gylstorff@...>
---
board-rzg2m.yml | 16 +
conf/machine/hihope-rzg2m.conf | 17 +
.../linux/files/hihope-rzg2m_defconfig | 330 ++++++++++++++++++
wic/hihope-rzg2m.wks | 15 +
4 files changed, 378 insertions(+)
create mode 100644 board-rzg2m.yml
create mode 100644 conf/machine/hihope-rzg2m.conf
create mode 100644 recipes-kernel/linux/files/hihope-rzg2m_defconfig
create mode 100644 wic/hihope-rzg2m.wks

diff --git a/board-rzg2m.yml b/board-rzg2m.yml
new file mode 100644
index 0000000..f68c7b8
--- /dev/null
+++ b/board-rzg2m.yml
@@ -0,0 +1,16 @@
+#
+# CIP Core, generic profile
+#
+# Copyright (c) Siemens AG, 2019
+#
+# Authors:
+# Quirin Gylstorff <quirin.gylstorff@...>
+#
+# SPDX-License-Identifier: MIT
+#
+
+header:
+ version: 8
+
+machine: hihope-rzg2m
+target: cip-core-image
diff --git a/conf/machine/hihope-rzg2m.conf b/conf/machine/hihope-
rzg2m.conf
new file mode 100644
index 0000000..5c456c7
--- /dev/null
+++ b/conf/machine/hihope-rzg2m.conf
@@ -0,0 +1,17 @@
+#
+# CIP Core, generic profile
+#
+# Copyright (c) Siemens AG, 2019
+#
+# Authors:
+# Quirin Gylstorff <quirin.gylstorff@...>
+#
+# SPDX-License-Identifier: MIT
+#
+
+DISTRO_ARCH = "arm64"
+
+IMAGE_TYPE ?= "wic-img"
+
+DTB_FILE = "r8a774a1-hihope-rzg2m.dtb"
Should be r8a774a1-hihope-rzg2m-ex.dtb. The 'ex' is the sub-board that adds Ethernet/PCIe/CAN etc.
OK, I will change both occurences and post a version 2.

+IMAGE_BOOT_FILES = "${KERNEL_IMAGE} ${DTB_FILE}"
diff --git a/recipes-kernel/linux/files/hihope-rzg2m_defconfig b/recipes-
kernel/linux/files/hihope-rzg2m_defconfig
new file mode 100644
index 0000000..f35793c
--- /dev/null
+++ b/recipes-kernel/linux/files/hihope-rzg2m_defconfig
Just to check, where did you copy this config from?
I used [0] as base.
Is there a way that the configuration could be taken directly from cip-kernel-config[0] rather than creating a copy that will need separate maintenance here?
I ask because there is currently a merge request open[1] that will update renesas_defconfig.
[0] https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/blob/master/4.19.y-cip/arm64/renesas_defconfig
[1] https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/merge_requests/15
I will look into it using the cip-kernel-config instead of using copies in isar.


Quirin


Re: [isar-cip-core PATCH 4/4] ci: add hihope-rzg2m to ci chain

Chris Paterson
 

Hello Quirin,

From: cip-dev-bounces@... <cip-dev-bounces@...
project.org> On Behalf Of Q. Gylstorff
Sent: 06 November 2019 12:45

From: Quirin Gylstorff <quirin.gylstorff@...>

Signed-off-by: Quirin Gylstorff <quirin.gylstorff@...>
---
.gitlab-ci.yml | 4 ++++
1 file changed, 4 insertions(+)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 36c152a..991862b 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -23,3 +23,7 @@ all:
- sudo rm -rf build/tmp
- kas build kas.yml:board-iwg20m.yml:opt-rt.yml
- scripts/deploy-cip-core.sh buster iwg20m r8a7743-iwg20d-q7-dbcm-ca.dtb
+
+ - sudo rm -rf build/tmp
+ - kas build kas.yml:board-rzg2m.yml:opt-rt.yml
+ - scripts/deploy-cip-core.sh buster hihope-rz2gm r8a774a1-hihope-
rzg2m.dtb
This'll need to be r8a774a1-hihope-rzg2m-ex.dtb

Kind regards, Chris

--
2.20.1

_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev


Re: [isar-cip-core PATCH 3/4] hihope-rzg2m: Add board support

Chris Paterson
 

Hello Quirin,

Thank you for the patch.

From: cip-dev-bounces@... <cip-dev-bounces@...
project.org> On Behalf Of Q. Gylstorff
Sent: 06 November 2019 12:45

From: Quirin Gylstorff <quirin.gylstorff@...>

The hihope-rzg2m is a ARM64 reference platform for the CIP project.

Signed-off-by: Quirin Gylstorff <quirin.gylstorff@...>
---
board-rzg2m.yml | 16 +
conf/machine/hihope-rzg2m.conf | 17 +
.../linux/files/hihope-rzg2m_defconfig | 330 ++++++++++++++++++
wic/hihope-rzg2m.wks | 15 +
4 files changed, 378 insertions(+)
create mode 100644 board-rzg2m.yml
create mode 100644 conf/machine/hihope-rzg2m.conf
create mode 100644 recipes-kernel/linux/files/hihope-rzg2m_defconfig
create mode 100644 wic/hihope-rzg2m.wks

diff --git a/board-rzg2m.yml b/board-rzg2m.yml
new file mode 100644
index 0000000..f68c7b8
--- /dev/null
+++ b/board-rzg2m.yml
@@ -0,0 +1,16 @@
+#
+# CIP Core, generic profile
+#
+# Copyright (c) Siemens AG, 2019
+#
+# Authors:
+# Quirin Gylstorff <quirin.gylstorff@...>
+#
+# SPDX-License-Identifier: MIT
+#
+
+header:
+ version: 8
+
+machine: hihope-rzg2m
+target: cip-core-image
diff --git a/conf/machine/hihope-rzg2m.conf b/conf/machine/hihope-
rzg2m.conf
new file mode 100644
index 0000000..5c456c7
--- /dev/null
+++ b/conf/machine/hihope-rzg2m.conf
@@ -0,0 +1,17 @@
+#
+# CIP Core, generic profile
+#
+# Copyright (c) Siemens AG, 2019
+#
+# Authors:
+# Quirin Gylstorff <quirin.gylstorff@...>
+#
+# SPDX-License-Identifier: MIT
+#
+
+DISTRO_ARCH = "arm64"
+
+IMAGE_TYPE ?= "wic-img"
+
+DTB_FILE = "r8a774a1-hihope-rzg2m.dtb"
Should be r8a774a1-hihope-rzg2m-ex.dtb. The 'ex' is the sub-board that adds Ethernet/PCIe/CAN etc.

+IMAGE_BOOT_FILES = "${KERNEL_IMAGE} ${DTB_FILE}"
diff --git a/recipes-kernel/linux/files/hihope-rzg2m_defconfig b/recipes-
kernel/linux/files/hihope-rzg2m_defconfig
new file mode 100644
index 0000000..f35793c
--- /dev/null
+++ b/recipes-kernel/linux/files/hihope-rzg2m_defconfig
Just to check, where did you copy this config from?

Is there a way that the configuration could be taken directly from cip-kernel-config[0] rather than creating a copy that will need separate maintenance here?
I ask because there is currently a merge request open[1] that will update renesas_defconfig.

[0] https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/blob/master/4.19.y-cip/arm64/renesas_defconfig
[1] https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/merge_requests/15

Kind regards, Chris


@@ -0,0 +1,330 @@
+CONFIG_SYSVIPC=y
+CONFIG_POSIX_MQUEUE=y
+CONFIG_AUDIT=y
+CONFIG_NO_HZ_IDLE=y
+CONFIG_HIGH_RES_TIMERS=y
+CONFIG_PREEMPT=y
+CONFIG_IRQ_TIME_ACCOUNTING=y
+CONFIG_BSD_PROCESS_ACCT=y
+CONFIG_BSD_PROCESS_ACCT_V3=y
+CONFIG_TASKSTATS=y
+CONFIG_TASK_DELAY_ACCT=y
+CONFIG_TASK_XACCT=y
+CONFIG_TASK_IO_ACCOUNTING=y
+CONFIG_IKCONFIG=y
+CONFIG_IKCONFIG_PROC=y
+CONFIG_MEMCG=y
+CONFIG_MEMCG_SWAP=y
+CONFIG_BLK_CGROUP=y
+CONFIG_CGROUP_PIDS=y
+CONFIG_CGROUP_HUGETLB=y
+CONFIG_CPUSETS=y
+CONFIG_CGROUP_DEVICE=y
+CONFIG_CGROUP_CPUACCT=y
+CONFIG_CGROUP_PERF=y
+CONFIG_USER_NS=y
+CONFIG_SCHED_AUTOGROUP=y
+CONFIG_BLK_DEV_INITRD=y
+# CONFIG_COMPAT_BRK is not set
+CONFIG_PROFILING=y
+CONFIG_ARCH_RENESAS=y
+CONFIG_ARCH_R8A774A1=y
+CONFIG_ARCH_R8A774C0=y
+CONFIG_PCI=y
+CONFIG_PCIEPORTBUS=y
+CONFIG_HOTPLUG_PCI_PCIE=y
+CONFIG_PCI_IOV=y
+CONFIG_HOTPLUG_PCI=y
+CONFIG_PCIE_RCAR=y
+CONFIG_PCI_HOST_GENERIC=y
+# CONFIG_CAVIUM_ERRATUM_22375 is not set
+# CONFIG_CAVIUM_ERRATUM_23154 is not set
+# CONFIG_CAVIUM_ERRATUM_27456 is not set
+# CONFIG_CAVIUM_ERRATUM_30115 is not set
+# CONFIG_QCOM_FALKOR_ERRATUM_1003 is not set
+# CONFIG_QCOM_FALKOR_ERRATUM_1009 is not set
+# CONFIG_QCOM_QDF2400_ERRATUM_0065 is not set
+# CONFIG_SOCIONEXT_SYNQUACER_PREITS is not set
+# CONFIG_HISILICON_ERRATUM_161600802 is not set
+CONFIG_ARM64_VA_BITS_48=y
+CONFIG_SCHED_MC=y
+CONFIG_NR_CPUS=8
+CONFIG_SECCOMP=y
+CONFIG_KEXEC=y
+CONFIG_CRASH_DUMP=y
+CONFIG_XEN=y
+# CONFIG_ARM64_LSE_ATOMICS is not set
+# CONFIG_ARM64_RAS_EXTN is not set
+CONFIG_COMPAT=y
+CONFIG_HIBERNATION=y
+CONFIG_WQ_POWER_EFFICIENT_DEFAULT=y
+CONFIG_CPU_IDLE=y
+CONFIG_ARM_CPUIDLE=y
+CONFIG_CPU_FREQ=y
+CONFIG_CPUFREQ_DT=y
+# CONFIG_DMIID is not set
+CONFIG_VIRTUALIZATION=y
+CONFIG_KVM=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
+CONFIG_JUMP_LABEL=y
+CONFIG_BLK_DEV_INTEGRITY=y
+# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
+CONFIG_KSM=y
+CONFIG_TRANSPARENT_HUGEPAGE=y
+CONFIG_CMA=y
+CONFIG_NET=y
+CONFIG_PACKET=y
+CONFIG_UNIX=y
+CONFIG_INET=y
+CONFIG_IP_MULTICAST=y
+CONFIG_IP_PNP=y
+CONFIG_IP_PNP_DHCP=y
+CONFIG_IP_PNP_BOOTP=y
+# CONFIG_IPV6 is not set
+CONFIG_NETFILTER=y
+CONFIG_CAN=y
+CONFIG_CAN_RCAR=y
+CONFIG_CAN_RCAR_CANFD=y
+CONFIG_DEVTMPFS=y
+CONFIG_DEVTMPFS_MOUNT=y
+CONFIG_DMA_CMA=y
+CONFIG_CMA_SIZE_MBYTES=128
+CONFIG_CMA_ALIGNMENT=9
+CONFIG_MTD=y
+CONFIG_MTD_BLOCK=y
+CONFIG_MTD_SPI_NOR=y
+CONFIG_BLK_DEV_LOOP=y
+CONFIG_VIRTIO_BLK=y
+CONFIG_SRAM=y
+# CONFIG_SCSI_PROC_FS is not set
+CONFIG_BLK_DEV_SD=y
+CONFIG_SCSI_SAS_LIBSAS=y
+CONFIG_SCSI_SAS_ATA=y
+CONFIG_ATA=y
+# CONFIG_SATA_PMP is not set
+CONFIG_SATA_RCAR=y
+CONFIG_NETDEVICES=y
+CONFIG_TUN=y
+CONFIG_VIRTIO_NET=y
+# CONFIG_CAVIUM_PTP is not set
+CONFIG_RAVB=y
+CONFIG_MDIO_BUS_MUX_MMIOREG=y
+CONFIG_MICREL_PHY=y
+CONFIG_REALTEK_PHY=y
+# CONFIG_WLAN is not set
+CONFIG_INPUT_MATRIXKMAP=y
+CONFIG_INPUT_EVDEV=y
+# CONFIG_KEYBOARD_ATKBD is not set
+CONFIG_KEYBOARD_GPIO=y
+# CONFIG_MOUSE_PS2 is not set
+CONFIG_INPUT_MISC=y
+# CONFIG_SERIO is not set
+CONFIG_SERIAL_SH_SCI=y
+CONFIG_VIRTIO_CONSOLE=y
+# CONFIG_HW_RANDOM is not set
+CONFIG_I2C_CHARDEV=y
+CONFIG_I2C_MUX=y
+CONFIG_I2C_MUX_PCA954x=y
+CONFIG_I2C_DESIGNWARE_PLATFORM=y
+CONFIG_I2C_SH_MOBILE=y
+CONFIG_I2C_RCAR=y
+CONFIG_SPI=y
+CONFIG_SPI_SH_MSIOF=y
+CONFIG_SPI_SPIDEV=y
+CONFIG_SPMI=y
+CONFIG_PINCTRL_SINGLE=y
+CONFIG_GPIO_GENERIC_PLATFORM=y
+CONFIG_GPIO_RCAR=y
+CONFIG_GPIO_PCA953X=y
+CONFIG_GPIO_BD9571MWV=y
+CONFIG_THERMAL=y
+CONFIG_THERMAL_GOV_POWER_ALLOCATOR=y
+CONFIG_CPU_THERMAL=y
+CONFIG_THERMAL_EMULATION=y
+CONFIG_RCAR_THERMAL=y
+CONFIG_RCAR_GEN3_THERMAL=y
+CONFIG_WATCHDOG=y
+CONFIG_RENESAS_WDT=y
+CONFIG_MFD_BD9571MWV=y
+CONFIG_REGULATOR=y
+CONFIG_REGULATOR_FIXED_VOLTAGE=y
+CONFIG_REGULATOR_BD9571MWV=y
+CONFIG_REGULATOR_GPIO=y
+CONFIG_REGULATOR_PWM=y
+CONFIG_MEDIA_SUPPORT=y
+CONFIG_MEDIA_CAMERA_SUPPORT=y
+CONFIG_MEDIA_SDR_SUPPORT=y
+CONFIG_MEDIA_CONTROLLER=y
+CONFIG_VIDEO_V4L2_SUBDEV_API=y
+CONFIG_V4L_PLATFORM_DRIVERS=y
+CONFIG_VIDEO_RCAR_CSI2=y
+CONFIG_VIDEO_RCAR_VIN=y
+CONFIG_V4L_MEM2MEM_DRIVERS=y
+CONFIG_VIDEO_RENESAS_FDP1=y
+CONFIG_VIDEO_RENESAS_FCP=y
+CONFIG_VIDEO_RENESAS_VSP1=y
+CONFIG_SDR_PLATFORM_DRIVERS=y
+CONFIG_VIDEO_RCAR_DRIF=y
+# CONFIG_MEDIA_SUBDRV_AUTOSELECT is not set
+CONFIG_VIDEO_ADV748X=y
+# CONFIG_MEDIA_TUNER_SIMPLE is not set
+# CONFIG_MEDIA_TUNER_TDA18250 is not set
+# CONFIG_MEDIA_TUNER_TDA8290 is not set
+# CONFIG_MEDIA_TUNER_TDA827X is not set
+# CONFIG_MEDIA_TUNER_TDA18271 is not set
+# CONFIG_MEDIA_TUNER_TDA9887 is not set
+# CONFIG_MEDIA_TUNER_TEA5761 is not set
+# CONFIG_MEDIA_TUNER_TEA5767 is not set
+# CONFIG_MEDIA_TUNER_MSI001 is not set
+# CONFIG_MEDIA_TUNER_MT20XX is not set
+# CONFIG_MEDIA_TUNER_MT2060 is not set
+# CONFIG_MEDIA_TUNER_MT2063 is not set
+# CONFIG_MEDIA_TUNER_MT2266 is not set
+# CONFIG_MEDIA_TUNER_MT2131 is not set
+# CONFIG_MEDIA_TUNER_QT1010 is not set
+# CONFIG_MEDIA_TUNER_XC2028 is not set
+# CONFIG_MEDIA_TUNER_XC5000 is not set
+# CONFIG_MEDIA_TUNER_XC4000 is not set
+# CONFIG_MEDIA_TUNER_MXL5005S is not set
+# CONFIG_MEDIA_TUNER_MXL5007T is not set
+# CONFIG_MEDIA_TUNER_MC44S803 is not set
+# CONFIG_MEDIA_TUNER_MAX2165 is not set
+# CONFIG_MEDIA_TUNER_TDA18218 is not set
+# CONFIG_MEDIA_TUNER_FC0011 is not set
+# CONFIG_MEDIA_TUNER_FC0012 is not set
+# CONFIG_MEDIA_TUNER_FC0013 is not set
+# CONFIG_MEDIA_TUNER_TDA18212 is not set
+# CONFIG_MEDIA_TUNER_E4000 is not set
+# CONFIG_MEDIA_TUNER_FC2580 is not set
+# CONFIG_MEDIA_TUNER_M88RS6000T is not set
+# CONFIG_MEDIA_TUNER_TUA9001 is not set
+# CONFIG_MEDIA_TUNER_SI2157 is not set
+# CONFIG_MEDIA_TUNER_IT913X is not set
+# CONFIG_MEDIA_TUNER_R820T is not set
+# CONFIG_MEDIA_TUNER_MXL301RF is not set
+# CONFIG_MEDIA_TUNER_QM1D1C0042 is not set
+# CONFIG_MEDIA_TUNER_QM1D1B0004 is not set
+CONFIG_DRM=y
+CONFIG_DRM_I2C_NXP_TDA998X=y
+CONFIG_DRM_RCAR_DU=y
+CONFIG_DRM_RCAR_DW_HDMI=y
+CONFIG_DRM_RCAR_LVDS=y
+CONFIG_DRM_DUMB_VGA_DAC=y
+CONFIG_DRM_THINE_THC63LVD1024=y
+CONFIG_DRM_DW_HDMI_AHB_AUDIO=y
+CONFIG_DRM_DW_HDMI_I2S_AUDIO=y
+CONFIG_DRM_DW_HDMI_CEC=y
+CONFIG_FB_MODE_HELPERS=y
+CONFIG_BACKLIGHT_LCD_SUPPORT=y
+# CONFIG_LCD_CLASS_DEVICE is not set
+# CONFIG_BACKLIGHT_GENERIC is not set
+CONFIG_BACKLIGHT_PWM=y
+CONFIG_LOGO=y
+# CONFIG_LOGO_LINUX_MONO is not set
+# CONFIG_LOGO_LINUX_VGA16 is not set
+CONFIG_SOUND=y
+CONFIG_SND=y
+# CONFIG_SND_SPI is not set
+# CONFIG_SND_USB is not set
+CONFIG_SND_SOC=y
+CONFIG_SND_SOC_RCAR=y
+CONFIG_SND_SOC_AK4613=y
+CONFIG_SND_SOC_PCM3168A_I2C=y
+CONFIG_SND_SIMPLE_CARD=y
+CONFIG_SND_SIMPLE_SCU_CARD=y
+CONFIG_SND_AUDIO_GRAPH_CARD=y
+CONFIG_USB=y
+CONFIG_USB_OTG=y
+CONFIG_USB_XHCI_HCD=y
+CONFIG_USB_XHCI_PLATFORM=y
+CONFIG_USB_EHCI_HCD=y
+CONFIG_USB_EHCI_ROOT_HUB_TT=y
+CONFIG_USB_EHCI_HCD_PLATFORM=y
+CONFIG_USB_OHCI_HCD=y
+CONFIG_USB_OHCI_HCD_PLATFORM=y
+CONFIG_USB_RENESAS_USBHS_HCD=y
+CONFIG_USB_RENESAS_USBHS=y
+CONFIG_USB_STORAGE=y
+CONFIG_USB_HSIC_USB3503=y
+CONFIG_NOP_USB_XCEIV=y
+CONFIG_USB_ULPI=y
+CONFIG_USB_GADGET=y
+CONFIG_USB_RENESAS_USBHS_UDC=y
+CONFIG_USB_RENESAS_USB3=y
+CONFIG_USB_SNP_UDC_PLAT=y
+CONFIG_USB_BDC_UDC=y
+CONFIG_MMC=y
+CONFIG_MMC_SDHI=y
+CONFIG_NEW_LEDS=y
+CONFIG_LEDS_CLASS=y
+CONFIG_LEDS_GPIO=y
+CONFIG_LEDS_PWM=y
+CONFIG_LEDS_TRIGGERS=y
+CONFIG_LEDS_TRIGGER_HEARTBEAT=y
+CONFIG_LEDS_TRIGGER_CPU=y
+CONFIG_LEDS_TRIGGER_DEFAULT_ON=y
+CONFIG_EDAC=y
+CONFIG_RTC_CLASS=y
+CONFIG_RTC_DRV_RX8581=y
+CONFIG_DMADEVICES=y
+CONFIG_RCAR_DMAC=y
+CONFIG_RENESAS_USB_DMAC=y
+CONFIG_VFIO=y
+CONFIG_VFIO_PCI=y
+CONFIG_VIRTIO_PCI=y
+CONFIG_VIRTIO_BALLOON=y
+CONFIG_VIRTIO_MMIO=y
+CONFIG_CHROME_PLATFORMS=y
+CONFIG_COMMON_CLK_CS2000_CP=y
+# CONFIG_COMMON_CLK_XGENE is not set
+CONFIG_COMMON_CLK_VC5=y
+CONFIG_CLK_RCAR_USB2_CLOCK_SEL=y
+CONFIG_HWSPINLOCK=y
+# CONFIG_FSL_ERRATUM_A008585 is not set
+# CONFIG_HISILICON_ERRATUM_161010101 is not set
+# CONFIG_ARM64_ERRATUM_858921 is not set
+CONFIG_MAILBOX=y
+CONFIG_IOMMU_IO_PGTABLE_LPAE=y
+CONFIG_EXTCON_USB_GPIO=y
+CONFIG_IIO=y
+CONFIG_MAX9611=y
+CONFIG_PWM=y
+CONFIG_PWM_RCAR=y
+CONFIG_RESET_CONTROLLER=y
+CONFIG_PHY_RCAR_GEN3_PCIE=y
+CONFIG_PHY_RCAR_GEN3_USB2=y
+CONFIG_PHY_RCAR_GEN3_USB3=y
+CONFIG_TEE=y
+CONFIG_OPTEE=y
+CONFIG_EXT4_FS=y
+CONFIG_EXT4_FS_POSIX_ACL=y
+CONFIG_FANOTIFY=y
+CONFIG_QUOTA=y
+CONFIG_AUTOFS4_FS=y
+CONFIG_VFAT_FS=y
+CONFIG_TMPFS=y
+CONFIG_HUGETLBFS=y
+CONFIG_CONFIGFS_FS=y
+CONFIG_SQUASHFS=y
+CONFIG_NFS_FS=y
+CONFIG_NFS_V4=y
+CONFIG_NFS_V4_1=y
+CONFIG_NFS_V4_2=y
+CONFIG_ROOT_NFS=y
+CONFIG_NLS_CODEPAGE_437=y
+CONFIG_NLS_ISO8859_1=y
+CONFIG_CRYPTO_ANSI_CPRNG=y
+# CONFIG_CRYPTO_DEV_VIRTIO is not set
+CONFIG_CRYPTO_DEV_CCREE=y
+CONFIG_PRINTK_TIME=y
+CONFIG_MAGIC_SYSRQ=y
+CONFIG_DEBUG_KERNEL=y
+# CONFIG_SCHED_DEBUG is not set
+# CONFIG_DEBUG_PREEMPT is not set
+CONFIG_PROVE_LOCKING=y
+# CONFIG_FTRACE is not set
diff --git a/wic/hihope-rzg2m.wks b/wic/hihope-rzg2m.wks
new file mode 100644
index 0000000..c0a9f77
--- /dev/null
+++ b/wic/hihope-rzg2m.wks
@@ -0,0 +1,15 @@
+#
+# CIP Core, generic profile
+#
+# Copyright (c) Siemens AG, 2019
+#
+# Authors:
+# Quirin Gylstorff <quirin.gylstorff@...>
+#
+# SPDX-License-Identifier: MIT
+#
+
+part /boot --source bootimg-partition --ondisk mmcblk0 --fstype vfat --label
boot --align 1 --size 32M --extra-space 0
+
+# Rootfs partition
+part / --source rootfs --ondisk mmcblk0 --fstype ext4 --label root --align 1024 --
size 2G --active
--
2.20.1

_______________________________________________
cip-dev mailing list
cip-dev@...
https://lists.cip-project.org/mailman/listinfo/cip-dev


Re: [isar-cip-core PATCH 0/4] Add rzg2m support

Quirin Gylstorff
 

On 11/6/19 3:12 PM, Jan Kiszka wrote:
Nice! Beyond building and actually deploying this, what else would be
missing to hook up the result with a board in the lab?
We would need to change the configuration of the LAVA jobs in [1] to
use the tarballs generated by the build.

[1]: https://gitlab.com/cip-project/cip-testing/linux-cip-ci/blob/next/lava_templates/

From what I see the actions use a hardcoded rootfs url to boot via nfs.
We could use the same template mechanism from Chris for dtb and Kernel for the rootfs.

Kind regards,

Quirin


Re: [isar-cip-core PATCH 0/4] Add rzg2m support

Jan Kiszka
 

On 06.11.19 13:44, Q. Gylstorff wrote:
From: Quirin Gylstorff <quirin.gylstorff@...>

Add the rzg2m reference board.
Add the option to build rootfs tarballs for LAVA tests.
This option needs to be activated in the gitlab-ci.yml by
adding it to the builds for testing.
Nice! Beyond building and actually deploying this, what else would be
missing to hook up the result with a board in the lab?

Jan


Quirin Gylstorff (4):
kas: Increase Isar version
classes: add wic-targz-img.bbclass
hihope-rzg2m: Add board support
ci: add hihope-rzg2m to ci chain

.gitlab-ci.yml | 4 +
board-rzg2m.yml | 16 +
classes/wic-targz-img.bbclass | 13 +
conf/machine/bbb.conf | 2 +-
conf/machine/hihope-rzg2m.conf | 17 +
conf/machine/iwg20m.conf | 2 +-
conf/machine/qemu-amd64.conf | 2 +-
conf/machine/simatic-ipc227e.conf | 2 +-
kas.yml | 2 +-
opt-targz-img.yml | 20 ++
.../linux/files/hihope-rzg2m_defconfig | 330 ++++++++++++++++++
scripts/deploy-cip-core.sh | 4 +
wic/hihope-rzg2m.wks | 15 +
13 files changed, 424 insertions(+), 5 deletions(-)
create mode 100644 board-rzg2m.yml
create mode 100644 classes/wic-targz-img.bbclass
create mode 100644 conf/machine/hihope-rzg2m.conf
create mode 100644 opt-targz-img.yml
create mode 100644 recipes-kernel/linux/files/hihope-rzg2m_defconfig
create mode 100644 wic/hihope-rzg2m.wks
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux


[isar-cip-core PATCH 4/4] ci: add hihope-rzg2m to ci chain

Quirin Gylstorff
 

From: Quirin Gylstorff <quirin.gylstorff@...>

Signed-off-by: Quirin Gylstorff <quirin.gylstorff@...>
---
.gitlab-ci.yml | 4 ++++
1 file changed, 4 insertions(+)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 36c152a..991862b 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -23,3 +23,7 @@ all:
- sudo rm -rf build/tmp
- kas build kas.yml:board-iwg20m.yml:opt-rt.yml
- scripts/deploy-cip-core.sh buster iwg20m r8a7743-iwg20d-q7-dbcm-ca.dtb
+
+ - sudo rm -rf build/tmp
+ - kas build kas.yml:board-rzg2m.yml:opt-rt.yml
+ - scripts/deploy-cip-core.sh buster hihope-rz2gm r8a774a1-hihope-rzg2m.dtb
--
2.20.1


[isar-cip-core PATCH 3/4] hihope-rzg2m: Add board support

Quirin Gylstorff
 

From: Quirin Gylstorff <quirin.gylstorff@...>

The hihope-rzg2m is a ARM64 reference platform for the CIP project.

Signed-off-by: Quirin Gylstorff <quirin.gylstorff@...>
---
board-rzg2m.yml | 16 +
conf/machine/hihope-rzg2m.conf | 17 +
.../linux/files/hihope-rzg2m_defconfig | 330 ++++++++++++++++++
wic/hihope-rzg2m.wks | 15 +
4 files changed, 378 insertions(+)
create mode 100644 board-rzg2m.yml
create mode 100644 conf/machine/hihope-rzg2m.conf
create mode 100644 recipes-kernel/linux/files/hihope-rzg2m_defconfig
create mode 100644 wic/hihope-rzg2m.wks

diff --git a/board-rzg2m.yml b/board-rzg2m.yml
new file mode 100644
index 0000000..f68c7b8
--- /dev/null
+++ b/board-rzg2m.yml
@@ -0,0 +1,16 @@
+#
+# CIP Core, generic profile
+#
+# Copyright (c) Siemens AG, 2019
+#
+# Authors:
+# Quirin Gylstorff <quirin.gylstorff@...>
+#
+# SPDX-License-Identifier: MIT
+#
+
+header:
+ version: 8
+
+machine: hihope-rzg2m
+target: cip-core-image
diff --git a/conf/machine/hihope-rzg2m.conf b/conf/machine/hihope-rzg2m.conf
new file mode 100644
index 0000000..5c456c7
--- /dev/null
+++ b/conf/machine/hihope-rzg2m.conf
@@ -0,0 +1,17 @@
+#
+# CIP Core, generic profile
+#
+# Copyright (c) Siemens AG, 2019
+#
+# Authors:
+# Quirin Gylstorff <quirin.gylstorff@...>
+#
+# SPDX-License-Identifier: MIT
+#
+
+DISTRO_ARCH = "arm64"
+
+IMAGE_TYPE ?= "wic-img"
+
+DTB_FILE = "r8a774a1-hihope-rzg2m.dtb"
+IMAGE_BOOT_FILES = "${KERNEL_IMAGE} ${DTB_FILE}"
diff --git a/recipes-kernel/linux/files/hihope-rzg2m_defconfig b/recipes-kernel/linux/files/hihope-rzg2m_defconfig
new file mode 100644
index 0000000..f35793c
--- /dev/null
+++ b/recipes-kernel/linux/files/hihope-rzg2m_defconfig
@@ -0,0 +1,330 @@
+CONFIG_SYSVIPC=y
+CONFIG_POSIX_MQUEUE=y
+CONFIG_AUDIT=y
+CONFIG_NO_HZ_IDLE=y
+CONFIG_HIGH_RES_TIMERS=y
+CONFIG_PREEMPT=y
+CONFIG_IRQ_TIME_ACCOUNTING=y
+CONFIG_BSD_PROCESS_ACCT=y
+CONFIG_BSD_PROCESS_ACCT_V3=y
+CONFIG_TASKSTATS=y
+CONFIG_TASK_DELAY_ACCT=y
+CONFIG_TASK_XACCT=y
+CONFIG_TASK_IO_ACCOUNTING=y
+CONFIG_IKCONFIG=y
+CONFIG_IKCONFIG_PROC=y
+CONFIG_MEMCG=y
+CONFIG_MEMCG_SWAP=y
+CONFIG_BLK_CGROUP=y
+CONFIG_CGROUP_PIDS=y
+CONFIG_CGROUP_HUGETLB=y
+CONFIG_CPUSETS=y
+CONFIG_CGROUP_DEVICE=y
+CONFIG_CGROUP_CPUACCT=y
+CONFIG_CGROUP_PERF=y
+CONFIG_USER_NS=y
+CONFIG_SCHED_AUTOGROUP=y
+CONFIG_BLK_DEV_INITRD=y
+# CONFIG_COMPAT_BRK is not set
+CONFIG_PROFILING=y
+CONFIG_ARCH_RENESAS=y
+CONFIG_ARCH_R8A774A1=y
+CONFIG_ARCH_R8A774C0=y
+CONFIG_PCI=y
+CONFIG_PCIEPORTBUS=y
+CONFIG_HOTPLUG_PCI_PCIE=y
+CONFIG_PCI_IOV=y
+CONFIG_HOTPLUG_PCI=y
+CONFIG_PCIE_RCAR=y
+CONFIG_PCI_HOST_GENERIC=y
+# CONFIG_CAVIUM_ERRATUM_22375 is not set
+# CONFIG_CAVIUM_ERRATUM_23154 is not set
+# CONFIG_CAVIUM_ERRATUM_27456 is not set
+# CONFIG_CAVIUM_ERRATUM_30115 is not set
+# CONFIG_QCOM_FALKOR_ERRATUM_1003 is not set
+# CONFIG_QCOM_FALKOR_ERRATUM_1009 is not set
+# CONFIG_QCOM_QDF2400_ERRATUM_0065 is not set
+# CONFIG_SOCIONEXT_SYNQUACER_PREITS is not set
+# CONFIG_HISILICON_ERRATUM_161600802 is not set
+CONFIG_ARM64_VA_BITS_48=y
+CONFIG_SCHED_MC=y
+CONFIG_NR_CPUS=8
+CONFIG_SECCOMP=y
+CONFIG_KEXEC=y
+CONFIG_CRASH_DUMP=y
+CONFIG_XEN=y
+# CONFIG_ARM64_LSE_ATOMICS is not set
+# CONFIG_ARM64_RAS_EXTN is not set
+CONFIG_COMPAT=y
+CONFIG_HIBERNATION=y
+CONFIG_WQ_POWER_EFFICIENT_DEFAULT=y
+CONFIG_CPU_IDLE=y
+CONFIG_ARM_CPUIDLE=y
+CONFIG_CPU_FREQ=y
+CONFIG_CPUFREQ_DT=y
+# CONFIG_DMIID is not set
+CONFIG_VIRTUALIZATION=y
+CONFIG_KVM=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
+CONFIG_JUMP_LABEL=y
+CONFIG_BLK_DEV_INTEGRITY=y
+# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
+CONFIG_KSM=y
+CONFIG_TRANSPARENT_HUGEPAGE=y
+CONFIG_CMA=y
+CONFIG_NET=y
+CONFIG_PACKET=y
+CONFIG_UNIX=y
+CONFIG_INET=y
+CONFIG_IP_MULTICAST=y
+CONFIG_IP_PNP=y
+CONFIG_IP_PNP_DHCP=y
+CONFIG_IP_PNP_BOOTP=y
+# CONFIG_IPV6 is not set
+CONFIG_NETFILTER=y
+CONFIG_CAN=y
+CONFIG_CAN_RCAR=y
+CONFIG_CAN_RCAR_CANFD=y
+CONFIG_DEVTMPFS=y
+CONFIG_DEVTMPFS_MOUNT=y
+CONFIG_DMA_CMA=y
+CONFIG_CMA_SIZE_MBYTES=128
+CONFIG_CMA_ALIGNMENT=9
+CONFIG_MTD=y
+CONFIG_MTD_BLOCK=y
+CONFIG_MTD_SPI_NOR=y
+CONFIG_BLK_DEV_LOOP=y
+CONFIG_VIRTIO_BLK=y
+CONFIG_SRAM=y
+# CONFIG_SCSI_PROC_FS is not set
+CONFIG_BLK_DEV_SD=y
+CONFIG_SCSI_SAS_LIBSAS=y
+CONFIG_SCSI_SAS_ATA=y
+CONFIG_ATA=y
+# CONFIG_SATA_PMP is not set
+CONFIG_SATA_RCAR=y
+CONFIG_NETDEVICES=y
+CONFIG_TUN=y
+CONFIG_VIRTIO_NET=y
+# CONFIG_CAVIUM_PTP is not set
+CONFIG_RAVB=y
+CONFIG_MDIO_BUS_MUX_MMIOREG=y
+CONFIG_MICREL_PHY=y
+CONFIG_REALTEK_PHY=y
+# CONFIG_WLAN is not set
+CONFIG_INPUT_MATRIXKMAP=y
+CONFIG_INPUT_EVDEV=y
+# CONFIG_KEYBOARD_ATKBD is not set
+CONFIG_KEYBOARD_GPIO=y
+# CONFIG_MOUSE_PS2 is not set
+CONFIG_INPUT_MISC=y
+# CONFIG_SERIO is not set
+CONFIG_SERIAL_SH_SCI=y
+CONFIG_VIRTIO_CONSOLE=y
+# CONFIG_HW_RANDOM is not set
+CONFIG_I2C_CHARDEV=y
+CONFIG_I2C_MUX=y
+CONFIG_I2C_MUX_PCA954x=y
+CONFIG_I2C_DESIGNWARE_PLATFORM=y
+CONFIG_I2C_SH_MOBILE=y
+CONFIG_I2C_RCAR=y
+CONFIG_SPI=y
+CONFIG_SPI_SH_MSIOF=y
+CONFIG_SPI_SPIDEV=y
+CONFIG_SPMI=y
+CONFIG_PINCTRL_SINGLE=y
+CONFIG_GPIO_GENERIC_PLATFORM=y
+CONFIG_GPIO_RCAR=y
+CONFIG_GPIO_PCA953X=y
+CONFIG_GPIO_BD9571MWV=y
+CONFIG_THERMAL=y
+CONFIG_THERMAL_GOV_POWER_ALLOCATOR=y
+CONFIG_CPU_THERMAL=y
+CONFIG_THERMAL_EMULATION=y
+CONFIG_RCAR_THERMAL=y
+CONFIG_RCAR_GEN3_THERMAL=y
+CONFIG_WATCHDOG=y
+CONFIG_RENESAS_WDT=y
+CONFIG_MFD_BD9571MWV=y
+CONFIG_REGULATOR=y
+CONFIG_REGULATOR_FIXED_VOLTAGE=y
+CONFIG_REGULATOR_BD9571MWV=y
+CONFIG_REGULATOR_GPIO=y
+CONFIG_REGULATOR_PWM=y
+CONFIG_MEDIA_SUPPORT=y
+CONFIG_MEDIA_CAMERA_SUPPORT=y
+CONFIG_MEDIA_SDR_SUPPORT=y
+CONFIG_MEDIA_CONTROLLER=y
+CONFIG_VIDEO_V4L2_SUBDEV_API=y
+CONFIG_V4L_PLATFORM_DRIVERS=y
+CONFIG_VIDEO_RCAR_CSI2=y
+CONFIG_VIDEO_RCAR_VIN=y
+CONFIG_V4L_MEM2MEM_DRIVERS=y
+CONFIG_VIDEO_RENESAS_FDP1=y
+CONFIG_VIDEO_RENESAS_FCP=y
+CONFIG_VIDEO_RENESAS_VSP1=y
+CONFIG_SDR_PLATFORM_DRIVERS=y
+CONFIG_VIDEO_RCAR_DRIF=y
+# CONFIG_MEDIA_SUBDRV_AUTOSELECT is not set
+CONFIG_VIDEO_ADV748X=y
+# CONFIG_MEDIA_TUNER_SIMPLE is not set
+# CONFIG_MEDIA_TUNER_TDA18250 is not set
+# CONFIG_MEDIA_TUNER_TDA8290 is not set
+# CONFIG_MEDIA_TUNER_TDA827X is not set
+# CONFIG_MEDIA_TUNER_TDA18271 is not set
+# CONFIG_MEDIA_TUNER_TDA9887 is not set
+# CONFIG_MEDIA_TUNER_TEA5761 is not set
+# CONFIG_MEDIA_TUNER_TEA5767 is not set
+# CONFIG_MEDIA_TUNER_MSI001 is not set
+# CONFIG_MEDIA_TUNER_MT20XX is not set
+# CONFIG_MEDIA_TUNER_MT2060 is not set
+# CONFIG_MEDIA_TUNER_MT2063 is not set
+# CONFIG_MEDIA_TUNER_MT2266 is not set
+# CONFIG_MEDIA_TUNER_MT2131 is not set
+# CONFIG_MEDIA_TUNER_QT1010 is not set
+# CONFIG_MEDIA_TUNER_XC2028 is not set
+# CONFIG_MEDIA_TUNER_XC5000 is not set
+# CONFIG_MEDIA_TUNER_XC4000 is not set
+# CONFIG_MEDIA_TUNER_MXL5005S is not set
+# CONFIG_MEDIA_TUNER_MXL5007T is not set
+# CONFIG_MEDIA_TUNER_MC44S803 is not set
+# CONFIG_MEDIA_TUNER_MAX2165 is not set
+# CONFIG_MEDIA_TUNER_TDA18218 is not set
+# CONFIG_MEDIA_TUNER_FC0011 is not set
+# CONFIG_MEDIA_TUNER_FC0012 is not set
+# CONFIG_MEDIA_TUNER_FC0013 is not set
+# CONFIG_MEDIA_TUNER_TDA18212 is not set
+# CONFIG_MEDIA_TUNER_E4000 is not set
+# CONFIG_MEDIA_TUNER_FC2580 is not set
+# CONFIG_MEDIA_TUNER_M88RS6000T is not set
+# CONFIG_MEDIA_TUNER_TUA9001 is not set
+# CONFIG_MEDIA_TUNER_SI2157 is not set
+# CONFIG_MEDIA_TUNER_IT913X is not set
+# CONFIG_MEDIA_TUNER_R820T is not set
+# CONFIG_MEDIA_TUNER_MXL301RF is not set
+# CONFIG_MEDIA_TUNER_QM1D1C0042 is not set
+# CONFIG_MEDIA_TUNER_QM1D1B0004 is not set
+CONFIG_DRM=y
+CONFIG_DRM_I2C_NXP_TDA998X=y
+CONFIG_DRM_RCAR_DU=y
+CONFIG_DRM_RCAR_DW_HDMI=y
+CONFIG_DRM_RCAR_LVDS=y
+CONFIG_DRM_DUMB_VGA_DAC=y
+CONFIG_DRM_THINE_THC63LVD1024=y
+CONFIG_DRM_DW_HDMI_AHB_AUDIO=y
+CONFIG_DRM_DW_HDMI_I2S_AUDIO=y
+CONFIG_DRM_DW_HDMI_CEC=y
+CONFIG_FB_MODE_HELPERS=y
+CONFIG_BACKLIGHT_LCD_SUPPORT=y
+# CONFIG_LCD_CLASS_DEVICE is not set
+# CONFIG_BACKLIGHT_GENERIC is not set
+CONFIG_BACKLIGHT_PWM=y
+CONFIG_LOGO=y
+# CONFIG_LOGO_LINUX_MONO is not set
+# CONFIG_LOGO_LINUX_VGA16 is not set
+CONFIG_SOUND=y
+CONFIG_SND=y
+# CONFIG_SND_SPI is not set
+# CONFIG_SND_USB is not set
+CONFIG_SND_SOC=y
+CONFIG_SND_SOC_RCAR=y
+CONFIG_SND_SOC_AK4613=y
+CONFIG_SND_SOC_PCM3168A_I2C=y
+CONFIG_SND_SIMPLE_CARD=y
+CONFIG_SND_SIMPLE_SCU_CARD=y
+CONFIG_SND_AUDIO_GRAPH_CARD=y
+CONFIG_USB=y
+CONFIG_USB_OTG=y
+CONFIG_USB_XHCI_HCD=y
+CONFIG_USB_XHCI_PLATFORM=y
+CONFIG_USB_EHCI_HCD=y
+CONFIG_USB_EHCI_ROOT_HUB_TT=y
+CONFIG_USB_EHCI_HCD_PLATFORM=y
+CONFIG_USB_OHCI_HCD=y
+CONFIG_USB_OHCI_HCD_PLATFORM=y
+CONFIG_USB_RENESAS_USBHS_HCD=y
+CONFIG_USB_RENESAS_USBHS=y
+CONFIG_USB_STORAGE=y
+CONFIG_USB_HSIC_USB3503=y
+CONFIG_NOP_USB_XCEIV=y
+CONFIG_USB_ULPI=y
+CONFIG_USB_GADGET=y
+CONFIG_USB_RENESAS_USBHS_UDC=y
+CONFIG_USB_RENESAS_USB3=y
+CONFIG_USB_SNP_UDC_PLAT=y
+CONFIG_USB_BDC_UDC=y
+CONFIG_MMC=y
+CONFIG_MMC_SDHI=y
+CONFIG_NEW_LEDS=y
+CONFIG_LEDS_CLASS=y
+CONFIG_LEDS_GPIO=y
+CONFIG_LEDS_PWM=y
+CONFIG_LEDS_TRIGGERS=y
+CONFIG_LEDS_TRIGGER_HEARTBEAT=y
+CONFIG_LEDS_TRIGGER_CPU=y
+CONFIG_LEDS_TRIGGER_DEFAULT_ON=y
+CONFIG_EDAC=y
+CONFIG_RTC_CLASS=y
+CONFIG_RTC_DRV_RX8581=y
+CONFIG_DMADEVICES=y
+CONFIG_RCAR_DMAC=y
+CONFIG_RENESAS_USB_DMAC=y
+CONFIG_VFIO=y
+CONFIG_VFIO_PCI=y
+CONFIG_VIRTIO_PCI=y
+CONFIG_VIRTIO_BALLOON=y
+CONFIG_VIRTIO_MMIO=y
+CONFIG_CHROME_PLATFORMS=y
+CONFIG_COMMON_CLK_CS2000_CP=y
+# CONFIG_COMMON_CLK_XGENE is not set
+CONFIG_COMMON_CLK_VC5=y
+CONFIG_CLK_RCAR_USB2_CLOCK_SEL=y
+CONFIG_HWSPINLOCK=y
+# CONFIG_FSL_ERRATUM_A008585 is not set
+# CONFIG_HISILICON_ERRATUM_161010101 is not set
+# CONFIG_ARM64_ERRATUM_858921 is not set
+CONFIG_MAILBOX=y
+CONFIG_IOMMU_IO_PGTABLE_LPAE=y
+CONFIG_EXTCON_USB_GPIO=y
+CONFIG_IIO=y
+CONFIG_MAX9611=y
+CONFIG_PWM=y
+CONFIG_PWM_RCAR=y
+CONFIG_RESET_CONTROLLER=y
+CONFIG_PHY_RCAR_GEN3_PCIE=y
+CONFIG_PHY_RCAR_GEN3_USB2=y
+CONFIG_PHY_RCAR_GEN3_USB3=y
+CONFIG_TEE=y
+CONFIG_OPTEE=y
+CONFIG_EXT4_FS=y
+CONFIG_EXT4_FS_POSIX_ACL=y
+CONFIG_FANOTIFY=y
+CONFIG_QUOTA=y
+CONFIG_AUTOFS4_FS=y
+CONFIG_VFAT_FS=y
+CONFIG_TMPFS=y
+CONFIG_HUGETLBFS=y
+CONFIG_CONFIGFS_FS=y
+CONFIG_SQUASHFS=y
+CONFIG_NFS_FS=y
+CONFIG_NFS_V4=y
+CONFIG_NFS_V4_1=y
+CONFIG_NFS_V4_2=y
+CONFIG_ROOT_NFS=y
+CONFIG_NLS_CODEPAGE_437=y
+CONFIG_NLS_ISO8859_1=y
+CONFIG_CRYPTO_ANSI_CPRNG=y
+# CONFIG_CRYPTO_DEV_VIRTIO is not set
+CONFIG_CRYPTO_DEV_CCREE=y
+CONFIG_PRINTK_TIME=y
+CONFIG_MAGIC_SYSRQ=y
+CONFIG_DEBUG_KERNEL=y
+# CONFIG_SCHED_DEBUG is not set
+# CONFIG_DEBUG_PREEMPT is not set
+CONFIG_PROVE_LOCKING=y
+# CONFIG_FTRACE is not set
diff --git a/wic/hihope-rzg2m.wks b/wic/hihope-rzg2m.wks
new file mode 100644
index 0000000..c0a9f77
--- /dev/null
+++ b/wic/hihope-rzg2m.wks
@@ -0,0 +1,15 @@
+#
+# CIP Core, generic profile
+#
+# Copyright (c) Siemens AG, 2019
+#
+# Authors:
+# Quirin Gylstorff <quirin.gylstorff@...>
+#
+# SPDX-License-Identifier: MIT
+#
+
+part /boot --source bootimg-partition --ondisk mmcblk0 --fstype vfat --label boot --align 1 --size 32M --extra-space 0
+
+# Rootfs partition
+part / --source rootfs --ondisk mmcblk0 --fstype ext4 --label root --align 1024 --size 2G --active
--
2.20.1


[isar-cip-core PATCH 2/4] classes: add wic-targz-img.bbclass

Quirin Gylstorff
 

From: Quirin Gylstorff <quirin.gylstorff@...>

The Linaro Automated Validation Architecture (LAVA) uses tarballs
as root file-systems to modify the file-system during the deployment.
Add a new bbclass to build tarballs and wic images at the same time to
feed the build output of isar-cip-core directly into LAVA tests.

Signed-off-by: Quirin Gylstorff <quirin.gylstorff@...>
---
classes/wic-targz-img.bbclass | 13 +++++++++++++
conf/machine/bbb.conf | 2 +-
conf/machine/iwg20m.conf | 2 +-
conf/machine/qemu-amd64.conf | 2 +-
conf/machine/simatic-ipc227e.conf | 2 +-
opt-targz-img.yml | 20 ++++++++++++++++++++
scripts/deploy-cip-core.sh | 4 ++++
7 files changed, 41 insertions(+), 4 deletions(-)
create mode 100644 classes/wic-targz-img.bbclass
create mode 100644 opt-targz-img.yml

diff --git a/classes/wic-targz-img.bbclass b/classes/wic-targz-img.bbclass
new file mode 100644
index 0000000..4e9f89d
--- /dev/null
+++ b/classes/wic-targz-img.bbclass
@@ -0,0 +1,13 @@
+#
+# CIP Core, generic profile
+#
+# Copyright (c) Siemens AG, 2019
+#
+# Authors:
+# Quirin Gylstorff <quirin.gylstorff@...>
+#
+# SPDX-License-Identifier: MIT
+#
+
+inherit wic-img
+inherit targz-img
diff --git a/conf/machine/bbb.conf b/conf/machine/bbb.conf
index c945aac..a9b460e 100644
--- a/conf/machine/bbb.conf
+++ b/conf/machine/bbb.conf
@@ -8,7 +8,7 @@

DISTRO_ARCH = "armhf"

-IMAGE_TYPE = "wic-img"
+IMAGE_TYPE ?= "wic-img"
IMAGER_INSTALL += "u-boot-omap"

# On stretch, select U-Boot from buster which comes with distro-boot support
diff --git a/conf/machine/iwg20m.conf b/conf/machine/iwg20m.conf
index 2f91771..6c1a227 100644
--- a/conf/machine/iwg20m.conf
+++ b/conf/machine/iwg20m.conf
@@ -8,7 +8,7 @@
DISTRO_ARCH = "armhf"

# see wic/iwg20m.wks
-IMAGE_TYPE = "wic-img"
+IMAGE_TYPE ?= "wic-img"

# sets serial login getty
MACHINE_SERIAL = "ttySC0"
diff --git a/conf/machine/qemu-amd64.conf b/conf/machine/qemu-amd64.conf
index 90325d6..7cbd55b 100644
--- a/conf/machine/qemu-amd64.conf
+++ b/conf/machine/qemu-amd64.conf
@@ -8,4 +8,4 @@

DISTRO_ARCH = "amd64"

-IMAGE_TYPE = "ext4-img"
+IMAGE_TYPE ?= "ext4-img"
diff --git a/conf/machine/simatic-ipc227e.conf b/conf/machine/simatic-ipc227e.conf
index 73dac33..473e6c5 100644
--- a/conf/machine/simatic-ipc227e.conf
+++ b/conf/machine/simatic-ipc227e.conf
@@ -8,5 +8,5 @@

DISTRO_ARCH = "amd64"

-IMAGE_TYPE = "wic-img"
+IMAGE_TYPE ?= "wic-img"
IMAGER_INSTALL += "${GRUB_BOOTLOADER_INSTALL}"
diff --git a/opt-targz-img.yml b/opt-targz-img.yml
new file mode 100644
index 0000000..1a73024
--- /dev/null
+++ b/opt-targz-img.yml
@@ -0,0 +1,20 @@
+#
+# CIP Core, generic profile
+#
+# Copyright (c) Siemens AG, 2019
+#
+# Authors:
+# Quirin Gylstorff <quirin.gylstorff@...>
+#
+# SPDX-License-Identifier: MIT
+#
+
+header:
+ version: 8
+
+# lava uses nfs to deploy the image. For this we need a tarball instead of
+# full image
+
+local_conf_header:
+ image-type: |
+ IMAGE_TYPE = "wic-targz-img"
diff --git a/scripts/deploy-cip-core.sh b/scripts/deploy-cip-core.sh
index 081dc9d..e5c09ef 100755
--- a/scripts/deploy-cip-core.sh
+++ b/scripts/deploy-cip-core.sh
@@ -26,6 +26,10 @@ xz -9 -k $BASE_PATH.wic.img
echo "Uploading artifacts..."
aws s3 cp --no-progress $BASE_PATH.wic.img.xz s3://download.cip-project.org/cip-core/$TARGET/

+if [ -f $BASE_PATH.tar.gz ]; then
+ aws s3 cp --no-progress $BASE_PATH.tar.gz s3://download.cip-project.org/cip-core/$TARGET/
+fi
+
KERNEL_IMAGE=$BASE_PATH-vmlinuz
# iwg20m workaround
if [ -f build/tmp/deploy/images/$TARGET/zImage ]; then
--
2.20.1


[isar-cip-core PATCH 1/4] kas: Increase Isar version

Quirin Gylstorff
 

From: Quirin Gylstorff <quirin.gylstorff@...>

Add fix for manifest generation to avoid errors during build.

Signed-off-by: Quirin Gylstorff <quirin.gylstorff@...>
---
kas.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kas.yml b/kas.yml
index 4904715..aa7ddda 100644
--- a/kas.yml
+++ b/kas.yml
@@ -19,7 +19,7 @@ repos:

isar:
url: https://github.com/ilbers/isar
- refspec: c1bae4c7ae9dee4d2cf5fd77d0c5560d9e52d5e1
+ refspec: 20a5e368021d988d8f0dcd1951b395d194a37ebb
layers:
meta:

--
2.20.1


[isar-cip-core PATCH 0/4] Add rzg2m support

Quirin Gylstorff
 

From: Quirin Gylstorff <quirin.gylstorff@...>

Add the rzg2m reference board.
Add the option to build rootfs tarballs for LAVA tests.
This option needs to be activated in the gitlab-ci.yml by
adding it to the builds for testing.


Quirin Gylstorff (4):
kas: Increase Isar version
classes: add wic-targz-img.bbclass
hihope-rzg2m: Add board support
ci: add hihope-rzg2m to ci chain

.gitlab-ci.yml | 4 +
board-rzg2m.yml | 16 +
classes/wic-targz-img.bbclass | 13 +
conf/machine/bbb.conf | 2 +-
conf/machine/hihope-rzg2m.conf | 17 +
conf/machine/iwg20m.conf | 2 +-
conf/machine/qemu-amd64.conf | 2 +-
conf/machine/simatic-ipc227e.conf | 2 +-
kas.yml | 2 +-
opt-targz-img.yml | 20 ++
.../linux/files/hihope-rzg2m_defconfig | 330 ++++++++++++++++++
scripts/deploy-cip-core.sh | 4 +
wic/hihope-rzg2m.wks | 15 +
13 files changed, 424 insertions(+), 5 deletions(-)
create mode 100644 board-rzg2m.yml
create mode 100644 classes/wic-targz-img.bbclass
create mode 100644 conf/machine/hihope-rzg2m.conf
create mode 100644 opt-targz-img.yml
create mode 100644 recipes-kernel/linux/files/hihope-rzg2m_defconfig
create mode 100644 wic/hihope-rzg2m.wks

--
2.20.1


[Git][cip-project/cip-kernel/cip-kernel-sec][master] 9 commits: Import data from Debian and Ubuntu archives

Agustin Benito Bethencourt
 

SZ Lin (林上智) pushed to branch master at cip-project / cip-kernel / cip-kernel-sec

Commits:

  • 9f11fbee
    by SZ Lin (林上智) at 2019-10-14T11:40:54Z
    Import data from Debian and Ubuntu archives
    
    
    
    Signed-off-by: SZ Lin (林上智) <sz.lin@...>
    
    
  • c5fb22f6
    by SZ Lin (林上智) at 2019-10-14T11:45:01Z
    Fill in fixed-by commit lists for CVE-2019-17133
    
    
    
    Signed-off-by: SZ Lin (林上智) <sz.lin@...>
    
    
  • eb4b17f4
    by SZ Lin (林上智) at 2019-10-14T11:54:56Z
    Add comment for 4.4 status
    
    
    
    Signed-off-by: SZ Lin (林上智) <sz.lin@...>
    
    
  • 26f0cb2c
    by SZ Lin (林上智) at 2019-10-14T11:59:18Z
    Mark this issue to be ignored on CIP branches
    
    
    
    The components affected by this issue is not enabled by any CIP
    
    members.
    
    
    
    Signed-off-by: SZ Lin (林上智) <sz.lin@...>
    
    
  • 62045139
    by SZ Lin (林上智) at 2019-10-14T12:05:31Z
    Tidy the description
    
    
    
    Signed-off-by: SZ Lin (林上智) <sz.lin@...>
    
    
  • 8cc5fbbd
    by SZ Lin (林上智) at 2019-10-14T12:15:51Z
    Fill in fixed-by commit lists for CVE-2019-17351
    
    
    
    Signed-off-by: SZ Lin (林上智) <sz.lin@...>
    
    
  • 2b43b909
    by SZ Lin (林上智) at 2019-10-23T03:32:43Z
    Import data from Debian and Ubuntu archives
    
    
    
    Signed-off-by: SZ Lin (林上智) <sz.lin@...>
    
    
  • 3c2b0e9b
    by SZ Lin (林上智) at 2019-10-24T10:13:06Z
    Add comment about not affected of CVE-2019-18198
    
    
    
    Signed-off-by: SZ Lin (林上智) <sz.lin@...>
    
    
  • 28b5cda1
    by SZ Lin (林上智) at 2019-11-06T08:33:11Z
    Merge branch 'master' into 'master'
    
    
    
    Update issues
    
    
    
    See merge request cip-project/cip-kernel/cip-kernel-sec!16

23 changed files:

Changes:

  • issues/CVE-2016-10906.yml
    ... ... @@ -3,6 +3,7 @@ references:
    3 3
     - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10906
    
    
    4 4
     - https://git.kernel.org/linus/c278c253f3d992c6994d08aa0efb2b6806ca396f
    
    
    5 5
     - https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c278c253f3d992c6994d08aa0efb2b6806ca396f
    
    
    6
    +- https://usn.ubuntu.com/usn/usn-4163-1
    
    
    6 7
     comments:
    
    
    7 8
       Debian-bwh: CONFIG_ARC_EMAC not enabled, so only affected source-wise.
    
    
    8 9
       Ubuntu-tyhicks: |-
    
    

  • issues/CVE-2017-18232.yml
    ... ... @@ -2,6 +2,7 @@ description: 'scsi: libsas: direct call probe and destruct'
    2 2
     references:
    
    
    3 3
     - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-18232
    
    
    4 4
     - http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0558f33c06bb910e2879e355192227a8e8f0219d
    
    
    5
    +- https://usn.ubuntu.com/usn/usn-4163-1
    
    
    5 6
     comments:
    
    
    6 7
       Debian-bwh: |-
    
    
    7 8
         Commit message says this was introduced by commit 87c8331fcf72
    
    

  • issues/CVE-2018-20976.yml
    ... ... @@ -9,6 +9,7 @@ introduced-by:
    9 9
       mainline: [8daaa83145ef1f0a146680618328dbbd0fa76939]
    
    
    10 10
     fixed-by:
    
    
    11 11
       linux-3.16.y: [bf3878994377a97143f5f6b6e60a18f9b76e0476]
    
    
    12
    +  linux-4.9.y: [e6e3f36b1ac9c439d3bc0b2c2aaf1663ad705ac0]
    
    
    12 13
       mainline: [c9fbd7bbc23dbdd73364be4d045e5d3612cf6e82]
    
    
    13 14
     ignore:
    
    
    14 15
       linux-4.19.y-cip-rt: No member enables XFS
    
    

  • issues/CVE-2018-21008.yml
    ... ... @@ -4,6 +4,8 @@ references:
    4 4
     - https://git.kernel.org/linus/abd39c6ded9db53aa44c2540092bdd5fb6590fa8
    
    
    5 5
     - https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.16.7
    
    
    6 6
     - https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=abd39c6ded9db53aa44c2540092bdd5fb6590fa8
    
    
    7
    +- https://usn.ubuntu.com/usn/usn-4162-1
    
    
    8
    +- https://usn.ubuntu.com/usn/usn-4163-1
    
    
    7 9
     comments:
    
    
    8 10
       Debian-bwh: Apparently introduced in 3.15 when rsi driver was added.
    
    
    9 11
     introduced-by:
    
    

  • issues/CVE-2019-14814.yml
    ... ... @@ -4,6 +4,10 @@ references:
    4 4
     - https://lore.kernel.org/linux-wireless/20190828020751.13625-1-huangwenabc@.../
    
    
    5 5
     - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14814
    
    
    6 6
     - https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git/commit/?id=8b51dc7291473093c821195c4b6af85fadedbc2f
    
    
    7
    +- https://usn.ubuntu.com/usn/usn-4157-1
    
    
    8
    +- https://usn.ubuntu.com/usn/usn-4162-1
    
    
    9
    +- https://usn.ubuntu.com/usn/usn-4163-1
    
    
    10
    +- https://usn.ubuntu.com/usn/usn-4157-2
    
    
    7 11
     comments:
    
    
    8 12
       Debian-bwh: |-
    
    
    9 13
         Introduced in 3.7 by commit a3c2c4f6d8bc "mwifiex: parse rate info
    
    

  • issues/CVE-2019-14815.yml
    ... ... @@ -4,6 +4,9 @@ references:
    4 4
     - https://lore.kernel.org/linux-wireless/20190828020751.13625-1-huangwenabc@.../
    
    
    5 5
     - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14815
    
    
    6 6
     - https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git/commit/?id=8b51dc7291473093c821195c4b6af85fadedbc2f
    
    
    7
    +- https://usn.ubuntu.com/usn/usn-4157-1
    
    
    8
    +- https://usn.ubuntu.com/usn/usn-4162-1
    
    
    9
    +- https://usn.ubuntu.com/usn/usn-4157-2
    
    
    7 10
     comments:
    
    
    8 11
       Debian-bwh: |-
    
    
    9 12
         Introduced in 4.10 by commit 113630b581d6 "mwifiex: vendor_ie length
    
    

  • issues/CVE-2019-14816.yml
    ... ... @@ -4,6 +4,10 @@ references:
    4 4
     - https://lore.kernel.org/linux-wireless/20190828020751.13625-1-huangwenabc@.../
    
    
    5 5
     - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14816
    
    
    6 6
     - https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git/commit/?id=7caac62ed598a196d6ddf8d9c121e12e082cac3a
    
    
    7
    +- https://usn.ubuntu.com/usn/usn-4157-1
    
    
    8
    +- https://usn.ubuntu.com/usn/usn-4162-1
    
    
    9
    +- https://usn.ubuntu.com/usn/usn-4163-1
    
    
    10
    +- https://usn.ubuntu.com/usn/usn-4157-2
    
    
    7 11
     comments:
    
    
    8 12
       Debian-bwh: |-
    
    
    9 13
         Introduced in 3.6 by commit 2152fe9c2fa4 "mwifiex: parse WPS IEs from
    
    

  • issues/CVE-2019-14821.yml
    ... ... @@ -4,6 +4,10 @@ references:
    4 4
     - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14821
    
    
    5 5
     - https://www.openwall.com/lists/oss-security/2019/09/20/1
    
    
    6 6
     - https://bugzilla.redhat.com/show_bug.cgi?id=1746708
    
    
    7
    +- https://usn.ubuntu.com/usn/usn-4157-1
    
    
    8
    +- https://usn.ubuntu.com/usn/usn-4162-1
    
    
    9
    +- https://usn.ubuntu.com/usn/usn-4163-1
    
    
    10
    +- https://usn.ubuntu.com/usn/usn-4157-2
    
    
    7 11
     comments:
    
    
    8 12
       Debian-carnil: |-
    
    
    9 13
         Commit fixes 5f94c1741bdc ("KVM: Add coalesced MMIO support
    
    

  • issues/CVE-2019-15099.yml
    ... ... @@ -2,6 +2,7 @@ description: Fix a NULL-ptr-deref bug in ath10k_usb_alloc_urb_from_pipe
    2 2
     references:
    
    
    3 3
     - https://lore.kernel.org/linux-wireless/20190804003101.11541-1-benquike@.../T/#u
    
    
    4 4
     - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15099
    
    
    5
    +- https://lore.kernel.org/linux-wireless/20191018133516.12606-1-linux@.../
    
    
    5 6
     comments:
    
    
    6 7
       Debian-bwh: |-
    
    
    7 8
         Introduced in 4.14 by commit 4db66499df91 "ath10k: add initial USB
    
    

  • issues/CVE-2019-15117.yml
    ... ... @@ -4,6 +4,8 @@ references:
    4 4
     - https://lore.kernel.org/lkml/20190814023625.21683-1-benquike@.../
    
    
    5 5
     - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15117
    
    
    6 6
     - https://usn.ubuntu.com/usn/usn-4147-1
    
    
    7
    +- https://usn.ubuntu.com/usn/usn-4162-1
    
    
    8
    +- https://usn.ubuntu.com/usn/usn-4163-1
    
    
    7 9
     comments:
    
    
    8 10
       Ubuntu-tyhicks: |-
    
    
    9 11
         The parse_audio_mixer_unit() function has changed its handling of the
    
    

  • issues/CVE-2019-15118.yml
    ... ... @@ -4,6 +4,8 @@ references:
    4 4
     - https://lore.kernel.org/lkml/20190815043554.16623-1-benquike@.../
    
    
    5 5
     - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15118
    
    
    6 6
     - https://usn.ubuntu.com/usn/usn-4147-1
    
    
    7
    +- https://usn.ubuntu.com/usn/usn-4162-1
    
    
    8
    +- https://usn.ubuntu.com/usn/usn-4163-1
    
    
    7 9
     comments:
    
    
    8 10
       Debian-bwh: |-
    
    
    9 11
         This is actually a stack overflow (unbounded recursion), not a
    
    

  • issues/CVE-2019-15504.yml
    ... ... @@ -3,6 +3,8 @@ references:
    3 3
     - https://lore.kernel.org/lkml/20190819220230.10597-1-benquike@.../
    
    
    4 4
     - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15504
    
    
    5 5
     - https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git/commit/?id=8b51dc7291473093c821195c4b6af85fadedbc2f
    
    
    6
    +- https://usn.ubuntu.com/usn/usn-4157-1
    
    
    7
    +- https://usn.ubuntu.com/usn/usn-4157-2
    
    
    6 8
     comments:
    
    
    7 9
       Debian-bwh: I agree that commit a1854fae1414 introduced this.
    
    
    8 10
       Debian-carnil: |-
    
    

  • issues/CVE-2019-15505.yml
    ... ... @@ -4,6 +4,10 @@ references:
    4 4
     - https://lore.kernel.org/linux-media/20190821104408.w7krumcglxo6fz5q@.../
    
    
    5 5
     - https://lore.kernel.org/lkml/b9b256cb-95f2-5fa1-9956-5a602a017c11@.../
    
    
    6 6
     - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15505
    
    
    7
    +- https://usn.ubuntu.com/usn/usn-4157-1
    
    
    8
    +- https://usn.ubuntu.com/usn/usn-4162-1
    
    
    9
    +- https://usn.ubuntu.com/usn/usn-4163-1
    
    
    10
    +- https://usn.ubuntu.com/usn/usn-4157-2
    
    
    7 11
     comments:
    
    
    8 12
       Debian-bwh: Apparently introduced in 2.6.39 when technisat-usb2 driver was added.
    
    
    9 13
       Ubuntu-tyhicks: |-
    
    

  • issues/CVE-2019-15902.yml
    ... ... @@ -2,6 +2,10 @@ description: 'x86/ptrace: fix up botched merge of spectrev1 fix'
    2 2
     references:
    
    
    3 3
     - https://grsecurity.net/teardown_of_a_failed_linux_lts_spectre_fix.php
    
    
    4 4
     - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15902
    
    
    5
    +- https://usn.ubuntu.com/usn/usn-4157-1
    
    
    6
    +- https://usn.ubuntu.com/usn/usn-4162-1
    
    
    7
    +- https://usn.ubuntu.com/usn/usn-4163-1
    
    
    8
    +- https://usn.ubuntu.com/usn/usn-4157-2
    
    
    5 9
     reporters:
    
    
    6 10
     - Brad Spengler
    
    
    7 11
     introduced-by:
    
    

  • issues/CVE-2019-15918.yml
    ... ... @@ -4,6 +4,7 @@ references:
    4 4
     - https://git.kernel.org/linus/b57a55e2200ede754e4dc9cce4ba9402544b9365
    
    
    5 5
     - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.0.10
    
    
    6 6
     - https://github.com/torvalds/linux/commit/b57a55e2200ede754e4dc9cce4ba9402544b9365
    
    
    7
    +- https://usn.ubuntu.com/usn/usn-4162-1
    
    
    7 8
     comments:
    
    
    8 9
       Debian-bwh: |-
    
    
    9 10
         Introduced in 4.14 by commit 9764c02fcbad "SMB3: Add support for
    
    

  • issues/CVE-2019-16714.yml
    ... ... @@ -2,6 +2,8 @@ description: 'net/rds: Fix info leak in rds6_inc_info_copy()'
    2 2
     references:
    
    
    3 3
     - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16714
    
    
    4 4
     - https://git.kernel.org/linus/7d0a06586b2686ba80c4a2da5f91cb10ffbea736
    
    
    5
    +- https://usn.ubuntu.com/usn/usn-4157-1
    
    
    6
    +- https://usn.ubuntu.com/usn/usn-4157-2
    
    
    5 7
     comments:
    
    
    6 8
       Ubuntu-tyhicks: |-
    
    
    7 9
         This is a local info leak that is only reachable by calling the
    
    

  • issues/CVE-2019-16746.yml
    ... ... @@ -2,7 +2,14 @@ description: 'nl80211: validate beacon head'
    2 2
     references:
    
    
    3 3
     - https://marc.info/?l=linux-wireless&m=156901391225058&w=2
    
    
    4 4
     - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16746
    
    
    5
    +comments:
    
    
    6
    +  Moxa-szlin: |-
    
    
    7
    +    This issue was fixed in 4.19.79, and Greg mentioned [1]
    
    
    8
    +    he backported the patch to 4.4.
    
    
    9
    +    [1] https://www.mail-archive.com/linux-wireless@.../msg60345.html
    
    
    5 10
     introduced-by:
    
    
    6 11
       mainline: [ed1b6cc7f80f831e192704b05b9917f9cc37be15]
    
    
    7 12
     fixed-by:
    
    
    13
    +  linux-4.19.y: [1bd17a737c9e7e91483d9a603528b0e6d4c772f8]
    
    
    14
    +  linux-4.9.y: [a873afd7d888f7349bfabc9191afeb20eb1d3a45]
    
    
    8 15
       mainline: [f88eb7c0d002a67ef31aeb7850b42ff69abc46dc]

  • issues/CVE-2019-17075.yml
    ... ... @@ -7,3 +7,10 @@ reporters:
    7 7
     - Nicolas Waisman
    
    
    8 8
     introduced-by:
    
    
    9 9
       mainline: [cfdda9d764362ab77b11a410bb928400e6520d57]
    
    
    10
    +fixed-by:
    
    
    11
    +  mainline: [3840c5b78803b2b6cc1ff820100a74a092c40cbb]
    
    
    12
    +ignore:
    
    
    13
    +  linux-4.19.y-cip: No member enables cxgb4
    
    
    14
    +  linux-4.19.y-cip-rt: No member enables cxgb4
    
    
    15
    +  linux-4.4.y-cip: No member enables cxgb4
    
    
    16
    +  linux-4.4.y-cip-rt: No member enables cxgb4

  • issues/CVE-2019-17133.yml
    1
    -description: 'cfg80211: wext: Reject malformed SSID elements'
    
    
    1
    +description: 'cfg80211: wext: avoid copying malformed SSIDs'
    
    
    2 2
     references:
    
    
    3 3
     - https://marc.info/?l=linux-wireless&m=157018270915487&w=2
    
    
    4
    +- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17133
    
    
    5
    +reporters:
    
    
    6
    +- Nicolas Waisman
    
    
    7
    +introduced-by:
    
    
    8
    +  mainline: [a42dd7efd934888833c01199dbd21b242100ee92]
    
    
    9
    +fixed-by:
    
    
    10
    +  mainline: [4ac2813cc867ae563a1ba5a9414bfb554e5796fa]

  • issues/CVE-2019-17351.yml
    1
    +description: 'xen: let alloc_xenballooned_pages() fail if not enough memory free'
    
    
    2
    +references:
    
    
    3
    +- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17351
    
    
    4
    +- https://xenbits.xen.org/xsa/advisory-300.html
    
    
    5
    +comments:
    
    
    6
    +  Debian-benh: |-
    
    
    7
    +    The advisory says another patch will be needed for domU.
    
    
    8
    +    For 3.16 we need d02bd27bd33d "mm/page_alloc.c: calculate
    
    
    9
    +    'available' memory in a separate function" first.
    
    
    10
    +  Debian-carnil: |-
    
    
    11
    +    Is a1078e821b60 ("xen: let alloc_xenballooned_pages() fail if
    
    
    12
    +    not enough memory free") enough or is more needed?
    
    
    13
    +reporters:
    
    
    14
    +- Julien Grall
    
    
    15
    +introduced-by:
    
    
    16
    +  mainline: [1775826ceec51187aa868406585799b7e76ffa7d]
    
    
    17
    +fixed-by:
    
    
    18
    +  linux-3.16.y: [2ed58e578b03269b23eb7119fb38478725ae6470]
    
    
    19
    +  linux-4.19.y: [e73db096691e5f2720049502a3794a2a0c6d1b1f]
    
    
    20
    +  linux-4.19.y-cip: [e73db096691e5f2720049502a3794a2a0c6d1b1f]
    
    
    21
    +  linux-4.19.y-cip-rt: [e73db096691e5f2720049502a3794a2a0c6d1b1f]
    
    
    22
    +  linux-4.9.y: [259b0fc2caddc21a6b561b595747a8091102f7ff]
    
    
    23
    +  mainline: [a1078e821b605813b63bf6bca414a85f804d5c66]

  • issues/CVE-2019-17666.yml
    1
    +description: 'rtlwifi: Fix potential overflow on P2P code'
    
    
    2
    +references:
    
    
    3
    +- https://lkml.org/lkml/2019/10/16/1226
    
    
    4
    +- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17666
    
    
    5
    +- https://lore.kernel.org/lkml/20191016205716.2843-1-labbott@.../
    
    
    6
    +- https://twitter.com/nicowaisman/status/1184864519316758535
    
    
    7
    +- https://bugzilla.suse.com/show_bug.cgi?id=CVE-2019-17666
    
    
    8
    +reporters:
    
    
    9
    +- Nico Waisman

  • issues/CVE-2019-18198.yml
    1
    +description: |-
    
    
    2
    +  In the Linux 5.3 kernel before 5.3.4, a reference count usage error in
    
    
    3
    +  the fib6_rule_suppress() function in the fib6 suppression feature of
    
    
    4
    +  net/ipv6/fib6_rules.c, when handling the FIB_LOOKUP_NOREF flag, can be
    
    
    5
    +  exploited by a local attacker to corrupt memory, aka CID-ca7a03c41753.
    
    
    6
    +references:
    
    
    7
    +- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18198
    
    
    8
    +- https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ca7a03c4175366a92cee0ccc4fec0038c3266e26
    
    
    9
    +- https://usn.ubuntu.com/usn/usn-4161-1
    
    
    10
    +- https://launchpad.net/bugs/1847478
    
    
    11
    +comments:
    
    
    12
    +  Ubuntu-sbeattie: affects 5.3 kernels only
    
    
    13
    +  Moxa-szlin: |-
    
    
    14
    +    Since CIP only supports kernel 4.4 and 4.19, there is no impact for CIP member
    
    
    15
    +introduced-by:
    
    
    16
    +  mainline: [7d9e5f422150ed00de744e02a80734d74cc9704d]
    
    
    17
    +fixed-by:
    
    
    18
    +  mainline: [ca7a03c4175366a92cee0ccc4fec0038c3266e26]
    
    
    19
    +ignore
    
    
    20
    +  linux-4.19.y-cip: Not affected
    
    
    21
    +  linux-4.19.y-cip-rt: Not affected
    
    
    22
    +  linux-4.4.y-cip: Not affected
    
    
    23
    +  linux-4.4.y-cip-rt: Not affected

  • issues/CVE-2019-2215.yml
    1
    +description: |-
    
    
    2
    +  A use-after-free in binder.c allows an elevation of privilege from an
    
    
    3
    +  application to the Linux Kernel. No user interaction is required to exploit
    
    
    4
    +  this vulnerability, however exploitation does require either the
    
    
    5
    +  installation of a malicious local application or a separate vulnerability
    
    
    6
    +  in a network facing application.Product: AndroidAndroid ID: A-141720095
    
    
    7
    +references:
    
    
    8
    +- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2215
    
    
    9
    +- https://source.android.com/security/bulletin/2019-10-01
    
    
    10
    +- https://bugs.chromium.org/p/project-zero/issues/detail?id=1942
    
    
    11
    +fixed-by:
    
    
    12
    +  mainline: [f5cb779ba16334b45ba8946d6bfa6d9834d1527f]


  • Planned downtime for lab-cip-renesas on the 13th Nov

    Chris Paterson
     

    Hello all,

    Just a heads up that the Renesas LAVA lab (lab-cip-renesas) will be offline for 2/3 hours on the morning of the 13th November, from around 1000 GMT onwards.

    Our hardware is being PAT tested.

    Kind regards, Chris


    Re: Linux kernel vulnerability PoCs

    Chris Paterson
     

    Thank you Ben. Looping in the mailing list for general interest.

    Kind regards, Chris

    From: Ben Hutchings <ben.hutchings@...>
    Sent: 31 October 2019 23:44

    These are the repositories I know about:
    https://github.com/jollheef/lpe
    https://github.com/ScottyBauer/Android_Kernel_CVE_POCs

    I think that the more collaborative collection of PoCs that I was
    thinking of is vapourware so far.

    Ben.

    --
    Ben Hutchings, Software Developer Codethink Ltd
    https://www.codethink.co.uk/ Dale House, 35 Dale Street
    Manchester, M1 2HF, United Kingdom


    [ANNOUNCE] Release v4.19.80-cip13

    Nobuhiro Iwamatsu
     

    Hi all,

    The release was delayed, sorry.
    CIP kernel team has released Linux kernel v4.19.80-cip13 and v4.4.196-cip38.

    The linux-4.19.y-cip tree has been updated from base version from 4.19.78 to 4.19.80,
    and added support for WLAN and Bluetooth for hihope and cat 874 boards, and CANFD for
    r8a774a1.

    You can get this release via the git tree at:
    v4.19.80-cip13:

    repository: https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
    branch: linux-4.19.y-cip
    commit: 678c61cf1ee690282482f867aa9587d39d549e6c

    Best regards,
    Nobuhiro


    Re: Regarding RZ/G1CeMMC backporting patches

    Biju Das <biju.das@...>
     

    Hi Pavel & Nobuhiro-San ,

    Do you want me to send the patches instead of [1]? Please let me know.

    [1]. https://gitlab.com/bijud/emmc

    Regards,
    Biju

    -----Original Message-----
    From: Biju Das
    Sent: Monday, October 28, 2019 5:47 PM
    To: cip-dev@...; Pavel Machek <pavel@...>; Nobuhiro
    Iwamatsu <nobuhiro1.iwamatsu@...>
    Cc: Chris Paterson <Chris.Paterson2@...>; Fabrizio Castro
    <fabrizio.castro@...>
    Subject: Regarding RZ/G1CeMMC backporting patches

    Hi All,

    RZ/G1C eMMC IP is different from other RZ/G1 SoC's. It is having an internal
    DMA for data transfer which is similar to R-Car Gen3.

    Support for internal DMAC is added in 4.14 kernel and support for RZ/G1C
    added on 4.20 kernel.

    I have backported the relevant patches(86 patches) to 4.4 kernel and shared
    at [1].
    [1]. https://gitlab.com/bijud/emmc

    Please review this patches and share your opinion, so that I can send it to cip
    patchwork

    Regards,
    Biju


    Regarding RZ/G1CeMMC backporting patches

    Biju Das <biju.das@...>
     

    Hi All,

    RZ/G1C eMMC IP is different from other RZ/G1 SoC's. It is having an internal DMA for data transfer which is similar to R-Car Gen3.

    Support for internal DMAC is added in 4.14 kernel and support for RZ/G1C added on 4.20 kernel.

    I have backported the relevant patches(86 patches) to 4.4 kernel and shared at [1].
    [1]. https://gitlab.com/bijud/emmc

    Please review this patches and share your opinion, so that I can send it to cip patchwork

    Regards,
    Biju


    Re: [PATCH linux-4.4.y-cip v2 1/3] gitlab-ci: Split tests into separate jobs

    Nobuhiro Iwamatsu
     

    Hi all,

    In another email, there is a discussion on how to manage the gitlab-ci.yaml file,
    but I apply these patches and linux-4.19.y-cip as they are now needed for testing.

    Best regards,
    Nobuhiro

    -----Original Message-----
    From: cip-dev-bounces@...
    [mailto:cip-dev-bounces@...] On Behalf Of Chris
    Paterson
    Sent: Monday, October 14, 2019 4:49 PM
    To: cip-dev@...
    Subject: [cip-dev] [PATCH linux-4.4.y-cip v2 1/3] gitlab-ci: Split tests
    into separate jobs

    This will allow tests to run as soon as the corresponding build job is
    complete.

    This will help spread the load on the test infrastructure and save time.

    Signed-off-by: Chris Paterson <chris.paterson2@...>
    ---

    v1 -> v2
    * Added missing 'needs' entries

    .gitlab-ci.yml | 62
    +++++++++++++++++++++++++++++++++-----------------
    1 file changed, 41 insertions(+), 21 deletions(-)

    diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index
    e33099ea6594..ad8ec722b717 100644
    --- a/.gitlab-ci.yml
    +++ b/.gitlab-ci.yml
    @@ -4,8 +4,10 @@ variables:
    DOCKER_DRIVER: overlay2
    DOCKER_IMAGE_TAG: v2

    -# Building
    -arm_hitachi_omap_defconfig:
    +###############################
    +# Standard CIP configurations #
    +###############################
    +build:arm_hitachi_omap_defconfig:
    stage: build
    image:
    registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCK
    ER_IMAGE_TAG
    variables:
    @@ -21,7 +23,7 @@ arm_hitachi_omap_defconfig:
    paths:
    - output

    -arm_moxa_mxc_defconfig:
    +build:arm_moxa_mxc_defconfig:
    stage: build
    image:
    registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCK
    ER_IMAGE_TAG
    variables:
    @@ -37,7 +39,7 @@ arm_moxa_mxc_defconfig:
    paths:
    - output

    -arm_renesas_shmobile_defconfig:
    +build:arm_renesas_shmobile_defconfig:
    stage: build
    image:
    registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCK
    ER_IMAGE_TAG
    variables:
    @@ -54,7 +56,23 @@ arm_renesas_shmobile_defconfig:
    paths:
    - output

    -arm_siemens_am335x-axm2_defconfig:
    +test:arm_renesas_shmobile_defconfig:
    + stage: test
    + needs: ["build:arm_renesas_shmobile_defconfig"]
    + image:
    +registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:test-$DOCK
    ER_I
    +MAGE_TAG
    + when: always
    + variables:
    + GIT_STRATEGY: none
    + TEST_TIMEOUT: 60
    + script:
    + - /opt/submit_tests.sh
    + artifacts:
    + name: "$CI_JOB_NAME"
    + when: always
    + paths:
    + - output
    +
    +build:arm_siemens_am335x-axm2_defconfig:
    stage: build
    image:
    registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCK
    ER_IMAGE_TAG
    variables:
    @@ -70,7 +88,7 @@ arm_siemens_am335x-axm2_defconfig:
    paths:
    - output

    -arm_siemens_am335x-draco_defconfig:
    +build:arm_siemens_am335x-draco_defconfig:
    stage: build
    image:
    registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCK
    ER_IMAGE_TAG
    variables:
    @@ -86,7 +104,7 @@ arm_siemens_am335x-draco_defconfig:
    paths:
    - output

    -arm_siemens_am335x-dxr2_defconfig:
    +build:arm_siemens_am335x-dxr2_defconfig:
    stage: build
    image:
    registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCK
    ER_IMAGE_TAG
    variables:
    @@ -102,7 +120,7 @@ arm_siemens_am335x-dxr2_defconfig:
    paths:
    - output

    -arm_siemens_am335x-etamin_defconfig:
    +build:arm_siemens_am335x-etamin_defconfig:
    stage: build
    image:
    registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCK
    ER_IMAGE_TAG
    variables:
    @@ -118,7 +136,7 @@ arm_siemens_am335x-etamin_defconfig:
    paths:
    - output

    -arm_siemens_am57xx-pxm3.config:
    +build:arm_siemens_am57xx-pxm3.config:
    stage: build
    image:
    registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCK
    ER_IMAGE_TAG
    variables:
    @@ -134,7 +152,7 @@ arm_siemens_am57xx-pxm3.config:
    paths:
    - output

    -arm_siemens_dcu2.config:
    +build:arm_siemens_dcu2.config:
    stage: build
    image:
    registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCK
    ER_IMAGE_TAG
    variables:
    @@ -150,7 +168,7 @@ arm_siemens_dcu2.config:
    paths:
    - output

    -arm_siemens_imx6_defconfig:
    +build:arm_siemens_imx6_defconfig:
    stage: build
    image:
    registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCK
    ER_IMAGE_TAG
    variables:
    @@ -166,7 +184,7 @@ arm_siemens_imx6_defconfig:
    paths:
    - output

    -arm_toshiba_tegra_defconfig:
    +build:arm_toshiba_tegra_defconfig:
    stage: build
    image:
    registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCK
    ER_IMAGE_TAG
    variables:
    @@ -182,7 +200,7 @@ arm_toshiba_tegra_defconfig:
    paths:
    - output

    -arm_toshiba_zynq_defconfig:
    +build:arm_toshiba_zynq_defconfig:
    stage: build
    image:
    registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCK
    ER_IMAGE_TAG
    variables:
    @@ -198,7 +216,7 @@ arm_toshiba_zynq_defconfig:
    paths:
    - output

    -x86_plathome_obsvx1.config:
    +build:x86_plathome_obsvx1.config:
    stage: build
    image:
    registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCK
    ER_IMAGE_TAG
    variables:
    @@ -214,7 +232,7 @@ x86_plathome_obsvx1.config:
    paths:
    - output

    -x86_siemens_iot2000.config:
    +build:x86_siemens_iot2000.config:
    stage: build
    image:
    registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCK
    ER_IMAGE_TAG
    variables:
    @@ -230,7 +248,7 @@ x86_siemens_iot2000.config:
    paths:
    - output

    -x86_siemens_server_defconfig:
    +build:x86_siemens_server_defconfig:
    stage: build
    image:
    registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCK
    ER_IMAGE_TAG
    variables:
    @@ -246,7 +264,7 @@ x86_siemens_server_defconfig:
    paths:
    - output

    -x86_toshiba_defconfig:
    +build:x86_toshiba_defconfig:
    stage: build
    image:
    registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCK
    ER_IMAGE_TAG
    variables:
    @@ -262,8 +280,10 @@ x86_toshiba_defconfig:
    paths:
    - output

    -# Extra build configurations
    -arm_shmobile_defconfig:
    +########################
    +# Extra configurations #
    +########################
    +build:arm_shmobile_defconfig:
    stage: build
    image:
    registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:build-$DOCK
    ER_IMAGE_TAG
    variables:
    @@ -280,9 +300,9 @@ arm_shmobile_defconfig:
    paths:
    - output

    -# Testing
    -run_tests:
    +test:arm_shmobile_defconfig:
    stage: test
    + needs: ["build:arm_shmobile_defconfig"]
    image:
    registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:test-$DOCKE
    R_IMAGE_TAG
    when: always
    variables:
    --
    2.17.1

    _______________________________________________
    cip-dev mailing list
    cip-dev@...
    https://lists.cip-project.org/mailman/listinfo/cip-dev


    Re: [PATCH 4.19.y-cip 50/57] ASoC: rsnd: fixup 6ch settings to 8ch

    Kuninori Morimoto <kuninori.morimoto.gx@...>
     

    Hi Pavel

    +int rsnd_channel_normalization(int chan)
    +{
    + if ((chan > 8) || (chan < 0))
    + return 0;
    +
    + /* TDM Extend Mode needs 8ch */
    + if (chan == 6)
    + chan = 8;
    +
    + return chan;
    +}
    +
    Should the if ((chan > 8) || (chan < 0)) ever be true in practice?
    Sounds like bogus inputs to me. Should we dev_err() and return error
    in those cases? Or at least WARN_ON()?
    Hmm... indeed.
    Thank you for your report.
    I will re-check code, and post patch

    Thank you for your help !!
    Best regards
    ---
    Kuninori Morimoto


    Re: [PATCH 4.19.y-cip 39/57] ASoC: rsnd: remove RSND_REG_ from rsnd_reg

    Kuninori Morimoto <kuninori.morimoto.gx@...>
     

    Hi Pavel

    +#define SRCIN_TIMSEL(i) (SRCIN_TIMSEL0 + (i))
    +#define SRCOUT_TIMSEL(i) (SRCOUT_TIMSEL0 + (i))
    +#define CTU_SVxxR(i, j) (CTU_SV00R + (i * 8) + (j))
    +#define DVC_VOLxR(i) (DVC_VOL0R + (i))
    +#define AUDIO_CLK_SEL(i) (AUDIO_CLK_SEL0 + (i))
    +#define SSI_BUSIF_MODE(i) (SSI_BUSIF0_MODE + (i))
    +#define SSI_BUSIF_ADINR(i) (SSI_BUSIF0_ADINR + (i))
    +#define SSI_BUSIF_DALIGN(i) (SSI_BUSIF0_DALIGN + (i))
    +#define SSI_SYS_STATUS(i) (SSI_SYS_STATUS0 + (i))
    Would it still make sense to test that i is in expected range?

    #define CHECK_RANGE(i) ({ WARN_ON(i<0 || i>4); i; })
    #define SRCIN_TIMSEL(i) (SRCIN_TIMSEL0 + (i))
    Which range ?? for SRCIN ?
    I'm not sure it make sense. Can you send use case ??

    Thank you for your help !!
    Best regards
    ---
    Kuninori Morimoto

    6581 - 6600 of 10158