Message ID | 20240412073046.1192744-2-wenst@chromium.org (mailing list archive) |
---|---|
State | Accepted |
Commit | 556511c33388394f1a67780f3f37f00ceb20f41b |
Headers | show |
Series | bluetooth: mt7921s: Add binding and fixup existing dts | expand |
Context | Check | Description |
---|---|---|
tedd_an/pre-ci_am | success | Success |
tedd_an/CheckPatch | success | CheckPatch PASS |
tedd_an/GitLint | fail | WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search 35: B1 Line exceeds max length (99>80): " create mode 100644 Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml" |
tedd_an/SubjectPrefix | fail | "Bluetooth: " prefix is not specified in the subject |
tedd_an/BuildKernel | success | BuildKernel PASS |
tedd_an/CheckAllWarning | success | CheckAllWarning PASS |
tedd_an/CheckSparse | success | CheckSparse PASS |
tedd_an/CheckSmatch | fail | CheckSparse: FAIL: Segmentation fault (core dumped) make[4]: *** [scripts/Makefile.build:244: net/bluetooth/hci_core.o] Error 139 make[4]: *** Deleting file 'net/bluetooth/hci_core.o' make[3]: *** [scripts/Makefile.build:485: net/bluetooth] Error 2 make[2]: *** [scripts/Makefile.build:485: net] Error 2 make[2]: *** Waiting for unfinished jobs.... Segmentation fault (core dumped) make[4]: *** [scripts/Makefile.build:244: drivers/bluetooth/bcm203x.o] Error 139 make[4]: *** Deleting file 'drivers/bluetooth/bcm203x.o' make[4]: *** Waiting for unfinished jobs.... Segmentation fault (core dumped) make[4]: *** [scripts/Makefile.build:244: drivers/bluetooth/bpa10x.o] Error 139 make[4]: *** Deleting file 'drivers/bluetooth/bpa10x.o' make[3]: *** [scripts/Makefile.build:485: drivers/bluetooth] Error 2 make[2]: *** [scripts/Makefile.build:485: drivers] Error 2 make[1]: *** [/github/workspace/src/src/Makefile:1919: .] Error 2 make: *** [Makefile:240: __sub-make] Error 2 |
tedd_an/BuildKernel32 | success | BuildKernel32 PASS |
tedd_an/TestRunnerSetup | success | TestRunnerSetup PASS |
tedd_an/TestRunner_l2cap-tester | success | TestRunner PASS |
tedd_an/TestRunner_iso-tester | fail | TestRunner_iso-tester: Total: 122, Passed: 121 (99.2%), Failed: 1, Not Run: 0 |
tedd_an/TestRunner_bnep-tester | success | TestRunner PASS |
tedd_an/TestRunner_mgmt-tester | success | TestRunner PASS |
tedd_an/TestRunner_rfcomm-tester | success | TestRunner PASS |
tedd_an/TestRunner_sco-tester | success | TestRunner PASS |
tedd_an/TestRunner_ioctl-tester | success | TestRunner PASS |
tedd_an/TestRunner_mesh-tester | success | TestRunner PASS |
tedd_an/TestRunner_smp-tester | success | TestRunner PASS |
tedd_an/TestRunner_userchan-tester | success | TestRunner PASS |
tedd_an/IncrementalBuild | success | Incremental Build PASS |
This is automated email and please do not reply to this email! Dear submitter, Thank you for submitting the patches to the linux bluetooth mailing list. This is a CI test results with your patch series: PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=843894 ---Test result--- Test Summary: CheckPatch PASS 1.52 seconds GitLint FAIL 0.77 seconds SubjectPrefix FAIL 0.41 seconds BuildKernel PASS 29.88 seconds CheckAllWarning PASS 32.17 seconds CheckSparse PASS 38.03 seconds CheckSmatch FAIL 36.19 seconds BuildKernel32 PASS 28.55 seconds TestRunnerSetup PASS 514.71 seconds TestRunner_l2cap-tester PASS 18.44 seconds TestRunner_iso-tester FAIL 32.95 seconds TestRunner_bnep-tester PASS 4.85 seconds TestRunner_mgmt-tester PASS 110.31 seconds TestRunner_rfcomm-tester PASS 7.42 seconds TestRunner_sco-tester PASS 15.09 seconds TestRunner_ioctl-tester PASS 7.69 seconds TestRunner_mesh-tester PASS 9.75 seconds TestRunner_smp-tester PASS 6.85 seconds TestRunner_userchan-tester PASS 5.02 seconds IncrementalBuild PASS 31.76 seconds Details ############################## Test: GitLint - FAIL Desc: Run gitlint Output: [v3,1/2] dt-bindings: net: bluetooth: Add MediaTek MT7921S SDIO Bluetooth WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search 35: B1 Line exceeds max length (99>80): " create mode 100644 Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml" [v3,2/2] arm64: dts: mediatek: mt8183-pico6: Fix bluetooth node WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search 10: B1 Line exceeds max length (81>80): "Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>" ############################## Test: SubjectPrefix - FAIL Desc: Check subject contains "Bluetooth" prefix Output: "Bluetooth: " prefix is not specified in the subject "Bluetooth: " prefix is not specified in the subject ############################## Test: CheckSmatch - FAIL Desc: Run smatch tool with source Output: Segmentation fault (core dumped) make[4]: *** [scripts/Makefile.build:244: net/bluetooth/hci_core.o] Error 139 make[4]: *** Deleting file 'net/bluetooth/hci_core.o' make[3]: *** [scripts/Makefile.build:485: net/bluetooth] Error 2 make[2]: *** [scripts/Makefile.build:485: net] Error 2 make[2]: *** Waiting for unfinished jobs.... Segmentation fault (core dumped) make[4]: *** [scripts/Makefile.build:244: drivers/bluetooth/bcm203x.o] Error 139 make[4]: *** Deleting file 'drivers/bluetooth/bcm203x.o' make[4]: *** Waiting for unfinished jobs.... Segmentation fault (core dumped) make[4]: *** [scripts/Makefile.build:244: drivers/bluetooth/bpa10x.o] Error 139 make[4]: *** Deleting file 'drivers/bluetooth/bpa10x.o' make[3]: *** [scripts/Makefile.build:485: drivers/bluetooth] Error 2 make[2]: *** [scripts/Makefile.build:485: drivers] Error 2 make[1]: *** [/github/workspace/src/src/Makefile:1919: .] Error 2 make: *** [Makefile:240: __sub-make] Error 2 ############################## Test: TestRunner_iso-tester - FAIL Desc: Run iso-tester with test-runner Output: Total: 122, Passed: 121 (99.2%), Failed: 1, Not Run: 0 Failed Test Cases ISO Connect2 Suspend - Success Failed 6.221 seconds --- Regards, Linux Bluetooth
Il 12/04/24 09:30, Chen-Yu Tsai ha scritto: > The MediaTek MT7921S is a WiFi/Bluetooth combo chip that works over > SDIO. WiFi and Bluetooth are separate SDIO functions within the chip. > While the Bluetooth SDIO function is fully discoverable, the chip has > a pin that can reset just the Bluetooth core, as opposed to the full > chip. This should be described in the device tree. > > Add a device tree binding for the Bluetooth SDIO function of the MT7921S > specifically to document the reset line. This binding is based on the MMC > controller binding, which specifies one device node per SDIO function. > > Cc: Sean Wang <sean.wang@mediatek.com> > Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
On Fri, 12 Apr 2024 15:30:42 +0800, Chen-Yu Tsai wrote: > The MediaTek MT7921S is a WiFi/Bluetooth combo chip that works over > SDIO. WiFi and Bluetooth are separate SDIO functions within the chip. > While the Bluetooth SDIO function is fully discoverable, the chip has > a pin that can reset just the Bluetooth core, as opposed to the full > chip. This should be described in the device tree. > > Add a device tree binding for the Bluetooth SDIO function of the MT7921S > specifically to document the reset line. This binding is based on the MMC > controller binding, which specifies one device node per SDIO function. > > Cc: Sean Wang <sean.wang@mediatek.com> > Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> > --- > Changes since v2: > - Expand description and commit message to clearly state that WiFi and > Bluetooth are separate SDIO functions, and that each function should > be a separate device node, as specified by the MMC binding. > - Change 'additionalProperties' to 'unevaluatedProperties' > - Add missing separating new line > - s/ot/to/ > > Angelo's reviewed-by was not picked up due to the above changes. > > Changes since v1: > - Reworded descriptions > - Moved binding maintainer section before description > - Added missing reference to bluetooth-controller.yaml > - Added missing GPIO header to example > --- > .../bluetooth/mediatek,mt7921s-bluetooth.yaml | 55 +++++++++++++++++++ > MAINTAINERS | 1 + > 2 files changed, 56 insertions(+) > create mode 100644 Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml > Reviewed-by: Rob Herring <robh@kernel.org>
Hi Chen-Yu, On Fri, Apr 12, 2024 at 12:31 AM Chen-Yu Tsai <wenst@chromium.org> wrote: > > The MediaTek MT7921S is a WiFi/Bluetooth combo chip that works over > SDIO. WiFi and Bluetooth are separate SDIO functions within the chip. > While the Bluetooth SDIO function is fully discoverable, the chip has > a pin that can reset just the Bluetooth core, as opposed to the full > chip. This should be described in the device tree. > > Add a device tree binding for the Bluetooth SDIO function of the MT7921S > specifically to document the reset line. This binding is based on the MMC > controller binding, which specifies one device node per SDIO function. > > Cc: Sean Wang <sean.wang@mediatek.com> > Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> > --- > Changes since v2: > - Expand description and commit message to clearly state that WiFi and > Bluetooth are separate SDIO functions, and that each function should > be a separate device node, as specified by the MMC binding. > - Change 'additionalProperties' to 'unevaluatedProperties' > - Add missing separating new line > - s/ot/to/ > > Angelo's reviewed-by was not picked up due to the above changes. > > Changes since v1: > - Reworded descriptions > - Moved binding maintainer section before description > - Added missing reference to bluetooth-controller.yaml > - Added missing GPIO header to example > --- > .../bluetooth/mediatek,mt7921s-bluetooth.yaml | 55 +++++++++++++++++++ > MAINTAINERS | 1 + > 2 files changed, 56 insertions(+) > create mode 100644 Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml > > diff --git a/Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml b/Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml > new file mode 100644 > index 000000000000..67ff7caad599 > --- /dev/null > +++ b/Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml > @@ -0,0 +1,55 @@ > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/net/bluetooth/mediatek,mt7921s-bluetooth.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: MediaTek MT7921S Bluetooth > + > +maintainers: > + - Sean Wang <sean.wang@mediatek.com> > + > +description: > + MT7921S is an SDIO-attached dual-radio WiFi+Bluetooth Combo chip; each > + function is its own SDIO function on a shared SDIO interface. The chip > + has two dedicated reset lines, one for each function core. > + This binding only covers the Bluetooth SDIO function, with one device > + node describing only this SDIO function. > + > +allOf: > + - $ref: bluetooth-controller.yaml# > + > +properties: > + compatible: > + enum: > + - mediatek,mt7921s-bluetooth > + > + reg: > + const: 2 > + > + reset-gpios: > + maxItems: 1 > + description: > + An active-low reset line for the Bluetooth core; on typical M.2 > + key E modules this is the W_DISABLE2# pin. > + Thanks for adding the new setup for the MT7921S devices. They look good to me. Sometimes, the MT7921S might be set up to wake up the host when it's asleep using a sideband signal. This might need an extra pin called "wakeup" to make it happen. Can you help add this pin to the settings in the same update, or should I do it later? > +required: > + - compatible > + - reg > + > +unevaluatedProperties: false > + > +examples: > + - | > + #include <dt-bindings/gpio/gpio.h> > + > + mmc { > + #address-cells = <1>; > + #size-cells = <0>; > + > + bluetooth@2 { > + compatible = "mediatek,mt7921s-bluetooth"; > + reg = <2>; > + reset-gpios = <&pio 8 GPIO_ACTIVE_LOW>; > + }; > + }; > diff --git a/MAINTAINERS b/MAINTAINERS > index 88981d9f3958..218bc2a21207 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -13818,6 +13818,7 @@ M: Sean Wang <sean.wang@mediatek.com> > L: linux-bluetooth@vger.kernel.org > L: linux-mediatek@lists.infradead.org (moderated for non-subscribers) > S: Maintained > +F: Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml > F: Documentation/devicetree/bindings/net/mediatek-bluetooth.txt > F: drivers/bluetooth/btmtkuart.c > > -- > 2.44.0.683.g7961c838ac-goog > >
On Wed, Apr 17, 2024 at 4:04 PM Sean Wang <sean.wang@kernel.org> wrote: > > Hi Chen-Yu, > > On Fri, Apr 12, 2024 at 12:31 AM Chen-Yu Tsai <wenst@chromium.org> wrote: > > > > The MediaTek MT7921S is a WiFi/Bluetooth combo chip that works over > > SDIO. WiFi and Bluetooth are separate SDIO functions within the chip. > > While the Bluetooth SDIO function is fully discoverable, the chip has > > a pin that can reset just the Bluetooth core, as opposed to the full > > chip. This should be described in the device tree. > > > > Add a device tree binding for the Bluetooth SDIO function of the MT7921S > > specifically to document the reset line. This binding is based on the MMC > > controller binding, which specifies one device node per SDIO function. > > > > Cc: Sean Wang <sean.wang@mediatek.com> > > Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> > > --- > > Changes since v2: > > - Expand description and commit message to clearly state that WiFi and > > Bluetooth are separate SDIO functions, and that each function should > > be a separate device node, as specified by the MMC binding. > > - Change 'additionalProperties' to 'unevaluatedProperties' > > - Add missing separating new line > > - s/ot/to/ > > > > Angelo's reviewed-by was not picked up due to the above changes. > > > > Changes since v1: > > - Reworded descriptions > > - Moved binding maintainer section before description > > - Added missing reference to bluetooth-controller.yaml > > - Added missing GPIO header to example > > --- > > .../bluetooth/mediatek,mt7921s-bluetooth.yaml | 55 +++++++++++++++++++ > > MAINTAINERS | 1 + > > 2 files changed, 56 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml > > > > diff --git a/Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml b/Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml > > new file mode 100644 > > index 000000000000..67ff7caad599 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml > > @@ -0,0 +1,55 @@ > > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/net/bluetooth/mediatek,mt7921s-bluetooth.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: MediaTek MT7921S Bluetooth > > + > > +maintainers: > > + - Sean Wang <sean.wang@mediatek.com> > > + > > +description: > > + MT7921S is an SDIO-attached dual-radio WiFi+Bluetooth Combo chip; each > > + function is its own SDIO function on a shared SDIO interface. The chip > > + has two dedicated reset lines, one for each function core. > > + This binding only covers the Bluetooth SDIO function, with one device > > + node describing only this SDIO function. > > + > > +allOf: > > + - $ref: bluetooth-controller.yaml# > > + > > +properties: > > + compatible: > > + enum: > > + - mediatek,mt7921s-bluetooth > > + > > + reg: > > + const: 2 > > + > > + reset-gpios: > > + maxItems: 1 > > + description: > > + An active-low reset line for the Bluetooth core; on typical M.2 > > + key E modules this is the W_DISABLE2# pin. > > + > > Thanks for adding the new setup for the MT7921S devices. They look good to me. > Sometimes, the MT7921S might be set up to wake up the host when it's > asleep using a sideband signal. > This might need an extra pin called "wakeup" to make it happen. Can > you help add this pin to the settings in the same update, or should I > do it later? I suggest you send a patch on top of this one? I'm not sure if you would model it as a GPIO or interrupt. And there doesn't seem to be any code in the driver expecting it. ChenYu > > +required: > > + - compatible > > + - reg > > + > > +unevaluatedProperties: false > > + > > +examples: > > + - | > > + #include <dt-bindings/gpio/gpio.h> > > + > > + mmc { > > + #address-cells = <1>; > > + #size-cells = <0>; > > + > > + bluetooth@2 { > > + compatible = "mediatek,mt7921s-bluetooth"; > > + reg = <2>; > > + reset-gpios = <&pio 8 GPIO_ACTIVE_LOW>; > > + }; > > + }; > > diff --git a/MAINTAINERS b/MAINTAINERS > > index 88981d9f3958..218bc2a21207 100644 > > --- a/MAINTAINERS > > +++ b/MAINTAINERS > > @@ -13818,6 +13818,7 @@ M: Sean Wang <sean.wang@mediatek.com> > > L: linux-bluetooth@vger.kernel.org > > L: linux-mediatek@lists.infradead.org (moderated for non-subscribers) > > S: Maintained > > +F: Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml > > F: Documentation/devicetree/bindings/net/mediatek-bluetooth.txt > > F: drivers/bluetooth/btmtkuart.c > > > > -- > > 2.44.0.683.g7961c838ac-goog > > > >
Hi Chen-Yu, okay, we will add it once we have implemented it in the driver. thanks for adding the dt-binding. Sean On Wed, Apr 17, 2024 at 4:32 PM Chen-Yu Tsai <wenst@chromium.org> wrote: > > On Wed, Apr 17, 2024 at 4:04 PM Sean Wang <sean.wang@kernel.org> wrote: > > > > Hi Chen-Yu, > > > > On Fri, Apr 12, 2024 at 12:31 AM Chen-Yu Tsai <wenst@chromium.org> wrote: > > > > > > The MediaTek MT7921S is a WiFi/Bluetooth combo chip that works over > > > SDIO. WiFi and Bluetooth are separate SDIO functions within the chip. > > > While the Bluetooth SDIO function is fully discoverable, the chip has > > > a pin that can reset just the Bluetooth core, as opposed to the full > > > chip. This should be described in the device tree. > > > > > > Add a device tree binding for the Bluetooth SDIO function of the MT7921S > > > specifically to document the reset line. This binding is based on the MMC > > > controller binding, which specifies one device node per SDIO function. > > > > > > Cc: Sean Wang <sean.wang@mediatek.com> > > > Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> > > > --- > > > Changes since v2: > > > - Expand description and commit message to clearly state that WiFi and > > > Bluetooth are separate SDIO functions, and that each function should > > > be a separate device node, as specified by the MMC binding. > > > - Change 'additionalProperties' to 'unevaluatedProperties' > > > - Add missing separating new line > > > - s/ot/to/ > > > > > > Angelo's reviewed-by was not picked up due to the above changes. > > > > > > Changes since v1: > > > - Reworded descriptions > > > - Moved binding maintainer section before description > > > - Added missing reference to bluetooth-controller.yaml > > > - Added missing GPIO header to example > > > --- > > > .../bluetooth/mediatek,mt7921s-bluetooth.yaml | 55 +++++++++++++++++++ > > > MAINTAINERS | 1 + > > > 2 files changed, 56 insertions(+) > > > create mode 100644 Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml > > > > > > diff --git a/Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml b/Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml > > > new file mode 100644 > > > index 000000000000..67ff7caad599 > > > --- /dev/null > > > +++ b/Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml > > > @@ -0,0 +1,55 @@ > > > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) > > > +%YAML 1.2 > > > +--- > > > +$id: http://devicetree.org/schemas/net/bluetooth/mediatek,mt7921s-bluetooth.yaml# > > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > > + > > > +title: MediaTek MT7921S Bluetooth > > > + > > > +maintainers: > > > + - Sean Wang <sean.wang@mediatek.com> > > > + > > > +description: > > > + MT7921S is an SDIO-attached dual-radio WiFi+Bluetooth Combo chip; each > > > + function is its own SDIO function on a shared SDIO interface. The chip > > > + has two dedicated reset lines, one for each function core. > > > + This binding only covers the Bluetooth SDIO function, with one device > > > + node describing only this SDIO function. > > > + > > > +allOf: > > > + - $ref: bluetooth-controller.yaml# > > > + > > > +properties: > > > + compatible: > > > + enum: > > > + - mediatek,mt7921s-bluetooth > > > + > > > + reg: > > > + const: 2 > > > + > > > + reset-gpios: > > > + maxItems: 1 > > > + description: > > > + An active-low reset line for the Bluetooth core; on typical M.2 > > > + key E modules this is the W_DISABLE2# pin. > > > + > > > > Thanks for adding the new setup for the MT7921S devices. They look good to me. > > Sometimes, the MT7921S might be set up to wake up the host when it's > > asleep using a sideband signal. > > This might need an extra pin called "wakeup" to make it happen. Can > > you help add this pin to the settings in the same update, or should I > > do it later? > > I suggest you send a patch on top of this one? I'm not sure if you > would model it as a GPIO or interrupt. And there doesn't seem to be > any code in the driver expecting it. > > > ChenYu > > > > +required: > > > + - compatible > > > + - reg > > > + > > > +unevaluatedProperties: false > > > + > > > +examples: > > > + - | > > > + #include <dt-bindings/gpio/gpio.h> > > > + > > > + mmc { > > > + #address-cells = <1>; > > > + #size-cells = <0>; > > > + > > > + bluetooth@2 { > > > + compatible = "mediatek,mt7921s-bluetooth"; > > > + reg = <2>; > > > + reset-gpios = <&pio 8 GPIO_ACTIVE_LOW>; > > > + }; > > > + }; > > > diff --git a/MAINTAINERS b/MAINTAINERS > > > index 88981d9f3958..218bc2a21207 100644 > > > --- a/MAINTAINERS > > > +++ b/MAINTAINERS > > > @@ -13818,6 +13818,7 @@ M: Sean Wang <sean.wang@mediatek.com> > > > L: linux-bluetooth@vger.kernel.org > > > L: linux-mediatek@lists.infradead.org (moderated for non-subscribers) > > > S: Maintained > > > +F: Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml > > > F: Documentation/devicetree/bindings/net/mediatek-bluetooth.txt > > > F: drivers/bluetooth/btmtkuart.c > > > > > > -- > > > 2.44.0.683.g7961c838ac-goog > > > > > >
On Tue, Apr 16, 2024 at 7:05 AM Rob Herring <robh@kernel.org> wrote: > On Fri, 12 Apr 2024 15:30:42 +0800, Chen-Yu Tsai wrote: > > The MediaTek MT7921S is a WiFi/Bluetooth combo chip that works over > > SDIO. WiFi and Bluetooth are separate SDIO functions within the chip. > > While the Bluetooth SDIO function is fully discoverable, the chip has > > a pin that can reset just the Bluetooth core, as opposed to the full > > chip. This should be described in the device tree. > > > > Add a device tree binding for the Bluetooth SDIO function of the MT7921S > > specifically to document the reset line. This binding is based on the MMC > > controller binding, which specifies one device node per SDIO function. > > > > Cc: Sean Wang <sean.wang@mediatek.com> > > Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> > > --- > > Changes since v2: > > - Expand description and commit message to clearly state that WiFi and > > Bluetooth are separate SDIO functions, and that each function should > > be a separate device node, as specified by the MMC binding. > > - Change 'additionalProperties' to 'unevaluatedProperties' > > - Add missing separating new line > > - s/ot/to/ > > > > Angelo's reviewed-by was not picked up due to the above changes. > > > > Changes since v1: > > - Reworded descriptions > > - Moved binding maintainer section before description > > - Added missing reference to bluetooth-controller.yaml > > - Added missing GPIO header to example > > --- > > .../bluetooth/mediatek,mt7921s-bluetooth.yaml | 55 +++++++++++++++++++ > > MAINTAINERS | 1 + > > 2 files changed, 56 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml > > > > Reviewed-by: Rob Herring <robh@kernel.org> Luiz, could you pick up this patch? The other one is already merged in the MediaTek tree. Thanks! ChenYu
diff --git a/Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml b/Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml new file mode 100644 index 000000000000..67ff7caad599 --- /dev/null +++ b/Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml @@ -0,0 +1,55 @@ +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/net/bluetooth/mediatek,mt7921s-bluetooth.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: MediaTek MT7921S Bluetooth + +maintainers: + - Sean Wang <sean.wang@mediatek.com> + +description: + MT7921S is an SDIO-attached dual-radio WiFi+Bluetooth Combo chip; each + function is its own SDIO function on a shared SDIO interface. The chip + has two dedicated reset lines, one for each function core. + This binding only covers the Bluetooth SDIO function, with one device + node describing only this SDIO function. + +allOf: + - $ref: bluetooth-controller.yaml# + +properties: + compatible: + enum: + - mediatek,mt7921s-bluetooth + + reg: + const: 2 + + reset-gpios: + maxItems: 1 + description: + An active-low reset line for the Bluetooth core; on typical M.2 + key E modules this is the W_DISABLE2# pin. + +required: + - compatible + - reg + +unevaluatedProperties: false + +examples: + - | + #include <dt-bindings/gpio/gpio.h> + + mmc { + #address-cells = <1>; + #size-cells = <0>; + + bluetooth@2 { + compatible = "mediatek,mt7921s-bluetooth"; + reg = <2>; + reset-gpios = <&pio 8 GPIO_ACTIVE_LOW>; + }; + }; diff --git a/MAINTAINERS b/MAINTAINERS index 88981d9f3958..218bc2a21207 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -13818,6 +13818,7 @@ M: Sean Wang <sean.wang@mediatek.com> L: linux-bluetooth@vger.kernel.org L: linux-mediatek@lists.infradead.org (moderated for non-subscribers) S: Maintained +F: Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml F: Documentation/devicetree/bindings/net/mediatek-bluetooth.txt F: drivers/bluetooth/btmtkuart.c
The MediaTek MT7921S is a WiFi/Bluetooth combo chip that works over SDIO. WiFi and Bluetooth are separate SDIO functions within the chip. While the Bluetooth SDIO function is fully discoverable, the chip has a pin that can reset just the Bluetooth core, as opposed to the full chip. This should be described in the device tree. Add a device tree binding for the Bluetooth SDIO function of the MT7921S specifically to document the reset line. This binding is based on the MMC controller binding, which specifies one device node per SDIO function. Cc: Sean Wang <sean.wang@mediatek.com> Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> --- Changes since v2: - Expand description and commit message to clearly state that WiFi and Bluetooth are separate SDIO functions, and that each function should be a separate device node, as specified by the MMC binding. - Change 'additionalProperties' to 'unevaluatedProperties' - Add missing separating new line - s/ot/to/ Angelo's reviewed-by was not picked up due to the above changes. Changes since v1: - Reworded descriptions - Moved binding maintainer section before description - Added missing reference to bluetooth-controller.yaml - Added missing GPIO header to example --- .../bluetooth/mediatek,mt7921s-bluetooth.yaml | 55 +++++++++++++++++++ MAINTAINERS | 1 + 2 files changed, 56 insertions(+) create mode 100644 Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-bluetooth.yaml