Merge android-4.19.112 (417d28a4) into msm-4.19

			dynamic table installation which will install SSDT

			tables to /sys/firmware/acpi/tables/dynamic.

	acpi_no_watchdog	[HW,ACPI,WDT]

			Ignore the ACPI-based watchdog interface (WDAT) and let

			a native driver control the watchdog device instead.

	acpi_rsdp=	[ACPI,EFI,KEXEC]

			Pass the RSDP address to the kernel, mostly used

			on machines running EFI runtime service to boot the

Device links allow representation of such dependencies in the driver core.

In its standard form, a device link combines *both* dependency types:

It guarantees correct suspend/resume and shutdown ordering between a

In its standard or *managed* form, a device link combines *both* dependency

types:  It guarantees correct suspend/resume and shutdown ordering between a

"supplier" device and its "consumer" devices, and it guarantees driver

presence on the supplier.  The consumer devices are not probed before the

supplier is bound to a driver, and they're unbound before the supplier

Another example for an inconsistent state would be a device link that

represents a driver presence dependency, yet is added from the consumer's

``->probe`` callback while the supplier hasn't probed yet:  Had the driver

core known about the device link earlier, it wouldn't have probed the

``->probe`` callback while the supplier hasn't started to probe yet:  Had the

driver core known about the device link earlier, it wouldn't have probed the

consumer in the first place.  The onus is thus on the consumer to check

presence of the supplier after adding the link, and defer probing on

non-presence.

If a device link is added in the ``->probe`` callback of the supplier or

consumer driver, it is typically deleted in its ``->remove`` callback for

symmetry.  That way, if the driver is compiled as a module, the device

link is added on module load and orderly deleted on unload.  The same

restrictions that apply to device link addition (e.g. exclusion of a

parallel suspend/resume transition) apply equally to deletion.

non-presence.  [Note that it is valid to create a link from the consumer's

``->probe`` callback while the supplier is still probing, but the consumer must

know that the supplier is functional already at the link creation time (that is

the case, for instance, if the consumer has just acquired some resources that

would not have been available had the supplier not been functional then).]

If a device link with ``DL_FLAG_STATELESS`` set (i.e. a stateless device link)

is added in the ``->probe`` callback of the supplier or consumer driver, it is

typically deleted in its ``->remove`` callback for symmetry.  That way, if the

driver is compiled as a module, the device link is added on module load and

orderly deleted on unload.  The same restrictions that apply to device link

addition (e.g. exclusion of a parallel suspend/resume transition) apply equally

to deletion.  Device links managed by the driver core are deleted automatically

by it.

Several flags may be specified on device link addition, two of which

have already been mentioned above:  ``DL_FLAG_STATELESS`` to express that no

can be specified to runtime resume the supplier upon addition of the

device link.  ``DL_FLAG_AUTOREMOVE_CONSUMER`` causes the device link to be

automatically purged when the consumer fails to probe or later unbinds.

This obviates the need to explicitly delete the link in the ``->remove``

callback or in the error path of the ``->probe`` callback.

Similarly, when the device link is added from supplier's ``->probe`` callback,

``DL_FLAG_AUTOREMOVE_SUPPLIER`` causes the device link to be automatically

purged when the supplier fails to probe or later unbinds.

If neither ``DL_FLAG_AUTOREMOVE_CONSUMER`` nor ``DL_FLAG_AUTOREMOVE_SUPPLIER``

is set, ``DL_FLAG_AUTOPROBE_CONSUMER`` can be used to request the driver core

to probe for a driver for the consumer driver on the link automatically after

a driver has been bound to the supplier device.

Note, however, that any combinations of ``DL_FLAG_AUTOREMOVE_CONSUMER``,

``DL_FLAG_AUTOREMOVE_SUPPLIER`` or ``DL_FLAG_AUTOPROBE_CONSUMER`` with

``DL_FLAG_STATELESS`` are invalid and cannot be used.

Limitations

===========

Driver authors should be aware that a driver presence dependency (i.e. when

``DL_FLAG_STATELESS`` is not specified on link addition) may cause probing of

the consumer to be deferred indefinitely.  This can become a problem if the

consumer is required to probe before a certain initcall level is reached.

Worse, if the supplier driver is blacklisted or missing, the consumer will

never be probed.

Driver authors should be aware that a driver presence dependency for managed

device links (i.e. when ``DL_FLAG_STATELESS`` is not specified on link addition)

may cause probing of the consumer to be deferred indefinitely.  This can become

a problem if the consumer is required to probe before a certain initcall level

is reached.  Worse, if the supplier driver is blacklisted or missing, the

consumer will never be probed.

Moreover, managed device links cannot be deleted directly.  They are deleted

by the driver core when they are not necessary any more in accordance with the

``DL_FLAG_AUTOREMOVE_CONSUMER`` and ``DL_FLAG_AUTOREMOVE_SUPPLIER`` flags.

However, stateless device links (i.e. device links with ``DL_FLAG_STATELESS``

set) are expected to be removed by whoever called :c:func:`device_link_add()`

to add them with the help of either :c:func:`device_link_del()` or

:c:func:`device_link_remove()`.

Sometimes drivers depend on optional resources.  They are able to operate

in a degraded mode (reduced feature set or performance) when those resources

===

.. kernel-doc:: drivers/base/core.c

   :functions: device_link_add device_link_del

   :functions: device_link_add device_link_del device_link_remove

# SPDX-License-Identifier: GPL-2.0

VERSION = 4

PATCHLEVEL = 19

SUBLEVEL = 111

SUBLEVEL = 112

EXTRAVERSION =

NAME = "People's Front"

	 * this.

	 */

	np = of_find_compatible_node(NULL, NULL, "arm,armv7-timer");

	if (!np)

		np = of_find_compatible_node(NULL, NULL, "arm,armv8-timer");

	if (!np)

		goto out_put;