[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20bc744b-bbb1-8803-3844-97d59f708f43@samsung.com>
Date: Tue, 3 Nov 2020 13:32:33 +0100
From: Sylwester Nawrocki <s.nawrocki@...sung.com>
To: Chanwoo Choi <cw00.choi@...sung.com>
Cc: georgi.djakov@...aro.org, krzk@...nel.org,
devicetree@...r.kernel.org, robh+dt@...nel.org,
a.swigon@...sung.com, myungjoo.ham@...sung.com,
inki.dae@...sung.com, sw0312.kim@...sung.com,
b.zolnierkie@...sung.com, m.szyprowski@...sung.com,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
linux-samsung-soc@...r.kernel.org, dri-devel@...ts.freedesktop.org
Subject: Re: [PATCH v7 3/6] PM / devfreq: exynos-bus: Add registration of
interconnect child device
Hi Chanwoo,
On 03.11.2020 11:45, Chanwoo Choi wrote:
> On 10/30/20 9:51 PM, Sylwester Nawrocki wrote:
>> This patch adds registration of a child platform device for the exynos
>> interconnect driver. It is assumed that the interconnect provider will
>> only be needed when #interconnect-cells property is present in the bus
>> DT node, hence the child device will be created only when such a property
>> is present.
>>
>> Signed-off-by: Sylwester Nawrocki <s.nawrocki@...sung.com>
>> drivers/devfreq/exynos-bus.c | 17 +++++++++++++++++
> We don't need to add 'select INTERCONNECT_EXYNOS' in Kconfig?
I think by doing so we could run into some dependency issues.
> Do you want to remain it as optional according to user?
Yes, I would prefer to keep it selectable through defconfig.
Currently it's only needed by one 32-bit ARM board.
--
Regards,
Sylwester
Powered by blists - more mailing lists