1. 03 3月, 2018 1 次提交
  2. 24 2月, 2018 1 次提交
  3. 29 11月, 2017 1 次提交
  4. 02 11月, 2017 1 次提交
    • G
      License cleanup: add SPDX GPL-2.0 license identifier to files with no license · b2441318
      Greg Kroah-Hartman 提交于
      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: NKate Stewart <kstewart@linuxfoundation.org>
      Reviewed-by: NPhilippe Ombredanne <pombredanne@nexb.com>
      Reviewed-by: NThomas Gleixner <tglx@linutronix.de>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      b2441318
  5. 13 8月, 2017 1 次提交
  6. 28 7月, 2017 1 次提交
    • A
      ARM: mmp: mark usb_dma_mask as __maybe_unused · 1c1953f3
      Arnd Bergmann 提交于
      This variable may be used by some devices that each have their
      on Kconfig symbol, or by none of them, and that causes a build
      warning:
      
      arch/arm/mach-mmp/devices.c:241:12: error: 'usb_dma_mask' defined but not used [-Werror=unused-variable]
      
      Marking it __maybe_unused avoids the warning.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      1c1953f3
  7. 30 3月, 2017 1 次提交
  8. 25 12月, 2016 1 次提交
  9. 04 6月, 2016 1 次提交
    • L
      ARM: do away with ARCH_[WANT_OPTIONAL|REQUIRE]_GPIOLIB · 5c34a4e8
      Linus Walleij 提交于
      This replaces:
      
      - "select ARCH_REQUIRE_GPIOLIB" with "select GPIOLIB" as this can
        now be selected directly.
      
      - "select ARCH_WANT_OPTIONAL_GPIOLIB" with no dependency: GPIOLIB
        is now selectable by everyone, so we need not declare our
        intent to select it.
      
      When ordering the symbols the following rationale was used:
      if the selects were in alphabetical order, I moved select GPIOLIB
      to be in alphabetical order, but if the selects were not
      maintained in alphabetical order, I just replaced
      "select ARCH_REQUIRE_GPIOLIB" with "select GPIOLIB".
      
      Cc: Michael Büsch <m@bues.ch>
      Cc: arm@kernel.org
      Cc: linux-arm-kernel@lists.infradead.org
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      5c34a4e8
  10. 09 2月, 2016 1 次提交
  11. 02 12月, 2015 5 次提交
    • A
      ARM: mmp: avoid unused functions · 84f45ee9
      Arnd Bergmann 提交于
      mach-mmp/devices.c:81:21: warning: 'u2o_get' defined but not used [-Wunused-function]
       static unsigned int u2o_get(void __iomem *base, unsigned int offset)
                           ^
      mach-mmp/devices.c:86:13: warning: 'u2o_set' defined but not used [-Wunused-function]
       static void u2o_set(void __iomem *base, unsigned int offset,
                   ^
      mach-mmp/devices.c:97:13: warning: 'u2o_clear' defined but not used [-Wunused-function]
       static void u2o_clear(void __iomem *base, unsigned int offset,
                   ^
      mach-mmp/devices.c:108:13: warning: 'u2o_write' defined but not used [-Wunused-function]
       static void u2o_write(void __iomem *base, unsigned int offset,
                   ^
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      84f45ee9
    • A
      ARM: mmp: move into ARCH_MULTIPLATFORM · 377524dc
      Arnd Bergmann 提交于
      With all dependencies taken care of, this enables building
      the Marvell mmp platform as part of ARCH_MULTIPLATFORM, along
      with other ARMv5 and ARMv7 platforms.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NAndrew Lunn <andrew@lunn.ch>
      377524dc
    • A
      ARM: mmp: make all header files local · b501fd7b
      Arnd Bergmann 提交于
      The mach/*.h headers are now inaccessible to any external code,
      so we can move them all into the mach-mmp directory itself
      and remove the subdirectories.
      
      A few headers are not used at all, so we remove them here.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      b501fd7b
    • A
      ARM: mmp: remove remaining legacy pxa-dma support · 74911e3a
      Arnd Bergmann 提交于
      All drivers have stopped using this code, so we can just
      as well stop initializing it.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      74911e3a
    • A
      clk: mmp: stop using platform headers · 990f2f22
      Arnd Bergmann 提交于
      The mmp clock drivers currently hardcode the physical addresses for
      the clock registers. This is generally a bad idea, and it also gets in
      the way of multiplatform builds, which make the platform header files
      inaccessible to device drivers.
      
      To work around the header file problem, this patch changes the calling
      convention so the three mmp clock drivers get initialized with the base
      addresses as arguments from the platform code.
      
      It would still be useful to have a larger rework of the clock drivers,
      with DT integration to let the clocks actually be probed automatically,
      and the base addresses passed as DT properties. I am unsure if anyone
      is still interested in the mmp platform, so it is possible that this
      won't happen.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Cc: Mike Turquette <mturquette@linaro.org>
      Cc: Chao Xie <chao.xie@marvell.com>
      Cc: Eric Miao <eric.y.miao@gmail.com>
      Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
      990f2f22
  12. 06 9月, 2015 1 次提交
  13. 28 7月, 2015 1 次提交
  14. 25 7月, 2015 1 次提交
    • R
      ARM: move heavy barrier support out of line · f8130906
      Russell King 提交于
      The existing memory barrier macro causes a significant amount of code
      to be inserted inline at every call site.  For example, in
      gpio_set_irq_type(), we have this for mb():
      
      c0344c08:       f57ff04e        dsb     st
      c0344c0c:       e59f8190        ldr     r8, [pc, #400]  ; c0344da4 <gpio_set_irq_type+0x230>
      c0344c10:       e3590004        cmp     r9, #4
      c0344c14:       e5983014        ldr     r3, [r8, #20]
      c0344c18:       0a000054        beq     c0344d70 <gpio_set_irq_type+0x1fc>
      c0344c1c:       e3530000        cmp     r3, #0
      c0344c20:       0a000004        beq     c0344c38 <gpio_set_irq_type+0xc4>
      c0344c24:       e50b2030        str     r2, [fp, #-48]  ; 0xffffffd0
      c0344c28:       e50bc034        str     ip, [fp, #-52]  ; 0xffffffcc
      c0344c2c:       e12fff33        blx     r3
      c0344c30:       e51bc034        ldr     ip, [fp, #-52]  ; 0xffffffcc
      c0344c34:       e51b2030        ldr     r2, [fp, #-48]  ; 0xffffffd0
      c0344c38:       e5963004        ldr     r3, [r6, #4]
      
      Moving the outer_cache_sync() call out of line reduces the impact of
      the barrier:
      
      c0344968:       f57ff04e        dsb     st
      c034496c:       e35a0004        cmp     sl, #4
      c0344970:       e50b2030        str     r2, [fp, #-48]  ; 0xffffffd0
      c0344974:       0a000044        beq     c0344a8c <gpio_set_irq_type+0x1b8>
      c0344978:       ebf363dd        bl      c001d8f4 <arm_heavy_mb>
      c034497c:       e5953004        ldr     r3, [r5, #4]
      
      This should reduce the cache footprint of this code.  Overall, this
      results in a reduction of around 20K in the kernel size:
      
          text    data      bss      dec     hex filename
      10773970  667392 10369656 21811018 14ccf4a ../build/imx6/vmlinux-old
      10754219  667392 10369656 21791267 14c8223 ../build/imx6/vmlinux-new
      
      Another advantage to this approach is that we can finally resolve the
      issue of SoCs which have their own memory barrier requirements within
      multiplatform kernels (such as OMAP.)  Here, the bus interconnects
      need additional handling to ensure that writes become visible in the
      correct order (eg, between dma_map() operations, writes to DMA
      coherent memory, and MMIO accesses.)
      Acked-by: NTony Lindgren <tony@atomide.com>
      Acked-by: NRichard Woodruff <r-woodruff2@ti.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      f8130906
  15. 17 7月, 2015 1 次提交
    • V
      ARM/mmp/time: Migrate to new 'set-state' interface · a785fb39
      Viresh Kumar 提交于
      Migrate mmp driver to the new 'set-state' interface provided by
      clockevents core, the earlier 'set-mode' interface is marked obsolete
      now.
      
      This also enables us to implement callbacks for new states of clockevent
      devices, for example: ONESHOT_STOPPED.
      
      We weren't doing anything in set_mode(RESUME) except of
      local_irq_{save|restore}(), which isn't required and so ->tick_resume
      isn't implemented.
      
      Cc: Eric Miao <eric.y.miao@gmail.com>
      Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
      Signed-off-by: NViresh Kumar <viresh.kumar@linaro.org>
      a785fb39
  16. 19 2月, 2015 1 次提交
  17. 13 11月, 2014 1 次提交
  18. 29 10月, 2014 1 次提交
  19. 25 10月, 2014 1 次提交
  20. 04 7月, 2014 1 次提交
  21. 18 3月, 2014 1 次提交
    • A
      ARM: mmp: allow platform devices with modular USB · 35240808
      Arnd Bergmann 提交于
      The USB host drivers need platform data to be defined on
      pxa168 and pxa910, but the conditionals used in the devices.c
      file only work if the drivers are built-in. This patch
      fixes the definition by changing the #ifdef to #if IS_ENABLED(),
      which works both for built-in and modular Kconfig symbols.
      
      I found one specific problem using 'randconfig' builds, but
      for consistency, this patch uses IS_ENABLED() for all Kconfig
      symbols in these three files.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NHaojian Zhuang <haojian.zhuang@gmail.com>
      35240808
  22. 12 3月, 2014 1 次提交
  23. 05 3月, 2014 1 次提交
    • T
      arm: mmp: Remove pointless fiddling with irq internals · 49f3fbc7
      Thomas Gleixner 提交于
      The pm-mmp2 and pm-pxa910 power management related irq_set_wake
      callbacks fiddle pointlessly with the irq actions for no reason except
      for lack of understanding how the wakeup mechanism works.
      
      On supsend the core disables all interrupts lazily, i.e. it does not
      mask them at the irq controller level. So any interrupt which is
      firing during suspend will mark the corresponding interrupt line as
      pending. Just before the core powers down it checks whether there are
      interrupts pending from interrupt lines which are marked as wakeup
      sources and if so it aborts the suspend and resends the interrupts.
      If there was no interrupt at this point, the cpu goes into suspend
      with these interrupts unmasked.
      
      The IRQF_NO_SUSPEND flag for interrupt actions is a totally different
      mechanism. That allows the device driver to prevent the core from
      disabling the interrupt despite the fact that it is not marked as a
      wakeup source. This has nothing to do with the case at hand. It was
      introduced for special cases where lazy disable is not possible.
      
      Remove the nonsense along with the braindamaged boundary check. The
      core code does NOT call these functions out of boundary.
      
      Add a FIXME comment to an unhandled error path which merily printks
      some useless blurb instead of returning a proper error code.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Cc: arm <linux-arm-kernel@lists.infradead.org>
      Cc: Eric Miao <eric.y.miao@gmail.com>
      Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Link: http://lkml.kernel.org/r/20140223212737.214342433@linutronix.deSigned-off-by: NThomas Gleixner <tglx@linutronix.de>
      49f3fbc7
  24. 21 12月, 2013 1 次提交
  25. 20 12月, 2013 1 次提交
  26. 12 12月, 2013 1 次提交
  27. 22 11月, 2013 1 次提交
  28. 27 9月, 2013 1 次提交
  29. 20 9月, 2013 1 次提交
  30. 30 8月, 2013 1 次提交
  31. 24 8月, 2013 3 次提交
  32. 10 7月, 2013 1 次提交
  33. 19 6月, 2013 1 次提交
  34. 13 6月, 2013 1 次提交