summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/net/realtek-bluetooth.yaml
diff options
context:
space:
mode:
authorMaxime Ripard <maxime@cerno.tech>2021-09-24 09:27:54 +0200
committerRob Herring <robh@kernel.org>2021-10-12 09:05:34 -0500
commita9d2d57083b628709ffc4ef570b4f752715bba87 (patch)
tree06e3af1ea00d77330bdbd64fd1ae893ba37d9105 /Documentation/devicetree/bindings/net/realtek-bluetooth.yaml
parent88ffadce9d4cc14b04e7c21961a6ea9ceb9077e4 (diff)
dt-bindings: bluetooth: realtek: Add missing max-speed
additionalProperties prevent any property not explicitly defined in the binding to be used. Yet, some serial properties like max-speed are valid and validated through the serial/serial.yaml binding. Even though the ideal solution would be to use unevaluatedProperties instead, it's not pratical due to the way the bus bindings have been described. Let's add max-speed to remove the warning. Cc: Alistair Francis <alistair@alistair23.me> Cc: "David S. Miller" <davem@davemloft.net> Cc: Jakub Kicinski <kuba@kernel.org> Cc: netdev@vger.kernel.org Cc: Vasily Khoruzhick <anarsoul@gmail.com> Reviewed-by: Alistair Francis <alistair@alistair23.me> Reviewed-by: Rob Herring <robh@kernel.org> Signed-off-by: Maxime Ripard <maxime@cerno.tech> Signed-off-by: Rob Herring <robh@kernel.org> Link: https://lore.kernel.org/r/20210924072756.869731-2-maxime@cerno.tech
Diffstat (limited to 'Documentation/devicetree/bindings/net/realtek-bluetooth.yaml')
-rw-r--r--Documentation/devicetree/bindings/net/realtek-bluetooth.yaml2
1 files changed, 2 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/net/realtek-bluetooth.yaml b/Documentation/devicetree/bindings/net/realtek-bluetooth.yaml
index 0634e69dd9a6..157d606bf9cb 100644
--- a/Documentation/devicetree/bindings/net/realtek-bluetooth.yaml
+++ b/Documentation/devicetree/bindings/net/realtek-bluetooth.yaml
@@ -34,6 +34,8 @@ properties:
maxItems: 1
description: GPIO specifier, used to wakeup the host processor
+ max-speed: true
+
required:
- compatible