1. 20 Sep, 2018 2 commits
    • 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: Rob Herring's avatarRob Herring <robh@kernel.org>
      Signed-off-by: Linus Walleij's 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: Rob Herring's avatarRob Herring <robh@kernel.org>
      Signed-off-by: Linus Walleij's avatarLinus Walleij <linus.walleij@linaro.org>
      25db30c3
  2. 11 Sep, 2018 1 commit
  3. 27 Mar, 2018 1 commit
  4. 26 Dec, 2017 1 commit
  5. 29 May, 2017 2 commits
  6. 22 May, 2017 1 commit
  7. 30 Dec, 2016 1 commit
  8. 10 May, 2016 1 commit
    • Linus Walleij's avatar
      gpio: of: make it possible to name GPIO lines · fd9c5531
      Linus Walleij authored
      Make it possible to name the producer side of a GPIO line using
      a "gpio-line-names" property array, modeled on the
      "clock-output-names" property from the clock bindings.
      
      This naming is especially useful for:
      
      - Debugging: lines are named after function, not just opaque
        offset numbers.
      
      - Exploration: systems where some or all GPIO lines are available
        to end users, such as prototyping, one-off's "makerspace usecases"
        users are helped by the names of the GPIO lines when tinkering.
        This usecase has been surfacing recently.
      
      The gpio-line-names attribute is completely optional.
      
      Example output from lsgpio on a patched Snowball tree:
      
      GPIO chip: gpiochip6, "8000e180.gpio", 32 GPIO lines
              line  0: unnamed unused
              line  1: "AP_GPIO161" "extkb3" [kernel]
              line  2: "AP_GPIO162" "extkb4" [kernel]
              line  3: "ACCELEROMETER_INT1_RDY" unused [kernel]
              line  4: "ACCELEROMETER_INT2" unused
              line  5: "MAG_DRDY" unused [kernel]
              line  6: "GYRO_DRDY" unused [kernel]
              line  7: "RSTn_MLC" unused
              line  8: "RSTn_SLC" unused
              line  9: "GYRO_INT" unused
              line 10: "UART_WAKE" unused
              line 11: "GBF_RESET" unused
              line 12: unnamed unused
      
      Cc: Grant Likely <grant.likely@linaro.org>
      Cc: Amit Kucheria <amit.kucheria@linaro.org>
      Cc: David Mandala <david.mandala@linaro.org>
      Cc: Lee Campbell <leecam@google.com>
      Cc: devicetree@vger.kernel.org
      Acked-by: Rob Herring's avatarRob Herring <robh@kernel.org>
      Reviewed-by: default avatarMichael Welling <mwelling@ieee.org>
      Signed-off-by: Linus Walleij's avatarLinus Walleij <linus.walleij@linaro.org>
      fd9c5531
  9. 26 Apr, 2016 1 commit
  10. 31 Mar, 2016 1 commit
  11. 31 Oct, 2015 1 commit
  12. 02 Oct, 2015 1 commit
    • Linus Walleij's avatar
      gpio: add DT bindings for existing consumer flags · 69d301fd
      Linus Walleij authored
      It is customary for GPIO controllers to support open drain/collector
      and open source/emitter configurations. Add standard GPIO line flags
      to account for this and augment the documentation to say that these
      are the most generic bindings.
      
      Several people approached me to add new flags to the lines, and this
      makes sense, but let's first bind up the most common cases before we
      start to add exotic stuff.
      
      Thanks to H. Nikolaus Schaller for ideas on how to encode single-ended
      wiring such as open drain/source and open collector/emitter.
      
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Grygorii Strashko <grygorii.strashko@ti.com>
      Cc: H. Nikolaus Schaller <hns@goldelico.com>
      Signed-off-by: Linus Walleij's avatarLinus Walleij <linus.walleij@linaro.org>
      69d301fd
  13. 24 Sep, 2015 1 commit
  14. 04 Mar, 2015 1 commit
  15. 19 Jan, 2015 1 commit
  16. 30 Oct, 2014 1 commit
  17. 27 Feb, 2014 1 commit
  18. 16 Oct, 2013 1 commit
  19. 15 Aug, 2013 1 commit
    • Stephen Warren's avatar
      gpio: clean up gpio-ranges documentation · a1bc260b
      Stephen Warren authored
      This change makes documentation of the the gpio-ranges property shorter
      and more succinct, more consistent with the style of the rest of the
      document, and not mention Linux-specifics such as the API
      pinctrl_request_gpio(); DT binding documents should be OS independant
      where at all possible. As part of this, the gpio-ranges property's format
      is described in BNF form, in order to match the rest of the document.
      
      This change also deprecates the #gpio-range-cells property. Such
      properties are useful when one node references a second node, and that
      second node dictates the format of the reference. However, that is not
      the case here; the definition of gpio-ranges itself always dictates its
      format entirely, and hence the value #gpio-range-cells must always be 3,
      and hence there is no point requiring any referenced node to include
      this property. The only remaining need for this property is to ensure
      compatibility of DTs with older SW that was written to support the
      previous version of the binding.
      
      v4:
      * Mention #gpio-range-cells as being deprecated, rather than removing all
        documentation of that property. This allows DTs to be written in a
        backwards-compatible way if desired, and also allows older DTs to be
        interpreted fully using the latest documentation.
      v3:
      * Mention BNF in commit description.
      * Fixed typo.
      * Dropped patch that removed the deprecated property from *.dts, since
        it's required to boot older kernels.
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Acked-by: default avatarMark Rutland <mark.rutland@arm.com>
      Signed-off-by: Linus Walleij's avatarLinus Walleij <linus.walleij@linaro.org>
      a1bc260b
  20. 07 Mar, 2013 1 commit
  21. 11 Nov, 2012 1 commit
  22. 28 Jun, 2011 1 commit
  23. 31 Jan, 2011 1 commit
  24. 23 Jun, 2009 1 commit