summaryrefslogtreecommitdiff
path: root/meta-phosphor/aspeed-layer/recipes-kernel
AgeCommit message (Collapse)AuthorFilesLines
2021-04-06phosphor: Remove phosphor-vlan machine featureJoel Stanley3-14/+0
This feature is used to turn on the CONFIG_VLAN_8021Q kernel option for all systems using the phosphor layer. However, the kernel option has been enabled in the defconfigs for aspeed g4, g5, g6, and nuvoton via gbs, and gxp. Drop the feature and subseqently remove KERNEL_DANGLING_FEATURES_WARN_ONLY. Change-Id: I544cb5ba8e74f1217f90cc1eaccf725beb32bd3b Signed-off-by: Joel Stanley <joel@jms.id.au>
2021-03-01Remove phsophor-gpio-keys as a standalone featureJoel Stanley3-11/+0
The feature was implemented as an append to the kernel (BSP) layers in meta-phsophor. This created a three way dance between machine layers, BSP and meta-phosphor, when it should have been the kernel layer providing this feature and machines could then opt in. Fixing this means we could remove the KERNEL_DANGLING_FEATURES_WARN_ONLY workaround. As the feature is simply turning on a pair of kernel options without any other impact, we can implement it by adding the options to our defconfigs. In fact, aspeed and hpe kernel configurations enable the two kernel options: $ git grep CONFIG_KEYBOARD_GPIO=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g4/defconfig:CONFIG_KEYBOARD_GPIO=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g5/defconfig:CONFIG_KEYBOARD_GPIO=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/defconfig:CONFIG_KEYBOARD_GPIO=y meta-hpe/meta-gxp/recipes-kernel/linux/linux-obmc/defconfig:CONFIG_KEYBOARD_GPIO=y $ git grep CONFIG_INPUT_EVDEV meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g4/defconfig:CONFIG_INPUT_EVDEV=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g5/defconfig:CONFIG_INPUT_EVDEV=y meta-aspeed/recipes-kernel/linux/linux-aspeed/aspeed-g6/defconfig:CONFIG_INPUT_EVDEV=y meta-hpe/meta-gxp/recipes-kernel/linux/linux-obmc/defconfig:CONFIG_INPUT_EVDEV=y Other machines that wish to enable this feature should ensure it is added to their BSP's defconfig, or add it to their machine specific defconfig. Change-Id: I0726836319022f96c1d13d4a0cbd73708047302c Signed-off-by: Joel Stanley <joel@jms.id.au>
2020-10-22wdt-on-panic: remove overrides from meta-phosphorAndrew Geissler3-6/+0
If these are needed, they really should be done within the meta-aspeed layer. This was originally done to allow the BMC hardware watchdogs to control the reboot of the BMC in error scenarios vs. the kernel auto rebooting itself. This is causing issues on AST2600 hardware because the watchdogs are not setup correctly. Kernel panics result in the BMC becoming unusable and not rebooting, requiring a manual power cycle. The goal with letting the hardware watchdogs control the reboot was that fancy things like flash side switches could be performed for recovery scenarios. However the end to end software stack for this was never fully implemented so if a flash side switch did occur, there would be no notice to the user of the system, and in most cases the BMC was still inoperable because the network settings were missing. For now, we should just go back to the defaults built into the meta-aspeed layer which is to panic on oops and have the kernel immediately reboot the BMC when a panic occurs. Once we iron out the watchdog usage, we can look into changing these back in the meta-aspeed layer if needed. (From meta-phosphor rev: 7777a8eda2b4909f34605476813e1e364b0d5728) Change-Id: I18a15a7769b27d6dd577bcc4e35cc9f60c4d3240 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-09-09simplify setting of KERNEL_DANGLING_FEATURES_WARN_ONLYAndrew Geissler1-6/+3
Setting this within python is not required (From meta-phosphor rev: b737ffb23aff232b2ce212ad54171afe7b216a71) Change-Id: I3d799b5cd9e66c9bc1a4d145274bfa3c06bdf575 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-09-01kernel: enable KERNEL_DANGLING_FEATURES_WARN_ONLYAndrew Geissler1-0/+7
Uptream yocto recently added some new code which enforces kernel feature validation. The commit which did this is: https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=095175595d9f28d5a0eb7ea520c9af0100bb8dfd This caused OpenBMC builds to start failing with the following: | ERROR: Feature 'phosphor-wdt-on-panic' not found, this will cause configuration failures. | ERROR: Check the SRC_URI for meta-data repositories or directories that may be missing | ERROR: Set KERNEL_DANGLING_FEATURES_WARN_ONLY to ignore this issue OpenBMC does not utilize this aspect of the kernel-yocto.bbclass so make it a warning only. Tested: Verified that the resultant build still had the expected CONFIG options set in the linux-aspeed defconfig. Resolves openbmc/openbmc#3690 (From meta-phosphor rev: d9a065db400bea4b026e240532dd369e588c967d) Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I7590e6304307599cbc77ef26ca9708a70d47d8a0 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2019-04-08aspeed: Remove Witherspoon DTS patchJoel Stanley2-91/+0
An atomic cross-layer update is required to do this - as such this commit consists of these subtree commits, squashed: meta-aspeed linux-aspeed: Witherspoon flash layout, GFX DRM meta-phosphor aspeed: Remove Witherspoon DTS patch Change-Id: I57d466163fdc5dc188424e7cade688779f15def0 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-10-27meta-phosphor: aspeed-layer: cf-fsi-firmware: rename as gitPatrick Venture1-0/+3
Rename cf-fsi-firmware.bb as git per OE norms. (From meta-phosphor rev: 1387adce04d049311de7dbebc8d7ae9dc324f6c4) Change-Id: I3a73fa25d31c30be5425490e41fd8ef09355318a Signed-off-by: Patrick Venture <venture@google.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-09-05Spelling fixesGunnar Mills1-1/+1
Spelling errors found using github.com/lucasdemarchi/codespell A tool to fix common misspellings. This tool is licensed under GNU General Public License, version 2. (From meta-phosphor rev: 38f27112a9bc38337d8f4c63c333d2a1f28945fa) Change-Id: I834b99d63a260f21c60b58c91ec328cf04b683fe Signed-off-by: Gunnar Mills <gmills@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-08-07cf-fsi-firmware: Update to v4Joel Stanley1-2/+2
The latest version uses a unified firmware binary, so we can use the one binary on all machines. Change-Id: I59525c9203a491ac786a5199e457c1847a4ae0e0 Signed-off-by: Joel Stanley <joel@jms.id.au>
2018-07-05kernel: FSI, ASPEED SPI NOR, ASPEED GFXJoel Stanley1-8/+9
Benjamin Herrenschmidt (11): drm: aspeed: Enable/disable vblank in pipe enable/disable devres: Add devm_of_iomap() fsi: Move code around to avoid forward declaration fsi: Add mechanism to set the tSendDelay and tEchoDelay values fsi: master-gpio: Rename and adjust send delay fsi: master-gpio: Add support for link_config fsi: master-gpio: Add more tracepoints fsi: master-gpio: Remove unused definitions fsi: master-gpio: Remove "GPIO" prefix on some definitions fsi: master-gpio: Add missing release function fsi: Move various master definitions to a common header Cédric Le Goater (2): ARM: dts: aspeed: Add "spi-max-frequency" property mtd: spi-nor: aspeed: limit the maximum SPI frequency Joel Stanley (2): ARM: config: aspeed: Enable SHA256 and HMAC ARM: config: aspeed: Re-enable DEVMEM Resolves: openbmc/openbmc#3164 Change-Id: I7f1970a8123b6d335e6dd2bda525c02cc393ede4 Signed-off-by: Joel Stanley <joel@jms.id.au> Signed-off-by: Eddie James <eajames@linux.vnet.ibm.com>
2018-06-27aspeed: Add cf-fsi firmwareJoel Stanley1-0/+25
This project installs the machine specific ColdFire firmware file into /lib/firmware for using the ColdFire FSI master kenrel driver. The repository contains source and corresponding assembled binaries. We do not assemble our own binaries as that would require building binutils for the 68k. Change-Id: Iac13f94532e0cdf92814f2521f170778505f30f7 Signed-off-by: Joel Stanley <joel@jms.id.au>
2018-06-15Rename and move kernel recipeBrad Bishop8-0/+117
Rename linux-obmc to linux-aspeed and move to the Aspeed layer. Like recipes for u-boot forks, recipes for kernel forks in support of different SOCs are typically provided in the BSP supporting the SOC. Moved a number of phosphor-isms out of the kernel recipe and put those in a bbappend in aspeed-layer/bbappend. Removed COMPATIBLE_MACHINE setting. We simply use PREFERRED_PROVIDER in machine configuration files to set the default kernel recipe. Tested: Booted spoon/palmetto images using QEMU Change-Id: I7dc73629cad4789dcd5aeb0f7b6214fe064c6adc Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>