1. 06 2月, 2018 1 次提交
  2. 05 1月, 2018 1 次提交
  3. 27 11月, 2017 3 次提交
  4. 04 10月, 2017 2 次提交
  5. 04 8月, 2017 2 次提交
  6. 12 6月, 2017 1 次提交
    • M
      ACPICA: ACPI 6.2: Add support for PinConfig() resource · 97028ce6
      Mika Westerberg 提交于
      ACPICA commit a06fdba686cefccd5dd5b93b52fa0f1e3f984906
      
      ACPI 6.2 introduced a new resource that is used to specify fine-grained
      configuration of a pin or set of pins used by a device. The ASL syntax of
      this new resource looks like:
      
        PinConfig (Shared/Exclusive, PinConfigType, PinConfigValue,
                   ResourceSource, ResourceSourceIndex, ResourceUsage,
                   DescriptorName, Vendordata) {Pin List}
      
      PinConfigType is an integer with following accepted values:
      
        0x00 (Default) - No configuration is applied to the pin
        0x01 (Bias Pull-up) - Pin is pulled up using certain size resistor
        0x02 (Bias Pull-down) - Pin is pulled down using certain size resistor
        0x03 (Bias Default) - Set to default biasing
        0x04 (Bias Disable) - All bias settings will be disabled
        0x05 (Bias High Impedance) - Configure the pin as hi_z
        0x06 (Bias Bus Hold) - Configure the pin in a weak latch state where
                               it drives the last value on a tristate bus
        0x07 (Drive Open Drain) - Configure the pin into open drain state
        0x08 (Drive Open Source) - Configure the pin into open source state
        0x09 (Drive Push Pull) - Configure the pin into push-pull state
        0x0a (Drive Strength) - How much the pin can supply current
        0x0b (Slew Rate) - Configure slew rate of the pin
        0x0c (Input Debounce) - Enable input debouncer for the pin
        0x0d (Input Schmitt Trigger) - Enable schmitt trigger for the pin
        0x0e - 0x7f - Reserved
        0x80 - 0xff - Vendor defined types
      
      The PinConfigValue depends on the type and is expressed as units
      suitable for that type (for example bias uses Ohms).
      
      Link: https://github.com/acpica/acpica/commit/a06fdba6Signed-off-by: NMika Westerberg <mika.westerberg@linux.intel.com>
      Signed-off-by: NLv Zheng <lv.zheng@intel.com>
      Signed-off-by: NBob Moore <robert.moore@intel.com>
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      97028ce6
  7. 09 2月, 2017 1 次提交
  8. 09 12月, 2016 1 次提交
  9. 10 9月, 2016 1 次提交
  10. 13 8月, 2016 3 次提交
  11. 05 5月, 2016 2 次提交
  12. 05 4月, 2016 2 次提交
  13. 16 1月, 2016 1 次提交
  14. 01 1月, 2016 4 次提交
  15. 22 10月, 2015 1 次提交
    • L
      ACPI: Enable build of AML interpreter debugger · 4d946f79
      Lv Zheng 提交于
      This patch enables ACPICA debugger files using a configurable
      CONFIG_ACPI_DEBUGGER configuration item. Those debugger related code that
      was originally masked as ACPI_FUTURE_USAGE now gets unmasked.
      
      Necessary OSL stubs are also added in this patch:
      1. acpi_os_readable(): This should be arch specific in Linux, while this
          patch doesn't introduce real implementation and a complex mechanism to
          allow architecture specific acpi_os_readable() to be implemented to
          validate the address. It may be done by future commits.
      2. acpi_os_get_line(): This is used to obtain debugger command input. This
          patch only introduces a simple KDB concept example in it and the
          example should be co-working with the code implemented in
          acpi_os_printf(). Since this KDB example won't be compiled unless
          ENABLE_DEBUGGER is defined and it seems Linux has already stopped to
          use ENABLE_DEBUGGER, thus do not expect it can work properly.
      
      This patch also cleans up all other ACPI_FUTURE_USAGE surroundings
      accordingly.
      1. Since linkage error can be automatically detected, declaration in the
         headers needn't be surrounded by ACPI_FUTURE_USAGE.
         So only the following separate exported fuction bodies are masked by
         this macro (other exported fucntions may have already been masked at
         entire module level via drivers/acpi/acpica/Makefile):
           acpi_install_exception_handler()
           acpi_subsystem_status()
           acpi_get_system_info()
           acpi_get_statistics()
           acpi_install_initialization_handler()
      2. Since strip can automatically zap the no-user functions, functions that
         are not marked with ACPI_EXPORT_SYMBOL() needn't get surrounded by
         ACPI_FUTURE_USAGE.
         So the following function which is not used by Linux kernel now won't
         get surrounded by this macro:
           acpi_ps_get_name()
      Signed-off-by: NLv Zheng <lv.zheng@intel.com>
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      4d946f79
  16. 26 8月, 2015 1 次提交
  17. 24 7月, 2015 1 次提交
  18. 02 7月, 2015 3 次提交
  19. 22 5月, 2015 1 次提交
  20. 14 4月, 2015 3 次提交
  21. 05 2月, 2015 1 次提交
  22. 31 7月, 2014 1 次提交
  23. 08 7月, 2014 3 次提交