dt-bindings: ti-serdes-mux: Deprecate header with constantsThe constants to define the idle state of SERDES MUX were defined inbindings header. They are used only in DTS and driver uses the dt pro
dt-bindings: ti-serdes-mux: Deprecate header with constantsThe constants to define the idle state of SERDES MUX were defined inbindings header. They are used only in DTS and driver uses the dt propertyto set the idle state making it unsuitable for bindings.The constants are moved to header next to DTS ("arch/arm64/boot/dts/ti/")and all the references to bindings header are removed.So add a warning to mark this bindings header as deprecated.Signed-off-by: Jayesh Choudhary <[email protected]>Reviewed-by: Krzysztof Kozlowski <[email protected]>Acked-by: Roger Quadros <[email protected]>Acked-by: Peter Rosin <[email protected]>Link: https://lore.kernel.org/r/[email protected]Signed-off-by: Nishanth Menon <[email protected]>
show more ...
dt-bindings: ti-serdes-mux: Add defines for J784S4 SoCThere are 4 lanes in the single instance of J784S4 SERDES. Each SERDESlane mux can select up to 4 different IPs. Define all the possiblefunct
dt-bindings: ti-serdes-mux: Add defines for J784S4 SoCThere are 4 lanes in the single instance of J784S4 SERDES. Each SERDESlane mux can select up to 4 different IPs. Define all the possiblefunctions.Signed-off-by: Matt Ranostay <[email protected]>Acked-by: Krzysztof Kozlowski <[email protected]>Signed-off-by: Siddharth Vadapalli <[email protected]>Signed-off-by: Peter Rosin <[email protected]>Link: https://lore.kernel.org/r/[email protected]Signed-off-by: Greg Kroah-Hartman <[email protected]>
dt-bindings: ti-serdes-mux: Add defines for J721S2 SoCThere are 4 lanes in the single instance of J721S2 SERDES. Each SERDESlane mux can select upto 4 different IPs. Define all the possiblefuncti
dt-bindings: ti-serdes-mux: Add defines for J721S2 SoCThere are 4 lanes in the single instance of J721S2 SERDES. Each SERDESlane mux can select upto 4 different IPs. Define all the possiblefunctions.Signed-off-by: Aswath Govindraju <[email protected]>Acked-by: Rob Herring <[email protected]>Signed-off-by: Peter Rosin <[email protected]>Link: https://lore.kernel.org/r/[email protected]Signed-off-by: Greg Kroah-Hartman <[email protected]>
dt-bindings: ti-serdes-mux: Add defines for AM64 SoCAM64 has a single lane SERDES which can be configured to be usedwith either PCIe or USB. Define the possilbe values for the SERDESfunction in A
dt-bindings: ti-serdes-mux: Add defines for AM64 SoCAM64 has a single lane SERDES which can be configured to be usedwith either PCIe or USB. Define the possilbe values for the SERDESfunction in AM64 SoC here.Signed-off-by: Kishon Vijay Abraham I <[email protected]>Acked-by: Peter Rosin <[email protected]>Acked-by: Rob Herring <[email protected]>Link: https://lore.kernel.org/r/[email protected]Signed-off-by: Vinod Koul <[email protected]>
dt-bindings: ti-serdes-mux: Add defines for J7200 SoCThere are 4 lanes in each J7200 SERDES. Each SERDES lane mux canselect upto 4 different IPs. Define all the possible functions.Signed-off-by:
dt-bindings: ti-serdes-mux: Add defines for J7200 SoCThere are 4 lanes in each J7200 SERDES. Each SERDES lane mux canselect upto 4 different IPs. Define all the possible functions.Signed-off-by: Roger Quadros <[email protected]>Signed-off-by: Nishanth Menon <[email protected]>Reviewed-by: Vignesh Raghavendra <[email protected]>Acked-by: Rob Herring <[email protected]>Acked-by: Peter Rosin <[email protected]>Cc: Peter Rosin <[email protected]>Link: https://lore.kernel.org/r/[email protected]
arm64: dts: ti: k3-j721e: Rename mux header and update macro namesWe intend to use one header file for SERDES MUX for allTI SoCs so rename the header file.The exsting macros are too generic. Pre
arm64: dts: ti: k3-j721e: Rename mux header and update macro namesWe intend to use one header file for SERDES MUX for allTI SoCs so rename the header file.The exsting macros are too generic. Prefix them with SoC name.While at that, add the missing configurations for completeness.Fixes: b766e3b0d5f6 ("arm64: dts: ti: k3-j721e-main: Add system controller node and SERDES lane mux")Reported-by: Peter Rosin <[email protected]>Signed-off-by: Roger Quadros <[email protected]>Signed-off-by: Nishanth Menon <[email protected]>Acked-by: Peter Rosin <[email protected]>Link: https://lore.kernel.org/r/[email protected]
of: reserved-memory: remove duplicated call to of_get_flat_dt_prop() for no-map nodeJust use nomap instead of the second call to of_get_flat_dt_prop(). Andchange nomap as a bool type due to != NUL
of: reserved-memory: remove duplicated call to of_get_flat_dt_prop() for no-map nodeJust use nomap instead of the second call to of_get_flat_dt_prop(). Andchange nomap as a bool type due to != NULL operator. Also, correct commentabout node of 'align' -> 'alignment'.Signed-off-by: Yue Hu <[email protected]>Link: https://lore.kernel.org/r/[email protected]Signed-off-by: Rob Herring <[email protected]>
arm64: dts: ti: k3-j721e-main: Add system controller node and SERDES lane muxThe system controller node manages the CTRL_MMR0 region.Add serdes_ln_ctrl node which is used for controlling the SERDE
arm64: dts: ti: k3-j721e-main: Add system controller node and SERDES lane muxThe system controller node manages the CTRL_MMR0 region.Add serdes_ln_ctrl node which is used for controlling the SERDES lane mux.Signed-off-by: Kishon Vijay Abraham I <[email protected]>Signed-off-by: Roger Quadros <[email protected]>Acked-by: Rob Herring <[email protected]>Signed-off-by: Tero Kristo <[email protected]>
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
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 <[email protected]>Reviewed-by: Philippe Ombredanne <[email protected]>Reviewed-by: Thomas Gleixner <[email protected]>Signed-off-by: Greg Kroah-Hartman <[email protected]>
dt-bindings: document devicetree bindings for mux-controllers and gpio-muxAllow specifying that a single multiplexer controller can be used tocontrol several parallel multiplexers, thus enabling s
dt-bindings: document devicetree bindings for mux-controllers and gpio-muxAllow specifying that a single multiplexer controller can be used tocontrol several parallel multiplexers, thus enabling sharing of themultiplexer controller by different consumers.Add a binding for a first mux controller in the form of a GPIO based muxcontroller.Acked-by: Jonathan Cameron <[email protected]>Acked-by: Rob Herring <[email protected]>Signed-off-by: Peter Rosin <[email protected]>Signed-off-by: Greg Kroah-Hartman <[email protected]>