linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Georgi Djakov <georgi.djakov@linaro.org>
To: linux-pm@vger.kernel.org, gregkh@linuxfoundation.org
Cc: rjw@rjwysocki.net, robh+dt@kernel.org, khilman@baylibre.com,
	mturquette@baylibre.com, vincent.guittot@linaro.org,
	skannan@codeaurora.org, sboyd@codeaurora.org,
	andy.gross@linaro.org, seansw@qti.qualcomm.com,
	davidai@quicinc.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, mark.rutland@arm.com,
	lorenzo.pieralisi@arm.com
Subject: Re: [PATCH v3 1/3] interconnect: Add generic on-chip interconnect API
Date: Fri, 20 Oct 2017 17:43:02 +0300	[thread overview]
Message-ID: <a7cf55ba-0475-d74c-f759-a24e58ccde47@linaro.org> (raw)
In-Reply-To: <20170908171830.13813-2-georgi.djakov@linaro.org>

Hi,

On 09/08/2017 08:18 PM, Georgi Djakov wrote:
> This patch introduce a new API to get requirements and configure the
> interconnect buses across the entire chipset to fit with the current demand.
> 
> The API is using a consumer/provider-based model, where the providers are
> the interconnect buses and the consumers could be various drivers.
> The consumers request interconnect resources (path) between endpoints and
> set the desired constraints on this data flow path. The providers receive
> requests from consumers and aggregate these requests for all master-slave
> pairs on that path. Then the providers configure each participating in the
> topology node according to the requested data flow path, physical links and
> constraints. The topology could be complicated and multi-tiered and is SoC
> specific.
> 
> Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
> ---
>  Documentation/interconnect/interconnect.rst |  93 +++++++
>  drivers/Kconfig                             |   2 +
>  drivers/Makefile                            |   1 +
>  drivers/interconnect/Kconfig                |  10 +
>  drivers/interconnect/Makefile               |   1 +
>  drivers/interconnect/interconnect.c         | 382 ++++++++++++++++++++++++++++
>  include/linux/interconnect-consumer.h       |  73 ++++++
>  include/linux/interconnect-provider.h       | 119 +++++++++
>  8 files changed, 681 insertions(+)
>  create mode 100644 Documentation/interconnect/interconnect.rst
>  create mode 100644 drivers/interconnect/Kconfig
>  create mode 100644 drivers/interconnect/Makefile
>  create mode 100644 drivers/interconnect/interconnect.c
>  create mode 100644 include/linux/interconnect-consumer.h
>  create mode 100644 include/linux/interconnect-provider.h

Any comments on this patch?

I am planning to change the prefix that is used for naming for example
the functions from "interconnect_" to something shorter like icbus_.

Thanks,
Georgi

  reply	other threads:[~2017-10-20 14:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-08 17:18 [PATCH v3 0/3] Introduce on-chip interconnect API Georgi Djakov
2017-09-08 17:18 ` [PATCH v3 1/3] interconnect: Add generic " Georgi Djakov
2017-10-20 14:43   ` Georgi Djakov [this message]
2017-10-20 22:34     ` Bjorn Andersson
2017-10-23  2:58       ` Michael Turquette
2017-11-02  7:28   ` Amit Kucheria
2017-11-02 16:00     ` Georgi Djakov
2017-12-08 18:38   ` Amit Kucheria
2017-12-12 15:46     ` Georgi Djakov
2017-12-19 15:21   ` Rob Clark
2017-09-08 17:18 ` [RFC v3 2/3] interconnect: Add basic event tracing Georgi Djakov
2017-09-08 18:13   ` Steven Rostedt
2017-09-08 20:16     ` Georgi Djakov
2017-09-08 17:18 ` [PATCH v3 3/3] interconnect: Add Qualcomm msm8916 interconnect provider driver Georgi Djakov
2017-11-02  7:28   ` Amit Kucheria
2017-11-02 16:00     ` Georgi Djakov

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=a7cf55ba-0475-d74c-f759-a24e58ccde47@linaro.org \
    --to=georgi.djakov@linaro.org \
    --cc=andy.gross@linaro.org \
    --cc=davidai@quicinc.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=khilman@baylibre.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=lorenzo.pieralisi@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@baylibre.com \
    --cc=rjw@rjwysocki.net \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=seansw@qti.qualcomm.com \
    --cc=skannan@codeaurora.org \
    --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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).