For firmware that supports it, allow multiple SCM calls to be passed
down to it by removing the serialization lock in the SCM driver.
This patch is based on this YAML conversion patch [1] that is in-flight
currently.
[1] https://lore.kernel.org/lkml/[email protected]/
Signed-off-by: Guru Das Srinagesh <[email protected]>
---
Documentation/devicetree/bindings/firmware/qcom,scm.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/firmware/qcom,scm.yaml b/Documentation/devicetree/bindings/firmware/qcom,scm.yaml
index 9fdeee0..e279fd2 100644
--- a/Documentation/devicetree/bindings/firmware/qcom,scm.yaml
+++ b/Documentation/devicetree/bindings/firmware/qcom,scm.yaml
@@ -70,6 +70,11 @@ properties:
'#reset-cells':
const: 1
+ allow-multi-call:
+ description:
+ Specify this flag to remove SCM call serialization. Need to ensure that
+ the firmware being used supports this feature first.
+
qcom,dload-mode:
$ref: /schemas/types.yaml#/definitions/phandle-array
items:
--
2.7.4
On 22/07/2022 18:37, Guru Das Srinagesh wrote:
> For firmware that supports it, allow multiple SCM calls to be passed
> down to it by removing the serialization lock in the SCM driver.
>
> This patch is based on this YAML conversion patch [1] that is in-flight
> currently.
>
> [1] https://lore.kernel.org/lkml/[email protected]/
>
> Signed-off-by: Guru Das Srinagesh <[email protected]>
> ---
> Documentation/devicetree/bindings/firmware/qcom,scm.yaml | 5 +++++
> 1 file changed, 5 insertions(+)
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
Best regards,
Krzysztof