1. 23 3月, 2011 2 次提交
  2. 22 3月, 2011 3 次提交
  3. 16 3月, 2011 1 次提交
    • C
      mmc: export eMMC4.4 enhanced area details to sysfs · 709de99d
      Chuanxiao Dong 提交于
      Enhanced area feature is a new feature defined in eMMC4.4 standard. This
      user data area provides higher performance/reliability, at the expense
      of using twice the effective media space due to the area using SLC.
      
      The MMC driver now reads out the enhanced area offset and size and adds
      them to the device attributes in sysfs. Enabling the enhanced area can
      only be done once, and should be done in manufacturing. To use this
      feature, bit ERASE_GRP_DEF should also be set.
      
      Documentation/ABI/testing/sysfs-devices-mmc describes the two new
      attributes.
      Signed-off-by: NChuanxiao Dong <chuanxiao.dong@intel.com>
      Reviewed-by: NChris Ball <cjb@laptop.org>
      Signed-off-by: NChris Ball <cjb@laptop.org>
      709de99d
  4. 15 3月, 2011 1 次提交
    • R
      PM: Do not create wakeup sysfs files for devices that cannot wake up · cb8f51bd
      Rafael J. Wysocki 提交于
      Currently, wakeup sysfs attributes are created for all devices,
      regardless of whether or not they are wakeup-capable.  This is
      excessive and complicates wakeup device identification from user
      space (i.e. to identify wakeup-capable devices user space has to read
      /sys/devices/.../power/wakeup for all devices and see if they are not
      empty).
      
      Fix this issue by avoiding to create wakeup sysfs files for devices
      that cannot wake up the system from sleep states (i.e. whose
      power.can_wakeup flags are unset during registration) and modify
      device_set_wakeup_capable() so that it adds (or removes) the relevant
      sysfs attributes if a device's wakeup capability status is changed.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      cb8f51bd
  5. 14 3月, 2011 1 次提交
  6. 05 3月, 2011 1 次提交
    • N
      PCI: Export ACPI _DSM provided firmware instance number and string name to sysfs · 6058989b
      Narendra_K@Dell.com 提交于
      This patch exports ACPI _DSM (Device Specific Method) provided firmware
      instance number and string name of PCI devices as defined by 'PCI
      Firmware Specification Revision 3.1' section 4.6.7.( DSM for Naming a
      PCI or PCI Express Device Under Operating Systems) to sysfs.
      
      New files created are:
        /sys/bus/pci/devices/.../label which contains the firmware name for
      the device in question, and
        /sys/bus/pci/devices/.../acpi_index which contains the firmware device type
      instance for the given device.
      
      cat /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/acpi_index
      1
      cat /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/label
      Embedded Broadcom 5709C NIC 1
      
      cat /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.1/acpi_index
      2
      cat /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.1/label
      Embedded Broadcom 5709C NIC 2
      
      The ACPI _DSM provided firmware 'instance number' and 'string name' will
      be given priority if the firmware also provides 'SMBIOS type 41 device
      type instance and string'.
      Signed-off-by: NMatthew Garrett <mjg@redhat.com>
      Signed-off-by: NJordan Hargrave <jordan_hargrave@dell.com>
      Signed-off-by: NNarendra K <narendra_k@dell.com>
      Signed-off-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      6058989b
  7. 26 2月, 2011 1 次提交
  8. 17 2月, 2011 1 次提交
  9. 05 2月, 2011 1 次提交
    • P
      drivers:misc: ti-st: move from rfkill to sysfs · ec60d0ad
      Pavan Savoy 提交于
      The communication between ST KIM and UIM was interfaced
      over the /dev/rfkill device node.
      Move the interface to a simpler less abusive sysfs entry
      mechanism and document it in Documentation/ABI/testing/
      under sysfs-platform-kim.
      
      Shared transport driver would now read the UART details
      originally received by bootloader or firmware as platform
      data.
      The data read will be shared over sysfs entries for the user-space
      UIM or other n/w manager/plugins to be read, and assist the driver
      by opening up the UART, setting the baud-rate and installing the
      line discipline.
      Signed-off-by: NPavan Savoy <pavan_savoy@ti.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      ec60d0ad
  10. 04 2月, 2011 1 次提交
  11. 03 2月, 2011 1 次提交
  12. 24 1月, 2011 1 次提交
    • M
      can: at91_can: make can_id of mailbox 0 configurable · 3a5655a5
      Marc Kleine-Budde 提交于
      Due to a chip bug (errata 50.2.6.3 & 50.3.5.3 in
      "AT91SAM9263 Preliminary 6249H-ATARM-27-Jul-09") the contents of mailbox
      0 may be send under certain conditions (even if disabled or in rx mode).
      
      The workaround in the errata suggests not to use the mailbox and load it
      with an unused identifier.
      
      This patch implements the second part of the workaround. A sysfs entry
      "mb0_id" is introduced. While the interface is down it can be used to
      configure the can_id of mailbox 0. The default value id 0x7ff.
      
      In order to use an extended can_id add the CAN_EFF_FLAG (0x80000000U)
      to the can_id. Example:
      
      - standard id 0x7ff:
      echo 0x7ff      > /sys/class/net/can0/mb0_id
      
      - extended id 0x1fffffff:
      echo 0x9fffffff > /sys/class/net/can0/mb0_id
      Signed-off-by: NMarc Kleine-Budde <mkl@pengutronix.de>
      Acked-by: NWolfgang Grandegger <wg@grandegger.com>
      Acked-by: NKurt Van Dijck <kurt.van.dijck@eia.be>
      For the Documentation-part:
      Acked-by: NWolfram Sang <w.sang@pengutronix.de>
      3a5655a5
  13. 20 1月, 2011 1 次提交
  14. 14 1月, 2011 1 次提交
  15. 12 1月, 2011 1 次提交
  16. 08 1月, 2011 3 次提交
  17. 29 12月, 2010 1 次提交
    • T
      pstore: new filesystem interface to platform persistent storage · ca01d6dd
      Tony Luck 提交于
      Some platforms have a small amount of non-volatile storage that
      can be used to store information useful to diagnose the cause of
      a system crash.  This is the generic part of a file system interface
      that presents information from the crash as a series of files in
      /dev/pstore.  Once the information has been seen, the underlying
      storage is freed by deleting the files.
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      ca01d6dd
  18. 17 12月, 2010 2 次提交
  19. 02 12月, 2010 1 次提交
  20. 25 11月, 2010 2 次提交
  21. 12 11月, 2010 1 次提交
  22. 23 10月, 2010 1 次提交
    • M
      add Packet hub driver for Topcliff Platform controller hub · cf4ece53
      Masayuki Ohtak 提交于
      Packet hub driver of Topcliff PCH
      
      Topcliff PCH is the platform controller hub that is going to be used in
      Intel's upcoming general embedded platform. All IO peripherals in
      Topcliff PCH are actually devices sitting on AMBA bus. Packet hub is
      a special converter device in Topcliff PCH that translate AMBA transactions
      to PCI Express transactions and vice versa. Thus packet hub helps present
      all IO peripherals in Topcliff PCH as PCIE devices to IA system.
      Topcliff PCH has MAC address and Option ROM data.
      These data are in SROM which is connected to PCIE bus.
      Packet hub driver of Topcliff PCH can access MAC address and Option ROM data in
      SROM via sysfs interface.
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      cf4ece53
  23. 22 10月, 2010 1 次提交
  24. 21 10月, 2010 1 次提交
    • V
      IBM Real-Time "SMI Free" mode driver -v7 · 35f0ce03
      Vernon Mauery 提交于
      After a period of RFC for this driver, I think it is ready
      for inclusion in the platform-driver-x86 tree, hopefully to
      be staged in the next merge window into Linus's tree.
      
      --Vernon
      
      ------------------------------------------------------------
      
      IBM Real-Time "SMI Free" mode driver
      
      This driver supports the Real-Time Linux (RTL) BIOS feature.
      The RTL feature allows non-fatal System Management Interrupts
      (SMIs) to be disabled on supported IBM platforms and is
      intended to be coupled with a user-space daemon to monitor
      the hardware in a way that can be prioritized and scheduled
      to better suit the requirements for the system.
      
      The Device is presented as a special "_RTL_" table to the OS
      in the Extended BIOS Data Area.  There is a simple protocol
      for entering and exiting the mode at runtime.  This driver
      creates a simple sysfs interface to allow a simple entry and
      exit from RTL mode in the UFI/BIOS.
      
      Since the driver is specific to IBM SystemX hardware (x86-
      based servers) it only builds on x86 builds.  To reduce the
      risk of loading on the wrong hardware, the module uses DMI
      information and checks a list of servers that are known to
      work.
      Signed-off-by: NVernon Mauery <vernux@us.ibm.com>
      Signed-off-by: NMatthew Garrett <mjg@redhat.com>
      35f0ce03
  25. 17 10月, 2010 3 次提交
    • J
      PM: Add sysfs attr for rechecking dev hash from PM trace · d33ac60b
      James Hogan 提交于
      If the device which fails to resume is part of a loadable kernel module
      it won't be checked at startup against the magic number stored in the
      RTC.
      
      Add a read-only sysfs attribute /sys/power/pm_trace_dev_match which
      contains a list of newline separated devices (usually just the one)
      which currently match the last magic number. This allows the device
      which is failing to resume to be found after the modules are loaded
      again.
      Signed-off-by: NJames Hogan <james@albanarts.com>
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      d33ac60b
    • A
      PM / Runtime: Implement autosuspend support · 15bcb91d
      Alan Stern 提交于
      This patch (as1427) implements the "autosuspend" facility for runtime
      PM.  A few new fields are added to the dev_pm_info structure and
      several new PM helper functions are defined, for telling the PM core
      whether or not a device uses autosuspend, for setting the autosuspend
      delay, and for marking periods of device activity.
      
      Drivers that do not want to use autosuspend can continue using the
      same helper functions as before; their behavior will not change.  In
      addition, drivers supporting autosuspend can also call the old helper
      functions to get the old behavior.
      
      The details are all explained in Documentation/power/runtime_pm.txt
      and Documentation/ABI/testing/sysfs-devices-power.
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      15bcb91d
    • R
      PM / Wakeup: Introduce wakeup source objects and event statistics (v3) · 074037ec
      Rafael J. Wysocki 提交于
      Introduce struct wakeup_source for representing system wakeup sources
      within the kernel and for collecting statistics related to them.
      Make the recently introduced helper functions pm_wakeup_event(),
      pm_stay_awake() and pm_relax() use struct wakeup_source objects
      internally, so that wakeup statistics associated with wakeup devices
      can be collected and reported in a consistent way (the definition of
      pm_relax() is changed, which is harmless, because this function is
      not called directly by anyone yet).  Introduce new wakeup-related
      sysfs device attributes in /sys/devices/.../power for reporting the
      device wakeup statistics.
      
      Change the global wakeup events counters event_count and
      events_in_progress into atomic variables, so that it is not necessary
      to acquire a global spinlock in pm_wakeup_event(), pm_stay_awake()
      and pm_relax(), which should allow us to avoid lock contention in
      these functions on SMP systems with many wakeup devices.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Acked-by: NGreg Kroah-Hartman <gregkh@suse.de>
      074037ec
  26. 11 10月, 2010 1 次提交
    • S
      ieee1394: remove the old IEEE 1394 driver stack · 66fa12c5
      Stefan Richter 提交于
      The drivers
        - ohci1394 (controller driver)
        - ieee1394 (core)
        - dv1394, raw1394, video1394 (userspace ABI)
        - eth1394, sbp2 (protocol drivers)
      are replaced by
        - firewire-ohci (controller driver)
        - firewire-core (core and userspace ABI)
        - firewire-net, firewire-sbp2 (protocol drivers)
      which are more featureful, better performing, and more secure than the older
      drivers; all with a smaller and more modern code base.
      
      The driver firedtv in drivers/media/dvb/firewire/ contains backends to both
      ieee1394 and firewire-core.  Its ieee1394 backend code can be removed in an
      independent commit; firedtv as-is builds and works fine without ieee1394.
      
      The driver pcilynx (an incomplete controller driver) is deleted without
      replacement since PCILynx cards are extremely rare.  Owners of these cards
      use them with the stand-alone bus sniffer driver nosy instead.
      
      The drivers nosy and init_ohci1394_dma which do not interact with either of
      the two IEEE 1394 stacks are not affected by the ieee1394 subsystem removal.
      
      There are still some issues with the newer firewire subsystem compared to
      the older one:
        - The rare and quirky controllers ALi M52xx, Apple UniNorth v1, NVIDIA
          NForce2 are even less well supported by firewire-ohci than by ohci1394.
          I am looking into the M52xx issue.
        - The experimental firewire-net is reportedly less stable than its
          experimental cousin eth1394.
        - Audio playback of a certain group of audio devices (ones based on DICE
          chipset with EAP; supported by prerelease FFADO code) does not work yet.
          This issue is still under investigation.
        - There were some ieee1394 based out-of-the-mainline drivers.  Of them,
          only lisight, an audio driver for iSight webcams, seems still useful.
          Work is underway to reimplement it on top of firewire-core.
      
      All these remainig issues are minor; they should not stand in the way of
      overall better user experience of IEEE 1394 on Linux, together with a
      reduction in support efforts and maintenance burden.  The coexistence of two
      IEEE 1394 kernel driver stacks in the mainline since 2.6.22 shall end now,
      as announced earlier this year.
      Signed-off-by: NStefan Richter <stefanr@s5r6.in-berlin.de>
      66fa12c5
  27. 01 9月, 2010 2 次提交
  28. 11 8月, 2010 1 次提交
    • A
      USB: gadget: storage: optional SCSI WRITE FUA bit · a93917d3
      Andy Shevchenko 提交于
      MS Windows mounts removable storage in "Removal optimized mode" by
      default. All the writes to the media are synchronous which is achieved
      by setting FUA (Force Unit Access) bit in SCSI WRITE(10,12) commands.
      This prevents I/O requests aggregation in block layer dramatically
      decreasing performance.
      
      This patch brings an option to accept or ignore mentioned bit
       a) via specifying module parameter "nofua", or
       b) through sysfs entry
      	/sys/devices/platform/_UDC_/gadget/gadget-lunX/nofua
      	(_UDC_ is the name of the USB Device Controller driver)
      
      Patch is based on the work that was done by Denis Karpov for Maemo 5
      platform.
      Signed-off-by: NAndy Shevchenko <ext-andriy.shevchenko@nokia.com>
      Acked-by: NAlan Stern <stern@rowland.harvard.edu>
      Cc: Denis Karpov <ext-denis.2.karpov@nokia.com>
      Cc: Adrian Hunter <adrian.hunter@nokia.com>
      Cc: David Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      a93917d3
  29. 10 8月, 2010 2 次提交