Eric Lee / smarc-fsl-linux-kernel

05 Oct, 2009

1 commit

  • 0314b020c   ds2482: Discard obsolete detect method ... Browse Code »

    There is no point in implementing a detect callback for the DS2482, as
    this device can't be detected. It was there solely to handle "force"
    module parameters to instantiate devices, but now we have a better sysfs
    interface that can do the same.

    So we can get rid of the ugly module parameters and the detect callback.
    This shrinks the binary module size by 21%.

    Signed-off-by: Jean Delvare
    Acked-by: Ben Gardner

    Jean Delvare
     

09 Jan, 2009

4 commits

13 Nov, 2008

1 commit

17 Oct, 2008

3 commits

07 Feb, 2008

1 commit

  • ad8dc96e3   w1-gpio: add GPIO w1 bus master driver ... Browse Code »

    Add a GPIO 1-wire bus master driver. The driver used the GPIO API to
    control the wire and the GPIO pin can be specified using platform data
    similar to i2c-gpio. The driver was tested with AT91SAM9260 + DS2401.

    Signed-off-by: Ville Syrjala
    Cc: Evgeniy Polyakov
    Cc: David Brownell
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Ville Syrjala
     

17 Oct, 2007

1 commit

23 Jun, 2006

3 commits

  • 12003375a   [PATCH] w1: Userspace communication protocol over connector. ... Browse Code »

    There are three types of messages between w1 core and userspace:
    1. Events. They are generated each time new master or slave device found
    either due to automatic or requested search.
    2. Userspace commands. Includes read/write and search/alarm search comamnds.
    3. Replies to userspace commands.

    From: Evgeniy Polyakov
    Signed-off-by: Greg Kroah-Hartman

    Evgeniy Polyakov
     
  • 81f6075eb   [PATCH] w1: Replace dscore and ds_w1_bridge with ds2490 driver. Browse Code »
    Evgeniy Polyakov
     
  • f522d2396   [PATCH] w1: Added default generic read/write operations. ... Browse Code »

    Special file in each w1 slave device's directory called "rw" is created
    each time new slave and no appropriate w1 family is registered.
    "rw" file supports read and write operations, which allows to perform
    almost any kind of operations. Each logical operation is a transaction
    in nature, which can contain several (two or one) low-level operations.
    Let's see how one can read EEPROM context:
    1. one must write control buffer, i.e. buffer containing command byte
    and two byte address. At this step bus is reset and appropriate device
    is selected using either W1_SKIP_ROM or W1_MATCH_ROM command.
    Then provided control buffer is being written to the wire.
    2. reading. This will issue reading eeprom response.

    It is possible that between 1. and 2. w1 master thread will reset bus for
    searching and slave device will be even removed, but in this case 0xff will
    be read, since no device was selected.

    Signed-off-by: Evgeniy Polyakov
    Signed-off-by: Greg Kroah-Hartman

    Evgeniy Polyakov
     

24 Mar, 2006

1 commit

22 Jun, 2005

1 commit

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

    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