Changes in Kconfig

e3217540 - ARM/dma-mapping: remove dmabounce

Tue, 19 Apr 2022 07:35:29 +0000

ARM/dma-mapping: remove dmabounceRemove the now unused dmabounce code.Signed-off-by: Christoph Hellwig Reviewed-by: Arnd Bergmann List of files: /linux-6.15/arch/arm/common/Kconfig

9ba26f5c - ARM: sa1100/assabet: move dmabounce hack to ohci driver

Thu, 03 Feb 2022 08:36:33 +0000

ARM: sa1100/assabet: move dmabounce hack to ohci driverThe sa1111 platform is one of the two remaining users of the old Armspecific "dmabounce" code, which is an earlier implementation of thegeneric swiotlb.Linus Walleij submitted a patch that removes dmabounce support fromthe ixp4xx, and I had a look at the other user, which is the sa1111companion chip.Looking at how dmabounce is used, I could narrow it down to one driverone three machines: - dmabounce is only initialized on assabet/neponset, jornada720 and badge4, which are the platforms that have an sa1111 and support DMA on it. - All three of these suffer from "erratum #7" that requires only doing DMA to half the memory sections based on one of the address lines, in addition, the neponset also can't DMA to the RAM that is connected to sa1111 itself. - the pxa lubbock machine also has sa1111, but does not support DMA on it and does not set dmabounce. - only the OHCI and audio devices on sa1111 support DMA, but as there is no audio driver for this hardware, only OHCI remains.In the OHCI code, I noticed that two other platforms already havea local bounce buffer support in the form of the "local_mem"allocator. Specifically, TMIO and SM501 use this on a few other ARMboards with 16KB or 128KB of local SRAM that can be accessed from theOHCI and from the CPU.While this is not the same problem as on sa1111, I could not find areason why we can't re-use the existing implementation but replace thephysical SRAM address mapping with a locally allocated DMA buffer.There are two main downsides: - rather than using a dynamically sized pool, this buffer needs to be allocated at probe time using a fixed size. Without having any idea of what it should be, I picked a size of 64KB, which is between what the other two OHCI front-ends use in their SRAM. If anyone has a better idea what that size is reasonable, this can be trivially changed. - Previously, only USB transfers to unaddressable memory needed to go through the bounce buffer, now all of them do, which may impact runtime performance for USB endpoints that do a lot of transfers.On the upside, the local_mem support uses write-combining buffers,which should be a bit faster for transfers to the device compared tonormal uncached coherent memory as used in dmabounce.Cc: Linus Walleij Cc: Russell King Cc: Christoph Hellwig Cc: Laurentiu Tudor Cc: linux-usb@vger.kernel.orgSigned-off-by: Arnd Bergmann Reviewed-by: Greg Kroah-Hartman Acked-by: Alan Stern Signed-off-by: Christoph Hellwig List of files: /linux-6.15/arch/arm/common/Kconfig

36d68f64 - ARM: Add Krait L2 register accessor functions

Tue, 14 Aug 2018 12:12:20 +0000

ARM: Add Krait L2 register accessor functionsKrait CPUs have a handful of L2 cache controller registers thatlive behind a cp15 based indirection register. First you programthe indirection register (l2cpselr) to point the L2 'window'register (l2cpdr) at what you want to read/write. Then youread/write the 'window' register to do what you want. Thel2cpselr register is not banked per-cpu so we must lock aroundaccesses to it to prevent other CPUs from re-pointing l2cpdrunderneath us.Cc: Mark Rutland Cc: Russell King Acked-by: Bjorn Andersson Signed-off-by: Stephen Boyd Signed-off-by: Sricharan R Tested-by: Craig Tatlor Signed-off-by: Stephen Boyd List of files: /linux-6.15/arch/arm/common/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/arm/common/Kconfig

ba3fae06 - ARM/clk: move the ICST library to drivers/clk

Wed, 01 Feb 2017 09:41:43 +0000

ARM/clk: move the ICST library to drivers/clkThis moves the ICST clock divider helper library fromarch/arm/common to drivers/clk/versatile so it is maintainedwith the other clock drivers.We keep the structure as a helper library intact and do notfuse it with the clk-icst.c Versatile ICST clock driver: theremay be other users out there that need to use this library fortheir clocking, and then it will be helpful to keep thelibrary contained. (The icst.[c|h] files could just be movedto drivers/clk/lib or a similar location to share the library.)Acked-by: Stephen Boyd Signed-off-by: Linus Walleij List of files: /linux-6.15/arch/arm/common/Kconfig

2b6b3b74 - ARM/dmaengine: edma: Merge the two drivers under drivers/dma/

Wed, 14 Oct 2015 11:42:53 +0000

ARM/dmaengine: edma: Merge the two drivers under drivers/dma/Move the code out from arch/arm/common and merge it inside of the dmaenginedriver.This change is done with as minimal (if eny) functional change to the codeas possible to avoid introducing regression.Signed-off-by: Peter Ujfalusi Acked-by: Tony Lindgren Signed-off-by: Vinod Koul List of files: /linux-6.15/arch/arm/common/Kconfig

