devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Georgi Djakov <georgi.djakov@linaro.org>,
	linux-pm@vger.kernel.org, rjw@rjwysocki.net, robh+dt@kernel.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	vincent.guittot@linaro.org, seansw@qti.qualcomm.com,
	gregkh@linuxfoundation.org, mturquette@baylibre.com,
	sboyd@codeaurora.org, linux-kernel@vger.kernel.org,
	davidai@quicinc.com, skannan@codeaurora.org,
	khilman@baylibre.com, andy.gross@linaro.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC v0 1/2] interconnect: Add generic interconnect controller API
Date: Thu, 2 Mar 2017 15:53:35 -0800	[thread overview]
Message-ID: <15929d7a-65e5-f8ba-2fac-0381c5f8e8fc@infradead.org> (raw)
In-Reply-To: <20170301182235.19154-2-georgi.djakov@linaro.org>

On 03/01/17 10:22, Georgi Djakov wrote:
> 
> diff --git a/drivers/interconnect/Kconfig b/drivers/interconnect/Kconfig
> new file mode 100644
> index 000000000000..103524b59905
> --- /dev/null
> +++ b/drivers/interconnect/Kconfig
> @@ -0,0 +1,10 @@
> +menuconfig INTERCONNECT
> +	bool "On-Chip Interconnect management support"

Why isn't this symbol tristate instead of bool so that the
interconnect management support can be built as a loadable module?


> +	help
> +	  Support for management of the on-chip interconnects.
> +
> +	  This framework is designed to provide a generic interface for
> +          managing the interconnects in a SoC.
> +
> +	  If unsure, say no.
> +


-- 
~Randy

  reply	other threads:[~2017-03-02 23:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 18:22 [RFC v0 0/2] Introduce on-chip interconnect API Georgi Djakov
2017-03-01 18:22 ` [RFC v0 1/2] interconnect: Add generic interconnect controller API Georgi Djakov
2017-03-02 23:53   ` Randy Dunlap [this message]
     [not found]     ` <15929d7a-65e5-f8ba-2fac-0381c5f8e8fc-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-03-14 15:35       ` Georgi Djakov
2017-03-03  2:07   ` Saravana Kannan
2017-03-14 15:39     ` Georgi Djakov
2017-03-09  9:56   ` Lucas Stach
2017-03-14 15:45     ` Georgi Djakov
     [not found]   ` <20170301182235.19154-2-georgi.djakov-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-03-23  1:21     ` Michael Turquette
2017-03-23 15:21       ` Georgi Djakov
2017-03-01 18:22 ` [RFC v0 2/2] interconnect: Add Qualcomm msm8916 interconnect provider driver Georgi Djakov
2017-03-03  6:21 ` [RFC v0 0/2] Introduce on-chip interconnect API Rob Herring
2017-03-14 15:41   ` Georgi Djakov
2017-03-23  3:32     ` Moritz Fischer

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=15929d7a-65e5-f8ba-2fac-0381c5f8e8fc@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=andy.gross@linaro.org \
    --cc=davidai@quicinc.com \
    --cc=devicetree@vger.kernel.org \
    --cc=georgi.djakov@linaro.org \
    --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=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).