Eric Lee / smarc-fsl-linux-kernel

11 Nov, 2017

2 commits

  • 863dbc52e   staging: greybus: Remove redundant license text ... Browse Code »

    Now that the SPDX tag is in all greybus files, that identifies the
    license in a specific and legally-defined manner. So the extra GPL text
    wording can be removed as it is no longer needed at all.

    This is done on a quest to remove the 700+ different ways that files in
    the kernel describe the GPL license text. And there's unneeded stuff
    like the address (sometimes incorrect) for the FSF which is never
    needed.

    No copyright headers or other non-license-description text was removed.

    Cc: Vaibhav Hiremath
    Reviewed-by: Alex Elder
    Acked-by: Vaibhav Agarwal
    Acked-by: David Lin
    Acked-by: Johan Hovold
    Acked-by: Viresh Kumar
    Acked-by: Mark Greer
    Acked-by: Rui Miguel Silva
    Acked-by: "Bryan O'Donoghue"
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     
  • eb50fd3a2   staging: greybus: add SPDX identifiers to all greybus driver files ... Browse Code »

    It's good to have SPDX identifiers in all files to make it easier to
    audit the kernel tree for correct licenses.

    Update the drivers/staging/greybus files files with the correct SPDX
    license identifier based on the license text in the file itself. The
    SPDX identifier is a legally binding shorthand, which can be used
    instead of the full boiler plate text.

    This work is based on a script and data from Thomas Gleixner, Philippe
    Ombredanne, and Kate Stewart.

    Cc: Vaibhav Hiremath
    Cc: "Bryan O'Donoghue"
    Cc: Thomas Gleixner
    Cc: Kate Stewart
    Cc: Philippe Ombredanne
    Acked-by: Vaibhav Agarwal
    Acked-by: David Lin
    Reviewed-by: Alex Elder
    Acked-by: Johan Hovold
    Acked-by: Viresh Kumar
    Acked-by: Mark Greer
    Acked-by: Rui Miguel Silva
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     

21 Aug, 2017

1 commit

12 Feb, 2017

1 commit

19 Sep, 2016

1 commit

18 Aug, 2016

1 commit

  • 0900845ab   greybus: Add workqueue to handle vibrator timeout ... Browse Code »

    In the beginning, module side can control the vibrator timeout value,
    it can disable vibrator until timeout. But after Runtime PM control added
    in, AP side didn't know when module can be suspended, the vibrator
    task will be interrupted by suspending event.

    Because of this problem, the module can not be in charge of counting down
    the timeout value, it is now up to the AP to manage this. So add workqueue
    to handle the vibrator timeout.

    Signed-off-by: Ann Chen
    Reviewed-by: Viresh Kumar
    Signed-off-by: Greg Kroah-Hartman

    Ann Chen
     

23 Jul, 2016

1 commit

  • 633e45eaa   greybus: vibrator: integrate runtime pm ... Browse Code »

    Integrate greybus drivers with the Linux Kernel RuntimePM framework
    for vibrator driver.

    Testing Done: AP side (kernel) can control the vibrator driver with
    suspend and resume.

    Signed-off-by: Ann Chen
    Reviewed-by: David Lin
    Reviewed-by: Viresh Kumar
    Signed-off-by: Greg Kroah-Hartman

    Ann Chen
     

01 Jun, 2016

1 commit

23 Mar, 2016

1 commit

22 Jan, 2016

1 commit

16 Oct, 2015

1 commit

15 Oct, 2015

1 commit

15 Sep, 2015

1 commit

12 Aug, 2015

1 commit

11 Aug, 2015

1 commit

09 Jul, 2015

1 commit

15 May, 2015

1 commit

08 May, 2015

1 commit

  • 6d653370c   greybus: eliminate extra response flag definitions ... Browse Code »

    All protocols use the same value to distinguish between request and
    response message types. This is a requirement.

    Use GB_MESSAGE_TYPE_RESPONSE rather than GB_OPERATION_TYPE_RESPONSE
    for the name of the flag used to distiguish between request and
    response messages.

    Get rid of the redundant response flag definitions that are
    associated with specific protocols.

    Describe the symbolic values as "operation types" rather than
    "message types" where they are defined. The message type for a
    request is the same as the operation type; the message type for a
    response is the operation type OR'd with GB_MESSAGE_TYPE_RESPONSE.

    Signed-off-by: Alex Elder
    Signed-off-by: Greg Kroah-Hartman

    Alex Elder
     

25 Mar, 2015

1 commit

18 Mar, 2015

1 commit

22 Jan, 2015

3 commits