3ad7a42d - ARM: davinci: move private EDMA API to arm/common

Wed, 06 Mar 2013 16:15:31 +0000

ARM: davinci: move private EDMA API to arm/commonMove mach-davinci/dma.c to common/edma.c so it can be usedby OMAP (specifically AM33xx) as well.Signed-off-by: Matt Porter Acked-by: Chris Ball # davinci_mmc.cAcked-by: Mark Brown Acked-by: Olof Johansson [nsekhar@ti.com: dropped davinci sffsdr changes]Signed-off-by: Sekhar Nori List of files: /linux-6.15/arch/arm/common/Kconfig

44430ec0 - irqchip: Move ARM VIC to drivers/irqchip

Sat, 27 Oct 2012 22:25:26 +0000

irqchip: Move ARM VIC to drivers/irqchipNow that we have drivers/irqchip, move VIC irqchip to drivers/irqchip.Signed-off-by: Rob Herring Cc: Russell King Cc: Thomas Gleixner List of files: /linux-6.15/arch/arm/common/Kconfig

81243e44 - irqchip: Move ARM GIC to drivers/irqchip

Wed, 21 Nov 2012 03:21:40 +0000

irqchip: Move ARM GIC to drivers/irqchipNow that we have drivers/irqchip, move GIC irqchip to drivers/irqchip. Thisis necessary to share the GIC with arm and arm64.Signed-off-by: Rob Herring Cc: Russell King Cc: Thomas Gleixner List of files: /linux-6.15/arch/arm/common/Kconfig

b1b3f49c - ARM: config: sort select statements alphanumerically

Sat, 06 Oct 2012 16:12:25 +0000

ARM: config: sort select statements alphanumericallyAs suggested by Andrew Morton: This is a pet peeve of mine. Any time there's a long list of items (header file inclusions, kconfig entries, array initalisers, etc) and someone wants to add a new item, they *always* go and stick it at the end of the list. Guys, don't do this. Either put the new item into a randomly-chosen position or, probably better, alphanumerically sort the list.lets sort all our select statements alphanumerically. This commit wascreated by the following perl:while (<>) { while (/\\\s*$/) { $_ .= <>; } undef %selects if /^\s*config\s+/; if (/^\s+select\s+(\w+).*/) { if (defined($selects{$1})) { if ($selects{$1} eq $_) { print STDERR "Warning: removing duplicated $1 entry\n"; } else { print STDERR "Error: $1 differently selected\n". "\tOld: $selects{$1}\n". "\tNew: $_\n"; exit 1; } } $selects{$1} = $_; next; } if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or /^endif/ or /^endchoice/)) { foreach $k (sort (keys %selects)) { print "$selects{$k}"; } undef %selects; } print;}if (%selects) { foreach $k (sort (keys %selects)) { print "$selects{$k}"; }}It found two duplicates:Warning: removing duplicated S5P_SETUP_MIPIPHY entryWarning: removing duplicated HARDIRQS_SW_RESEND entryand they are identical duplicates, hence the shrinkage in the diffstatof two lines.We have four testers reporting success of this change (Tony, Stephen,Linus and Sekhar.)Acked-by: Jason Cooper Acked-by: Tony Lindgren Acked-by: Stephen Warren Acked-by: Linus Walleij Acked-by: Sekhar Nori Signed-off-by: Russell King List of files: /linux-6.15/arch/arm/common/Kconfig

a1be5d64 - ARM: riscpc: move time-acorn.c to mach-rpc

Thu, 01 Mar 2012 15:35:50 +0000

ARM: riscpc: move time-acorn.c to mach-rpcNothing but RiscPC makes use of the Acorn timekeeping code, so moveit into mach-rpc.Signed-off-by: Russell King List of files: /linux-6.15/arch/arm/common/Kconfig

b7d861d9 - DMA: PL330: Merge PL330 driver into drivers/dma/

Mon, 26 Dec 2011 09:49:52 +0000

DMA: PL330: Merge PL330 driver into drivers/dma/Currently there were two part of DMAC PL330 driver forsupport old styled s3c-pl330 which has been merged intodrivers/dma/pl330.c driver. Actually, there is no reasonto separate them now.Basically this patch merges arch/arm/common/pl330.c intodrivers/dma/pl330.c driver and removes useless exportedsymbol, externed function and so on.The newer pl330 driver tested on SMDKV310 and SMDK4212 boardsCc: Jassi Brar Cc: Russell King Acked-by: Linus Walleij Acked-by: Vinod Koul Signed-off-by: Boojin Kim Signed-off-by: Kukjin Kim Acked-by: Jassi Brar Signed-off-by: Vinod Koul List of files: /linux-6.15/arch/arm/common/Kconfig

