1. May 05, 2013
  2. May 04, 2013
    • Jean Delvare's avatar
      hwmon: (lm75) Add support for the Dallas/Maxim DS7505 · 3fbc81e3
      Jean Delvare authored
      
      
      Basically it's the same as the original DS75 but much faster.
      
      Signed-off-by: default avatarJean Delvare <khali@linux-fr.org>
      Acked-by: default avatarGuenter Roeck <linux@roeck-us.net>
      3fbc81e3
    • Jean Delvare's avatar
      hwmon: (lm75) Tune resolution and sample time per chip · 0cd2c72d
      Jean Delvare authored
      
      
      Most LM75-compatible chips can either sample much faster or with a
      much better resolution than the original LM75 chip. So far the lm75
      driver did not let the user take benefit of these improvements. Do it
      now.
      
      I decided to almost always configure the chip to use the best
      resolution possible, which also means the longest sample time. The
      only chips for which I didn't are the DS75, DS1775 and STDS75, because
      they are really too slow in 12-bit mode (1.2 to 1.5 second worst case)
      so I went for 11-bit mode as a more reasonable tradeoff. This choice is
      dictated by the fact that the hwmon subsystem is meant for system
      monitoring, it has never been supposed to be ultra-fast, and as a
      matter of fact we do cache the sampled values in almost all drivers.
      
      If anyone isn't pleased with these default settings, they can always
      introduce a platform data structure or DT support for the lm75. That
      being said, it seems nobody ever complained that the driver wouldn't
      refresh the value faster than every 1.5 second, and the change made
      it faster for all chips even in 12-bit mode, so I don't expect any
      complaint.
      
      Signed-off-by: default avatarJean Delvare <khali@linux-fr.org>
      Acked-by: default avatarGuenter Roeck <linux@roeck-us.net>
      0cd2c72d
    • Jean Delvare's avatar
      hwmon: (lm75) Prepare to support per-chip resolution and sample time · 87d0621a
      Jean Delvare authored
      
      
      Prepare the lm75 driver to support per-chip resolution and sample
      time. For now we only make the code generic enough to support it, but
      we still use the same, unchanged resolution (9-bit) and sample time
      (1.5 s) for all chips.
      
      Signed-off-by: default avatarJean Delvare <khali@linux-fr.org>
      Acked-by: default avatarGuenter Roeck <linux@roeck-us.net>
      87d0621a
    • Jean Delvare's avatar
      hwmon: (lm75) Per-chip configuration register initialization · 8a5c5cc6
      Jean Delvare authored
      
      
      There is no standard for the configuration register bits of LM75-like
      chips. We shouldn't blindly clear bits setting the resolution as they
      are either unused or used for something else on some of the supported
      chips.
      
      So, switch to per-chip configuration initialization. This will allow
      for better tuning later, for example using more resolution bits when
      available.
      
      Signed-off-by: default avatarJean Delvare <khali@linux-fr.org>
      Acked-by: default avatarGuenter Roeck <linux@roeck-us.net>
      8a5c5cc6
    • Linus Torvalds's avatar
      Merge branch 'for-3.10' of git://linux-nfs.org/~bfields/linux · 1db77221
      Linus Torvalds authored
      Pull nfsd changes from J Bruce Fields:
       "Highlights include:
      
         - Some more DRC cleanup and performance work from Jeff Layton
      
         - A gss-proxy upcall from Simo Sorce: currently krb5 mounts to the
           server using credentials from Active Directory often fail due to
           limitations of the svcgssd upcall interface.  This replacement
           lifts those limitations.  The existing upcall is still supported
           for backwards compatibility.
      
         - More NFSv4.1 support: at this point, if a user with a current
           client who upgrades from 4.0 to 4.1 should see no regressions.  In
           theory we do everything a 4.1 server is required to do.  Patches
           for a couple minor exceptions are ready for 3.11, and with those
           and some more testing I'd like to turn 4.1 on by default in 3.11."
      
      Fix up semantic conflict as per Stephen Rothwell and linux-next:
      
      Commit 030d794b ("SUNRPC: Use gssproxy upcall for server RPCGSS
      authentication") adds two new users of "PDE(inode)->data", but we're
      supposed to use "PDE_DATA(inode)" instead since commit d9dda78b
      ("procfs: new helper - PDE_DATA(inode)").
      
      The old PDE() macro is no longer available since commit c30480b9
      ("proc: Make the PROC_I() and PDE() macros internal to procfs")
      
      * 'for-3.10' of git://linux-nfs.org/~bfields/linux: (60 commits)
        NFSD: SECINFO doesn't handle unsupported pseudoflavors correctly
        NFSD: Simplify GSS flavor encoding in nfsd4_do_encode_secinfo()
        nfsd: make symbol nfsd_reply_cache_shrinker static
        svcauth_gss: fix error return code in rsc_parse()
        nfsd4: don't remap EISDIR errors in rename
        svcrpc: fix gss-proxy to respect user namespaces
        SUNRPC: gssp_procedures[] can be static
        SUNRPC: define {create,destroy}_use_gss_proxy_proc_entry in !PROC case
        nfsd4: better error return to indicate SSV non-support
        nfsd: fix EXDEV checking in rename
        SUNRPC: Use gssproxy upcall for server RPCGSS authentication.
        SUNRPC: Add RPC based upcall mechanism for RPCGSS auth
        SUNRPC: conditionally return endtime from import_sec_context
        SUNRPC: allow disabling idle timeout
        SUNRPC: attempt AF_LOCAL connect on setup
        nfsd: Decode and send 64bit time values
        nfsd4: put_client_renew_locked can be static
        nfsd4: remove unused macro
        nfsd4: remove some useless code
        nfsd4: implement SEQ4_STATUS_RECALLABLE_STATE_REVOKED
        ...
      1db77221