Changes in Kconfig

666173ee - MIPS: generic: Allow generating FIT image for Marduk board

Fri, 23 Jul 2021 02:25:35 +0000

MIPS: generic: Allow generating FIT image for Marduk boardMarduk is based on IMG pistachio SoC. The platform is usingMIPS UHI booting protocol and does have a proper devicetreeimplement, thus it could be a part of generic kernel.Signed-off-by: Jiaxun Yang Signed-off-by: Thomas Bogendoerfer List of files: /linux-6.15/arch/mips/generic/Kconfig

fe005201 - MIPS: mscc: Add serval support

Tue, 10 Nov 2020 11:45:08 +0000

MIPS: mscc: Add serval supportAdd a device trees and FIT image support for the Microsemi Serval SoCwhich belongs to same family of the Ocelot SoC.It is based on the work of Lars Povlsen .Signed-off-by: Gregory CLEMENT Acked-by: Alexandre Belloni Signed-off-by: Thomas Bogendoerfer List of files: /linux-6.15/arch/mips/generic/Kconfig

f84778f7 - MIPS: mscc: Add jaguar2 support

Tue, 10 Nov 2020 11:45:07 +0000

MIPS: mscc: Add jaguar2 supportAdd a device trees and FIT image support for the Microsemi Jaguar2 SoCwhich belongs to same family of the Ocelot SoC.It is based on the work of Lars Povlsen .Signed-off-by: Gregory CLEMENT Acked-by: Alexandre Belloni Signed-off-by: Thomas Bogendoerfer List of files: /linux-6.15/arch/mips/generic/Kconfig

378e413f - MIPS: mscc: build FIT image for Luton

Tue, 10 Nov 2020 11:45:06 +0000

MIPS: mscc: build FIT image for LutonLuton now has already an u-boot port so let's build FIT images.Signed-off-by: Gregory CLEMENT Acked-by: Alexandre Belloni Signed-off-by: Thomas Bogendoerfer List of files: /linux-6.15/arch/mips/generic/Kconfig

2825f4c0 - MIPS: mscc: Fix configuration name for ocelot legacy boards

Tue, 10 Nov 2020 11:45:03 +0000

MIPS: mscc: Fix configuration name for ocelot legacy boardsOcelots is supported by the generic MIPS build so make it clears thatLEGACY_BOARD_OCELOT is only needed for legacy boards which didn't havebootloader supporting device tree.Signed-off-by: Gregory CLEMENT Acked-by: Alexandre Belloni Signed-off-by: Thomas Bogendoerfer List of files: /linux-6.15/arch/mips/generic/Kconfig

700364da - MIPS: mscc: Prepare configuration to handle more SoCs

Tue, 10 Nov 2020 11:45:02 +0000

MIPS: mscc: Prepare configuration to handle more SoCsOcelot belongs to a family of SoC named the VCore III. In order to addthese new Soc, use the new symbol SOC_VCOREIII instead of a onededicated to Ocelot.In order to avoid regression on driver building, the MSCC_OCELOTconfiguration symbol is kept until the driver will be converted.Signed-off-by: Gregory CLEMENT Acked-by: Alexandre Belloni Signed-off-by: Thomas Bogendoerfer List of files: /linux-6.15/arch/mips/generic/Kconfig

f0f4a753 - MIPS: generic: Add support for Ingenic SoCs

Sun, 06 Sep 2020 19:29:31 +0000

MIPS: generic: Add support for Ingenic SoCsAdd support for Ingenic SoCs in arch/mips/generic/.The Kconfig changes are here to ensure that it is possible to compileeither a generic kernel that supports Ingenic SoCs, or a Ingenic-onlykernel, both using the same code base, to avoid duplicated code.Signed-off-by: Paul Cercueil Signed-off-by: Thomas Bogendoerfer List of files: /linux-6.15/arch/mips/generic/Kconfig

c434b9f8 - MIPS: Kconfig: add MIPS_GENERIC_KERNEL symbol

Sun, 06 Sep 2020 19:29:25 +0000

MIPS: Kconfig: add MIPS_GENERIC_KERNEL symbolThe MIPS_GENERIC symbol now won't select any other configuration option.The MIPS_GENERIC_KERNEL will select all the options that the previousMIPS_GENERIC option did select, and will select MIPS_GENERIC as well.The whole point of this, is that it now becomes possible to compile akernel for a SoC supported by the arch/mips/generic/ code, withoutmaking that kernel generic itself.Signed-off-by: Paul Cercueil Signed-off-by: Thomas Bogendoerfer List of files: /linux-6.15/arch/mips/generic/Kconfig

39249d77 - MIPS: mscc: add PCB120 to the ocelot fitImage

Mon, 08 Oct 2018 10:14:45 +0000