11f1c5de - ARM: VIC: remove non MULTI_IRQ_HANDLER support

Thu, 03 Nov 2011 17:32:39 +0000

ARM: VIC: remove non MULTI_IRQ_HANDLER supportNow that all platforms are converted to MULTI_IRQ_HANDLER, remove thelegacy support.Tested-by: Thomas Abraham Signed-off-by: Jamie Iles List of files: /linux-6.15/arch/arm/common/Kconfig

f9b28ccb - ARM: vic: device tree binding

Tue, 27 Sep 2011 10:00:46 +0000

ARM: vic: device tree bindingThis adds a device tree binding for the VIC based on the of_irq_init()support. This adds an irqdomain to the vic and always registers allvics in the static vic array rather than for pm only to keep track ofthe irq domain. struct irq_data::hwirq is used where appropriate ratherthan runtime masking.v3: - include linux/export.h for THIS_MODULEv2: - use irq_domain_simple_ops - remove stub implementation of vic_of_init for !CONFIG_OF - Make VIC select IRQ_DOMAINReviewed-by: Rob Herring Reviewed-by: Grant Likely Tested-by: Thomas Abraham Signed-off-by: Jamie Iles List of files: /linux-6.15/arch/arm/common/Kconfig

08d33b27 - ARM: GIC: Make MULTI_IRQ_HANDLER mandatory

Tue, 06 Sep 2011 12:27:10 +0000

ARM: GIC: Make MULTI_IRQ_HANDLER mandatoryNow that MULTI_IRQ_HANDLER is selected by all the in-treeGIC users, make it mandatory and remove the unused macros.Signed-off-by: Marc Zyngier List of files: /linux-6.15/arch/arm/common/Kconfig

db0d4db2 - ARM: gic: allow GIC to support non-banked setups

Sat, 12 Nov 2011 16:09:49 +0000

ARM: gic: allow GIC to support non-banked setupsThe GIC support code is heavily using the fact that hardwareimplementations are exposing banked registers. Unfortunately, itlooks like at least one GIC implementation (EXYNOS) offers boththe distributor and the CPU interfaces at different addresses,depending on the CPU.This problem is solved by allowing the distributor and CPU interfaceaddresses to be per-cpu variables for the platforms that require it.The EXYNOS code is updated not to mess with the GIC internals whilehandling interrupts, and struct gic_chip_data is back to being private.The DT binding for the gic is updated to allow an optional "cpu-offset"value, which is used to compute the various base addresses.Finally, a new config option (GIC_NON_BANKED) is used to control thisfeature, so the overhead is only present on kernels compiled withsupport for EXYNOS.Tested on Origen (EXYNOS4) and Panda (OMAP4).Cc: Kukjin Kim Cc: Will Deacon Cc: Thomas Abraham Acked-by: Rob Herring Signed-off-by: Marc Zyngier List of files: /linux-6.15/arch/arm/common/Kconfig

4294f8ba - ARM: gic: add irq_domain support

Thu, 29 Sep 2011 02:25:31 +0000

ARM: gic: add irq_domain supportConvert the gic interrupt controller to use irq domains in preparationfor device-tree binding and MULTI_IRQ. This allows for translation betweenGIC interrupt IDs and Linux irq numbers.The meaning of irq_offset has changed. It now is just the number of skippedGIC interrupt IDs for the controller. It will be 16 for primary GIC and 32for secondary GICs.Signed-off-by: Rob Herring Cc: Marc Zyngier Reviewed-by: Jamie Iles Tested-by: Thomas Abraham Acked-by: Grant Likely List of files: /linux-6.15/arch/arm/common/Kconfig

a73ddc61 - ARM: S5P6442: Removing ARCH_S5P6442

Wed, 11 May 2011 07:27:51 +0000

ARM: S5P6442: Removing ARCH_S5P6442Signed-off-by: Kukjin Kim List of files: /linux-6.15/arch/arm/common/Kconfig

59a4f92a - ARM: 6762/1: Update number of VIC for S5P6442 and S5PC100

Thu, 24 Feb 2011 01:12:44 +0000

ARM: 6762/1: Update number of VIC for S5P6442 and S5PC100The S5P6442 and S5PC100 SoCs have 4 VICs. However, default VIC numberis defined 2 in arch/arm/common. So can be happened some problem on it.Basically, it requires for suspend and resume.Signed-off-by: Kukjin Kim Signed-off-by: Russell King List of files: /linux-6.15/arch/arm/common/Kconfig

6cc6b33a - ARM: 6761/1: Update number of VIC for S5PV210

Thu, 24 Feb 2011 01:12:00 +0000

ARM: 6761/1: Update number of VIC for S5PV210The S5PV210 SoC have 4 VICs. It requires for suspend and resume.Signed-off-by: Kyungmin Park Signed-off-by: Kukjin Kim Signed-off-by: Russell King List of files: /linux-6.15/arch/arm/common/Kconfig