Adding cc: David Collins
Plus my comments below.
On 6/3/19 5:32 PM, Saravana Kannan wrote:
> Add a generic "depends-on" property that allows specifying mandatory
> functional dependencies between devices. Add device-links after the
> devices are created (but before they are probed) by looking at this
> "depends-on" property.
>
> This property is used instead of existing DT properties that specify
> phandles of other devices (Eg: clocks, pinctrl, regulators, etc). This
> is because not all resources referred to by existing DT properties are
> mandatory functional dependencies. Some devices/drivers might be able
> to operate with reduced functionality when some of the resources
> aren't available. For example, a device could operate in polling mode
> if no IRQ is available, a device could skip doing power management if
> clock or voltage control isn't available and they are left on, etc.
>
> So, adding mandatory functional dependency links between devices by
> looking at referred phandles in DT properties won't work as it would
> prevent probing devices that could be probed. By having an explicit
> depends-on property, we can handle these cases correctly.
>
> Having functional dependencies explicitly called out in DT and
> automatically added before the devices are probed, provides the
> following benefits:
>
> - Optimizes device probe order and avoids the useless work of
> attempting probes of devices that will not probe successfully
> (because their suppliers aren't present or haven't probed yet).
>
> For example, in a commonly available mobile SoC, registering just
> one consumer device's driver at an initcall level earlier than the
> supplier device's driver causes 11 failed probe attempts before the
> consumer device probes successfully. This was with a kernel with all
> the drivers statically compiled in. This problem gets a lot worse if
> all the drivers are loaded as modules without direct symbol
> dependencies.
>
> - Supplier devices like clock providers, regulators providers, etc
> need to keep the resources they provide active and at a particular
> state(s) during boot up even if their current set of consumers don't
> request the resource to be active. This is because the rest of the
> consumers might not have probed yet and turning off the resource
> before all the consumers have probed could lead to a hang or
> undesired user experience.
>
> Some frameworks (Eg: regulator) handle this today by turning off
> "unused" resources at late_initcall_sync and hoping all the devices
> have probed by then. This is not a valid assumption for systems with
> loadable modules. Other frameworks (Eg: clock) just don't handle
> this due to the lack of a clear signal for when they can turn off
> resources. This leads to downstream hacks to handle cases like this
> that can easily be solved in the upstream kernel.
>
> By linking devices before they are probed, we give suppliers a clear
> count of the number of dependent consumers. Once all of the
> consumers are active, the suppliers can turn off the unused
> resources without making assumptions about the number of consumers.
>
> By default we just add device-links to track "driver presence" (probe
> succeeded) of the supplier device. If any other functionality provided
> by device-links are needed, it is left to the consumer/supplier
> devices to change the link when they probe.
>
>
> Saravana Kannan (5):
> of/platform: Speed up of_find_device_by_node()
> driver core: Add device links support for pending links to suppliers
> dt-bindings: Add depends-on property
> of/platform: Add functional dependency link from "depends-on" property
> driver core: Add sync_state driver/bus callback
>
> .../devicetree/bindings/depends-on.txt | 26 +++++
> drivers/base/core.c | 106 ++++++++++++++++++
> drivers/of/platform.c | 75 ++++++++++++-
> include/linux/device.h | 24 ++++
> include/linux/of.h | 3 +
> 5 files changed, 233 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/devicetree/bindings/depends-on.txt
>
I don't think the above description adequately describes one key problem
that the patch set addresses.
David Collins described the problem in an email late in the thread of
the first submission of this series. Instead of providing a link to
that email, I am going to fully copy it here:
On 5/31/19 4:27 PM, David Collins wrote:
> Hello Saravana,
>
> On 5/23/19 6:01 PM, Saravana Kannan wrote:
> ...
>> Having functional dependencies explicitly called out in DT and
>> automatically added before the devices are probed, provides the
>> following benefits:
> ...
>> - Supplier devices like clock providers, regulators providers, etc
>> need to keep the resources they provide active and at a particular
>> state(s) during boot up even if their current set of consumers don't
>> request the resource to be active. This is because the rest of the
>> consumers might not have probed yet and turning off the resource
>> before all the consumers have probed could lead to a hang or
>> undesired user experience.
> This benefit provided by the sync_state() callback function introduced in
> this series gives us a mechanism to solve a specific problem encountered
> on Qualcomm Technologies, Inc. (QTI) boards when booting with drivers
> compiled as modules. QTI boards have a regulator that powers the PHYs for
> display, camera, USB, UFS, and PCIe. When these boards boot up, the boot
> loader enables this regulator along with other resources in order to
> display a splash screen image. The regulator must remain enabled until
> the Linux display driver has probed and made a request with the regulator
> framework to keep the regulator enabled. If the regulator is disabled
> prematurely, then the screen image is corrupted and the display hardware
> enters a bad state.
>
> We have observed that when the camera driver probes before the display
> driver, it performs this sequence: regulator_enable(), camera register IO,
> regulator_disable(). Since it is the first consumer of the shared
> regulator, the regulator is physically disabled (even though display
> hardware still requires it to be enabled). We have solved this problem
> when compiling drivers statically with a downstream regulator
> proxy-consumer driver. This proxy-consumer is able to make an enable
> request for the shared regulator before any other consumer. It then
> removes its request at late_initcall_sync.
>
> Unfortunately, when drivers are compiled as modules instead of compiled
> statically into the kernel image, late_initcall_sync is not a meaningful
> marker of driver probe completion. This means that our existing proxy
> voting system will not work when drivers are compiled as modules. The
> sync_state() callback resolves this issue by providing a notification that
> is guaranteed to arrive only after all consumers of the shared regulator
> have probed.
>
> QTI boards have other cases of shared resources such as bus bandwidth
> which must remain at least at a level set by boot loaders in order to
> properly support hardware blocks that are enabled before the Linux kernel
> starts booting.
>
> Take care,
> David
>
To paraphrase, the problem is:
- bootloader enables a regulator for display
- during Linux boot camera driver probes:
* enable the regulator also used for display
* disable the regulator
+ screen image is corrupted
+ display hardware enters bad state
- later during Linux boot display driver probes:
* enable the regulator, but too late
So the problem is an ordering dependency between the camera driver probe
and the display driver probe.
Or alternatively the problem could be seen as: the bootloader has enabled
a regulator for a device that the bootloader is aware of, but has not
communicated to the Linux regulator framework that the device requires
the regulator to remain enabled.
Thinking about the problem this way could lead to an entirely different
solution.
-Frank
