Skip to content
Snippets Groups Projects
  1. Jun 07, 2019
  2. May 28, 2019
  3. Apr 11, 2019
  4. Mar 22, 2019
  5. Feb 22, 2019
  6. Feb 21, 2019
  7. Feb 14, 2019
  8. Feb 13, 2019
    • Thomas Petazzoni's avatar
      dt-bindings: gpio: document the new pull-up/pull-down flags · ede033e1
      Thomas Petazzoni authored
      
      This commit extends the flags that can be used in GPIO specifiers to
      indicate if a pull-up resistor or pull-down resistor should be
      enabled.
      
      While some pinctrl DT bindings already offer the capability of
      configuring pull-up/pull-down resistors at the pin level, a number of
      simple GPIO controllers don't have any pinmuxing capability, and
      therefore do not rely on the pinctrl DT bindings.
      
      Such simple GPIO controllers however sometimes allow to configure
      pull-up and pull-down resistors on a per-pin basis, and whether such
      resistors should be enabled or not is a highly board-specific HW
      characteristic.
      
      By using two additional bits of the GPIO flag specifier, we can easily
      allow the Device Tree to describe which GPIOs should have their
      pull-up or pull-down resistors enabled. Even though the two options
      are mutually exclusive, we still need two bits to encode at least
      three states: no pull-up/pull-down, pull-up, pull-down.
      
      Signed-off-by: default avatarThomas Petazzoni <thomas.petazzoni@bootlin.com>
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      ede033e1
  9. Feb 08, 2019
  10. Jan 16, 2019
  11. Dec 21, 2018
  12. Dec 20, 2018
  13. Dec 17, 2018
  14. Dec 07, 2018
    • Vladimir Zapolskiy's avatar
      dt-bindings: gpio: lpc18xx: describe interrupt controllers of GPIO controller · e96fd5ce
      Vladimir Zapolskiy authored
      
      From LPC18xx and LPC43xx User Manuals the GPIO controller consists of
      the following weakly connected blocks:
      * GPIO pin interrupt block at 0x40087000,
      * GPIO GROUP0 interrupt block at 0x40088000,
      * GPIO GROUP1 interrupt block at 0x40089000,
      * GPIO port block at 0x400F4000.
      
      While all 4 sub-controller blocks have their own I/O addresses, moreover
      all 3 interrupt blocks are APB0 peripherals and high-speed GPIO block is
      an AHB slave, according to the hardware manual interrupt controllers and
      GPIO controller block are seen as a single device, all 4 sub-controllers
      have the shared reset signal RGU #28 and the same shared clock to access
      registers CLK_Mx_GPIO on CCU1.
      
      The change adds descriptions of the currently missing interrupt controller
      blocks found on GPIO controller, new added properties are 'reg-names',
      'resets', 'interrupt-controller' and '#interrupt-cells', also the example
      is updated to reflect the changes in device tree binding description.
      
      Signed-off-by: default avatarVladimir Zapolskiy <vz@mleia.com>
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      e96fd5ce
  15. Nov 26, 2018
  16. Nov 05, 2018
    • A.s. Dong's avatar
      dt-bindings: gpio: vf610: add optional clocks property · b45f2869
      A.s. Dong authored
      
      On some SoCs(e.g. MX7ULP), GPIO clock is gatable and maybe
      disabled by default. Users have to make sure it's enabled before
      being able to access controller registers, otherwise an external
      abort error may occur. Let's add the optional clocks property to
      handle this case.
      
      For ULP GPIO clock, it includes two separate clocks: one is for
      GPIO controller Input/Output function clock while another is
      GPIO port control clock for interrupt function.
      
      Cc: Linus Walleij <linus.walleij@linaro.org>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Cc: Stefan Agner <stefan@agner.ch>
      Cc: linux-gpio@vger.kernel.org
      Cc: devicetree@vger.kernel.org
      Reviewed-by: default avatarRob Herring <robh@kernel.org>
      Signed-off-by: default avatarDong Aisheng <aisheng.dong@nxp.com>
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      b45f2869
  17. Oct 10, 2018
  18. Sep 25, 2018
  19. Sep 20, 2018
    • Linus Walleij's avatar
      gpio: OF: Remove bad practice examples · c02980d6
      Linus Walleij authored
      
      We remove the references to anything but two-cell GPIO specifiers
      and just mention that controllers need to specify their bindings
      and that we strongly recommend two-cell bindings.
      
      Cc: devicetree@vger.kernel.org
      Reviewed-by: default avatarRob Herring <robh@kernel.org>
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      c02980d6
    • Linus Walleij's avatar
      gpio: OF: Cut painful BNF experiments from bindings · 25db30c3
      Linus Walleij authored
      
      In 2011 the commit bf859f84
      ("gpio/dt: Refine GPIO device tree binding") introduced an
      experimental BNF notation for defining a regular grammar for
      the GPIO phandles used by different devices.
      
      This was an interesting approach, and shows that we have long
      nutured the idea to formally verify device tree files using
      regular grammar.
      
      Most if not all other bindings use natural language to define
      the bindings, and the recent thinking for verifying device
      tree files is to use JSON schemas in separate definitions.
      
      Cut the BNF business and replace it with natural language
      so that it becomes more human-readable for now.
      
      Cc: devicetree@vger.kernel.org
      Cc: Grant Likely <grant.likely@secretlab.ca>
      Cc: Kumar Gala <galak@kernel.crashing.org>
      Reviewed-by: default avatarRob Herring <robh@kernel.org>
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      25db30c3
  20. Sep 11, 2018
  21. Aug 29, 2018
  22. Aug 06, 2018
  23. Jul 25, 2018
    • Rob Herring's avatar
      dt-bindings: remove 'interrupt-parent' from bindings · 791d3ef2
      Rob Herring authored
      
      'interrupt-parent' is often documented as part of define bindings, but
      it is really outside the scope of a device binding. It's never required
      in a given node as it is often inherited from a parent node. Or it can
      be implicit if a parent node is an 'interrupt-controller' node. So
      remove it from all the binding files.
      
      Cc: Mark Rutland <mark.rutland@arm.com>
      Cc: devicetree@vger.kernel.org
      Signed-off-by: default avatarRob Herring <robh@kernel.org>
      791d3ef2
  24. Jul 10, 2018
  25. Jul 09, 2018
  26. Jul 02, 2018
  27. Jun 26, 2018
  28. Jun 18, 2018
  29. May 23, 2018
  30. May 16, 2018
  31. Mar 27, 2018
Loading