1. 29 12月, 2013 1 次提交
    • D
      x86: Export x86 boot_params to sysfs · 5039e316
      Dave Young 提交于
      kexec-tools use boot_params for getting the 1st kernel hardware_subarch,
      the kexec kernel EFI runtime support also needs to read the old efi_info
      from boot_params. Currently it exists in debugfs which is not a good
      place for such infomation. Per HPA, we should avoid "sploit debugfs".
      
      In this patch /sys/kernel/boot_params are exported, also the setup_data is
      exported as a subdirectory. kexec-tools is using debugfs for hardware_subarch
      for a long time now so we're not removing it yet.
      
      Structure is like below:
      
      /sys/kernel/boot_params
      |__ data                /* boot_params in binary*/
      |__ setup_data
      |   |__ 0               /* the first setup_data node */
      |   |   |__ data        /* setup_data node 0 in binary*/
      |   |   |__ type        /* setup_data type of setup_data node 0, hex string */
      [snip]
      |__ version             /* boot protocal version (in hex, "0x" prefixed)*/
      Signed-off-by: NDave Young <dyoung@redhat.com>
      Acked-by: NBorislav Petkov <bp@suse.de>
      Tested-by: NToshi Kani <toshi.kani@hp.com>
      Signed-off-by: NMatt Fleming <matt.fleming@intel.com>
      5039e316
  2. 21 12月, 2013 2 次提交
  3. 30 10月, 2013 2 次提交
  4. 28 10月, 2013 1 次提交
  5. 19 10月, 2013 4 次提交
  6. 17 10月, 2013 1 次提交
  7. 12 10月, 2013 1 次提交
  8. 10 10月, 2013 2 次提交
  9. 09 10月, 2013 1 次提交
  10. 06 10月, 2013 1 次提交
    • D
      misc: mic: Enable OSPM suspend and resume support. · af190494
      Dasaratharaman Chandramouli 提交于
      This patch enables support for OSPM suspend and resume in the MIC
      driver. During a host suspend event, the driver performs an
      orderly shutdown of the cards if they are online. Upon resume, any
      cards that were previously online before suspend are rebooted.
      The driver performs an orderly shutdown of the card primarily to
      ensure that applications in the card are terminated and mounted
      devices are safely un-mounted before the card is powered down in
      the event of an OSPM suspend.
      
      The driver makes use of the MIC daemon to accomplish OSPM suspend
      and resume. The driver registers a PM notifier per MIC device.
      The devices get notified synchronously during PM_SUSPEND_PREPARE and
      PM_POST_SUSPEND phases.
      
      During the PM_SUSPEND_PREPARE phase, the driver performs one of the
      following three tasks.
      1) If the card is 'offline', the driver sets the card to a
         'suspended' state and returns.
      2) If the card is 'online', the driver initiates card shutdown by
         setting the card state to suspending. This notifies the MIC
         daemon which invokes shutdown and sets card state to 'suspended'.
         The driver returns after the shutdown is complete.
      3) If the card is already being shutdown, possibly by a host user
         space application, the driver sets the card state to 'suspended'
         and returns after the shutdown is complete.
      
      During the PM_POST_SUSPEND phase, the driver simply notifies the
      daemon and returns. The daemon boots those cards that were previously
      online during the suspend phase.
      Signed-off-by: NAshutosh Dixit <ashutosh.dixit@intel.com>
      Signed-off-by: NNikhil Rao <nikhil.rao@intel.com>
      Signed-off-by: NHarshavardhan R Kharche <harshavardhan.r.kharche@intel.com>
      Signed-off-by: NSudeep Dutt <sudeep.dutt@intel.com>
      Signed-off-by: NDasaratharaman Chandramouli <dasaratharaman.chandramouli@intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      af190494
  11. 01 10月, 2013 1 次提交
  12. 27 9月, 2013 3 次提交
  13. 15 9月, 2013 1 次提交
    • P
      iio: Add INT_TIME (integration time) channel info attribute · 899d90bd
      Peter Meerwald 提交于
      Integration time is in seconds; it controls the measurement
      time and influences the gain of a sensor.
      
      There are two typical ways that scaling is implemented in a device:
      1) input amplifier,
      2) reference to the ADC is changed.
      These both result in the accuracy of the ADC varying (by applying its
      sampling over a more relevant range).
      
      Integration time is a way of dealing with noise inherent in the analog
      sensor itself.  In the case of a light sensor, a mixture of photon noise
      and device specific noise.  Photon noise is dealt with by either improving
      the efficiency of the sensor, (more photons actually captured) which is not
      easily varied dynamically, or by integrating the measurement over a longer
      time period.  Note that this can also be thought of as an averaging of a
      number of individual samples and is infact sometimes implemented this way.
      Altering integration time implies that the duration of a measurement changes,
      a fact the device's user may be interested in.
      
      Hence it makes sense to distinguish between integration time and simple
      scale. In some devices both types of control are present and whilst they
      will have similar effects on the amplitude of the reading, their effect
      on the noise of the measurements will differ considerably.
      
      Used by adjd_s311, tsl4531, tcs3472
      The following drivers have similar controls (and could be adapted):
      * tsl2563 (integration time is controlled via CALIBSCALE among other things)
      * tsl2583 (has integration_time device_attr, but driver doesn't use channels yet)
      * tsl2x7x (has integration_time attr)
      Signed-off-by: NPeter Meerwald <pmeerw@pmeerw.net>
      Cc: Jon Brenner <jon.brenner@ams.com>
      Signed-off-by: NJonathan Cameron <jic23@kernel.org>
      899d90bd
  14. 31 8月, 2013 2 次提交
  15. 29 8月, 2013 1 次提交
  16. 27 8月, 2013 1 次提交
  17. 15 8月, 2013 1 次提交
  18. 13 8月, 2013 1 次提交
  19. 06 8月, 2013 2 次提交
  20. 04 8月, 2013 3 次提交
  21. 11 7月, 2013 1 次提交
    • M
      Add support driver for Intel Rapid Start Technology · 34a956db
      Matthew Garrett 提交于
      Intel Rapid Start Technology is a firmware-based suspend-to-disk
      implementation. Once placed in S3, the device will wake once either a
      timeout elapses or the battery reaches a critical level. It will then resume
      to the firmware and copy the contents of RAM to a specialised partition, and
      then power off the machine. If the user turns the machine back on the
      firmware will copy the contents of the partition back to RAM and then resume
      from S3 as normal.
      
      This driver provides an interface for configuring the wakeup events and
      timeout. It still requires firmware support and an appropriate suspend
      partition.
      Signed-off-by: NMatthew Garrett <mjg59@srcf.ucam.org>
      Signed-off-by: NMatthew Garrett <matthew.garrett@nebula.com>
      34a956db
  22. 09 7月, 2013 1 次提交
  23. 08 7月, 2013 1 次提交
  24. 28 6月, 2013 1 次提交
  25. 25 6月, 2013 1 次提交
  26. 21 6月, 2013 2 次提交
    • H
      pwm: Add sysfs interface · 76abbdde
      H Hartley Sweeten 提交于
      Add a simple sysfs interface to the generic PWM framework.
      
        /sys/class/pwm/
        `-- pwmchipN/           for each PWM chip
            |-- export          (w/o) ask the kernel to export a PWM channel
            |-- npwm            (r/o) number of PWM channels in this PWM chip
            |-- pwmX/           for each exported PWM channel
            |   |-- duty_cycle  (r/w) duty cycle (in nanoseconds)
            |   |-- enable      (r/w) enable/disable PWM
            |   |-- period      (r/w) period (in nanoseconds)
            |   `-- polarity    (r/w) polarity of PWM (normal/inversed)
            `-- unexport        (w/o) return a PWM channel to the kernel
      
      Based on work by Lars Poeschel.
      Signed-off-by: NH Hartley Sweeten <hsweeten@visionengravers.com>
      Cc: Thierry Reding <thierry.reding@gmail.com>
      Cc: Lars Poeschel <poeschel@lemonage.de>
      Cc: Ryan Mallon <rmallon@gmail.com>
      Cc: Rob Landley <rob@landley.net>
      Signed-off-by: NThierry Reding <thierry.reding@gmail.com>
      76abbdde
    • L
      ACPI: Add sysfs ABI documentation · 89ca78a0
      Lv Zheng 提交于
      Add initial ABI documentation for ACPI devices' sysfs interfaces.
      Contacts information fields are filled with current ACPI maintainer and the
      relevant authors are carbon copied.
      
      [rjw: Use my e-mail address that's likely to be valid longer.]
      Signed-off-by: NLv Zheng <lv.zheng@intel.com>
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      89ca78a0
  27. 18 6月, 2013 1 次提交