1. 02 May, 2018 1 commit
  2. 26 Mar, 2018 1 commit
  3. 01 Mar, 2018 1 commit
  4. 09 Jan, 2018 1 commit
  5. 20 Dec, 2017 1 commit
    • Sean Wang's avatar
      pinctrl: mediatek: add pinctrl driver for MT7622 SoC · d6ed9355
      Sean Wang authored
      Add support for pinctrl on MT7622 SoC. The IO core found on the SoC has
      the registers for pinctrl, pinconf and gpio mixed up in the same register
      range. However, the IO core for the MT7622 SoC is completely distinct from
      anyone of previous MediaTek SoCs which already had support, such as
      the hardware internal, register address map and register detailed
      definition for each pin.
      
      Therefore, instead, the driver is being newly implemented by reusing
      generic methods provided from the core layer with GENERIC_PINCONF,
      GENERIC_PINCTRL_GROUPS, and GENERIC_PINMUX_FUNCTIONS for the sake of code
      simplicity and rid of superfluous code. Where the function of pins
      determined by groups is utilized in this driver which can help developers
      less confused with what combinations of pins effective on the SoC and even
      reducing the mistakes during the integration of those relevant boards.
      
      As the gpio_chip handling is also only a few lines, the driver also
      implements the gpio functionality directly through GPIOLIB.
      Signed-off-by: default avatarSean Wang <sean.wang@mediatek.com>
      Reviewed-by: default avatarBiao Huang <biao.huang@mediatek.com>
      Signed-off-by: Linus Walleij's avatarLinus Walleij <linus.walleij@linaro.org>
      d6ed9355
  6. 07 Dec, 2017 1 commit
  7. 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
  8. 31 Aug, 2017 1 commit
  9. 21 Aug, 2017 1 commit
  10. 14 Aug, 2017 1 commit
  11. 23 Jun, 2017 1 commit
  12. 23 May, 2017 1 commit
  13. 22 May, 2017 2 commits
    • Paul Cercueil's avatar
      pinctrl: add a pinctrl driver for the Ingenic jz47xx SoCs · b5c23aa4
      Paul Cercueil authored
      This driver handles pin configuration and pin muxing for the
      JZ4740 and JZ4780 SoCs from Ingenic.
      Signed-off-by: Paul Cercueil's avatarPaul Cercueil <paul@crapouillou.net>
      Signed-off-by: Linus Walleij's avatarLinus Walleij <linus.walleij@linaro.org>
      b5c23aa4
    • Shawn Guo's avatar
      pinctrl: add ZTE ZX pinctrl driver support · cbff0c4d
      Shawn Guo authored
      The pin controller on ZTE ZX platforms is kinda of hybrid.  It consists
      of a main controller and an auxiliary one.  For example, on ZX296718 SoC,
      the main controller is TOP_PMM and the auxiliary one is AON_IOCFG.  Both
      controllers work together to control pin multiplexing and configuration.
      
      For most of pins, the pinmux function is controlled by main controller
      only, and this type of pins are meant by term 'TOP pins'.  For other
      pins, the pinmux is controlled by both main and auxiliary controllers,
      as the available multiplexing functions for the pin spread in both
      controllers.  This type of pins are called 'AON pins'.  Though pinmux
      implementation is quite different, pinconf is same for both types of
      pins.  Both are controlled by auxiliary controller, i.e. AON_IOCFG on
      ZX296718.
      
      The patch adds the ZTE ZX core pinctrl driver to support this hybrid
      pin controller as well as ZX296718 SoC specific pin data.
      Signed-off-by: Shawn Guo's avatarShawn Guo <shawn.guo@linaro.org>
      Signed-off-by: Linus Walleij's avatarLinus Walleij <linus.walleij@linaro.org>
      cbff0c4d
  14. 24 Apr, 2017 1 commit
  15. 07 Apr, 2017 1 commit
  16. 09 Jan, 2017 1 commit
    • Nishanth Menon's avatar
      pinctrl: Introduce TI IOdelay configuration driver · 003910eb
      Nishanth Menon authored
      SoC family such as DRA7 family of processors have, in addition
      to the regular muxing of pins (as done by pinctrl-single), a separate
      hardware module called IODelay which is also expected to be configured.
      The "IODelay" module has it's own register space that is independent
      of the control module and the padconf register area.
      
      With recent changes to the pinctrl framework, we can now support
      this hardware with a reasonably minimal driver by using #pinctrl-cells,
      GENERIC_PINCTRL_GROUPS and GENERIC_PINMUX_FUNCTIONS.
      
      It is advocated strongly in TI's official documentation considering
      the existing design of the DRA7 family of processors during mux or
      IODelay reconfiguration, there is a potential for a significant glitch
      which may cause functional impairment to certain hardware. It is
      hence recommended to do as little of muxing as absolutely necessary
      without I/O isolation (which can only be done in initial stages of
      bootloader).
      
      NOTE: with the system wide I/O isolation scheme present in DRA7 SoC
      family, it is not reasonable to do stop all I/O operations for every
      such pad configuration scheme. So, we will let it glitch when used in
      this mode.
      
      Even with the above limitation, certain functionality such as MMC has
      mandatory need for IODelay reconfiguration requirements, depending on
      speed of transfer. In these cases, with careful examination of usecase
      involved, the expected glitch can be controlled such that it does not
      impact functionality.
      
      In short, IODelay module support as a padconf driver being introduced
      here is not expected to do SoC wide I/O Isolation and is meant for
      a limited subset of IODelay configuration requirements that need to
      be dynamic and whose glitchy behavior will not cause functionality
      failure for that interface.
      
      IMPORTANT NOTE: we take the approach of keeping LOCK_BITs cleared
      to 0x0 at all times, even when configuring Manual IO Timing Modes.
      This is done by eliminating the LOCK_BIT=1 setting from Step
      of the Manual IO timing Mode configuration procedure. This option
      leaves the CFG_* registers unprotected from unintended writes to the
      CTRL_CORE_PAD_* registers while Manual IO Timing Modes are configured.
      
      This approach is taken to allow for a generic driver to exist in kernel
      world that has to be used carefully in required usecases.
      Signed-off-by: default avatarNishanth Menon <nm@ti.com>
      Signed-off-by: default avatarLokesh Vutla <lokeshvutla@ti.com>
      [tony@atomide.com: updated to use generic pinctrl functions, added
       binding documentation, updated comments]
      Acked-by: Rob Herring's avatarRob Herring <robh@kernel.org>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      Signed-off-by: Linus Walleij's avatarLinus Walleij <linus.walleij@linaro.org>
      003910eb
  17. 07 Dec, 2016 1 commit
  18. 24 Oct, 2016 1 commit
    • Neil Armstrong's avatar
      pinctrl: Add SX150X GPIO Extender Pinctrl Driver · 9e80f906
      Neil Armstrong authored
      Since the I2C sx150x GPIO expander driver uses platform_data to manage
      the pins configurations, rewrite the driver as a pinctrl driver using
      pinconf to get/set pin configurations from DT or debugfs.
      
      The pinctrl driver is functionnally equivalent as the gpio-only driver
      and can use DT for pinconf. The platform_data confirmation is dropped.
      
      This patchset removed the gpio-only driver and selects the Pinctrl driver
      config instead. This patchset also migrates the gpio dt-bindings to pinctrl
      and add the pinctrl optional properties.
      
      The driver was tested with a SX1509 device on a BeagleBone black with
      interrupt support and on an X86_64 machine over an I2C to USB converter.
      
      This is a fixed version that builds and runs on non-OF platforms and on
      arm based OF. The GPIO version is removed and the bindings are also moved
      to the pinctrl bindings.
      
      Changes since v2
       - rebased on v4.9-rc1
       - removed MODULE_DEVICE_TABLE as in upstream bb411e77
         ("gpio: sx150x: fix implicit assumption module.h is present")
      
      Changes since v1
       - Fix Kconfig descriptions on pinctrl and gpio
       - Fix Kconfig dependency
       - Remove oscio support for non-789 devices
       - correct typo in dt bindings
       - remove probe reset for non-789 devices
      
      Changes since RFC
       - Put #ifdef CONFIG_OF/CONFIG_OF_GPIO to remove OF code for non-of platforms
       - No more rely on OF_GPIO config
       - Moved and enhanced bindings to pinctrl bindings
       - Removed gpio-sx150x.c
       - Temporary select PINCTRL_SX150X when GPIO_SX150X
       - Temporary mark GPIO_SX150X as deprecated
      Signed-off-by: Neil Armstrong's avatarNeil Armstrong <narmstrong@baylibre.com>
      Tested-by: default avatarPeter Rosin <peda@axentia.se>
      Acked-by: Rob Herring's avatarRob Herring <robh@kernel.org>
      ested-by: default avatarAndrey Smirnov <andrew.smirnov@gmail.com>
      Signed-off-by: Linus Walleij's avatarLinus Walleij <linus.walleij@linaro.org>
      9e80f906
  19. 07 Sep, 2016 1 commit
    • Andrew Jeffery's avatar
      pinctrl: Add core support for Aspeed SoCs · 4d3d0e42
      Andrew Jeffery authored
      The Aspeed SoCs typically provide more than 200 pins for GPIO and other
      functions. The signal enabled on a pin is determined on a priority
      basis, where a given pin can provide a number of different signal types.
      
      In addition to the priority levels, the Aspeed pin controllers describe
      the signal active on a pin by compound logical expressions involving
      multiple operators, registers and bits. Some difficulty arises as a
      pin's function bit masks for each priority level are frequently not the
      same (i.e. we cannot just flip a bit to change from a high to low
      priority signal), or even in the same register(s). Some configuration
      bits affect multiple pins, while in other cases the signals for a bus
      must each be enabled individually.
      
      Together, these features give rise to some complexity in the
      implementation. A more complete description of the complexities is
      provided in the associated header file.
      
      The patch doesn't implement pinctrl/pinmux/pinconf for any particular
      Aspeed SoC, rather it adds the framework for defining pinmux
      configurations.
      Signed-off-by: default avatarAndrew Jeffery <andrew@aj.id.au>
      Reviewed-by: Joel Stanley's avatarJoel Stanley <joel@jms.id.au>
      Signed-off-by: Linus Walleij's avatarLinus Walleij <linus.walleij@linaro.org>
      4d3d0e42
  20. 22 Jun, 2016 1 commit
    • Axel Lin's avatar
      pinctrl: tegra: Fix build dependency · 19b5a917
      Axel Lin authored
      I got below build error:
      ERROR: "tegra_xusb_padctl_legacy_probe"
       [drivers/phy/tegra/phy-tegra-xusb.ko] undefined!
      with below build configuration:
      CONFIG_ARCH_TEGRA=y
      CONFIG_PINCTRL_TEGRA_XUSB=y
      CONFIG_PHY_TEGRA_XUSB=y
      
      The problem is below line in drivers/pinctrl/Makefile
      obj-$(CONFIG_PINCTRL_TEGRA)     += tegra/
      
      So even CONFIG_PINCTRL_TEGRA_XUSB=y is set, kbuild still does not compile
      the code in drivers/pinctrl/tegra folder if !CONFIG_PINCTRL_TEGRA.
      
      phy-tegra-xusb.c does not use any symbol from pinctrl-tegra.c,
      so build pinctrl-tegra.c only when CONFIG_PINCTRL_TEGRA is set.
      Signed-off-by: default avatarAxel Lin <axel.lin@ingics.com>
      Acked-by: default avatarJon Hunter <jonathanh@nvidia.com>
      Signed-off-by: Linus Walleij's avatarLinus Walleij <linus.walleij@linaro.org>
      19b5a917
  21. 13 Jun, 2016 1 commit
  22. 30 May, 2016 2 commits
  23. 13 Feb, 2016 1 commit
  24. 09 Feb, 2016 1 commit
  25. 05 Feb, 2016 2 commits
  26. 28 Jan, 2016 2 commits
  27. 27 Jan, 2016 1 commit
  28. 10 Dec, 2015 1 commit
  29. 01 Dec, 2015 3 commits
  30. 31 Oct, 2015 1 commit
  31. 21 Sep, 2015 1 commit
  32. 27 Jul, 2015 1 commit
    • Baruch Siach's avatar
      pinctrl: driver for Conexant Digicolor CX92755 pin mapping · 38b0e507
      Baruch Siach authored
      This adds pinctrl and gpio driver to the CX92755 SoC "General
      Purpose Pin Mapping" hardware block. The CX92755 is one SoC
      from the Conexant Digicolor series. Pin mapping hardware supports
      configuring pins as either GPIO, or up to 3 other "client select"
      functions. This driver adds support for pin muxing using the
      generic device tree binding, and a basic gpiolib driver for
      the GPIO functionality.
      
      This driver does not currently support GPIO interrupts, and
      pad configuration.
      
      v2:
      * Address review comments for Linus Walleij:
        - Add a pointer to pinctrl_desc in struct dc_pinmap
        - Drop the now redundant pinctrl_pin_desc field
        - Adapt dc_get_group_{name,pins} to these changes, and
          add a comment explaining the 1-to-1 pin-groups relation
      * Staticise dc_pmxops
      * Protect the GP_CLIENTSEL clct parameter with parenthesis
      Signed-off-by: default avatarBaruch Siach <baruch@tkos.co.il>
      Signed-off-by: Linus Walleij's avatarLinus Walleij <linus.walleij@linaro.org>
      38b0e507
  33. 16 Jul, 2015 2 commits