MIPS: mscc: add PCB120 to the ocelot fitImagePCB120 and PCB123 are both development boards based on Microsemi Ocelotso let's use the same fitImage for both.Reviewed-by: Alexandre Belloni Signed-off-by: Quentin Schulz Signed-off-by: Paul Burton Patchwork: https://patchwork.linux-mips.org/patch/20871/Cc: ralf@linux-mips.orgCc: jhogan@kernel.orgCc: robh+dt@kernel.orgCc: mark.rutland@arm.comCc: davem@davemloft.netCc: andrew@lunn.chCc: f.fainelli@gmail.comCc: allan.nielsen@microchip.comCc: linux-mips@linux-mips.orgCc: devicetree@vger.kernel.orgCc: linux-kernel@vger.kernel.orgCc: netdev@vger.kernel.orgCc: thomas.petazzoni@bootlin.comCc: antoine.tenart@bootlin.com List of files: /linux-6.15/arch/mips/generic/Kconfig

d5be4aeb - mips: mscc: build FIT image for Ocelot

Tue, 26 Jun 2018 11:57:11 +0000

mips: mscc: build FIT image for OcelotOcelot now has a u-boot port, allow building FIT images instead of relyingon the legacy detection and builtin DTB.Signed-off-by: Alexandre Belloni Reviewed-by: James Hogan Signed-off-by: Paul Burton Patchwork: https://patchwork.linux-mips.org/patch/19632/Cc: Ralf Baechle Cc: linux-mips@linux-mips.orgCc: linux-kernel@vger.kernel.org List of files: /linux-6.15/arch/mips/generic/Kconfig

6bce3dea - MIPS: generic: Add support for Microsemi Ocelot

Tue, 20 Mar 2018 13:08:00 +0000

MIPS: generic: Add support for Microsemi OcelotIntroduce support for the MIPS based Microsemi Ocelot SoCs.Signed-off-by: Alexandre Belloni Cc: Ralf Baechle Cc: Allan Nielsen Cc: linux-mips@linux-mips.orgPatchwork: https://patchwork.linux-mips.org/patch/18858/[jhogan@kernel.org: update ocelot_defconfig specification]Signed-off-by: James Hogan List of files: /linux-6.15/arch/mips/generic/Kconfig

f2d0b0d5 - MIPS: ranchu: Add Ranchu as a new generic-based board

Fri, 29 Dec 2017 15:41:47 +0000

MIPS: ranchu: Add Ranchu as a new generic-based boardProvide amendments to the MIPS generic platform framework so thatthe new generic-based board Ranchu can be chosen to be built.The Ranchu board is intended to be used by Android emulator. The name"Ranchu" originates from Android development community. "Goldfish" and"Ranchu" are terms used for two generations of virtual boards used byAndroid emulator. The name "Ranchu" is a newer one among the two, andthis patch deals with Ranchu. However, for historical reasons, somedevices/drivers still contain the name "Goldfish".MIPS Ranchu machine includes a number of Goldfish devices. The supportfor Virtio devices is also included. Ranchu board supports up to 16Virtio devices which can be attached using Virtio MMIO Bus. This issummarized in the following picture: ABUS ||----MIPS CPU || | IRQs ||----Goldfish PIC------------(32)-------- || | | | | | | | | | ||----Goldfish TTY------ | | | | | | | | || | | | | | | | | ||----Goldfish RTC-------- | | | | | | | || | | | | | | | ||----Goldfish FB----------- | | | | | | || | | | | | | ||----Goldfish Events--------- | | | | | || | | | | | ||----Goldfish Audio------------ | | | | || | | | | ||----Goldfish Battery------------ | | | || | | | ||----Android PIPE------------------ | | || | | ||----Virtio MMIO Bus | | || | | | | | || | | (virtio-block)--------- | || (16) | | || | (virtio-net)------------------Device Tree is created on the QEMU side based on the information aboutdevices IO map and IRQ numbers. Kernel will load this DTB using UHIboot protocol DTB handover mode.Signed-off-by: Miodrag Dinic Signed-off-by: Goran Ferenc Signed-off-by: Aleksandar Markovic Reviewed-by: James Hogan Cc: Ralf Baechle Cc: Paul Burton Cc: linux-mips@linux-mips.orgPatchwork: https://patchwork.linux-mips.org/patch/18138/Signed-off-by: James Hogan List of files: /linux-6.15/arch/mips/generic/Kconfig

b35565bb - MIPS: generic: Add support for MIPSfpga

Fri, 31 Mar 2017 09:00:41 +0000

MIPS: generic: Add support for MIPSfpgaAdd support for the MIPSfpga platform to generic kernel.Signed-off-by: Zubair Lutfullah Kakakhel Cc: Ralf Baechle Cc: linux-mips@linux-mips.orgPatchwork: https://patchwork.linux-mips.org/patch/15846/[jhogan@kernel.org: Use separate board-xilfpga.its.S. Add 32r2 and little endian requires to board-xilfpga.config]Signed-off-by: James Hogan List of files: /linux-6.15/arch/mips/generic/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/mips/generic/Kconfig

