Received: by 2002:a05:7412:3290:b0:fa:6e18:a558 with SMTP id ev16csp367663rdb; Thu, 25 Jan 2024 19:26:48 -0800 (PST) X-Google-Smtp-Source: AGHT+IGMQ4Ip93ecMnVsAZi/tF9q762cEmzaygHwyAOg679ey+GcvjWvUMi5/4MqTjsJwhta2I1l X-Received: by 2002:a05:622a:1aaa:b0:42a:62d0:5 with SMTP id s42-20020a05622a1aaa00b0042a62d00005mr1238371qtc.104.1706239608209; Thu, 25 Jan 2024 19:26:48 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1706239608; cv=pass; d=google.com; s=arc-20160816; b=pnP0kd0RH8Cz8eO9rpLW5kJ1bB51arEsq/jXN8dklbrTS69ilvc8en70ZilgudGwRP vqU8eV7zM/xWcVkKZEJzKxjPd8CwhXV5ROUR2eFve058C6F+A7OBj1xjvj1v5KVw8O0G tryigxUrqV8CGoXhVjtMCC+TRikxH+VoeoZljbscpvB5Piu/R5v+ztVO59kDfuKBGlUA piio4E4NJc4k3d6LACqHi9phNZniP8lkmPYlPDXclIf7ZB+3oNSbnjw3hCG7WuGjr80E KQBjmOIwSkgEtBtone38WBghCG7njRyI08YkGBT8n9gCST7af0m3yj2hjod5DB1QgyV4 3SAQ== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:list-unsubscribe:list-subscribe :list-id:precedence:dkim-signature; bh=9WyUC6MmB08/BiaNWVTf9K2ZnTvIR5FpF1Gb9asD+uw=; fh=w43e4oPZYO9pruXWEovS43NR0yTklwtVAd0+0qmTPm0=; b=1E3a1CcV9wLjpYP1YlYrs+1fa/WcQfN6G6nnNyM+a1ou3kOMafHmxR5zy0195dl4zG jj3/g/1deVOnrRoUahlWTz+rvnvyHt7xDtVUmAf26DZeF2K2B1nS42Y3A21+erTaceZB WYMNF1fjNaH5XN+Wc+oUuQLTGLg5g69QXKJymZe0lRy7o0KPbXQzDSFCTGU645/5C6kQ F+Ou7DxZi3uVvs53W3FSerXOGQNoQd5wVxBbv4emKaJTYNqtgV2B7QLnkzNIPD9Klp9q ZSceoNQ4dZCVAryO8Q0Qn1y9vzH1OQnJ3SQNQwHyD3U70TKxDG4HUsdDSfWKlItFQLfJ RNzA== ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=KvuGBhh+; arc=pass (i=1 spf=pass spfdomain=chromium.org dkim=pass dkdomain=chromium.org dmarc=pass fromdomain=chromium.org); spf=pass (google.com: domain of linux-bluetooth+bounces-1396-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-bluetooth+bounces-1396-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [2604:1380:45d1:ec00::1]) by mx.google.com with ESMTPS id c6-20020a056214224600b00681928444easi417159qvc.346.2024.01.25.19.26.48 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 25 Jan 2024 19:26:48 -0800 (PST) Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-1396-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=KvuGBhh+; arc=pass (i=1 spf=pass spfdomain=chromium.org dkim=pass dkdomain=chromium.org dmarc=pass fromdomain=chromium.org); spf=pass (google.com: domain of linux-bluetooth+bounces-1396-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-bluetooth+bounces-1396-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ny.mirrors.kernel.org (Postfix) with ESMTPS id E3A041C23FE9 for ; Fri, 26 Jan 2024 03:26:47 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id AA10EA947; Fri, 26 Jan 2024 03:26:40 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="KvuGBhh+" X-Original-To: linux-bluetooth@vger.kernel.org Received: from mail-lj1-f172.google.com (mail-lj1-f172.google.com [209.85.208.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 54313A94F for ; Fri, 26 Jan 2024 03:26:38 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.208.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706239600; cv=none; b=mzWJ8Wh6EbhnZJxCft5hcKvYRN1bRRJ+e7xuFtXjdP92i5aLK8Xymy3Oc+v8953tfprGpy24xkWSO9qMDMCMU33rrG2mO7fjEJiSc3HMwubZFc0NaafnnEV86TuvMvCjTZOg7eBhLOh8WXjFvXTtB7bfV05W0SebcXashj0k8Qc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706239600; c=relaxed/simple; bh=g4i+w63+sy9yYZPW+kGZdrOYodleOa12DosNrHLn0ww=; h=MIME-Version:References:In-Reply-To:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=f9MihumT5toNLV25rib+3Df+B6RDqhuTJ4/72xV3dubGWC9NKThGN7ZpmLfPRsgjvmnlmJ5CW9sAMOdA3/bimZuWvee65M7/WHNdgnu2ODVpHZIgcc3GCbwj60rsrfZDm+rQMyi1L7aPlTSpH79OJIbyFo1JCPwXIkUK5hqtbvY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=chromium.org; spf=pass smtp.mailfrom=chromium.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b=KvuGBhh+; arc=none smtp.client-ip=209.85.208.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=chromium.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=chromium.org Received: by mail-lj1-f172.google.com with SMTP id 38308e7fff4ca-2cf3ed3b917so12270761fa.1 for ; Thu, 25 Jan 2024 19:26:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; t=1706239596; x=1706844396; darn=vger.kernel.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=9WyUC6MmB08/BiaNWVTf9K2ZnTvIR5FpF1Gb9asD+uw=; b=KvuGBhh+zU0JKA19AEukbWG8KwvsdTj+hxPNAe3MX67kOBoX/+UQLmq0/N36s3XB6v f54yUKT7P3+avfVhCQj6yLZRfiFNNVDPHl244RJUtuM5qRLA+RMYoSXF98Pg7oI6wTzK q4uUbAUvTsF3XpTiADM6w9cgFXm4Bic4DZ9hc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706239596; x=1706844396; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=9WyUC6MmB08/BiaNWVTf9K2ZnTvIR5FpF1Gb9asD+uw=; b=BFDZuwK8UrHhbijuML45BLxqCfUE4S0ahGyHvw6y7be9jl0E/zjmE83sIbd2GwLrZh etCTQg208ShMsgEAdMtBj8OKssiLokK/TMbUWzT6M4oLbiseduxIIQXjqraLWDhNGXrO PvfcE7jCM27ZrcekwX2OfABgeAViizLocB7mCPNni8dWDTHiMnNUO8ej8rjpVTjiMYz6 kY6XN7FuUM85BvbHfCpnimBjxSVzvDgkZThv/pM4DgcC+tJn2yN2Tknu+xBT582RnZun WKkkEYlVrFhvtLxj8EekhsY2uEift6B3juC9XwcXo0Mc1tiF4ojBzslfsnm4MQACt1e5 LxGA== X-Gm-Message-State: AOJu0Ywv7WbihPZwRHfzD5/H/gaAXsZHtOqJOdFNK8gQh0OTWiB9Ejdb mXZdDe3lu567QF4Eif1UG8geEXKQWCxCqs89NRMCyUflssgz1YYk0YXjFWCgAD3obPrXjko41wU i5ml4+7F1aKgK5Fhl3L5rRSJJK3D1MM/UrNpd X-Received: by 2002:a05:651c:b1f:b0:2cc:a569:48d with SMTP id b31-20020a05651c0b1f00b002cca569048dmr210919ljr.44.1706239596392; Thu, 25 Jan 2024 19:26:36 -0800 (PST) Precedence: bulk X-Mailing-List: linux-bluetooth@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 References: <20240125095240.2308340-1-wenst@chromium.org> <20240125095240.2308340-2-wenst@chromium.org> <68249675-4081-48d9-abbb-1b2e49894fae@collabora.com> In-Reply-To: <68249675-4081-48d9-abbb-1b2e49894fae@collabora.com> From: Chen-Yu Tsai Date: Fri, 26 Jan 2024 11:26:25 +0800 Message-ID: Subject: Re: [PATCH 1/2] dt-bindings: net: bluetooth: Add MediaTek MT7921S SDIO Bluetooth To: AngeloGioacchino Del Regno Cc: Marcel Holtmann , Luiz Augusto von Dentz , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Matthias Brugger , Sean Wang , linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org, linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Jan 25, 2024 at 7:39=E2=80=AFPM AngeloGioacchino Del Regno wrote: > > Il 25/01/24 10:52, Chen-Yu Tsai ha scritto: > > The MediaTek MT7921S is a WiFi/Bluetooth combo chip that works over > > SDIO. While the Bluetooth function is fully discoverable, the chip > > has a pin that can reset just the Bluetooth side, as opposed to the > > full chip. This needs to be described in the device tree. > > > > Add a device tree binding for MT7921S Bluetooth over SDIO specifically > > ot document the reset line. > > > > Cc: Sean Wang > > Signed-off-by: Chen-Yu Tsai > > --- > > .../bluetooth/mediatek,mt7921s-bluetooth.yaml | 49 ++++++++++++++++++= + > > MAINTAINERS | 1 + > > 2 files changed, 50 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/net/bluetooth/me= diatek,mt7921s-bluetooth.yaml > > > > diff --git a/Documentation/devicetree/bindings/net/bluetooth/mediatek,m= t7921s-bluetooth.yaml b/Documentation/devicetree/bindings/net/bluetooth/med= iatek,mt7921s-bluetooth.yaml > > new file mode 100644 > > index 000000000000..bbe240e7cc40 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/net/bluetooth/mediatek,mt7921s-= bluetooth.yaml > > @@ -0,0 +1,49 @@ > > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/net/bluetooth/mediatek,mt7921s-blue= tooth.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: MediaTek MT7921S Bluetooth > > + > > title: > > maintainers: > > description: > > ... and then, you missed > > allOf: > - $ref: bluetooth-controller.yaml# (facepalm) > Everything else looks good. > > Cheers, > Angelo > > > +description: > > MT7921S is a (dual?) SDIO-attached dual-radio WiFi+Bluetooth combo chip; > this chip has two dedicated reset lines, one of which is used to reset > the Bluetooth core. > The WiFi part of this chip is described in ....where? :-) The function itself is fully probable and the implementation doesn't make use of the WiFi's reset line, so I don't see any reason to describe it? I don't actually know what the reset line does in the chip hardware. This patch is just described what is already used. > > + This binding describes the Bluetooth side of the SDIO-attached MT792= 1S > > + WiFi+Bluetooth combo chips. These chips are dual-radio chips support= ing > > + WiFi and Bluetooth. Bluetooth works over SDIO just like WiFi. Blueto= oth > > + has its own reset line, separate from WiFi, which can be used to res= et > > + the Bluetooth core. > > + > > +maintainers: > > + - Sean Wang > > + > > +properties: > > + compatible: > > + enum: > > + - mediatek,mt7921s-bluetooth > > + reg: > > + const: 2 > > + > > + reset-gpios: > > + maxItems: 1 > > + description: A GPIO line connected to the Bluetooth subsystem rese= t line. > > + Typically the W_DISABLE2# pin on M.2 E-key modules. If present t= his > > + shall be flagged as active low. > > description: > An active-low reset line connected for the Bluetooth core; connected to? > on typical M.2 Key-E modules this is the W_DISABLE2# pin. Otherwise this looks better. Thanks. ChenYu > Cheers, > Angelo > > > + > > +required: > > + - compatible > > + - reg > > + > > +additionalProperties: false > > + > > +examples: > > + - | > > + mmc { > > + #address-cells =3D <1>; > > + #size-cells =3D <0>; > > + > > + bluetooth@2 { > > + compatible =3D "mediatek,mt7921s-bluetooth"; > > + reg =3D <2>; > > + reset-gpios =3D <&pio 8 GPIO_ACTIVE_LOW>; > > + }; > > + }; > > diff --git a/MAINTAINERS b/MAINTAINERS > > index b64a64ca7916..662957146852 100644 > > --- a/MAINTAINERS > > +++ b/MAINTAINERS > > @@ -13657,6 +13657,7 @@ M: Sean Wang > > 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 > > >