1. 31 Aug, 2018 1 commit
  2. 15 May, 2018 2 commits
  3. 20 Mar, 2018 2 commits
  4. 19 Mar, 2018 3 commits
  5. 10 Jan, 2018 1 commit
    • Sean Wang's avatar
      clk: mediatek: adjust dependency of reset.c to avoid unexpectedly being built · bc27360b
      Sean Wang authored
      Changes from v1->v2:
      Add 'select RESET_CONTROLLER' under COMMON_CLK_MEDIATEK and enable
      reset.c to be built when COMMON_CLK_MEDIATEK is selected. That should
      be quite reasonable because the reset controller is tightly embedded
      inside and exported from these clock subsystems. At least it can be found
      on infracfg and pericfg subsystem that both are really fundamental block
      lots of devices must depend on.
      
      commit 74cb0d6d ("clk: mediatek: fixup test-building of MediaTek clock
      drivers") can let the build system looking into the directory where the
      clock drivers resides and then allow test-building the drivers.
      
      But the change also gives rise to certain incorrect behavior which is
      reset.c being built even not depending on either COMPILE_TEST or
      ARCH_MEDIATEK alternative dependency. To get rid of reset.c being built
      unexpectedly on the other platforms, it would be a good change that the
      file should be built depending on its own specific configuration rather
      than just on generic RESET_CONTROLLER one.
      Signed-off-by: 's avatarSean Wang <sean.wang@mediatek.com>
      Cc: Jean Delvare <jdelvare@suse.de>
      Signed-off-by: 's avatarStephen Boyd <sboyd@codeaurora.org>
      bc27360b
  6. 27 Dec, 2017 1 commit
    • Sean Wang's avatar
      clk: mediatek: Fix all warnings for missing struct clk_onecell_data · 5589818b
      Sean Wang authored
      Even though the header file linux/clk-provider.h is already being properly
      included in clk-mtk.h, the definition of struct clk_onecell_data still
      must depend on CONFIG_COMMON_CLK defined and thus it's possible that
      below build warnings occur when CONFIG_COMMON_CLK is not being selected.
      
      Therefore, these functions which need struct clk_onecell_data without
      declaring that structure first requires simply declaring that this struct
      exists prior to referencing it in clk-mtk.h
      
      Changes from v1->v2:
      enhance v1 based on two useful solutions Jean Delvare kindly suggested.
      
      All warnings (new ones prefixed by >>):
      
      In file included from drivers/clk/mediatek/reset.c:22:0:
      >>drivers/clk/mediatek/clk-mtk.h:44:19: warning: 'struct clk_onecell_data'
      declared inside parameter list will not be visible outside of
      this definition or declaration
        int num, struct clk_onecell_data *clk_data);
      		  ^~~~~~~~~~~~~~~~
      drivers/clk/mediatek/clk-mtk.h:63:19: warning: 'struct clk_onecell_data'
      declared inside parameter list will not be visible outside of
      this definition or declaration
        int num, struct clk_onecell_data *clk_data);
      		  ^~~~~~~~~~~~~~~~
      drivers/clk/mediatek/clk-mtk.h:145:10: warning: 'struct clk_onecell_data'
      declared inside parameter list will not be visible outside of
      this definition or declaration
        struct clk_onecell_data *clk_data);
      	 ^~~~~~~~~~~~~~~~
      drivers/clk/mediatek/clk-mtk.h:164:11: warning: 'struct clk_onecell_data'
      declared inside parameter list will not be visible outside of
      this definition or declaration
         struct clk_onecell_data *clk_data);
      	  ^~~~~~~~~~~~~~~~
      drivers/clk/mediatek/clk-mtk.h:190:12: warning: 'struct clk_onecell_data'
      declared inside parameter list will not be visible outside of this
      definition or declaration
          struct clk_onecell_data *clk_data);
      	   ^~~~~~~~~~~~~~~~
      Reported-by: 's avatarkbuild test robot <fengguang.wu@intel.com>
      Signed-off-by: 's avatarSean Wang <sean.wang@mediatek.com>
      Cc: kbuild-all@01.org
      Cc: Stephen Boyd <sboyd@codeaurora.org>
      Cc: Jean Delvare <jdelvare@suse.de>
      Cc: linux-clk@vger.kernel.org
      Signed-off-by: 's avatarStephen Boyd <sboyd@codeaurora.org>
      5589818b
  7. 22 Dec, 2017 1 commit
  8. 02 Nov, 2017 5 commits
    • 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: 's avatarKate Stewart <kstewart@linuxfoundation.org>
      Reviewed-by: 's avatarPhilippe Ombredanne <pombredanne@nexb.com>
      Reviewed-by: 's avatarThomas Gleixner <tglx@linutronix.de>
      Signed-off-by: 's avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      b2441318
    • Sean Wang's avatar
      clk: mediatek: add clock support for MT7622 SoC · 2fc0a509
      Sean Wang authored
      Add all supported clocks exported from every susbystem found on MT7622 SoC
      such as topckgen, apmixedsys, infracfg, pericfg , pciessys, ssusbsys,
      ethsys and audsys.
      Signed-off-by: 's avatarChen Zhong <chen.zhong@mediatek.com>
      Signed-off-by: 's avatarSean Wang <sean.wang@mediatek.com>
      Signed-off-by: 's avatarStephen Boyd <sboyd@codeaurora.org>
      2fc0a509
    • Chen Zhong's avatar
      clk: mediatek: add the option for determining PLL source clock · c955bf39
      Chen Zhong authored
      Since the previous setup always sets the PLL using crystal 26MHz, this
      doesn't always happen in every MediaTek platform. So the patch added
      flexibility for assigning extra member for determining the PLL source
      clock.
      Signed-off-by: 's avatarChen Zhong <chen.zhong@mediatek.com>
      Signed-off-by: 's avatarSean Wang <sean.wang@mediatek.com>
      Signed-off-by: 's avatarStephen Boyd <sboyd@codeaurora.org>
      c955bf39
    • Arnd Bergmann's avatar
      clk: mediatek: mark mtk_infrasys_init_early __init · 5ef288d4
      Arnd Bergmann authored
      On gcc-4.6, we get a harmless link-time warning:
      
      WARNING: vmlinux.o(.text.unlikely+0x196a0): Section mismatch in reference from the function mtk_infrasys_init_early() to the function .init.text:mtk_clk_register_cpumuxes()
      The function mtk_infrasys_init_early() references
      the function __init mtk_clk_register_cpumuxes().
      This is often because mtk_infrasys_init_early lacks a __init
      annotation or the annotation of mtk_clk_register_cpumuxes is wrong.
      
      Newer compilers inline this function so they don't warn, but
      marking it __init is the right solution for all versions.
      
      Fixes: e9862118 ("clk: mediatek: Add MT2701 clock support")
      Signed-off-by: 's avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: 's avatarStephen Boyd <sboyd@codeaurora.org>
      5ef288d4
    • weiyi.lu@mediatek.com's avatar
      clk: mediatek: Add MT2712 clock support · e2f744a8
      weiyi.lu@mediatek.com authored
      Add MT2712 clock support, include topckgen, apmixedsys,
      infracfg, pericfg, mcucfg and subsystem clocks.
      Signed-off-by: 's avatarWeiyi Lu <weiyi.lu@mediatek.com>
      [sboyd@codeaurora.org: Static on top_clk_data]
      Signed-off-by: 's avatarStephen Boyd <sboyd@codeaurora.org>
      e2f744a8
  9. 21 Jul, 2017 1 commit
  10. 18 Jul, 2017 1 commit
  11. 20 Jun, 2017 3 commits
  12. 22 Apr, 2017 1 commit
  13. 19 Apr, 2017 1 commit
  14. 27 Jan, 2017 2 commits
  15. 08 Nov, 2016 2 commits
  16. 17 Oct, 2016 1 commit
  17. 21 Sep, 2016 1 commit
  18. 19 Aug, 2016 2 commits
  19. 06 May, 2016 3 commits
  20. 29 Mar, 2016 1 commit
  21. 03 Mar, 2016 1 commit
  22. 29 Jan, 2016 2 commits
  23. 01 Oct, 2015 2 commits