1. 24 Jun, 2020 1 commit
  2. 10 Oct, 2019 1 commit
  3. 28 Feb, 2018 1 commit
  4. 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
         lines).
      
      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>
      b2441318
  5. 15 May, 2017 1 commit
  6. 11 Nov, 2016 1 commit
  7. 20 Apr, 2016 1 commit
  8. 31 Dec, 2015 1 commit
  9. 23 Oct, 2015 2 commits
    • Eric Anholt's avatar
      ARM: bcm2835: Add the DDC I2C controller to the device tree. · 121432c7
      Eric Anholt authored
      We need to use it for getting video modes over HDMI.
      Signed-off-by: default avatarEric Anholt <eric@anholt.net>
      Acked-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      121432c7
    • Eric Anholt's avatar
      ARM: bcm2835: Switch to using the new clock driver support. · 94cb7f76
      Eric Anholt authored
      This will give us the ability to set the pixel and HDMI state machine
      clocks for the VC4 KMS driver, change the CPU frequency, and
      potentially gate clocks in the future (once we also write a power
      domain driver).  It also gives the uart an explicit clock reference,
      so that we don't need to change the physical addresses of the old
      fixed clk_bcm2835.c clocks for Raspberry Pi 2 port.
      
      Two clocks get their frequencies updated as a result of this.  One is
      uart's apb_pclk, which was previously accidentally grabbing the fixed
      uart0_pclk due to the apb_pclk not having clk_register_clkdev()
      called.  The uart doesn't seem to do anything with apb_pclk other than
      make sure it's on, so that appears safe (also, as far as I can see,
      the apb clock is actually the same as the VPU clock).  The other is
      EMMC, which according to the docs was supposed to be in the 50-100Mhz
      range, but it turns out the firmware needed to change to running it at
      the 250Mhz core clock speed to avoid a bug in clock domain crossing.
      
      Additionally, anything using BCM2835_CLOCK_VPU will now have a correct
      clock rate if the user configures the boot-time core clock speed using
      config.txt.
      Signed-off-by: default avatarEric Anholt <eric@anholt.net>
      Acked-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      94cb7f76
  10. 14 Oct, 2015 1 commit
  11. 14 May, 2015 4 commits
  12. 25 Sep, 2014 1 commit
  13. 25 Feb, 2014 1 commit
    • Stephen Warren's avatar
      ARM: bcm2835: fix clock DT node names · b7c6c176
      Stephen Warren authored
      DT nodes should be named according to the type of object that they
      represent rather than the identity. DT nodes that contain a reg
      property should include a unit address in their name. Fix these issues.
      
      Add clock-output-names properties to the nodes so that the clocks get
      named something meaningful. This works around the fact that the fixed
      clock driver names clocks after the short node name, i.e. not including
      the unit address.
      Signed-off-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      b7c6c176
  14. 21 Feb, 2014 1 commit
    • Stephen Warren's avatar
      ARM: bcm2835: node name unit address cleanup · 25b2f1bd
      Stephen Warren authored
      DT nodes that contain a reg property should include a unit address in
      their name. Add the missing unit addresses.
      
      The unit address in a node name must match the value in the reg property.
      Fix the cases where they don't match.
      
      Don't fix the /clocks/* node names yet; that causes problems the clock
      driver to attempt to register multiple clocks with the same name, which
      fails.
      Signed-off-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      25b2f1bd
  15. 12 Feb, 2014 4 commits
  16. 02 Jan, 2014 1 commit
    • Stephen Warren's avatar
      ARM: bcm2835: add USB controller to device tree · 5631e7f4
      Stephen Warren authored
      The BCM2835 SoC contains a DWC2 USB controller. Add this to the DT.
      
      Set up the pin controller to fully enable the USB controller on the
      Raspberry Pi. The GPIO setup works because the default output value for
      GPIO 6 (LAN_RUN/n_reset) just happens to be 1, which enables the
      USB/LAN chip.
      
      Note that you'll need a U-Boot which enables power to the USB controller;
      search for U-Boot patch "ARM: rpi_b: power on SDHCI and USB HW modules".
      Signed-off-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      Signed-off-by: default avatarOlof Johansson <olof@lixom.net>
      5631e7f4
  17. 26 Nov, 2013 1 commit
  18. 02 Jun, 2013 1 commit
  19. 03 Apr, 2013 1 commit
  20. 12 Mar, 2013 1 commit
    • Stephen Warren's avatar
      ARM: bcm2835: add SPI device to DT · 6ce5f02e
      Stephen Warren authored
      The BCM2835 has a single instance of the "SPI0"-type SPI master
      controller. Instantiate it in the SoC .dtsi file, Don't enable it in
      the Raspberry Pi board .dts file, since we have no idea what is actually
      connected, and hence no idea what to set the bus clock rate to.
      Signed-off-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      6ce5f02e
  21. 05 Mar, 2013 1 commit
  22. 15 Jan, 2013 3 commits
    • Stephen Warren's avatar
      ARM: bcm2835: fix clock node aliasing in device tree · 9692c191
      Stephen Warren authored
      Both clock nodes in the current device tree are named "clock" and hence
      end up being the same node. Rename the nodes to different names to avoid
      this. In fact, fixed-clock uses the node name as the clock name, so name
      the nodes after the clock they represent. Move the clocks into a
      "clocks" sub-node to group them and avoid any possible naming conflicts
      with other nodes also named after the device type.
      Signed-off-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      9692c191
    • Stephen Warren's avatar
      ARM: bcm2835: add I2C controllers to DT · 232fed48
      Stephen Warren authored
      The BCM2835 has 3 identical I2C controllers. Instantiate them all in the
      SoC .dtsi file, and enable the relevant two in the Raspberry Pi board
      .dts file.
      
      Note that on the Raspberry Pi Model B revision 1, I2C0 is connected to
      the general-purpose expansion header, and I2C1 is connected to the camera
      connector. Revision 2 of the board swaps these assignments:-(
      Signed-off-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      232fed48
    • Stephen Warren's avatar
      ARM: bcm2835: add SDHCI node to DT · 5186bf28
      Stephen Warren authored
      Add the SDHCI device node to the SoC DT file. Add a dummy fixed-clock
      to satisfy the SDHCI driver's clock lookup; eventually this should be
      replaced by a real clock implementation. Add board specific properties
      to the Raspberry Pi board file.
      Signed-off-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      5186bf28
  23. 26 Oct, 2012 2 commits
    • Stephen Warren's avatar
      ARM: bcm2835: enable GPIO/pinctrl · 805504ab
      Stephen Warren authored
      Enable GPIO and pinctrl in Kconfig.
      
      Add required <mach/gpio.h> for gpiolib.
      
      Instantiate the BCM2835 GPIO module in bcm2835.dtsi.
      
      Add a pinctrl definition to bcm2835-rpi-b.dts that sets up all of the
      board's required pinmux configuration. GPIO aren't specified; that's
      left to gpio_request().
      Signed-off-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      Acked-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      805504ab
    • Stephen Warren's avatar
      ARM: bcm2835: implement machine restart hook · d0f1c7ff
      Stephen Warren authored
      Implement the machine restart hook using the SoC's watchdog timer module.
      To support this, define a DT binding for the watchdog module, and add it
      to the device tree.
      
      The downstream rpi-split branch contains a full watchdog timer driver
      implementation, which also implements the restart hook. However, the
      restart function is largely separate from the watchdog driver, so for
      simplicity, the restart hook is implemented here directly in the main
      machine source file.
      
      Overall structure (separate setup/restart) functions derived from the
      picoxcell ARM support.
      
      Watchdog register IO sequence taken from code by Simon Arlott. Note that
      the watchdog module is not documented in BCM2835-ARM-Peripherals.pdf.
      Signed-off-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      d0f1c7ff
  24. 20 Sep, 2012 4 commits