Skip to content
Snippets Groups Projects
  1. Nov 17, 2021
    • Mark Kettenis's avatar
      pinctrl: Add Apple pinctrl driver · b814e000
      Mark Kettenis authored and Tom Rini's avatar Tom Rini committed
      
      This driver supports both pin muxing and GPIO support for the
      pin control logic found on Apple SoCs.
      
      Signed-off-by: default avatarMark Kettenis <kettenis@openbsd.org>
      b814e000
    • Ryan Chen's avatar
      aspeed: AST2600 Pinctrl Driver · 46220bf0
      Ryan Chen authored and Tom Rini's avatar Tom Rini committed
      
      This driver uses Pinctrl framework and is compatible with the Linux
      driver for AST2600.
      
      Signed-off-by: default avatarRyan Chen <ryan_chen@aspeedtech.com>
      Signed-off-by: default avatarDylan Hung <dylan_hung@aspeedtech.com>
      46220bf0
    • Tom Rini's avatar
      Merge branch '2021-11-16-env-rework' into next · f299171c
      Tom Rini authored
      To quote Simon:
      
      One barrier to completing the 7-year-long Kconfig migration is that
      the default environment is implemented using ad-hoc CONFIG options.
      At present U-Boot environment variables, and thus scripts, are defined
      by CONFIG_EXTRA_ENV_SETTINGS.
      
      It is not really feasible to move the environment to Kconfig as it is
      hundreds of lines of text in some cases.
      
      Even considering the current situation, it is painful to add large
      amounts of text to the config-header file and dealing with quoting and
      newlines is harder than it should be. It would be better if we could just
      type the script into a text file and have it included by U-Boot.
      
      This is already supported by the CONFIG_USE_DEFAULT_ENV_FILE feature. But
      that does not support use of CONFIG options or comments, so is best suited
      for use by other build systems wanting to define the U-Boot environment.
      
      Add a feature that brings in a .env file associated with the board
      config, if present. To use it, create a file board/<vendor>/<board>.env or
      use CONFIG_ENV_SOURCE_FILE to set a filename.
      
      The environment variables should be of the form "var=value". Values can
      extend to multiple lines. This series converts the existing environment
      documentation to rST and updates it to explain how to use this.
      f299171c
  2. Nov 16, 2021
  3. Nov 15, 2021
  4. Nov 14, 2021
  5. Nov 13, 2021
  6. Nov 12, 2021
Loading