aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorSaravana Kannan <[email protected]>2020-04-16 13:58:38 -0700
committerRob Herring <[email protected]>2020-04-28 12:47:47 -0500
commit8f88fad370bb0884f7f7217dea254b202df44716 (patch)
tree0009ffe5782b6d83a73122717fe1a973d7a8907f /tools/perf/scripts/python/export-to-sqlite.py
parenta4a8ced6fbbce1caf0d39ebf8c163162cb69ad01 (diff)
of: property: Don't retry device_link_add() upon failure
When of_link_to_phandle() was implemented initially, there was no way to tell if device_link_add() was failing because the supplier device hasn't been parsed yet, hasn't been added yet, the links were creating a cycle, etc. Some of these were transient errors that'd go away at a later point. However, with the current set of improved checks, if device_link_add() fails, it'll only be for permanent errors like cycles or out-of-memory errors. Also, with the addition of DL_FLAG_SYNC_STATE_ONLY flag [1] to device links, all the valid dependency cycles due to "proxy" device links (needed for correctness of sync_state() device callback) will never fail device_link_add() due to cycles. So, continuing to retry failing device links (by returning -EAGAIN) is no longer useful. At worst, it prevents platforms from setting fw_devlink=on (or better) because it prevents proper boot up. So, let's not do that anymore. [1] - https://lore.kernel.org/lkml/[email protected]/ Cc: Nicolas Saenz Julienne <[email protected]> Cc: Greg Kroah-Hartman <[email protected]> Signed-off-by: Saravana Kannan <[email protected]> Tested-by: Nicolas Saenz Julienne <[email protected]> Signed-off-by: Rob Herring <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions