Hi Evan, On 12.05.18 г. 0:30, Evan Green wrote: > On Fri, Mar 9, 2018 at 1:11 PM Georgi Djakov <georgi.djakov@xxxxxxxxxx> > wrote: > >> On some Qualcomm SoCs, there is a remote processor, which controls some of >> the Network-On-Chip interconnect resources. Other CPUs express their needs >> by communicating with this processor. Add a driver to handle comminication >> with this remote processor. > >> Signed-off-by: Georgi Djakov <georgi.djakov@xxxxxxxxxx> >> --- >> .../devicetree/bindings/interconnect/qcom-smd.txt | 31 ++++++++ >> drivers/interconnect/qcom/Makefile | 1 + >> drivers/interconnect/qcom/smd-rpm.c | 90 > ++++++++++++++++++++++ >> drivers/interconnect/qcom/smd-rpm.h | 15 ++++ >> 4 files changed, 137 insertions(+) >> create mode 100644 > Documentation/devicetree/bindings/interconnect/qcom-smd.txt >> create mode 100644 drivers/interconnect/qcom/Makefile >> create mode 100644 drivers/interconnect/qcom/smd-rpm.c >> create mode 100644 drivers/interconnect/qcom/smd-rpm.h > >> diff --git a/Documentation/devicetree/bindings/interconnect/qcom-smd.txt > b/Documentation/devicetree/bindings/interconnect/qcom-smd.txt >> new file mode 100644 >> index 000000000000..14e83ed7019b >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/interconnect/qcom-smd.txt >> @@ -0,0 +1,31 @@ >> +Qualcomm SMD-RPM interconnect driver binding >> +------------------------------------------------ >> +The RPM is a dedicated hardware engine for managing the shared >> +SoC resources in order to keep the lowest power profile. It >> +communicates with other hardware subsystems via shared memory >> +and accepts requests for various resources. > > You never say what RPM or SMD stands for. RPM is Resource Power Manager, > right? But I'm not in the know about SMD. Can you define these somewhere? > Sure, it's the Shared Memory Driver back-end used for communicating with RPM. Now added this explanation into the docs. Thanks, Georgi -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html