[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <C6C73C77-669D-4552-AC0B-74BAA3FF583F@holtmann.org>
Date: Thu, 13 May 2021 17:21:43 +0200
From: Marcel Holtmann <marcel@...tmann.org>
To: Rob Herring <robh@...nel.org>
Cc: Venkata Lakshmi Narayana Gubba <gubbaven@...eaurora.org>,
Johan Hedberg <johan.hedberg@...il.com>,
devicetree@...r.kernel.org, Matthias Kaehlcke <mka@...omium.org>,
open list <linux-kernel@...r.kernel.org>,
Bluetooth Kernel Mailing List
<linux-bluetooth@...r.kernel.org>,
Hemantg <hemantg@...eaurora.org>,
MSM <linux-arm-msm@...r.kernel.org>,
Balakrishna Godavarthi <bgodavar@...eaurora.org>,
Rocky Liao <rjliao@...eaurora.org>, hbandi@...eaurora.org,
Abhishek Pandit-Subedi <abhishekpandit@...omium.org>
Subject: Re: [PATCH v3 4/5] dt-bindings: net: bluetooth: Convert Qualcomm BT
binding to DT schema
Hi Rob,
>>>> Converted Qualcomm Bluetooth binidings to DT schema.
>>>>
>>>> Signed-off-by: Venkata Lakshmi Narayana Gubba <gubbaven@...eaurora.org>
>>>> ---
>>>> .../devicetree/bindings/net/qualcomm-bluetooth.txt | 69 -------------
>>>> .../bindings/net/qualcomm-bluetooth.yaml | 111 +++++++++++++++++++++
>>>> 2 files changed, 111 insertions(+), 69 deletions(-)
>>>> delete mode 100644 Documentation/devicetree/bindings/net/qualcomm-bluetooth.txt
>>>> create mode 100644 Documentation/devicetree/bindings/net/qualcomm-bluetooth.yaml
>>>
>>>
>>>> diff --git a/Documentation/devicetree/bindings/net/qualcomm-bluetooth.yaml b/Documentation/devicetree/bindings/net/qualcomm-bluetooth.yaml
>>>> new file mode 100644
>>>> index 0000000..3f3ec4d
>>>> --- /dev/null
>>>> +++ b/Documentation/devicetree/bindings/net/qualcomm-bluetooth.yaml
>>>> @@ -0,0 +1,111 @@
>>>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
>>>> +%YAML 1.2
>>>> +---
>>>> +$id: http://devicetree.org/schemas/net/qualcomm-bluetooth.yaml#
>>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>>> +
>>>> +title: Qualcomm Bluetooth Chips
>>>> +
>>>> +maintainers:
>>>> + - Marcel Holtmann <marcel@...tmann.org>
>>>
>>> This should be someone who cares about Qcom BT.
>>
>> yes, please, assign this to someone that knows the hardware.
>>
>> Rob, can we leave this out for now if there is no dedicated person?
>
> No, it's required. It can be me if it comes to that. However, if no
> one can be bothered to step up, then we should just remove it perhaps.
> QCom is a big company, I'm sure they can find some name.
I hope so as well since my name is clearly the wrong one there. I have too little knowledge about that hardware and the platforms it is used in.
Regards
Marcel
Powered by blists - more mailing lists