All of lore.kernel.org
 help / color / mirror / Atom feed
From: Georgi Djakov <georgi.djakov@linaro.org>
To: Alexandre Bailon <abailon@baylibre.com>
Cc: linux-pm@vger.kernel.org, gregkh@linuxfoundation.org,
	mark.rutland@arm.com, lorenzo.pieralisi@arm.com,
	skannan@codeaurora.org, seansw@qti.qualcomm.com,
	khilman@baylibre.com, mturquette@baylibre.com, rjw@rjwysocki.net,
	linux-kernel@vger.kernel.org, amit.kucheria@linaro.org,
	bjorn.andersson@linaro.org, robh+dt@kernel.org,
	linux-arm-msm@vger.kernel.org, davidai@quicinc.com,
	vincent.guittot@linaro.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/7] interconnect: Add generic on-chip interconnect API
Date: Sat, 9 Jun 2018 22:15:41 +0300	[thread overview]
Message-ID: <625a529a-ae01-8615-e89b-409a20596806@linaro.org> (raw)
In-Reply-To: <ffd493a7-8c01-3f6b-074f-b4b67707dc83@baylibre.com>

Hi Alexandre,

On 8.06.18 г. 18:57, Alexandre Bailon wrote:
> On 03/09/2018 10:09 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 |  96 ++++++
>>  drivers/Kconfig                             |   2 +
>>  drivers/Makefile                            |   1 +
>>  drivers/interconnect/Kconfig                |  10 +
>>  drivers/interconnect/Makefile               |   1 +
>>  drivers/interconnect/core.c                 | 489 ++++++++++++++++++++++++++++
>>  include/linux/interconnect-provider.h       | 109 +++++++
>>  include/linux/interconnect.h                |  40 +++
>>  8 files changed, 748 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/core.c
>>  create mode 100644 include/linux/interconnect-provider.h
>>  create mode 100644 include/linux/interconnect.h
>>

[..]

