1. 09 6月, 2007 1 次提交
  2. 01 6月, 2007 1 次提交
  3. 18 5月, 2007 1 次提交
    • T
      libata: remove libata.spindown_compat · d9aca22c
      Tejun Heo 提交于
      With STANDBYDOWN tracking added, libata.spindown_compat isn't
      necessary anymore.  If userspace shutdown(8) issues STANDBYNOW, libata
      warns.  If userspace shutdown(8) doesn't issue STANDBYNOW, libata does
      the right thing.  Userspace can tell whether kernel supports spindown
      by testing whether sysfs node manage_start_stop exists as before.
      Signed-off-by: NTejun Heo <htejun@gmail.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      d9aca22c
  4. 17 5月, 2007 1 次提交
  5. 12 5月, 2007 1 次提交
    • T
      libata: implement libata.spindown_compat · 920a4b10
      Tejun Heo 提交于
      Now that libata uses sd->manage_start_stop, libata spins down disk on
      shutdown.  In an attempt to compensate libata's previous shortcoming,
      some distros sync and spin down disks attached via libata in their
      shutdown(8).  Some disks spin back up just to spin down again on
      STANDBYNOW1 if the command is issued when the disk is spun down, so
      this double spinning down causes problem.
      
      This patch implements module parameter libata.spindown_compat which,
      when set to one (default value), prevents libata from spinning down
      disks on shutdown thus avoiding double spinning down.  Note that
      libata spins down disks for suspend to mem and disk, so with
      libata.spindown_compat set to one, disks should be properly spun down
      in all cases without modifying shutdown(8).
      
      shutdown(8) should be fixed eventually.  Some drive do spin up on
      SYNCHRONZE_CACHE even when their cache is clean.  Those disks
      currently spin up briefly when sd tries to shutdown the device and
      then the machine powers off immediately, which can't be good for the
      head.  We can't skip SYNCHRONIZE_CACHE during shudown as it can be
      dangerous data integrity-wise.
      
      So, this spindown_compat parameter is already scheduled for removal by
      the end of the next year and here's what shutdown(8) should do.
      
        * Check whether /sys/modules/libata/parameters/spindown_compat
          exists.  If it does, write 0 to it.
      
        * For each libata harddisk {
      	* Check whether /sys/class/scsi_disk/h:c:i:l/manage_start_stop
      	  exists.  Iff it doesn't, synchronize cache and spin the disk
      	  down as before.
        }
      
      The above procedure will make shutdown(8) work properly with kernels
      before this change, ones with this workaround and later ones without
      it.
      
      To accelerate shutdown(8) updates, if the compat mode is in use, this
      patch prints BIG FAT warning for five seconds during shutdown (the
      optimal interval to annoy the user just the right amount discovered by
      hours of tireless usability testing).
      Signed-off-by: NTejun Heo <htejun@gmail.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      920a4b10
  6. 09 5月, 2007 4 次提交
  7. 06 5月, 2007 1 次提交
  8. 05 5月, 2007 1 次提交
  9. 03 5月, 2007 1 次提交
  10. 02 5月, 2007 2 次提交
    • J
      i2c: Obsolete i2c-ixp2000, i2c-ixp4xx and scx200_i2c · 11de70bd
      Jean Delvare 提交于
      The new generic i2c-gpio driver should be used instead.
      The obsolete drivers will be removed in September 2007.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Cc: Deepak Saxena <dsaxena@plexity.net>
      Cc: Jordan Crouse <jordan.crouse@amd.com>
      11de70bd
    • J
      i2c: Kill i2c_adapter.class_dev · fccb56e4
      Jean Delvare 提交于
      Kill i2c_adapter.class_dev. Instead, set the class of i2c_adapter.dev
      to i2c_adapter_class, so that a symlink will be created for every
      i2c_adapter in /sys/class/i2c-adapter.
      
      The same change must be mirrored to i2c-isa as it duplicates some
      of the i2c-core functionalities.
      
      User-space tools and libraries might need some adjustments. In
      particular, libsensors from lm_sensors 2.10.3 or later is required for
      proper discovery of i2c adapter names after this change.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      fccb56e4
  11. 01 5月, 2007 1 次提交
  12. 28 4月, 2007 2 次提交
  13. 27 4月, 2007 1 次提交
  14. 26 4月, 2007 2 次提交
  15. 10 4月, 2007 1 次提交
  16. 11 3月, 2007 1 次提交
  17. 05 3月, 2007 1 次提交
  18. 18 2月, 2007 1 次提交
  19. 17 2月, 2007 1 次提交
  20. 12 2月, 2007 1 次提交
  21. 10 2月, 2007 2 次提交
  22. 09 2月, 2007 2 次提交
  23. 08 2月, 2007 1 次提交
  24. 29 1月, 2007 1 次提交
  25. 23 1月, 2007 1 次提交
  26. 11 1月, 2007 1 次提交
  27. 04 1月, 2007 1 次提交
    • D
      i2c: Migration aids for i2c_adapter.dev removal · b119dc3f
      David Brownell 提交于
      Flag i2c_adapter.dev for removal after userspace tools get upgraded, and
      include a near-term code migration aid to facilitate this:
      
       - The class device gets the name attribute it should have had.  This
         was previously (wrongly) associated with the i2c_adapter.dev node.
         Sysfs based tools and libraries can start converting right away.
      
       - Issue a warning for legacy adapter drivers that don't provide any
         physical device node; so systems with those drivers will know to
         fix this problem earlier.
      
      This is one of a series of patches to help the I2C stack become a better
      citizen of the Linux Driver Model world.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      b119dc3f
  28. 14 12月, 2006 1 次提交
  29. 13 12月, 2006 1 次提交
  30. 11 12月, 2006 1 次提交
  31. 08 12月, 2006 2 次提交