From: Georgi Djakov <georgi.djakov@linaro.org> To: linux-pm@vger.kernel.org Cc: daidavid1@codeaurora.org, vincent.guittot@linaro.org, bjorn.andersson@linaro.org, amit.kucheria@linaro.org, evgreen@chromium.org, dianders@chromium.org, seansw@qti.qualcomm.com, mturquette@baylibre.com, abailon@baylibre.com, thierry.reding@gmail.com, ksitaraman@nvidia.com, sanjayc@nvidia.com, henryc.chen@mediatek.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, georgi.djakov@linaro.org Subject: [PATCH v1 0/2] interconnect: Add path tagging support Date: Fri, 8 Feb 2019 19:21:50 +0200 [thread overview] Message-ID: <20190208172152.1807-1-georgi.djakov@linaro.org> (raw) SoCs that have multiple coexisting CPUs and DSPs, may have shared interconnect buses between them. In such cases, each CPU/DSP may have different bandwidth needs, depending on whether it is active or sleeping. This means that we have to keep different bandwidth configurations for the CPU (active/sleep). In such systems, usually there is a way to communicate and synchronize this information with some firmware or pass it to another processor responsible for monitoring and switching the interconnect configurations based on the state of each CPU/DSP. The above problem can be solved by introducing the path tagging concept, that allows consumers to optionally attach a tag to each path they use. This tag is used to differentiate between the aggregated bandwidth values for each state. The tag is generic and how it's handled is up to the platform specific interconnect provider drivers. David Dai (1): interconnect: qcom: Add tagging and wake/sleep support for sdm845 Georgi Djakov (1): interconnect: Add support for path tags drivers/interconnect/core.c | 27 ++++++- drivers/interconnect/qcom/sdm845.c | 103 +++++++++++++++++++------- include/linux/interconnect-provider.h | 4 +- include/linux/interconnect.h | 5 ++ 4 files changed, 106 insertions(+), 33 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Georgi Djakov <georgi.djakov@linaro.org> To: linux-pm@vger.kernel.org Cc: vincent.guittot@linaro.org, sanjayc@nvidia.com, seansw@qti.qualcomm.com, linux-kernel@vger.kernel.org, mturquette@baylibre.com, daidavid1@codeaurora.org, dianders@chromium.org, evgreen@chromium.org, bjorn.andersson@linaro.org, thierry.reding@gmail.com, henryc.chen@mediatek.com, amit.kucheria@linaro.org, linux-arm-msm@vger.kernel.org, ksitaraman@nvidia.com, georgi.djakov@linaro.org, linux-arm-kernel@lists.infradead.org, abailon@baylibre.com Subject: [PATCH v1 0/2] interconnect: Add path tagging support Date: Fri, 8 Feb 2019 19:21:50 +0200 [thread overview] Message-ID: <20190208172152.1807-1-georgi.djakov@linaro.org> (raw) SoCs that have multiple coexisting CPUs and DSPs, may have shared interconnect buses between them. In such cases, each CPU/DSP may have different bandwidth needs, depending on whether it is active or sleeping. This means that we have to keep different bandwidth configurations for the CPU (active/sleep). In such systems, usually there is a way to communicate and synchronize this information with some firmware or pass it to another processor responsible for monitoring and switching the interconnect configurations based on the state of each CPU/DSP. The above problem can be solved by introducing the path tagging concept, that allows consumers to optionally attach a tag to each path they use. This tag is used to differentiate between the aggregated bandwidth values for each state. The tag is generic and how it's handled is up to the platform specific interconnect provider drivers. David Dai (1): interconnect: qcom: Add tagging and wake/sleep support for sdm845 Georgi Djakov (1): interconnect: Add support for path tags drivers/interconnect/core.c | 27 ++++++- drivers/interconnect/qcom/sdm845.c | 103 +++++++++++++++++++------- include/linux/interconnect-provider.h | 4 +- include/linux/interconnect.h | 5 ++ 4 files changed, 106 insertions(+), 33 deletions(-) _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-02-08 17:21 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-02-08 17:21 Georgi Djakov [this message] 2019-02-08 17:21 ` [PATCH v1 0/2] interconnect: Add path tagging support Georgi Djakov 2019-02-08 17:21 ` [PATCH v1 1/2] interconnect: Add support for path tags Georgi Djakov 2019-02-08 17:21 ` Georgi Djakov 2019-03-08 18:40 ` Evan Green 2019-03-08 18:40 ` Evan Green 2019-03-20 17:10 ` Georgi Djakov 2019-03-20 17:10 ` Georgi Djakov 2019-02-08 17:21 ` [PATCH v1 2/2] interconnect: qcom: Add tagging and wake/sleep support for sdm845 Georgi Djakov 2019-02-08 17:21 ` Georgi Djakov 2019-03-08 18:35 ` Evan Green 2019-03-08 18:35 ` Evan Green 2019-03-14 1:00 ` David Dai 2019-03-14 1:00 ` David Dai 2019-03-14 16:35 ` Evan Green 2019-03-14 16:35 ` Evan Green
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20190208172152.1807-1-georgi.djakov@linaro.org \ --to=georgi.djakov@linaro.org \ --cc=abailon@baylibre.com \ --cc=amit.kucheria@linaro.org \ --cc=bjorn.andersson@linaro.org \ --cc=daidavid1@codeaurora.org \ --cc=dianders@chromium.org \ --cc=evgreen@chromium.org \ --cc=henryc.chen@mediatek.com \ --cc=ksitaraman@nvidia.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pm@vger.kernel.org \ --cc=mturquette@baylibre.com \ --cc=sanjayc@nvidia.com \ --cc=seansw@qti.qualcomm.com \ --cc=thierry.reding@gmail.com \ --cc=vincent.guittot@linaro.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.