>> +
>> +/**
>> + * icc_link_create() - create a link between two nodes
>> + * @src_id: source node id
> I guess src_id has become node and is not an id anymore,
> so it should be updated.

Yes, absolutely!

>> + * @dst_id: destination node id
>> + *
>> + * Return: 0 on success, or an error code otherwise
>> + */
>> +int icc_link_create(struct icc_node *node, const int dst_id)
>> +{

Thanks,
Georgi

WARNING: multiple messages have this Message-ID (diff)
From: georgi.djakov@linaro.org (Georgi Djakov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/7] interconnect: Add generic on-chip interconnect API
Date: Sat, 9 Jun 2018 22:15:41 +0300	[thread overview]
Message-ID: <625a529a-ae01-8615-e89b-409a20596806@linaro.org> (raw)
In-Reply-To: <ffd493a7-8c01-3f6b-074f-b4b67707dc83@baylibre.com>

Hi Alexandre,

On 8.06.18 ?. 18:57, Alexandre Bailon wrote:
> On 03/09/2018 10:09 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 |  96 ++++++
>>  drivers/Kconfig                             |   2 +
>>  drivers/Makefile                            |   1 +
>>  drivers/interconnect/Kconfig                |  10 +
>>  drivers/interconnect/Makefile               |   1 +
>>  drivers/interconnect/core.c                 | 489 ++++++++++++++++++++++++++++
>>  include/linux/interconnect-provider.h       | 109 +++++++
>>  include/linux/interconnect.h                |  40 +++
>>  8 files changed, 748 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/core.c
>>  create mode 100644 include/linux/interconnect-provider.h
>>  create mode 100644 include/linux/interconnect.h
>>

[..]

>> +
>> +/**
>> + * icc_link_create() - create a link between two nodes
>> + * @src_id: source node id
> I guess src_id has become node and is not an id anymore,
> so it should be updated.

Yes, absolutely!

>> + * @dst_id: destination node id
>> + *
>> + * Return: 0 on success, or an error code otherwise
>> + */
>> +int icc_link_create(struct icc_node *node, const int dst_id)
>> +{

Thanks,
Georgi

  reply	other threads:[~2018-06-09 19:15 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09 21:09 [PATCH v4 0/7] Introduce on-chip interconnect API Georgi Djakov
2018-03-09 21:09 ` Georgi Djakov
2018-03-09 21:09 ` [PATCH v4 1/7] interconnect: Add generic " Georgi Djakov
2018-03-09 21:09   ` Georgi Djakov
2018-03-09 21:09   ` Georgi Djakov
2018-04-06 17:38   ` Matthias Kaehlcke
2018-04-06 17:38     ` Matthias Kaehlcke
2018-04-12 13:06     ` Georgi Djakov
2018-04-12 13:06       ` Georgi Djakov
2018-05-11 21:30   ` Evan Green
2018-05-11 21:30     ` Evan Green
2018-06-06 14:59     ` Georgi Djakov
2018-06-06 14:59       ` Georgi Djakov
2018-06-06 18:09       ` Georgi Djakov
2018-06-06 18:09         ` Georgi Djakov
2018-06-07  1:06         ` Evan Green
2018-06-07  1:06           ` Evan Green
2018-06-07  1:06           ` Evan Green
2018-05-25  8:26   ` Amit Kucheria
2018-05-25  8:26     ` Amit Kucheria
2018-06-06 15:08     ` Georgi Djakov
2018-06-06 15:08       ` Georgi Djakov
2018-06-08 15:57   ` Alexandre Bailon
2018-06-08 15:57     ` Alexandre Bailon
2018-06-09 19:15     ` Georgi Djakov [this message]
2018-06-09 19:15       ` Georgi Djakov
2018-03-09 21:09 ` [PATCH v4 2/7] dt-bindings: Introduce interconnect provider bindings Georgi Djakov
2018-03-09 21:09   ` Georgi Djakov
2018-03-18 22:50   ` Bjorn Andersson
2018-03-18 22:50     ` Bjorn Andersson
2018-03-19  9:34     ` Georgi Djakov
2018-03-19  9:34       ` Georgi Djakov
2018-04-12 13:15   ` Neil Armstrong
2018-04-12 13:15     ` Neil Armstrong
2018-06-06 15:23     ` Georgi Djakov
2018-06-06 15:23       ` Georgi Djakov
2018-03-09 21:09 ` [PATCH v4 3/7] interconnect: Add debugfs support Georgi Djakov
2018-03-09 21:09   ` Georgi Djakov
2018-03-09 21:09 ` [PATCH v4 4/7] interconnect: qcom: Add RPM communication Georgi Djakov
2018-03-09 21:09   ` Georgi Djakov
2018-05-11 21:30   ` Evan Green
2018-05-11 21:30     ` Evan Green
2018-06-06 15:00     ` Georgi Djakov
2018-06-06 15:00       ` Georgi Djakov
2018-03-09 21:09 ` [PATCH v4 5/7] interconnect: qcom: Add msm8916 interconnect provider driver Georgi Djakov
2018-03-09 21:09   ` Georgi Djakov
2018-04-05 22:58   ` Matthias Kaehlcke
2018-04-05 22:58     ` Matthias Kaehlcke
2018-04-12 13:09     ` Georgi Djakov
2018-04-12 13:09       ` Georgi Djakov
2018-05-11 21:29   ` Evan Green
2018-05-11 21:29     ` Evan Green
2018-06-06 15:03     ` Georgi Djakov
2018-06-06 15:03       ` Georgi Djakov
2018-05-25  8:27   ` Amit Kucheria
2018-05-25  8:27     ` Amit Kucheria
2018-06-06 15:14     ` Georgi Djakov
2018-06-06 15:14       ` Georgi Djakov
2018-03-09 21:09 ` [PATCH v4 6/7] dt-bindings: Introduce interconnect consumers bindings Georgi Djakov
2018-03-09 21:09   ` Georgi Djakov
2018-03-18 22:49   ` Bjorn Andersson
2018-03-18 22:49     ` Bjorn Andersson
2018-03-19  9:41     ` Georgi Djakov
2018-03-19  9:41       ` Georgi Djakov
2018-03-09 21:09 ` [PATCH v4 7/7] interconnect: Allow endpoints translation via DT Georgi Djakov
2018-03-09 21:09   ` Georgi Djakov
2018-05-11 21:29   ` Evan Green
2018-05-11 21:29     ` 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=625a529a-ae01-8615-e89b-409a20596806@linaro.org \
    --to=georgi.djakov@linaro.org \
    --cc=abailon@baylibre.com \
    --cc=amit.kucheria@linaro.org \
    --cc=bjorn.andersson@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=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 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.