Message ID | 20240126063500.2684087-3-wenst@chromium.org |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel+bounces-39667-ouuuleilei=gmail.com@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:7300:e09d:b0:103:945f:af90 with SMTP id gm29csp528793dyb; Fri, 26 Jan 2024 00:56:06 -0800 (PST) X-Google-Smtp-Source: AGHT+IGLTo9VC7Fmc8Iqwis5QrrRP7BV/dw8aOuRZQ1r7bkgzztxDqcY52G7laRxWFH/jke/qNiI X-Received: by 2002:a17:906:3950:b0:a34:c924:3ffe with SMTP id g16-20020a170906395000b00a34c9243ffemr524530eje.31.1706259366468; Fri, 26 Jan 2024 00:56:06 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1706259366; cv=pass; d=google.com; s=arc-20160816; b=SLXuwA4NuWMAuxCEkRNHh6I6hChuv+TJsk16RpkIAGmqF1MZwnixOiu4J1YBpLQ1h1 MHFS752bs0lE49y5+/TwPkpm8hbRsVlXQ9HXaubOEWdVmYkIIqON5BQXP22qEhsCGbgZ v4DOXe+z3mCvq0Nr87RNtxHysLqymBzRAwTPy7AUNZIZlfzEOcsjUGcIqXoORsz1EmM7 D0xNSArVbyw1lIUsmKD3pXhUf82gdgbigKVO7oRmafe7tt7aAk1QTiKQ9kuwKn9Ak8eU O0wNQztolgY6m1czrk5dB0aLb0ZHGm6/3No+PRadWXmlsKDzlBWonh4BJTKzd0RDv9/d B2Jw== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:in-reply-to:message-id :date:subject:cc:to:from:dkim-signature; bh=vuuqWS/zETzQP4dBpV3f94YH5YVYzrmMgulqqtiHf0Y=; fh=Dq0KyaWQMV1+xKd1qM9MI32PdsWXz3CFCYPcvTEh9EA=; b=tR3VJN//ChHoexYpAEg7dlMpzLBDd24wZ3uijONq2AZIYY6ef54SkImDpY/kbQAufE dW92ARgPS+Gb3mrURJ8VCs/fHMNOrqvSIjrqG9/EgH6VZF4ReCdpv28wc5ccB/m9GNDH xmr6r5o8FLdA6Cx6kVEqiE+UC2mNGh65M/Y/o/6yiA7rwTV2m1v9mySqYjbh3jYYCinM KLkupi5s94eAOZu1GW2YX8IcO8ap8bkBTJejdeO11iNUuk1U1YCRQgsUJg62/b5k00u6 Kdp/p97rl36LdwsoN3I+IwfYVMNR59joBcfVOndwEey0nr0NgBRVRmEZ6SyjdU+IerK7 XgyA== ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b="DKA/3TXG"; 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-kernel+bounces-39667-ouuuleilei=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) smtp.mailfrom="linux-kernel+bounces-39667-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: from am.mirrors.kernel.org (am.mirrors.kernel.org. [147.75.80.249]) by mx.google.com with ESMTPS id l22-20020a170906079600b00a30f4e39fe1si339976ejc.782.2024.01.26.00.56.06 for <ouuuleilei@gmail.com> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 26 Jan 2024 00:56:06 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-39667-ouuuleilei=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b="DKA/3TXG"; 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-kernel+bounces-39667-ouuuleilei=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) smtp.mailfrom="linux-kernel+bounces-39667-ouuuleilei=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 am.mirrors.kernel.org (Postfix) with ESMTPS id AA7001F27187 for <ouuuleilei@gmail.com>; Fri, 26 Jan 2024 08:50:32 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 142671EB21; Fri, 26 Jan 2024 06:35:16 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="DKA/3TXG" Received: from mail-pf1-f180.google.com (mail-pf1-f180.google.com [209.85.210.180]) (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 2839C1DA40 for <linux-kernel@vger.kernel.org>; Fri, 26 Jan 2024 06:35:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.210.180 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706250913; cv=none; b=kQbO9/XgeivNrqulkEyYLSre/Eh+OoM36WblvIGBvGL3Yrp8bgEUJnGvDQI+XXX31juMPdX/vxVyT2u+JrcDT5XQN+j1XzA+NgGrqzJjkMrGJ9Ariijdjx9cA+3mgh4PPiIujh6u1vBQjTTLlacnxYw1CnnSj4Zvx9EW31klFfQ= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706250913; c=relaxed/simple; bh=crqtlQZPAGF9IP0JqUMkmEhjwAwKUs1v7HhOiB2r0og=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=RZ9CXEcQQIH2wRZ9O7HK7k6zrCq8tGyA83odFJ4/sQVPgf9m9JmjCeN6jSVlgJyN9CJTnJdCXLWE1F5XHZBpkDNdddkFa25knJsuS9GIR7zYUgZh4s7RfP1EoFszcm4tttuqP4t8iNpr7eA1/9rXmS0JnIzW4KrNzVyVi+/3kEU= 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=DKA/3TXG; arc=none smtp.client-ip=209.85.210.180 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-pf1-f180.google.com with SMTP id d2e1a72fcca58-6ddc1fad6ddso282103b3a.0 for <linux-kernel@vger.kernel.org>; Thu, 25 Jan 2024 22:35:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; t=1706250911; x=1706855711; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=vuuqWS/zETzQP4dBpV3f94YH5YVYzrmMgulqqtiHf0Y=; b=DKA/3TXGuY8Hj0RMDyBWAdyDt2y2ICDLnEEtCFtYAH0fstLQLZt6FV4NpdtsFsgn7r zxK8PdHMdXBsXLtKSeIwfmahc6LL21GCRZlVyKlS4lwgGLRXB/8isLrGDjrBcY5DS0S8 UT3LWtRQTNh1uWOP6q/e93j2rs0QeEcLjEdVE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706250911; x=1706855711; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=vuuqWS/zETzQP4dBpV3f94YH5YVYzrmMgulqqtiHf0Y=; b=Yft01Dq/MKMVi2poETM6Krmso7S6nXgTxDT9jKULCcn6m4RlKCZAa+Hwe+OC1HLvsZ iLEKO1eNZJeHd0BGB7bPCYCwHYE1Erwso6IArF0Z/hpvoatUCN+5KeAONt/toIZ29UfS 4/KThUrBBVpImMQWDqjFAHGU9BARunW2OB6HZGrVpj2Pv+Jh4GuwvR4apxTWur01WmF/ zCa95aXKVsjpLEdjXd3im/BjNxDE7CmL1t5EzzbhH+Z77p81WjF38eoGHJbd4UNyb1Wx oS7DuELqQbkZy+8csdosGtGH1tOvMHNFOK9JNq4uSTXo+KxHfq8IScfH78VrEUd6SNL+ M4ZQ== X-Gm-Message-State: AOJu0YxnmXz98e0/ILZsAz9qARs/cL2Ls/pcjSH53Q6c4rC49qNyP6bv YYwd5En6F/7AbWZukyMpXg+l/1SbeU4TTMzZxwvLBCfMbRsphIIQ7Ak3RXFu3g== X-Received: by 2002:a05:6a20:d805:b0:19c:8eb9:5d51 with SMTP id iv5-20020a056a20d80500b0019c8eb95d51mr101790pzb.43.1706250911400; Thu, 25 Jan 2024 22:35:11 -0800 (PST) Received: from wenstp920.tpe.corp.google.com ([2401:fa00:1:10:2614:bbbd:8db2:1f54]) by smtp.gmail.com with ESMTPSA id ka3-20020a056a00938300b006db13a02921sm488735pfb.183.2024.01.25.22.35.08 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 25 Jan 2024 22:35:11 -0800 (PST) From: Chen-Yu Tsai <wenst@chromium.org> To: Marcel Holtmann <marcel@holtmann.org>, Luiz Augusto von Dentz <luiz.dentz@gmail.com>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Conor Dooley <conor+dt@kernel.org>, Matthias Brugger <matthias.bgg@gmail.com>, AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> Cc: Chen-Yu Tsai <wenst@chromium.org>, Sean Wang <sean.wang@mediatek.com>, 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 Subject: [PATCH v2 2/2] arm64: dts: mediatek: mt8183-pico6: Fix bluetooth node Date: Fri, 26 Jan 2024 14:34:58 +0800 Message-ID: <20240126063500.2684087-3-wenst@chromium.org> X-Mailer: git-send-email 2.43.0.429.g432eaa2c6b-goog In-Reply-To: <20240126063500.2684087-1-wenst@chromium.org> References: <20240126063500.2684087-1-wenst@chromium.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: <linux-kernel.vger.kernel.org> List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org> List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1789142621485184047 X-GMAIL-MSGID: 1789142621485184047 |
Series |
bluetooth: mt7921s: Add binding and fixup existing dts
|
|
Commit Message
Chen-Yu Tsai
Jan. 26, 2024, 6:34 a.m. UTC
Bluetooth is not a random device connected to the MMC/SD controller. It is function 2 of the SDIO device. Fix the address of the bluetooth node. Also fix the node name and drop the label. Fixes: 055ef10ccdd4 ("arm64: dts: mt8183: Add jacuzzi pico/pico6 board") Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> --- Changes since v1: - Collected reviewed-by arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
Comments
On 26/01/2024 07:34, Chen-Yu Tsai wrote: > Bluetooth is not a random device connected to the MMC/SD controller. It > is function 2 of the SDIO device. > > Fix the address of the bluetooth node. Also fix the node name and drop > the label. > > Fixes: 055ef10ccdd4 ("arm64: dts: mt8183: Add jacuzzi pico/pico6 board") > Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> > Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com> > --- > Changes since v1: > - Collected reviewed-by > > arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts b/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts > index a2e74b829320..6a7ae616512d 100644 > --- a/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts > +++ b/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts > @@ -82,7 +82,8 @@ pins-clk { > }; > > &mmc1 { > - bt_reset: bt-reset { > + bluetooth@2 { > + reg = <2>; > compatible = "mediatek,mt7921s-bluetooth"; > pinctrl-names = "default"; > pinctrl-0 = <&bt_pins_reset>;
Dear Chen-Yu, Thank you for your patch. Am 26.01.24 um 07:34 schrieb Chen-Yu Tsai: > Bluetooth is not a random device connected to the MMC/SD controller. It > is function 2 of the SDIO device. > > Fix the address of the bluetooth node. Also fix the node name and drop > the label. Excuse my ignorance: Is this a cosmetic fix or does it fix the device somehow? > Fixes: 055ef10ccdd4 ("arm64: dts: mt8183: Add jacuzzi pico/pico6 board") > Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> > Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> > --- > Changes since v1: > - Collected reviewed-by > > arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts b/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts > index a2e74b829320..6a7ae616512d 100644 > --- a/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts > +++ b/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts > @@ -82,7 +82,8 @@ pins-clk { > }; > > &mmc1 { > - bt_reset: bt-reset { > + bluetooth@2 { > + reg = <2>; To avoid confusion, would it be possible to use sdio as a “name”. > compatible = "mediatek,mt7921s-bluetooth"; > pinctrl-names = "default"; > pinctrl-0 = <&bt_pins_reset>; Kind regards, Paul
Il 29/01/24 17:31, Paul Menzel ha scritto: > Dear Chen-Yu, > > > Thank you for your patch. > > Am 26.01.24 um 07:34 schrieb Chen-Yu Tsai: >> Bluetooth is not a random device connected to the MMC/SD controller. It >> is function 2 of the SDIO device. >> >> Fix the address of the bluetooth node. Also fix the node name and drop >> the label. > > Excuse my ignorance: Is this a cosmetic fix or does it fix the device somehow? > >> Fixes: 055ef10ccdd4 ("arm64: dts: mt8183: Add jacuzzi pico/pico6 board") >> Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> >> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> >> --- >> Changes since v1: >> - Collected reviewed-by >> >> arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts | 3 ++- >> 1 file changed, 2 insertions(+), 1 deletion(-) >> >> diff --git a/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts >> b/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts >> index a2e74b829320..6a7ae616512d 100644 >> --- a/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts >> +++ b/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts >> @@ -82,7 +82,8 @@ pins-clk { >> }; >> &mmc1 { >> - bt_reset: bt-reset { >> + bluetooth@2 { >> + reg = <2>; > > To avoid confusion, would it be possible to use sdio as a “name”. > Names must be generic and descriptive; this is the Bluetooth part of the MT7921s hence it's called "bluetooth". If its functionality was "sdio", it'd be as such, but this is BT anyway. "sdio@xxx" would be applicable to, for example, a controller that provides support exclusively for SDIO (with no support for eMMC/SD). Regards, Angelo
On Tue, Jan 30, 2024 at 12:31 AM Paul Menzel <pmenzel@molgen.mpg.de> wrote: > > Dear Chen-Yu, > > > Thank you for your patch. > > Am 26.01.24 um 07:34 schrieb Chen-Yu Tsai: > > Bluetooth is not a random device connected to the MMC/SD controller. It > > is function 2 of the SDIO device. > > > > Fix the address of the bluetooth node. Also fix the node name and drop > > the label. > > Excuse my ignorance: Is this a cosmetic fix or does it fix the device > somehow? It's a cosmetic change, since the driver already searches the whole device tree for the specific compatible string. However it also fixes the device tree description to match the actual hardware. > > Fixes: 055ef10ccdd4 ("arm64: dts: mt8183: Add jacuzzi pico/pico6 board") > > Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> > > Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> > > --- > > Changes since v1: > > - Collected reviewed-by > > > > arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts | 3 ++- > > 1 file changed, 2 insertions(+), 1 deletion(-) > > > > diff --git a/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts b/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts > > index a2e74b829320..6a7ae616512d 100644 > > --- a/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts > > +++ b/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts > > @@ -82,7 +82,8 @@ pins-clk { > > }; > > > > &mmc1 { > > - bt_reset: bt-reset { > > + bluetooth@2 { > > + reg = <2>; > > To avoid confusion, would it be possible to use sdio as a “name”. Not sure where the confusion is. Bluetooth is the functionality this SDIO function provides. ChenYu > > > compatible = "mediatek,mt7921s-bluetooth"; > > pinctrl-names = "default"; > > pinctrl-0 = <&bt_pins_reset>; > > > Kind regards, > > Paul
diff --git a/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts b/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts index a2e74b829320..6a7ae616512d 100644 --- a/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts +++ b/arch/arm64/boot/dts/mediatek/mt8183-kukui-jacuzzi-pico6.dts @@ -82,7 +82,8 @@ pins-clk { }; &mmc1 { - bt_reset: bt-reset { + bluetooth@2 { + reg = <2>; compatible = "mediatek,mt7921s-bluetooth"; pinctrl-names = "default"; pinctrl-0 = <&bt_pins_reset>;