linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation.org (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v2 1/3] interconnect: Add generic interconnect controller API
Date: Tue, 13 Jun 2017 15:42:00 +0200	[thread overview]
Message-ID: <20170613134200.GA4769@kroah.com> (raw)
In-Reply-To: <20170612141359.26117-2-georgi.djakov@linaro.org>

On Mon, Jun 12, 2017 at 05:13:57PM +0300, Georgi Djakov wrote:
> This patch introduce a new API to get the requirement 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 controllers and the consumers could be various drivers.
> The consumers request interconnect resources (path) to an endpoint and set
> the desired constraints on this data flow path. The provider(s) 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.txt |  65 +++++
>  drivers/Kconfig                             |   2 +
>  drivers/Makefile                            |   1 +
>  drivers/interconnect/Kconfig                |  10 +
>  drivers/interconnect/Makefile               |   1 +
>  drivers/interconnect/interconnect.c         | 376 ++++++++++++++++++++++++++++
>  include/linux/interconnect-consumer.h       |  72 ++++++
>  include/linux/interconnect-provider.h       | 120 +++++++++
>  8 files changed, 647 insertions(+)
>  create mode 100644 Documentation/interconnect/interconnect.txt
>  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
> 
> diff --git a/Documentation/interconnect/interconnect.txt b/Documentation/interconnect/interconnect.txt
> new file mode 100644
> index 000000000000..f761a2fb553c
> --- /dev/null
> +++ b/Documentation/interconnect/interconnect.txt

.rst for new Documenation files please, and hook it up to the larger
documentation build process at the same time.

And why are these RFC patches?  Don't you feel they are ready to be
reviewed?  I know I ignore RFC patches for the most part as obviously
the author does not think they are ready :)

thanks,

greg k-h

  reply	other threads:[~2017-06-13 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12 14:13 [RFC v2 0/3] Introduce on-chip interconnect API Georgi Djakov
2017-06-12 14:13 ` [RFC v2 1/3] interconnect: Add generic interconnect controller API Georgi Djakov
2017-06-13 13:42   ` Greg KH [this message]
2017-06-13 14:12     ` Georgi Djakov
2017-06-12 14:13 ` [RFC v2 2/3] interconnect: Add Qualcomm msm8916 interconnect provider driver Georgi Djakov
2017-06-12 14:13 ` [RFC v2 3/3] dt-binding: Interconnect device-tree bindings draft 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=20170613134200.GA4769@kroah.com \
    --to=gregkh@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).