[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <44201af052a70efd42f7ff5a2125316c@kernel.org>
Date: Wed, 13 Jan 2021 11:48:24 +0000
From: Marc Zyngier <maz@...nel.org>
To: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
Cc: Saravana Kannan <saravanak@...gle.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>, kernel-team@...roid.com,
linux-kernel@...r.kernel.org,
Jisheng Zhang <Jisheng.Zhang@...aptics.com>,
Kevin Hilman <khilman@...libre.com>,
John Stultz <john.stultz@...aro.org>
Subject: Re: [PATCH v1 0/5] Enable fw_devlink=on by default
On 2021-01-13 11:44, Nicolas Saenz Julienne wrote:
> On Thu, 2020-12-17 at 19:16 -0800, Saravana Kannan wrote:
>> As discussed in LPC 2020, cyclic dependencies in firmware that
>> couldn't
>> be broken using logic was one of the last remaining reasons
>> fw_devlink=on couldn't be set by default.
>>
>> This series changes fw_devlink so that when a cyclic dependency is
>> found
>> in firmware, the links between those devices fallback to permissive
>> mode
>> behavior. This way, the rest of the system still benefits from
>> fw_devlink, but the ambiguous cases fallback to permissive mode.
>>
>> Setting fw_devlink=on by default brings a bunch of benefits
>> (currently,
>> only for systems with device tree firmware):
>> * Significantly cuts down deferred probes.
>> * Device probe is effectively attempted in graph order.
>> * Makes it much easier to load drivers as modules without having to
>> worry about functional dependencies between modules (depmod is still
>> needed for symbol dependencies).
>
> FWIW I don't see any issues with this on Raspberry Pi 4 :).
Keep bragging! ;-)
M.
--
Jazz is not dead. It just smells funny...
Powered by blists - more mailing lists