Changes in Kconfig

7bf5f056 - powerpc: Replace CONFIG_4xx with CONFIG_44x

Fri, 28 Jun 2024 12:12:00 +0000

powerpc: Replace CONFIG_4xx with CONFIG_44xReplace 4xx usage with 44x, and replace 4xx_SOC with 44x.Also, as pointed out by Christophe, if 44x || BOOKE can be simplified tojust test BOOKE, because 44x always selects BOOKE.Retain the CONFIG_4xx symbol, as there are drivers that use it to mean4xx || 44x, those will need updating before CONFIG_4xx can be removed.Signed-off-by: Michael Ellerman Link: https://msgid.link/20240628121201.130802-6-mpe@ellerman.id.au List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig

4f1d038b - powerpc/4xx: Remove MSI support which never worked

Mon, 06 Dec 2021 22:27:25 +0000

powerpc/4xx: Remove MSI support which never workedThis code is broken since day one. ppc4xx_setup_msi_irqs() has thefollowing gems: 1) The handling of the result of msi_bitmap_alloc_hwirqs() is completely broken: When the result is greater than or equal 0 (bitmap allocation successful) then the loop terminates and the function returns 0 (success) despite not having installed an interrupt. When the result is less than 0 (bitmap allocation fails), it prints an error message and continues to "work" with that error code which would eventually end up in the MSI message data. 2) On every invocation the file global pp4xx_msi::msi_virqs bitmap is allocated thereby leaking the previous one.IOW, this has never worked and for more than 10 years nobody cared. Removethe gunk.Fixes: 3fb7933850fa ("powerpc/4xx: Adding PCIe MSI support")Fixes: 247540b03bfc ("powerpc/44x: Fix PCI MSI support for Maui APM821xx SoC and Bluestone board")Signed-off-by: Thomas Gleixner Reviewed-by: Jason Gunthorpe Link: https://lore.kernel.org/r/20211206210223.872249537@linutronix.de List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig

08a456aa - powerpc/powernv: Move SCOM access code into powernv platform

Thu, 09 May 2019 05:11:15 +0000

powerpc/powernv: Move SCOM access code into powernv platformThe powernv platform is the only one that directly accesses SCOMs.Move the support code to platforms/powernv, and get rid of thePPC_SCOM Kconfig option, as SCOM support is always selected whencompiling for powernv.This also means that the Kconfig item for CONFIG_SCOM_DEBUGFS willshow up in menuconfig in the platform menu, rather than at the root,which is a much better location.Signed-off-by: Andrew Donnellan Signed-off-by: Michael Ellerman Link: https://lore.kernel.org/r/20190509051119.7694-1-ajd@linux.ibm.com List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig

cd238eff - docs: kbuild: convert docs to ReST and rename to *.rst

Wed, 12 Jun 2019 17:52:48 +0000

docs: kbuild: convert docs to ReST and rename to *.rstThe kbuild documentation clearly shows that the documentsthere are written at different times: some use markdown,some use their own peculiar logic to split sections.Convert everything to ReST without affecting too muchthe author's style and avoiding adding uneeded markups.The conversion is actually: - add blank lines and identation in order to identify paragraphs; - fix tables markups; - add some lists markups; - mark literal blocks; - adjust title markups.At its new index.rst, let's add a :orphan: while this is not linked tothe main index.rst file, in order to avoid build warnings.Signed-off-by: Mauro Carvalho Chehab Signed-off-by: Jonathan Corbet List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig

719736e1 - powerpc: remove redundant 'default n' from Kconfig-s

Tue, 09 Oct 2018 15:39:46 +0000