7aacf86b - MIPS: NI 169445 board support

Tue, 18 Jul 2017 18:29:09 +0000

MIPS: NI 169445 board supportSupport the National Instruments 169445 board.Signed-off-by: Nathan Sullivan Acked-by: Rob Herring Cc: devicetree@vger.kernel.orgCc: linux-mips@linux-mips.orgCc: linux-kernel@vger.kernel.orgPatchwork: https://patchwork.linux-mips.org/patch/16782/Signed-off-by: Ralf Baechle List of files: /linux-6.15/arch/mips/generic/Kconfig

6e62a888 - MIPS: generic: Support MIPS Boston development boards

Sat, 17 Jun 2017 20:52:49 +0000

MIPS: generic: Support MIPS Boston development boardsAdd support for the MIPS Boston development board to generic kernels,which essentially amounts to: - Adding the device tree source for the MIPS Boston board. - Adding a Kconfig fragment which enables the appropriate drivers for the MIPS Boston board.With these changes in place generic kernels will support the board bydefault, and kernels with only the drivers needed for Boston enabled canbe configured by setting BOARDS=boston during configuration. Forexample: $ make ARCH=mips 64r6el_defconfig BOARDS=bostonSigned-off-by: Paul Burton Reviewed-by: James Hogan Cc: linux-mips@linux-mips.orgPatchwork: https://patchwork.linux-mips.org/patch/16485/Signed-off-by: Ralf Baechle List of files: /linux-6.15/arch/mips/generic/Kconfig

571b7e69 - MIPS: generic/yamon-dt: Pull YAMON DT shim code out of SEAD-3 board

Fri, 02 Jun 2017 19:29:51 +0000

MIPS: generic/yamon-dt: Pull YAMON DT shim code out of SEAD-3 boardIn preparation for supporting other YAMON-using boards (Malta) & sharingcode to translate information from YAMON into device tree properties,pull the code doing so for the kernel command line, system memory &serial configuration out of the SEAD-3 board code.Signed-off-by: Paul Burton Cc: linux-mips@linux-mips.orgPatchwork: https://patchwork.linux-mips.org/patch/16181/Signed-off-by: Ralf Baechle List of files: /linux-6.15/arch/mips/generic/Kconfig

3f5f0a44 - MIPS: generic: Convert SEAD-3 to a generic board

Wed, 05 Oct 2016 17:18:21 +0000

MIPS: generic: Convert SEAD-3 to a generic boardConvert the MIPS SEAD-3 board support to be a generic board, supportedby generic kernels.Because the SEAD-3 boot protocol was defined long ago and we don't wantto force a switch to the UHI protocol, SEAD-3 is added as a legacy boardwhich is detected by reading the REVISION register. This may technicallynot be a valid memory read & future work will include attempting tohandle that gracefully. In practice since SEAD-3 is the only legacyboard supported by the generic kernel so far the read will only happenon SEAD-3 boards, and even once Malta is converted the same REVISIONregister exists there too. Other boards such as Boston, Ci20 & Ci40 willuse the UHI boot protocol & thus not run any of the legacy board detectfunctions.Signed-off-by: Paul Burton Cc: linux-mips@linux-mips.orgPatchwork: https://patchwork.linux-mips.org/patch/14354/Signed-off-by: Ralf Baechle List of files: /linux-6.15/arch/mips/generic/Kconfig

eed0eabd - MIPS: generic: Introduce generic DT-based board support

Wed, 05 Oct 2016 17:18:20 +0000

MIPS: generic: Introduce generic DT-based board supportIntroduce a "generic" platform, which aims to be board-agnostic bymaking use of device trees passed by the boot protocol defined in theMIPS UHI (Universal Hosting Interface) specification. Provision is madefor supporting boards which use a legacy boot protocol that can't bechanged, but adding support for such boards or any others is left tofollowon patches.Right now the built kernels expect to be loaded to 0x80100000, ie. inkseg0. This is fine for the vast majority of MIPS platforms, butnevertheless it would be good to remove this limitation in the future bymapping the kernel via the TLB such that it can be loaded anywhere & mapitself appropriately.Configuration is handled by dynamically generating configs usingscripts/kconfig/merge_config.sh, somewhat similar to the way powerpcmakes use of it. This allows for variations upon the configuration, eg.differing architecture revisions or subsets of driver support fordiffering boards, to be handled without having a large number ofdefconfig files.Signed-off-by: Paul Burton Cc: linux-mips@linux-mips.orgPatchwork: https://patchwork.linux-mips.org/patch/14353/Signed-off-by: Ralf Baechle List of files: /linux-6.15/arch/mips/generic/Kconfig