From: bjorn.andersson@linaro.org (Bjorn Andersson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/3] interconnect: Add generic on-chip interconnect API
Date: Fri, 20 Oct 2017 15:34:53 -0700 [thread overview]
Message-ID: <20171020223452.GD1165@minitux> (raw)
In-Reply-To: <a7cf55ba-0475-d74c-f759-a24e58ccde47@linaro.org>
On Fri 20 Oct 07:43 PDT 2017, Georgi Djakov wrote:
> 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?
>
Sorry, I still haven't found the time to do a proper review of this yet.
> I am planning to change the prefix that is used for naming for example
> the functions from "interconnect_" to something shorter like icbus_.
>
This isn't implementing a bus; if you feel that just ic_ is too short I
would suggest naming things inter_. (But keep the full name in the file
names)
Regards,
Bjorn
next prev parent reply other threads:[~2017-10-20 22:34 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
2017-10-20 22:34 ` Bjorn Andersson [this message]
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=20171020223452.GD1165@minitux \
--to=bjorn.andersson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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