commit 9cad72dfc5567c66ab0e5a0a2474c5f36c268694 upstream. The RZ/V2M USB3.1 Gen1 Interface (USB) composed of a USB3.1 Gen1 Dual Role Device controller (USB3DRD), a USB3.1 Gen1 Host controller (USB3HOS

commit 9486e56c49be7dc771ecae9bf67b1034cd440d10 upstream. Add device tree bindings for the RZ/V2{M, MA} USB3DRD module. Signed-off-by: Biju Das <biju.das.jz@...> Reviewed-by: Rob Herring <robh@...> Li

commit 2c5502a4dc9ffb9145ef80e642be0f1f03c037e8 upstream. Document RZ/V2MA usb3-peri bindings. RZ/V2MA usb3-peri is identical to one found on the RZ/V2M SoC. No driver changes are required as generic

From: Phil Edworthy <phil.edworthy@...> commit b9f20cff54f76e5fdc5be3eb33286416b3494492 upstream. RZ/V2M (r9a09g011) has a few differences: - The USB3_DRD_CON register has moved, its called USB_PERI_D

commit 29218d6ce4da741f8a1a86974999e8790683c23b upstream. On RZ/V2M, USB3DRD module manages the drd_reset. Moreover, the interrupts drd, gpi and bc are part of USB3DRD block. This patch removes drd_re

From: Phil Edworthy <phil.edworthy@...> commit 3c3ce77c9dab7f9628a9a96e881d0afb50ed74a6 upstream. Document the RZ/V2M SoC bindings. The RZ/V2M SoC is a little different to the R-Car implementations. A

commit e696d70f600abbe2b7fe81008bcb24d239a74672 upstream. Document the RZ/V2M SoC bindings. The RZ/V2M SoC is a little different to the R-Car implementations. You can access the registers associated w

commit 569d23e9bf58464887c55aa0d2bdb0ead97f8592 upstream. Some platforms(for eg: RZ/V2M EVK) does not have interrupt pin connected to HD3SS3220. Add polling support for role detection. Signed-off-by:

commit 5edf5b51e760af749c4a8e67cde92db4f3680be5 upstream. Add USB clock and reset entries to CPG driver. Signed-off-by: Biju Das <biju.das.jz@...> Reviewed-by: Geert Uytterhoeven <geert+renesas@...> L

Hi All, RZ/G2L MTU3a counter driver support is added to 6.4 mainline kernel [1]. Counter framework restructure happened from 5.15 along with that all vendor specific driver code is also updated[2] and

From: venkata pyla <venkata.pyla@...> Hi, This patch series enable ext4 file system images in reproducible check CI, which is next step after tarball images are being reproducible, let's see new issue

This is a copy of the IPC227e defconfig, just `CONFIG_WDAT_WDT=3Dm` added for watchdog support on that platform. Signed-off-by: Claudius Heine <ch@...> --- 6.1.y-cip/x86/siemens_ipc127e.sources | 1096

This is a copy of the IPC227e defconfig, just `CONFIG_WDAT_WDT=3Dm` added for watchdog support on that platform. Signed-off-by: Claudius Heine <ch@...> --- 4.19.y-cip/x86/siemens_ipc127e.sources | 913

From: venkata pyla <venkata.pyla@...> html output is easy to watch the differences in the browser. Signed-off-by: venkata pyla <venkata.pyla@...> --- .reproducible-check-ci.yml | 2 +- scripts/repro-te

From: venkata pyla <venkata.pyla@...> Till now we are using tarball images in reproducible checks and with this commit we are also verifying ext4 file system images in reproducible check CI. Signed-of

From: venkata pyla <venkata.pyla@...> This option file helps to create tarball and ext4 images for the rootfs and which can be used in reproducible build checks. Signed-off-by: venkata pyla <venkata.p

Hi all, Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today. Our channel is the following: irc:irc.libera.chat:6667/cip The IRC meeting is sch

Hi ! It's this week's CVE report. This week reported 5 new CVEs and 3 updated CVEs. * New CVEs CVE-2023-2898: f2fs: fix to avoid NULL pointer dereference f2fs_write_end_io() CVSS v3 score is not provi

cip/linux-4.4.y-st-rc ltp-pty: 3 runs, 1 regressions (v4.4-st20-1307-g20af3740f4fc) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig | regressions -----------------

cip/linux-4.4.y-st-rc ltp-ipc: 5 runs, 1 regressions (v4.4-st20-1307-g20af3740f4fc) Regressions Summary ------------------- platform | arch | lab | compiler | defconfig | regressions -----------------