1. 18 Apr, 2018 1 commit
  2. 06 Mar, 2018 2 commits
  3. 23 Feb, 2018 3 commits
  4. 12 Feb, 2018 1 commit
  5. 12 Jan, 2018 1 commit
  6. 15 Dec, 2017 1 commit
  7. 13 Dec, 2017 1 commit
    • Thierry Reding's avatar
      memory: tegra: Add Tegra186 support · 02b0cc52
      Thierry Reding authored
      The memory controller found on Tegra186 is different in some respects to
      its predecessors. Most notably it no longer implements an SMMU, but does
      assign ARM SMMU stream IDs for each memory client instead.
      Provide a driver that programs these registers so that memory clients
      can translate addresses via the ARM SMMU.
      Signed-off-by: default avatarThierry Reding <treding@nvidia.com>
  8. 06 Dec, 2017 1 commit
  9. 03 Dec, 2017 1 commit
    • Dave Gerlach's avatar
      memory: ti-emif-sram: introduce relocatable suspend/resume handlers · 8428e5ad
      Dave Gerlach authored
      Certain SoCs like Texas Instruments AM335x and AM437x require parts
      of the EMIF PM code to run late in the suspend sequence from SRAM,
      such as saving and restoring the EMIF context and placing the memory
      into self-refresh.
      One requirement for these SoCs to suspend and enter its lowest power
      mode, called DeepSleep0, is that the PER power domain must be shut off.
      Because the EMIF (DDR Controller) resides within this power domain, it
      will lose context during a suspend operation, so we must save it so we
      can restore once we resume. However, we cannot execute this code from
      external memory, as it is not available at this point, so the code must
      be executed late in the suspend path from SRAM.
      This patch introduces a ti-emif-sram driver that includes several
      functions written in ARM ASM that are relocatable so the PM SRAM
      code can use them. It also allocates a region of writable SRAM to
      be used by the code running in the executable region of SRAM to save
      and restore the EMIF context. It can export a table containing the
      absolute addresses of the available PM functions so that other SRAM
      code can branch to them. This code is required for suspend/resume on
      AM335x and AM437x to work.
      In addition to this, to be able to share data structures between C and
      the ti-emif-sram-pm assembly code, we can automatically generate all of
      the C struct member offsets and sizes as macros by processing
      emif-asm-offsets.c into assembly code and then extracting the relevant
      data as is done for the generated platform asm-offsets.h files.
      Acked-by: default avatarTony Lindgren <tony@atomide.com>
      Acked-by: default avatarRussell King <rmk+kernel@armlinux.org.uk>
      Signed-off-by: default avatarDave Gerlach <d-gerlach@ti.com>
      Signed-off-by: default avatarSantosh Shilimkar <santosh.shilimkar@oracle.com>
  10. 01 Dec, 2017 1 commit
  11. 03 Nov, 2017 1 commit
  12. 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>
  13. 17 Oct, 2017 1 commit
  14. 06 Oct, 2017 2 commits
  15. 18 Sep, 2017 1 commit
  16. 05 Sep, 2017 1 commit
  17. 22 Aug, 2017 2 commits
    • Yong Wu's avatar
      memory: mtk-smi: Degrade SMI init to module_init · 4f608d38
      Yong Wu authored
      The initialization of MediaTek power manager(SCPSYS) is
      builtin_platform_driver, and SMI must depend on power-domain.
      Thus, currently subsys_initcall for SMI is unnecessary, SMI will be
      always probe defered by power-domain. Degrade it to module_init.
      In addition, there are two small changes about the probe sequence:
      1) Delete this two lines.
          	if (!dev->pm_domain)
      		return -EPROBE_DEFER;
         This is not helpful. the platform driver framework guarantee this.
         The "dev_pm_domain_attach" in the "platform_drv_probe" will return
         EPROBE_DEFER if its powerdomain is not ready.
      2) Add the probe-defer for the smi-larb device should waiting for
         In mt2712, there are 2 smi-commons, 10 smi-larbs. All will be
         probe-defered by the power-domain, there is seldom case that
         smi-larb probe done before smi-common. then it will hang like
         Unable to handle kernel NULL pointer dereference at virtual address
      00000000 pgd = ffffff800a4e0000
      [00000000] *pgd=00000000beffe003[   17.610026] , *pud=00000000beffe003
      [<ffffff800897fe04>] mtk_smi_enable+0x1c/0xd0
      [<ffffff800897fee8>] mtk_smi_larb_get+0x30/0x98
      [<ffffff80088edfa8>] mtk_mipicsi0_resume+0x38/0x1b8
      [<ffffff8008634f44>] pm_generic_runtime_resume+0x3c/0x58
      [<ffffff8008644ff8>] __genpd_runtime_resume+0x38/0x98
      [<ffffff8008647434>] genpd_runtime_resume+0x164/0x220
      [<ffffff80086372f8>] __rpm_callback+0x78/0xa0
      [<ffffff8008637358>] rpm_callback+0x38/0xa0
      [<ffffff8008638a4c>] rpm_resume+0x4a4/0x6f8
      [<ffffff8008638d04>] __pm_runtime_resume+0x64/0xa0
      [<ffffff80088ed05c>] mtk_mipicsi0_probe+0x40c/0xb70
      [<ffffff800862cdc0>] platform_drv_probe+0x58/0xc0
      [<ffffff800862a514>] driver_probe_device+0x284/0x438
      [<ffffff800862a8ac>] __device_attach_driver+0xb4/0x160
      [<ffffff8008627d58>] bus_for_each_drv+0x68/0xa8
      [<ffffff800862a0a4>] __device_attach+0xd4/0x168
      [<ffffff800862a9d4>] device_initial_probe+0x24/0x30
      [<ffffff80086291d8>] bus_probe_device+0xa0/0xa8
      [<ffffff8008629784>] deferred_probe_work_func+0x94/0xf0
      [<ffffff80080f03a8>] process_one_work+0x1d8/0x6e0
      Signed-off-by: default avatarYong Wu <yong.wu@mediatek.com>
      Signed-off-by: default avatarJoerg Roedel <jroedel@suse.de>
    • Yong Wu's avatar
      iommu/mediatek: Add mt2712 IOMMU support · e6dec923
      Yong Wu authored
      The M4U IP blocks in mt2712 is MTK's generation2 M4U which use the
      ARM Short-descriptor like mt8173, and most of the HW registers are
      the same.
      The difference is that there are 2 M4U HWs in mt2712 while there's
      only one in mt8173. The purpose of 2 M4U HWs is for balance the
      Normally if there are 2 M4U HWs, there should be 2 iommu domains,
      each M4U has a iommu domain.
      Signed-off-by: default avatarYong Wu <yong.wu@mediatek.com>
      Signed-off-by: default avatarJoerg Roedel <jroedel@suse.de>
  18. 16 Aug, 2017 1 commit
  19. 15 Aug, 2017 1 commit
  20. 04 Aug, 2017 2 commits
  21. 26 Jul, 2017 3 commits
  22. 03 Jun, 2017 1 commit
  23. 31 May, 2017 2 commits
  24. 16 May, 2017 1 commit
  25. 15 May, 2017 1 commit
  26. 27 Apr, 2017 5 commits
  27. 16 Mar, 2017 1 commit