25 Oct, 2010

1 commit

  • The functions the functions amd_ec_wait_write and amd_ec_wait_read have an
    unsigned return type, but return a negative constant to indicate an error
    condition.

    A sematic match that finds this problem is as follows:
    (http://coccinelle.lip6.fr/)

    //
    @exists@
    identifier f;
    constant C;
    @@

    unsigned f(...)
    { }
    //

    Fixing amd_ec_wait_write and amd_ec_wait_read leads to the need to adjust
    the return type of the functions amd_ec_write and amd_ec_read, which are
    the only functions that call amd_ec_wait_write and amd_ec_wait_read.
    amd_ec_write and amd_ec_read, in turn, are only called from within the
    function amd8111_access, which already returns a signed typed value. Each
    of the calls to amd_ec_write and amd_ec_read are updated using the
    following semantic patch:

    //
    @@
    @@

    + status = amd_ec_write
    - amd_ec_write
    (...);
    + if (status) return status;

    @@
    @@

    + status = amd_ec_read
    - amd_ec_read
    (...);
    + if (status) return status;
    //

    The patch also adds the declaration of the status variable.

    Signed-off-by: Julia Lawall
    Signed-off-by: Jean Delvare

    Julia Lawall
     

22 May, 2010

1 commit


30 Mar, 2010

1 commit

  • …it slab.h inclusion from percpu.h

    percpu.h is included by sched.h and module.h and thus ends up being
    included when building most .c files. percpu.h includes slab.h which
    in turn includes gfp.h making everything defined by the two files
    universally available and complicating inclusion dependencies.

    percpu.h -> slab.h dependency is about to be removed. Prepare for
    this change by updating users of gfp and slab facilities include those
    headers directly instead of assuming availability. As this conversion
    needs to touch large number of source files, the following script is
    used as the basis of conversion.

    http://userweb.kernel.org/~tj/misc/slabh-sweep.py

    The script does the followings.

    * Scan files for gfp and slab usages and update includes such that
    only the necessary includes are there. ie. if only gfp is used,
    gfp.h, if slab is used, slab.h.

    * When the script inserts a new include, it looks at the include
    blocks and try to put the new include such that its order conforms
    to its surrounding. It's put in the include block which contains
    core kernel includes, in the same order that the rest are ordered -
    alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
    doesn't seem to be any matching order.

    * If the script can't find a place to put a new include (mostly
    because the file doesn't have fitting include block), it prints out
    an error message indicating which .h file needs to be added to the
    file.

    The conversion was done in the following steps.

    1. The initial automatic conversion of all .c files updated slightly
    over 4000 files, deleting around 700 includes and adding ~480 gfp.h
    and ~3000 slab.h inclusions. The script emitted errors for ~400
    files.

    2. Each error was manually checked. Some didn't need the inclusion,
    some needed manual addition while adding it to implementation .h or
    embedding .c file was more appropriate for others. This step added
    inclusions to around 150 files.

    3. The script was run again and the output was compared to the edits
    from #2 to make sure no file was left behind.

    4. Several build tests were done and a couple of problems were fixed.
    e.g. lib/decompress_*.c used malloc/free() wrappers around slab
    APIs requiring slab.h to be added manually.

    5. The script was run on all .h files but without automatically
    editing them as sprinkling gfp.h and slab.h inclusions around .h
    files could easily lead to inclusion dependency hell. Most gfp.h
    inclusion directives were ignored as stuff from gfp.h was usually
    wildly available and often used in preprocessor macros. Each
    slab.h inclusion directive was examined and added manually as
    necessary.

    6. percpu.h was updated not to include slab.h.

    7. Build test were done on the following configurations and failures
    were fixed. CONFIG_GCOV_KERNEL was turned off for all tests (as my
    distributed build env didn't work with gcov compiles) and a few
    more options had to be turned off depending on archs to make things
    build (like ipr on powerpc/64 which failed due to missing writeq).

    * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
    * powerpc and powerpc64 SMP allmodconfig
    * sparc and sparc64 SMP allmodconfig
    * ia64 SMP allmodconfig
    * s390 SMP allmodconfig
    * alpha SMP allmodconfig
    * um on x86_64 SMP allmodconfig

    8. percpu.h modifications were reverted so that it could be applied as
    a separate patch and serve as bisection point.

    Given the fact that I had only a couple of failures from tests on step
    6, I'm fairly confident about the coverage of this conversion patch.
    If there is a breakage, it's likely to be something in one of the arch
    headers which should be easily discoverable easily on most builds of
    the specific arch.

    Signed-off-by: Tejun Heo <tj@kernel.org>
    Guess-its-ok-by: Christoph Lameter <cl@linux-foundation.org>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>

    Tejun Heo
     

02 Mar, 2010

1 commit

  • The id_table field of the struct pci_driver is constant in
    so it is worth to make initialization data also constant.

    The semantic match that finds this kind of pattern is as follows:
    (http://coccinelle.lip6.fr/)

    //
    @r@
    disable decl_init,const_decl_init;
    identifier I1, I2, x;
    @@
    struct I1 {
    ...
    const struct I2 *x;
    ...
    };
    @s@
    identifier r.I1, y;
    identifier r.x, E;
    @@
    struct I1 y = {
    .x = E,
    };
    @c@
    identifier r.I2;
    identifier s.E;
    @@
    const struct I2 E[] = ... ;
    @depends on !c@
    identifier r.I2;
    identifier s.E;
    @@
    + const
    struct I2 E[] = ...;
    //

    Signed-off-by: Márton Németh
    Cc: Julia Lawall
    Signed-off-by: Jean Delvare

    Márton Németh
     

05 Oct, 2009

1 commit

  • When an ACPI resource conflict is detected, error messages are already
    printed by ACPI. There's no point in causing the driver core to print
    more error messages, so return one of the error codes for which no
    message is printed.

    This fixes bug #14293:
    http://bugzilla.kernel.org/show_bug.cgi?id=14293

    Signed-off-by: Jean Delvare

    Jean Delvare
     

25 Feb, 2009

1 commit

  • With a postfix decrement these timeouts reach -1 rather than 0, but
    after the loop it is tested whether they have become 0.

    As pointed out by Jean Delvare, the condition we are waiting for should
    also be tested before the timeout. With the current order, you could
    exit with a timeout error while the job is actually done.

    Signed-off-by: Roel Kluin
    Signed-off-by: Jean Delvare

    Roel Kluin
     

27 Jan, 2009

1 commit


15 Jul, 2008

3 commits

  • Check for ACPI resource conflicts in i2c bus drivers. I've included
    all recent SMBus master drivers for PC hardware.

    I've voluntarily left out:
    * Drivers that don't run on PCs: they can't conflict with ACPI.
    * Bit-banged bus device drivers: it's very unlikely that ACPI would
    deal with such buses.

    Signed-off-by: Jean Delvare

    Jean Delvare
     
  • Let general purpose I2C/SMBus bus drivers add SPD to their class. Once
    this is done, we will be able to tell the eeprom driver to only probe
    for SPD EEPROMs and similar on these buses.

    Note that I took a conservative approach here, adding I2C_CLASS_SPD to
    many drivers that have no idea whether they can host SPD EEPROMs or not.
    This is to make sure that the eeprom driver doesn't stop probing buses
    where SPD EEPROMs or equivalent live.

    So, bus driver maintainers and users should feel free to remove the SPD
    class from drivers those buses never have SPD EEPROMs or they don't
    want the eeprom driver to bind to them. Likewise, feel free to add the
    SPD class to any bus driver I might have missed.

    Signed-off-by: Jean Delvare

    Jean Delvare
     
  • Tighten error paths used by various i2c adapters (mostly x86) so
    they return real fault/errno codes instead of a "-1" (which is
    most often interpreted as "-EPERM"). Build tested, with eyeball
    review.

    One minor initial goal is to have adapters consistently return
    the code "-ENXIO" when addressing a device doesn't get an ACK
    response, at least in the probe paths where they are already
    good at stifling related logspam.

    Signed-off-by: David Brownell
    Signed-off-by: Jean Delvare

    David Brownell
     

14 Oct, 2007

1 commit

  • Rename I2C_FUNC_SMBUS_HWPEC_CALC as I2C_FUNC_SMBUS_PEC, and list that
    functionality as always available through the software implementation.
    Update documentation accordingly (and list similar requirements).

    The way it's currently packaged doesn't present the capability in a
    useful way.

    Signed-off-by: David Brownell
    Signed-off-by: Jean Delvare

    David Brownell
     

02 May, 2007

1 commit

  • This shrinks the size of "struct i2c_client" by 40 bytes:

    - Substantially shrinks the string used to identify the chip type
    - The "flags" don't need to be so big
    - Removes some internal padding

    It also adds kerneldoc for that struct, explaining how "name" is really a
    chip type identifier; it's otherwise potentially confusing.

    Because the I2C_NAME_SIZE symbol was abused for both i2c_client.name
    and for i2c_adapter.name, this needed to affect i2c_adapter too. The
    adapters which used that symbol now use the more-obviously-correct
    idiom of taking the size of that field.

    JD: Shorten i2c_adapter.name from 50 to 48 bytes while we're here, to
    avoid wasting space in padding.

    Signed-off-by: David Brownell
    Signed-off-by: Jean Delvare

    David Brownell
     

23 Mar, 2007

1 commit


18 Feb, 2007

1 commit


15 Feb, 2007

1 commit

  • After Al Viro (finally) succeeded in removing the sched.h #include in module.h
    recently, it makes sense again to remove other superfluous sched.h includes.
    There are quite a lot of files which include it but don't actually need
    anything defined in there. Presumably these includes were once needed for
    macros that used to live in sched.h, but moved to other header files in the
    course of cleaning it up.

    To ease the pain, this time I did not fiddle with any header files and only
    removed #includes from .c-files, which tend to cause less trouble.

    Compile tested against 2.6.20-rc2 and 2.6.20-rc2-mm2 (with offsets) on alpha,
    arm, i386, ia64, mips, powerpc, and x86_64 with allnoconfig, defconfig,
    allmodconfig, and allyesconfig as well as a few randconfigs on x86_64 and all
    configs in arch/arm/configs on arm. I also checked that no new warnings were
    introduced by the patch (actually, some warnings are removed that were emitted
    by unnecessarily included header files).

    Signed-off-by: Tim Schmielau
    Acked-by: Russell King
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Tim Schmielau
     

14 Feb, 2007

2 commits

  • Proposed cleanups to the i2c-amd8111 SMBus driver:
    * Fold long lines.
    * Add an explicit mask when writing the low byte of a word.
    * Use I2C_SMBUS_BLOCK_MAX instead of hardcoding 32.
    * Discard extra blank lines.
    * Use boolean not instead of bitwise not for bit tests, it's clearer.
    * Return -EBUSY rather than -1 on I/O resource conflict.
    * Fix a race on device registration, initialization should be done
    before the bus is registered.

    Signed-off-by: Jean Delvare

    Jean Delvare
     
  • IDs have been defined but not used by most of the I2C adapters.
    By having a unique ID, clients can check for correct connection
    during probe.

    Signed-off-by: Stephen Hemminger
    Signed-off-by: Jean Delvare

    Stephen Hemminger
     

27 Sep, 2006

1 commit


11 Nov, 2005

1 commit


29 Oct, 2005

5 commits

  • The new SMBus PEC implementation doesn't support PEC emulation on
    non-PEC non-I2C SMBus masters, so we can drop all related code.

    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Jean Delvare
     
  • Use kzalloc instead of kmalloc+memset in all remaining i2c bus and
    chip drivers.

    Signed-off-by: Deepak Saxena
    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Deepak Saxena
     
  • This patch updates .owner field for various struct pci_driver variables.

    Signed-off-by: Laurent Riffard
    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Laurent Riffard
     
  • I noticed a useless instruction in the i2c-amd8111 driver.

    Signed-off-by: Jean Delvare
    CC: Vojtech Pavlik
    Signed-off-by: Greg Kroah-Hartman

    drivers/i2c/busses/i2c-amd8111.c | 1 -
    1 file changed, 1 deletion(-)

    Jean Delvare
     
  • Clean up name string usage in 12 i2c bus drivers:
    * Use the i2c_adapter name for requesting the I/O region rather than
    redefining a new string.
    * Do not initialize the i2c_adapter name to "unset".
    This should save a few data bytes here and there.

    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    drivers/i2c/busses/i2c-ali1535.c | 6 +++---
    drivers/i2c/busses/i2c-ali1563.c | 6 ++++--
    drivers/i2c/busses/i2c-ali15x3.c | 5 +++--
    drivers/i2c/busses/i2c-amd756.c | 5 ++---
    drivers/i2c/busses/i2c-amd8111.c | 4 +++-
    drivers/i2c/busses/i2c-i801.c | 4 ++--
    drivers/i2c/busses/i2c-nforce2.c | 4 ++--
    drivers/i2c/busses/i2c-piix4.c | 4 ++--
    drivers/i2c/busses/i2c-sis5595.c | 5 +++--
    drivers/i2c/busses/i2c-sis630.c | 6 ++++--
    drivers/i2c/busses/i2c-sis96x.c | 5 +++--
    drivers/i2c/busses/i2c-via.c | 4 ++--
    12 files changed, 33 insertions(+), 25 deletions(-)

    Jean Delvare
     

06 Sep, 2005

2 commits


22 Jun, 2005

1 commit


17 Apr, 2005

1 commit

  • Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds