summaryrefslogtreecommitdiffstats
path: root/meta-agl-bsp/meta-rcar-gen3-adas/recipes-kernel/linux
AgeCommit message (Collapse)AuthorFilesLines
2021-10-29[RCAR] Update RCAR BSP recipes to 5.5.0 versionRonan Le Martret1-20/+50
* rename the dts/dtsi file, the new BSP 5.5.0 change the file name of the dts file. * update the driver files hash * Add "meta-yocto-bsp" to BBLAYERS, it's new dependency of meta-renesas. Bug-AGL: SPEC-4081 Signed-off-by: Ronan Le Martret <ronan.lemartret@iot.bzh> Change-Id: I53b71906e7174d7b1153a6912f7181171730147c Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/26703 Tested-by: Jenkins Job builder account ci-image-build: Jenkins Job builder account ci-image-boot-test: Jenkins Job builder account Reviewed-by: Scott Murray <scott.murray@konsulko.com> Reviewed-by: Stephane Desneux <stephane.desneux@iot.bzh> Reviewed-by: Harunobu Kurokawa <harunobu.kurokawa.dn@renesas.com>
2021-08-23Convert to new override syntaxScott Murray1-3/+3
This is mostly the result of running a slightly customized version of the convert-overrides.py script from poky with additional overrides added. A few minor fixups were done by hand afterwards during a review of the changes. The intent of these changes is to minimize the effort to keep the "next" branch that builds against poky master up to date and tested in preparation for the switch to the next Yocto LTS release in early 2022. Bug-AGL: SPEC-4052 Signed-off-by: Scott Murray <scott.murray@konsulko.com> Change-Id: Ia3bf63b7cb1aa1d95ada373d1a3ab56def0a125d Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/26564 Tested-by: Jenkins Job builder account ci-image-build: Jenkins Job builder account ci-image-boot-test: Jenkins Job builder account Reviewed-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
2021-06-29Refactor kernel configuration fragment handlingScott Murray2-10/+0
Refactor the kernel configuration fragment handling to shift all AGL applied configuration fragments into a new AGL_KCONFIG_FRAGMENTS variable that is used to generate SRC_URI and KERNEL_CONFIG_FRAGMENTS additions for the various BSPs. The intent is to make it simple to disable AGL provided configuration in downstream builds as the IC EG has expressed as a requirement. Additionally, the rework has allowed for some clean up of accumulated cruft. In practice, clearing AGL_KCONFIG_FRAGMENTS drops all non-BSP provided kernel configuration with the exception of some qemu BSP related additions required for AGL CI and some explicitly configurable things like netboot support. Notable changes: - Instead of always using AGL's own fragment merging logic on top of the BSP kernel recipe, an effort is now made to leverage the BSP recipes' own merging schemes, so there are now separate include files for kernel-yocto.bbclass and plain kernel.bbclass based kernel recipes, as well as a common include file that defines the AGL_KCONFIG_FRAGMENTS variable and its derivations. That file can be included directly in bbappends for BSP kernel recipes that use the KERNEL_CONFIG_FRAGMENTS scheme (e.g. meta-ti, meta-qcom). - The SMACK enabling configuration in meta-app-framework has been updated to supply different fragments for enabling SMACK by default for 4.x and 5.x kernels. This removes a warning from always supplying the old configuration, and allows providing a CONFIG_LSM definition to ensure over-riding any BSP modifications. This allows removing the previous hack to handle CONFIG_LSM being set in the defconfigs in linux-raspberrypi. - By request, the linux-yocto support from meta-agl-bsp/meta-core has been rationalized into meta-agl-core to improve the experience when using meta-agl-core standalone for testing. - All demo supporting kernel configuration has been removed, a subsequent change to meta-agl-demo will add it there by leveraging AGL_KCONFIG_FRAGMENTS. - The hardware device support has been split out of the can-bus.cfg fragment, in favor of shifting it to meta-agl-demo. A few other stray non-CAN configuration options have also been removed from can-bus.cfg, as they do not seem to be required. Bug-AGL: SPEC-3983 Signed-off-by: Scott Murray <scott.murray@konsulko.com> Change-Id: If6662fd36e26cec767b1d53b1188a74d01ef9dcf Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/26460 Reviewed-by: Hiroyuki Ishii <ishii.hiroyuki002@jp.panasonic.com> Reviewed-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org> Tested-by: Jenkins Job builder account ci-image-build: Jenkins Job builder account ci-image-boot-test: Jenkins Job builder account
2020-12-17[RCAR] disable a default config in kernelronan1-0/+4
The meta-rcar layer activates by default the configuration MTD_RENESAS_RPC_HYPERFLASH in kernel. MTD_RENESAS_RPC_HYPERFLASH is not upstream, it's a meta-rcar specific feature. MTD_RENESAS_RPC_HYPERFLASH feature in the kernel need an firmware update on the board and can be considered (IMHO) as a security issues in production. We need to set DISABLE_RPC_ACCESS to deactivate it. v2 (jsmoeller): Use ?= for DISABLE_RPC_ACCESS . Bug-AGL: SPEC-3674 Signed-off-by: ronan <ronan.lemartret@iot.bzh> Change-Id: Iefaf9ca115d1fb805b0d3766fc0c800b74daecee Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/25815 Tested-by: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org> ci-image-build: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org> ci-image-boot-test: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org> Reviewed-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
2020-08-24[RCAR] Remove perf fix on renesas boardronan1-3/+0
* In RCAR BSP 4.14 the perf fix is upstream, we don't need to keep this fix in AGL. Bug-AGL: SPEC-3516 Signed-off-by: Ronan Le Martret <ronan.lemartret@iot.bzh> Change-Id: Ic014347319318122f99eabf48170a5b393ab46c5 Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/25069 Reviewed-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org> Tested-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
2020-07-14meta-rcar-gen3-adas: Restore local linux-renesas changes for KFScott Murray1-0/+5
The local patch to fix the KingFisher HDMI connector ordering and a configuration fragment to disable its onboard MOST support were accidentally dropped in the previous change for the perf BFD patch issue. Add them back to restore previous behavior. Bug-AGL: SPEC-3443 Signed-off-by: Scott Murray <scott.murray@konsulko.com> Change-Id: I527d073901bad4860475df81da36bbf60d8c5be5 Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/25011 Tested-by: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org> ci-image-build: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org> Reviewed-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org> Reviewed-by: Stéphane Desneux <stephane.desneux@iot.bzh> ci-image-boot-test: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org>
2020-07-07Apply the perf fix only when meta-rcar-gen3-adas is not presentJan-Simon Möller1-9/+2
Currently the upstream rcar bsp does need the fix for building perf. The meta-rcar-gen3-adas layer contains a fix in the big patchqueue. Thus conditionally apply the perf build fix. Bug-AGL: SPEC-3443 Signed-off-by: Jan-Simon Möller <jsmoeller@linuxfoundation.org> Change-Id: Icbf53add71ed731c35dec149841691c82ae4372c Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/24914 Reviewed-by: Stéphane Desneux <stephane.desneux@iot.bzh>
2020-07-07Use upstream meta-renesas from github and update meta-rcar-gen3-adas integrationJan-Simon Moeller1-0/+0
Thanks to the work done by Renesas and members of our community, we can now directly use meta-renesas from upstream github. A shout-out to everyone involved (Kurokawa-san, Ronan, Stephane). It turned-out it is simpler to create a symlink-based slim version of meta-rcar-gen3-adas layer instead of BBMASK'ing what should not be in there. See the comments in meta-agl-bsp/meta-rcar-gen3-adas/conf/NOTES as to why. Remaining work is to include the packages outside of the layer.conf in a follow-up. Bug-AGL: SPEC-3380 Change-Id: I2be1b44049d74146546380e2eb866f0558a26822 Signed-off-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org> Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/24796 Reviewed-by: Stéphane Desneux <stephane.desneux@iot.bzh>
2020-01-30[RCAR] Split ADSP path for ulcb and ulcb-kfRonan Le Martret2-0/+59
- If we want to build AGL for ulcb board without the meta-rcar (kingficher board support), we need to split the patch. Change-Id: I145887d4619a7132e46f98f30e1fc0dd3de6b29a Signed-off-by: Ronan Le Martret <ronan.lemartret@iot.bzh>
2019-06-06[RCAR] Remove unnecessary device tree fileHarunobu Kurokawa1-0/+20
Bug-AGL: SPEC-2486 Change-Id: Ic0cf9128d1630ede1af8024e3bd5258b7529b683 Signed-off-by: Harunobu Kurokawa <harunobu.kurokawa.dn@renesas.com>
2018-11-15[RCAR][upstream] remove dts patch for SDIO frequencyHarunobu Kurokawa1-0/+4
Bug-AGL: SPEC-1945 Latest meta-rcar update SDIO frequency for TI's WLAN driver. However, in M3 case, the this patch raise ti/wlcore driver WANING. [ 107.009706] ------------[ cut here ]------------ [ 107.014342] WARNING: CPU: 0 PID: 4224 at /kernel-source//drivers/net/wireless/ti/wlcore/sdio.c:145 wl12xx_sdio_raw_write+0xb0/0x160 [wlcore_sdio] [ 107.027375] Modules linked in: rfcomm 8021q garp stp mrp llc can_bcm can bnep nfc arc4 wl18xx wlcore mac80211 cfg80211 crc32_ce crct10dif_ce btwilink bluetooth ecdh_generic wlcore_sdio rcar_can st_drv rfkill can_dev vspm_if(O) vsp2(O) vspm(O) uvcs_drv(O) sllin(O) pvrsrvkm(O) mmngrbuf(O) mmngr(O) hdm_usb(O) hdm_i2c(O) hdm_dim2(O) aim_v4l2(O) aim_sound(O) aim_network(O) aim_cdev(O) mostcore(O) ipv6 [ 107.062537] CPU: 0 PID: 4224 Comm: wpa_supplicant Tainted: G O 4.14.35-yocto-standard #1 [ 107.071749] Hardware name: Renesas M3ULCB Kingfisher board based on r8a7796 (DT) [ 107.079138] task: ffff8005fc610e00 task.stack: ffff000020bc8000 [ 107.085054] PC is at wl12xx_sdio_raw_write+0xb0/0x160 [wlcore_sdio] [ 107.091316] LR is at wl12xx_sdio_raw_write+0x7c/0x160 [wlcore_sdio] <snip> [ 107.467808] ---[ end trace 0140d637a5afd50b ]--- [ 107.472613] wl1271_sdio mmc2:0001:2: sdio write failed (-84) [ 107.478340] ------------[ cut here ]------------ [ 107.483008] WARNING: CPU: 0 PID: 4224 at /kernel-source//drivers/net/wireless/ti/wlcore/main.c:796 wl12xx_queue_recovery_work.part.26+0x58/0x60 [wlcore] [ 107.496648] Modules linked in: rfcomm 8021q garp stp mrp llc can_bcm can bnep nfc arc4 wl18xx wlcore mac80211 cfg80211 crc32_ce crct10dif_ce btwilink bluetooth ecdh_generic wlcore_sdio rcar_can st_drv rfkill can_dev vspm_if(O) vsp2(O) vspm(O) uvcs_drv(O) sllin(O) pvrsrvkm(O) mmngrbuf(O) mmngr(O) hdm_usb(O) hdm_i2c(O) hdm_dim2(O) aim_v4l2(O) aim_sound(O) aim_network(O) aim_cdev(O) mostcore(O) ipv6 [ 107.531806] CPU: 0 PID: 4224 Comm: wpa_supplicant Tainted: G W O 4.14.35-yocto-standard #1 [ 107.541018] Hardware name: Renesas M3ULCB Kingfisher board based on r8a7796 (DT) [ 107.548406] task: ffff8005fc610e00 task.stack: ffff000020bc8000 [ 107.554363] PC is at wl12xx_queue_recovery_work.part.26+0x58/0x60 [wlcore] [ 107.561265] LR is at wl12xx_queue_recovery_work+0x1c/0x28 [wlcore] Change-Id: I6f15251e6997f52892efd118e8941af5930c5ca9 Signed-off-by: Harunobu Kurokawa <harunobu.kurokawa.dn@renesas.com>
2018-03-20[AGL] ulcb: Disable build-in most driverHarunobu Kurokawa2-1/+11
Kingfisher has MedlaLB Interface for most, kernel tree has most driver as build-in driver. So these configs is enabled. Howemver AGL use most driver in gerrit repository. So AGL should be disable it. Change-Id: Ia46500d58fc16f348a098c58f5e807cf37913e5e Signed-off-by: Harunobu Kurokawa <harunobu.kurokawa.dn@renesas.com>
2018-03-20Preserve HDMI naming for kingficher boardRonan Le Martret2-0/+89
Change-Id: Id1b6b88e606d0a102eefbdb9c8deae2dfe0cf73b Signed-off-by: Ronan Le Martret <ronan.lemartret@iot.bzh> Signed-off-by: Harunobu Kurokawa <harunobu.kurokawa.dn@renesas.com>