[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <535c8517-b983-29d8-6b06-bffe4243aec1@gmail.com>
Date: Thu, 16 Sep 2021 04:29:44 +0300
From: Dmitry Osipenko <digetx@...il.com>
To: Chanwoo Choi <cwchoi00@...il.com>,
Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
Viresh Kumar <vireshk@...nel.org>, Nishanth Menon <nm@...com>,
MyungJoo Ham <myungjoo.ham@...sung.com>,
Stephen Boyd <sboyd@...nel.org>,
Kyungmin Park <kyungmin.park@...sung.com>,
Chanwoo Choi <cw00.choi@...sung.com>
Cc: linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org
Subject: Re: [PATCH v1 2/4] PM / devfreq: Add devm_devfreq_add_governor()
15.09.2021 21:37, Chanwoo Choi пишет:
> Hi,
>
> There is ordering dependency between devfreq device and devfreq
> governor. Theoretically, devfreq governor must be released after
> released of devfreq device.
>
> devm_* support the release ordering by the sequence of registration
> in probe()?
Yes, the release order is always opposite to the registration order.
Powered by blists - more mailing lists