powerpc: remove redundant 'default n' from Kconfig-s'default n' is the default value for any bool or tristate Kconfigsetting so there is no need to write it explicitly.Also since commit f467c5640c29 ("kconfig: only write '# CONFIG_FOOis not set' for visible symbols") the Kconfig behavior is the sameregardless of 'default n' being present or not: ... One side effect of (and the main motivation for) this change is making the following two definitions behave exactly the same: config FOO bool config FOO bool default n With this change, neither of these will generate a '# CONFIG_FOO is not set' line (assuming FOO isn't selected/implied). That might make it clearer to people that a bare 'default n' is redundant. ...Signed-off-by: Bartlomiej Zolnierkiewicz Signed-off-by: Michael Ellerman List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig

243e2511 - powerpc/xive: Native exploitation of the XIVE interrupt controller

Wed, 05 Apr 2017 07:54:50 +0000

powerpc/xive: Native exploitation of the XIVE interrupt controllerThe XIVE interrupt controller is the new interrupt controllerfound in POWER9. It supports advanced virtualization capabilitiesamong other things.Currently we use a set of firmware calls that simulate the old"XICS" interrupt controller but this is fairly inefficient.This adds the framework for using XIVE along with a nativebackend which OPAL for configuration. Later, a backend allowingthe use in a KVM or PowerVM guest will also be provided.This disables some fast path for interrupts in KVM when XIVE isenabled as these rely on the firmware emulation code which is nolonger available when the XIVE is used natively by Linux.A latter patch will make KVM also directly exploit the XIVE, thusrecovering the lost performance (and more).Signed-off-by: Benjamin Herrenschmidt [mpe: Fixup pr_xxx("XIVE:"...), don't split pr_xxx() strings, tweak Kconfig so XIVE_NATIVE selects XIVE and depends on POWERNV, fix build errors when SMP=n, fold in fixes from Ben: Don't call cpu_online() on an invalid CPU number Fix irq target selection returning out of bounds cpu# Extra sanity checks on cpu numbers ]Signed-off-by: Michael Ellerman List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig

d17799f9 - powerpc/rcpm: add RCPM driver

Fri, 20 Nov 2015 09:13:59 +0000

powerpc/rcpm: add RCPM driverThere is a RCPM (Run Control/Power Management) in Freescale QorIQseries processors. The device performs tasks associated with devicerun control and power management.The driver implements some features: mask/unmask irq, enter/exit lowpower states, freeze time base, etc.Signed-off-by: Chenhui Zhao Signed-off-by: Tang Yuantian [scottwood: remove __KERNEL__ ifdef]Signed-off-by: Scott Wood List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig

e2c37d90 - powerpc: Added PCI MSI support using the HSTA module

Thu, 06 Mar 2014 03:52:28 +0000

powerpc: Added PCI MSI support using the HSTA moduleThe PPC476GTR SoC supports message signalled interrupts (MSI) by writingto special addresses within the High Speed Transfer Assist (HSTA) module.This patch adds support for PCI MSI with a new system device. The DMAwindow is also updated to allow access to the entire 42-bit address rangeto allow PCI devices write access to the HSTA module.Signed-off-by: Alistair Popple Signed-off-by: Benjamin Herrenschmidt List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig

66c29da6 - powerpc/powernv: Replace CONFIG_POWERNV_MSI with just CONFIG_PPC_POWERNV

Thu, 26 Sep 2013 07:52:17 +0000

powerpc/powernv: Replace CONFIG_POWERNV_MSI with just CONFIG_PPC_POWERNVWe currently have a user visible CONFIG_POWERNV_MSI option, but itdoesn't actually disable MSI for powernv. The MSI code is always built,what it does disable is the inclusion of the MSI bitmap code, whichleads to a build error.eg, with PPC_POWERNV=y and POWERNV_MSI=n we get: arch/powerpc/platforms/built-in.o: In function `.pnv_teardown_msi_irqs': pci.c:(.text+0x3558): undefined reference to `.msi_bitmap_free_hwirqs'We don't really need a POWERNV_MSI symbol, just have the MSI bitmap codedepend directly on PPC_POWERNV.Signed-off-by: Michael Ellerman Reviewed-by: Gavin Shan Signed-off-by: Benjamin Herrenschmidt List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig

4777f796 - powerpc/scom: CONFIG_SCOM_DEBUGFS should depend on CONFIG_DEBUG_FS

Thu, 29 Aug 2013 06:58:12 +0000

powerpc/scom: CONFIG_SCOM_DEBUGFS should depend on CONFIG_DEBUG_FSSigned-off-by: Benjamin Herrenschmidt List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig

a486bdb0 - powerpc/powernv: Add option CONFIG_POWERNV_MSI

Thu, 25 Apr 2013 19:20:58 +0000

powerpc/powernv: Add option CONFIG_POWERNV_MSIAs Michael Ellerman suggested, to add CONFIG_POWERNV_MSI for PowerNVplatform. That's similar to CONFIG_PSERIES_MSI for pSeries platform.For now, we don't make it dependent on CONFIG_EEH since it's not readyto enable that yet.Apart from that, we also enable CONFIG_PPC_MSI_BITMAP on selectingCONFIG_POWERNV_MSI.Signed-off-by: Gavin Shan Signed-off-by: Benjamin Herrenschmidt List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig

6263fb3b - powerpc/powernv: Fix missing Kconfig dependency for MSIs

Wed, 24 Apr 2013 05:15:33 +0000

powerpc/powernv: Fix missing Kconfig dependency for MSIsWe need PPC_MSI_BITMAP supportSigned-off-by: Benjamin Herrenschmidt List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig

44b24b74 - powerpc: Move GE PIC drivers

Mon, 12 Mar 2012 17:12:59 +0000

powerpc: Move GE PIC driversMove the GE PIC drivers to allow these to be used by non-86xx boards.Signed-off-by: Martyn Welch Signed-off-by: Kumar Gala List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig

3fb79338 - powerpc/4xx: Adding PCIe MSI support

Tue, 29 Mar 2011 23:10:24 +0000

powerpc/4xx: Adding PCIe MSI supportThis patch adds MSI support for 440SPe, 460Ex, 460Sx and 405Ex.Signed-off-by: Rupjyoti Sarmah Signed-off-by: Tirumala R Marri Acked-by: Josh Boyer Signed-off-by: Benjamin Herrenschmidt List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig

ab814b93 - powerpc: Add SCOM infrastructure

Thu, 14 Apr 2011 22:31:58 +0000

powerpc: Add SCOM infrastructureSCOM is a side-band configuration bus implemented on some processors.This code provides a way for code to map and operate on devices viaSCOM, while the details of how that is implemented is left up to aSCOM "controller" in the platform code.Signed-off-by: Benjamin Herrenschmidt Signed-off-by: Michael Ellerman Signed-off-by: Benjamin Herrenschmidt List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig

0b05ac6e - powerpc/xics: Rewrite XICS driver

Mon, 04 Apr 2011 03:46:58 +0000

powerpc/xics: Rewrite XICS driverThis is a significant rework of the XICS driver, too significant toconveniently break it up into a series of smaller patches to be honest.The driver is moved to a more generic location to allow new platformsto use it, and is broken up into separate ICP and ICS "backends". Fornow we have the native and "hypervisor" ICP backends and one commonRTAS ICS backend.The driver supports one ICP backend instanciation, and many ICS ones,in order to accomodate future platforms with multiple possibly differentinterrupt "sources" mechanisms.Signed-off-by: Benjamin Herrenschmidt List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig

782f04fc - powerpc: Move 8xxx GPIO Kconfig under the platform menu

Wed, 24 Sep 2008 04:36:32 +0000

powerpc: Move 8xxx GPIO Kconfig under the platform menuThe initial patch had the option at the top level which wasn'tquite right. Moving under the platform options is a bit better.Signed-off-by: Kumar Gala List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig

1e16dfc1 - powerpc: gpio driver for mpc8349/8572/8610 and compatible

Tue, 23 Sep 2008 15:35:38 +0000

powerpc: gpio driver for mpc8349/8572/8610 and compatibleStructured similar to the existing QE GPIO support.Signed-off-by: Peter Korsgaard Acked-by: Anton Vorontsov Signed-off-by: Kumar Gala List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig

7e302869 - powerpc: Split-out common MSI bitmap logic into msi_bitmap.c

Tue, 05 Aug 2008 23:10:01 +0000

powerpc: Split-out common MSI bitmap logic into msi_bitmap.cThere are now two almost identical implementations of an MSI bitmapallocator, one in mpic_msi.c and the other in fsl_msi.c.Merge them together and put the result in msi_bitmap.c. Some of theMPIC bits will remain to provide a nicer interface for the MPIC users.In the process we fix two buglets. The first is that the allocationroutines, now msi_bitmap_alloc_hwirqs(), returned an unsigned result,even though they use -1 to indicate allocation failure. Although allthe callers were checking correctly, it is much better for the routineto just return an int. At least until someone wants > ~2 billion MSIs.The second buglet is that the device tree reservation logic onlyallowed power-of-two reservations. AFAICT that didn't effect anyexisting code but it's nicer if we can reserve arbitrary irqs from MSIuse.We also add some selftests, which exposed the two buglets and now testfor them, as well as some basic sanity tests. The tests are only builtwhen CONFIG_DEBUG_KERNEL=y.Signed-off-by: Michael Ellerman Signed-off-by: Paul Mackerras List of files: /linux-6.15/arch/powerpc/sysdev/Kconfig