Eric Lee / smarc-fsl-linux-kernel

09 Jul, 2020

1 commit

  • 5abfe5cf0   remoteproc: qcom: Add per subsystem SSR notification ... Browse Code »

    Currently there is a single notification chain which is called whenever any
    remoteproc shuts down. This leads to all the listeners being notified, and
    is not an optimal design as kernel drivers might only be interested in
    listening to notifications from a particular remoteproc. Create a global
    list of remoteproc notification info data structures. This will hold the
    name and notifier_list information for a particular remoteproc. The API
    to register for notifications will use name argument to retrieve the
    notification info data structure and the notifier block will be added to
    that data structure's notification chain. Also move from blocking notifier
    to srcu notifer based implementation to support dynamic notifier head
    creation.

    Reviewed-by: Alex Elder
    Co-developed-by: Siddharth Gupta
    Signed-off-by: Siddharth Gupta
    Signed-off-by: Rishabh Bhatnagar
    Link: https://lore.kernel.org/r/1592965408-16908-2-git-send-email-rishabhb@codeaurora.org
    Signed-off-by: Bjorn Andersson

    Rishabh Bhatnagar
     

08 May, 2020

1 commit

  • cd9fc8f1b   remoteproc: qcom: Pass ssr_name to glink subdevice ... Browse Code »

    Pass ssr_name to glink subdevice in preparation for tying glink_ssr to
    the glink subdevice, rather than having its own "ssr subdevice".

    Acked-by: Chris Lew
    Acked-by: Mathieu Poirier
    Acked-by: Rishabh Bhatnagar
    Link: https://lore.kernel.org/r/20200423003736.2027371-2-bjorn.andersson@linaro.org
    Signed-off-by: Bjorn Andersson

    Bjorn Andersson
     

13 Feb, 2018

2 commits

16 Jan, 2018

1 commit

02 Nov, 2017

1 commit

  • b24413180   License cleanup: add SPDX GPL-2.0 license identifier to files with no license ... Browse Code »

    Many source files in the tree are missing licensing information, which
    makes it harder for compliance tools to determine the correct license.

    By default all files without license information are under the default
    license of the kernel, which is GPL version 2.

    Update the files which contain no license information with the 'GPL-2.0'
    SPDX license identifier. The SPDX identifier is a legally binding
    shorthand, which can be used instead of the full boiler plate text.

    This patch is based on work done by Thomas Gleixner and Kate Stewart and
    Philippe Ombredanne.

    How this work was done:

    Patches were generated and checked against linux-4.14-rc6 for a subset of
    the use cases:
    - file had no licensing information it it.
    - file was a */uapi/* one with no licensing information in it,
    - file was a */uapi/* one with existing licensing information,

    Further patches will be generated in subsequent months to fix up cases
    where non-standard license headers were used, and references to license
    had to be inferred by heuristics based on keywords.

    The analysis to determine which SPDX License Identifier to be applied to
    a file was done in a spreadsheet of side by side results from of the
    output of two independent scanners (ScanCode & Windriver) producing SPDX
    tag:value files created by Philippe Ombredanne. Philippe prepared the
    base worksheet, and did an initial spot review of a few 1000 files.

    The 4.13 kernel was the starting point of the analysis with 60,537 files
    assessed. Kate Stewart did a file by file comparison of the scanner
    results in the spreadsheet to determine which SPDX license identifier(s)
    to be applied to the file. She confirmed any determination that was not
    immediately clear with lawyers working with the Linux Foundation.

    Criteria used to select files for SPDX license identifier tagging was:
    - Files considered eligible had to be source code files.
    - Make and config files were included as candidates if they contained >5
    lines of source
    - File already had some variant of a license header in it (even if
    Reviewed-by: Philippe Ombredanne
    Reviewed-by: Thomas Gleixner
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     

10 Sep, 2017

1 commit

  • 7151202b6   Merge tag 'rpmsg-v4.14' of git://github.com/andersson/remoteproc ... Browse Code »

    Pull rpmsg updates from Bjorn Andersson:
    "This extends the Qualcomm GLINK implementation to support the
    additional features used for communicating with modem and DSP
    coprocessors in modern Qualcomm platforms.

    In addition to this there's support for placing virtio RPMSG buffers
    in non-System RAM"

    * tag 'rpmsg-v4.14' of git://github.com/andersson/remoteproc: (29 commits)
    rpmsg: glink: initialize ret to zero to ensure error status check is correct
    rpmsg: glink: fix null pointer dereference on a null intent
    dt-bindings: soc: qcom: Extend GLINK to cover SMEM
    remoteproc: qcom: adsp: Allow defining GLINK edge
    rpmsg: glink: Export symbols from common code
    rpmsg: glink: Release idr lock before returning on error
    rpmsg: glink: Handle remote rx done command
    rpmsg: glink: Request for intents when unavailable
    rpmsg: glink: Use the intents passed by remote
    rpmsg: glink: Receive and store the remote intent buffers
    rpmsg: glink: Add announce_create ops and preallocate intents
    rpmsg: glink: Add rx done command
    rpmsg: glink: Make RX FIFO peak accessor to take an offset
    rpmsg: glink: Use the local intents when receiving data
    rpmsg: glink: Add support for TX intents
    rpmsg: glink: Fix idr_lock from mutex to spinlock
    rpmsg: glink: Add support for transport version negotiation
    rpmsg: glink: Introduce glink smem based transport
    rpmsg: glink: Do a mbox_free_channel in remove
    rpmsg: glink: Return -EAGAIN when there is no FIFO space
    ...

    Linus Torvalds
     

02 Sep, 2017

1 commit

03 Aug, 2017

1 commit

  • 1e140df04   remoteproc: qcom: Add support for SSR notifications ... Browse Code »

    This adds the remoteproc part of subsystem restart, which is responsible
    for emitting notifications to other processors in the system about a
    dying remoteproc instance.

    These notifications are propagated to the various communication systems
    in the various remote processors to shut down communication links that
    was left in a dangling state as the remoteproc was stopped (or crashed).

    Signed-off-by: Bjorn Andersson

    Bjorn Andersson
     

07 Feb, 2017

2 commits