1. 05 Oct, 2018 1 commit
  2. 09 Aug, 2018 3 commits
  3. 12 May, 2018 2 commits
  4. 13 Mar, 2018 1 commit
  5. 28 Feb, 2018 1 commit
  6. 27 Feb, 2018 1 commit
  7. 26 Jan, 2018 1 commit
  8. 16 Jan, 2018 1 commit
    • James Hogan's avatar
      ssb: Disable PCI host for PCI_DRIVERS_GENERIC · 58eae141
      James Hogan authored
      Since commit d41e6858 ("MIPS: Kconfig: Set default MIPS system type
      as generic") changed the default MIPS platform to the "generic"
      platform, which uses PCI_DRIVERS_GENERIC instead of PCI_DRIVERS_LEGACY,
      various files in drivers/ssb/ have failed to build.
      This is particularly due to the existence of struct pci_controller being
      dependent on PCI_DRIVERS_LEGACY since commit c5611df9 ("MIPS: PCI:
      Introduce CONFIG_PCI_DRIVERS_LEGACY"), so add that dependency to Kconfig
      to prevent these files being built for the "generic" platform including
      all{yes,mod}config builds.
      Fixes: c5611df9 ("MIPS: PCI: Introduce CONFIG_PCI_DRIVERS_LEGACY")
      Signed-off-by: default avatarJames Hogan <jhogan@kernel.org>
      Cc: Michael Buesch <m@bues.ch>
      Cc: Ralf Baechle <ralf@linux-mips.org>
      Cc: Paul Burton <paul.burton@mips.com>
      Cc: Matt Redfearn <matt.redfearn@imgtec.com>
      Cc: Guenter Roeck <linux@roeck-us.net>
      Cc: linux-wireless@vger.kernel.org
      Cc: linux-mips@linux-mips.org
      Tested-by: default avatarGuenter Roeck <linux@roeck-us.net>
      Signed-off-by: default avatarKalle Valo <kvalo@codeaurora.org>
  9. 07 Dec, 2017 1 commit
  10. 02 Nov, 2017 1 commit
    • Greg Kroah-Hartman's avatar
      License cleanup: add SPDX GPL-2.0 license identifier to files with no license · b2441318
      Greg Kroah-Hartman authored
      Many source files in the tree are missing licensing information, which
      makes it harder for compliance tools to determine the correct license.
      By default all files without license information are under the default
      license 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 binding
      shorthand, which can be used instead of the full boiler plate text.
      This patch is based on work done by Thomas Gleixner and Kate Stewart and
      Philippe Ombredanne.
      How this work was done:
      Patches were generated and checked against linux-4.14-rc6 for a subset of
      the 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 cases
      where non-standard license headers were used, and references to license
      had to be inferred by heuristics based on keywords.
      The analysis to determine which SPDX License Identifier to be applied to
      a file was done in a spreadsheet of side by side results from of the
      output of two independent scanners (ScanCode & Windriver) producing SPDX
      tag:value files created by Philippe Ombredanne.  Philippe prepared the
      base 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 files
      assessed.  Kate Stewart did a file by file comparison of the scanner
      results in the spreadsheet to determine which SPDX license identifier(s)
      to be applied to the file. She confirmed any determination that was not
      immediately 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
      All documentation files were explicitly excluded.
      The following heuristics were used to determine which SPDX license
      identifiers 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 the
      spreadsheet to determine the SPDX license identifiers to apply to the
      source files by Kate, Philippe, Thomas and, in some cases, confirmation
      by lawyers working with the Linux Foundation.
      Kate also obtained a third independent scan of the 4.13 code base from
      FOSSology, and compared selected files where the other two scanners
      disagreed against that SPDX file, to see if there was new insights.  The
      Windriver scanner is based on an older version of FOSSology in part, so
      they are related.
      Thomas did random spot checks in about 500 files from the spreadsheets
      for the uapi headers and agreed with SPDX license identifier in the
      files he inspected. For the non-uapi files Thomas did random spot checks
      in about 15000 files.
      In initial set of patches against 4.14-rc6, 3 files were found to have
      copy/paste license identifier errors, and have been fixed to reflect the
      correct identifier.
      Additionally Philippe spent 10 hours this week doing a detailed manual
      inspection and review of the 12,461 patched files from the initial patch
      version 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 correct
      This produced a worksheet with 20 files needing minor correction.  This
      worksheet was then exported into 3 different .csv files for the
      different types of files to be modified.
      These .csv files were then reviewed by Greg.  Thomas wrote a script to
      parse the csv files and add the proper SPDX tag to the file, in the
      format that the file expected.  This script was further refined by Greg
      based on the output to detect more types of files automatically and to
      distinguish between header and source .c files (which need different
      comment types.)  Finally Greg ran the script using the .csv files to
      generate the patches.
      Reviewed-by: default avatarKate Stewart <kstewart@linuxfoundation.org>
      Reviewed-by: default avatarPhilippe Ombredanne <pombredanne@nexb.com>
      Reviewed-by: default avatarThomas Gleixner <tglx@linutronix.de>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
  11. 24 May, 2017 1 commit
  12. 17 Nov, 2016 1 commit
  13. 06 Jul, 2016 1 commit
  14. 26 Apr, 2016 1 commit
  15. 26 Feb, 2016 1 commit
    • Arnd Bergmann's avatar
      ssb: host_soc depends on sprom · 10da848f
      Arnd Bergmann authored
      Drivers that use the SSB sprom functionality typically 'select SSB_SPROM'
      from Kconfig, but CONFIG_SSB_HOST_SOC misses this, which results in
      a build failure unless at least one of the other drivers that selects
      it is enabled:
      drivers/built-in.o: In function `ssb_host_soc_get_invariants':
      (.text+0x459494): undefined reference to `ssb_fill_sprom_with_fallback'
      This adds the same select statement that is used elsewhere.
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Fixes: 541c9a84 ("ssb: pick SoC invariants code from MIPS BCM47xx arch")
      Signed-off-by: default avatarKalle Valo <kvalo@codeaurora.org>
  16. 19 Jan, 2016 1 commit
    • Arnd Bergmann's avatar
      ssb: mark ssb_bus_register as __maybe_unused · b7e2d195
      Arnd Bergmann authored
      The SoC variant of the ssb code is now optional like the other
      ones, which means we can build the framwork without any
      front-end, but that results in a warning:
      drivers/ssb/main.c:616:12: warning: 'ssb_bus_register' defined but not used [-Wunused-function]
      This annotates the ssb_bus_register function as __maybe_unused to
      shut up the warning. A configuration like this will not work on
      any hardware of course, but we still want this to silently build
      without warnings if the configuration is allowed in the first
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Fixes: 845da6e5 ("ssb: add Kconfig entry for compiling SoC related code")
      Acked-by: default avatarMichael Buesch <m@bues.ch>
      Signed-off-by: default avatarKalle Valo <kvalo@codeaurora.org>
  17. 16 Dec, 2015 1 commit
    • Rafał Miłecki's avatar
      ssb: pick SoC invariants code from MIPS BCM47xx arch · 541c9a84
      Rafał Miłecki authored
      There is code in ssb fetching "invariants" that is basically a set of
      board specific data. Every host requires its own implementation of
      reading function. In ssb we have support for PCI, PCMCIA & SDIO.
      For some (historical?) reason code reading "invariants" for SoC was
      placed in arch code and provided by a callback. This is not needed
      nowadays, so lets move that into ssb. This way we keep all "invariants"
      functions in a single module making code cleaner.
      Signed-off-by: default avatarRafał Miłecki <zajec5@gmail.com>
      Signed-off-by: default avatarKalle Valo <kvalo@codeaurora.org>
  18. 28 Oct, 2015 3 commits
  19. 29 Sep, 2015 4 commits
  20. 09 Jun, 2015 1 commit
  21. 20 May, 2015 1 commit
  22. 10 Apr, 2015 1 commit
  23. 07 Apr, 2015 1 commit
  24. 01 Apr, 2015 1 commit
  25. 03 Mar, 2015 1 commit
  26. 11 Feb, 2015 1 commit
  27. 29 Jan, 2015 1 commit
  28. 04 Dec, 2014 1 commit
    • Andrey Skvortsov's avatar
      SSB / B44: fix WOL for BCM4401 · 5580373f
      Andrey Skvortsov authored
      Wake On Lan was not working on laptop DELL Vostro 1500.
      If WOL was turned on, BCM4401 was powered up in suspend mode. LEDs blinked.
      But the laptop could not be woken up with the Magic Packet. The reason for
      that was that PCIE was not enabled as a system wakeup source and
      therefore the host PCI bridge was not powered up in suspend mode.
      PCIE was not enabled in suspend by PM because no child devices were
      registered as wakeup source during suspend process.
      On laptop BCM4401 is connected through the SSB bus, that is connected to the
      PCI-Express bus. SSB and B44 did not use standard PM wakeup functions
      and did not forward wakeup settings to their parents.
      To fix that B44 driver enables PM wakeup and registers new wakeup source
      using device_set_wakeup_enable(). Wakeup is automatically reported to the parent SSB
      bus via power.wakeup_path. SSB bus enables wakeup for the parent PCI bridge, if there is any
      child devices with enabled wakeup functionality. All other steps are
      done by PM core code.
      Signed-off-by: default avatarAndrey Skvortsov <Andrej.Skvortzov@gmail.com>
      Signed-off-by: default avatarMichael Buesch <m@bues.ch>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
  29. 24 Nov, 2014 1 commit
  30. 18 Sep, 2014 1 commit
  31. 25 Aug, 2014 1 commit
  32. 18 Jul, 2014 1 commit