[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20fa9f6c-22b8-08d0-8fbd-82cbad9acc87@linaro.org>
Date: Tue, 14 Mar 2017 17:35:57 +0200
From: Georgi Djakov <georgi.djakov@...aro.org>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: linux-pm@...r.kernel.org, rjw@...ysocki.net, robh+dt@...nel.org,
gregkh@...uxfoundation.org, khilman@...libre.com,
mturquette@...libre.com, vincent.guittot@...aro.org,
skannan@...eaurora.org, sboyd@...eaurora.org,
andy.gross@...aro.org, seansw@....qualcomm.com,
davidai@...cinc.com, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-arm-msm@...r.kernel.org
Subject: Re: [RFC v0 1/2] interconnect: Add generic interconnect controller
API
On 03/03/2017 12:53 AM, Randy Dunlap wrote:
> 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?
>
Thanks for the comment! For simplicity, the core API currently is
only supported as a built-in, but we can definitely try making it
modular. I can do it after we get some initial feedback on if and
how this concept fits in the kernel and set the direction we want
to go.
BR,
Georgi
>
>> + 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.
>> +
>
>
Powered by blists - more mailing lists