Message ID | 20240215091524.14732-3-mihai.sain@microchip.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel+bounces-66507-ouuuleilei=gmail.com@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:7300:b825:b0:106:860b:bbdd with SMTP id da37csp268690dyb; Thu, 15 Feb 2024 01:16:43 -0800 (PST) X-Forwarded-Encrypted: i=3; AJvYcCWAa66H3EqLJITb2IDWtWdjinVFxxGOSEVN6L5x0usA+KiTr91VGhUX5veD3Y6S4vuk5+lxA4dBVNvq/IUNetIL/jdIVw== X-Google-Smtp-Source: AGHT+IF71uYMQD0/vpiOgPVADBB+miy6LpP32cUFyeYppgpgxJt4xBXGnFfNJTVzs5/aigB2Vhf3 X-Received: by 2002:aa7:c54b:0:b0:55f:f5d2:ef27 with SMTP id s11-20020aa7c54b000000b0055ff5d2ef27mr721092edr.41.1707988603305; Thu, 15 Feb 2024 01:16:43 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1707988603; cv=pass; d=google.com; s=arc-20160816; b=jEHP6Nwcu7X3mjphcVsO5G9pMa2p98YRIwpExY50xzFKcw+KSbL0EhJ9agefzo2p1u TohlfP0r++xISgwBjFQA6eY0ySOJRaLxmkrCrrJWc65Gf2dp1+eJdozQNDUhEt1+9Qh3 HH2Q8cgHP7VK/OumIzHj6Q0uHEY8o6/6RmqQ2ZY2Z6L9xSJTKG9j6QFoc28ZKqebjcEm 1yHrp7k9r9oY8G5FztDVspp5MLZJLsitgyHzm8S1DNAd8965NqnXNV18pbNgEW7/ZGQe JvLPJZ3vnkJL91wNud5cBuAhLUhqc/rLyLFA9jLRme30lIdN7AG0k0UHvV4azxnWKVOe ReIQ== 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=7Hb7NzIacCcMPwWgvq3taL66jtcxHcZrWuBFOR0umcg=; fh=pwiTAhnHM6rwwjkZ1m/aXYuIpXSgy4PNY+g+LslYgCI=; b=dV77UxjwMPPurvDVjEVqvLYKCvMnJkz5IS8dN/VMYy2ozR2nxmh+eNzwVRXHu/obls qksHjvgkZWT4Ydz4b5IPYwwOOhB5eH5T3JJ5Kqa/zOWNW2t8WURgI8RdcTNJBZ2UNs+k URrzG60oEzW1s/H8T5J4m8t3GVHfsd7wR8BuduBVCN50CeG7JTBZgiplsyDBNEUsKT0V +KGfdTTHv47V2trbZ9fyuxnrqiEYtv3hXyUfs4BN3UeK0lidqXJfj+DybliEEWGFAmVx kPUX9dU4JBBQ6v/eepYpwhTOhsY6Tdq3qJsUZcKJf/xmfvjH/9VOU5qwHwv6iP9ZDnXN QqDQ==; dara=google.com ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@microchip.com header.s=mchp header.b=evAvT0SQ; arc=pass (i=1 spf=pass spfdomain=microchip.com dkim=pass dkdomain=microchip.com dmarc=pass fromdomain=microchip.com); spf=pass (google.com: domain of linux-kernel+bounces-66507-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) smtp.mailfrom="linux-kernel+bounces-66507-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=QUARANTINE sp=REJECT dis=NONE) header.from=microchip.com Received: from am.mirrors.kernel.org (am.mirrors.kernel.org. [2604:1380:4601:e00::3]) by mx.google.com with ESMTPS id s29-20020a50d49d000000b005624d3edbd8si453531edi.490.2024.02.15.01.16.43 for <ouuuleilei@gmail.com> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 15 Feb 2024 01:16:43 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-66507-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3; Authentication-Results: mx.google.com; dkim=pass header.i=@microchip.com header.s=mchp header.b=evAvT0SQ; arc=pass (i=1 spf=pass spfdomain=microchip.com dkim=pass dkdomain=microchip.com dmarc=pass fromdomain=microchip.com); spf=pass (google.com: domain of linux-kernel+bounces-66507-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) smtp.mailfrom="linux-kernel+bounces-66507-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=QUARANTINE sp=REJECT dis=NONE) header.from=microchip.com 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 DF3A01F2EEE6 for <ouuuleilei@gmail.com>; Thu, 15 Feb 2024 09:16:42 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 19E4818637; Thu, 15 Feb 2024 09:16:06 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=microchip.com header.i=@microchip.com header.b="evAvT0SQ" Received: from esa.microchip.iphmx.com (esa.microchip.iphmx.com [68.232.154.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7C39816430; Thu, 15 Feb 2024 09:16:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=68.232.154.123 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707988563; cv=none; b=cwSlYXYEi0RjV4gDR0refgbVoI/M32f/irbPnT6TFRdxyBRuPQw+GNLEC6xtM0VtYhQYBIbv6yKHZSzaQR61wmUW7p8s+4u6Tbz2Pt2vQZBpXWsSJ184WqrPLP+qN0zuP6uhgFC3XOQUXgkHcRA/N6t6gWTDUDqGAPBm8pa0zEA= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707988563; c=relaxed/simple; bh=mpAIdYIZdLlbXbUTnkpoAZC9mXd6lxjFuCW9oFcNu6g=; h=From:To:CC:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=L2IFCmZPCJT3i2FCJ5ZDDnX5RxPZF3t0mRNTsQhg8IBrVaD9yZ8QZftnheNkLRfdCTcF9M1whieiJIC6CwD35VGF35jQFP5yzdtfPqVhU4eZO76mUpaK+mO4B+VzGXvPiSnX9uKHR+SL465YjfyQo0nRxZnscdn5nEtAFjWQZN0= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=microchip.com; spf=pass smtp.mailfrom=microchip.com; dkim=pass (2048-bit key) header.d=microchip.com header.i=@microchip.com header.b=evAvT0SQ; arc=none smtp.client-ip=68.232.154.123 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=microchip.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=microchip.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=microchip.com; i=@microchip.com; q=dns/txt; s=mchp; t=1707988561; x=1739524561; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=mpAIdYIZdLlbXbUTnkpoAZC9mXd6lxjFuCW9oFcNu6g=; b=evAvT0SQEjcQ+N0Cq9fm4TLejrqCeMhNhtLMHX++1bLthOr8FC18rBr0 qdUisVm0CEQjZu1XzSvyO27uwnSuRjB8kwk0n4868Gmr70QafV0FcOOsa ydiwt14nIeEFJCoge6ppvd9wbUSD77OZ7Tev5rRLf8okhIwxGgll04oOJ wKV3a8PTGdkofWaJ7yhT+nKjCG5o4D1ngGzAwL87sdqAKkb+phvWpILTq hqtUPlzXBNyEd4g6xG6XeZ02XYHNsa3LqGrBF8WW07eFomZ0sgO6kwT65 opEqCX87YZvHTXBwF4Oxfk4vg7KaQRtNcHNFaHuH4UfkUG2USlOGSfovJ Q==; X-CSE-ConnectionGUID: KRer2CuFQguroFb+z375Pg== X-CSE-MsgGUID: GZrf6E6nRD6+jf5dZIBtog== X-IronPort-AV: E=Sophos;i="6.06,161,1705388400"; d="scan'208";a="183550555" X-Amp-Result: SKIPPED(no attachment in message) Received: from unknown (HELO email.microchip.com) ([170.129.1.10]) by esa6.microchip.iphmx.com with ESMTP/TLS/ECDHE-RSA-AES128-GCM-SHA256; 15 Feb 2024 02:15:57 -0700 Received: from chn-vm-ex04.mchp-main.com (10.10.85.152) by chn-vm-ex04.mchp-main.com (10.10.85.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Thu, 15 Feb 2024 02:15:36 -0700 Received: from virtualbox.microchip.com (10.10.85.11) by chn-vm-ex04.mchp-main.com (10.10.85.152) with Microsoft SMTP Server id 15.1.2507.35 via Frontend Transport; Thu, 15 Feb 2024 02:15:33 -0700 From: Mihai Sain <mihai.sain@microchip.com> To: <claudiu.beznea@tuxon.dev>, <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>, <nicolas.ferre@microchip.com>, <alexandre.belloni@bootlin.com>, <andre.przywara@arm.com>, <devicetree@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org> CC: <cristian.birsan@microchip.com>, Mihai Sain <mihai.sain@microchip.com> Subject: [PATCH v3 2/3] ARM: dts: microchip: sama7g5: Add flexcom 10 node Date: Thu, 15 Feb 2024 11:15:23 +0200 Message-ID: <20240215091524.14732-3-mihai.sain@microchip.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20240215091524.14732-1-mihai.sain@microchip.com> References: <20240215091524.14732-1-mihai.sain@microchip.com> 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 Content-Type: text/plain X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1790955857700795511 X-GMAIL-MSGID: 1790955857700795511 |
Series |
Add initial support for Microchip SAMA7G54 Curiosity board
|
|
Commit Message
Mihai Sain
Feb. 15, 2024, 9:15 a.m. UTC
Add flexcom 10 node for usage on the SAMA7G54 Curiosity board.
Signed-off-by: Mihai Sain <mihai.sain@microchip.com>
---
arch/arm/boot/dts/microchip/sama7g5.dtsi | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
Comments
On Thu, Feb 15, 2024 at 11:15:23AM +0200, Mihai Sain wrote: > Add flexcom 10 node for usage on the SAMA7G54 Curiosity board. > > Signed-off-by: Mihai Sain <mihai.sain@microchip.com> > --- > arch/arm/boot/dts/microchip/sama7g5.dtsi | 24 ++++++++++++++++++++++++ > 1 file changed, 24 insertions(+) > > diff --git a/arch/arm/boot/dts/microchip/sama7g5.dtsi b/arch/arm/boot/dts/microchip/sama7g5.dtsi > index 269e0a3ca269..c030b318985a 100644 > --- a/arch/arm/boot/dts/microchip/sama7g5.dtsi > +++ b/arch/arm/boot/dts/microchip/sama7g5.dtsi > @@ -958,6 +958,30 @@ i2c9: i2c@600 { > }; > }; > > + flx10: flexcom@e2820000 { > + compatible = "atmel,sama5d2-flexcom"; My comment here was ignored: https://lore.kernel.org/all/20240214-robe-pregnancy-a1b056c9fe14@spud/ > + reg = <0xe2820000 0x200>; > + clocks = <&pmc PMC_TYPE_PERIPHERAL 48>; > + #address-cells = <1>; > + #size-cells = <1>; > + ranges = <0x0 0xe2820000 0x800>; > + status = "disabled"; > + > + i2c10: i2c@600 { > + compatible = "microchip,sama7g5-i2c", "microchip,sam9x60-i2c"; > + reg = <0x600 0x200>; > + interrupts = <GIC_SPI 48 IRQ_TYPE_LEVEL_HIGH>; > + #address-cells = <1>; > + #size-cells = <0>; > + clocks = <&pmc PMC_TYPE_PERIPHERAL 48>; > + atmel,fifo-size = <32>; > + dmas = <&dma0 AT91_XDMAC_DT_PERID(26)>, > + <&dma0 AT91_XDMAC_DT_PERID(25)>; > + dma-names = "tx", "rx"; > + status = "disabled"; > + }; > + }; > + > flx11: flexcom@e2824000 { > compatible = "atmel,sama5d2-flexcom"; > reg = <0xe2824000 0x200>; > -- > 2.43.0 >
> diff --git a/arch/arm/boot/dts/microchip/sama7g5.dtsi b/arch/arm/boot/dts/microchip/sama7g5.dtsi > index 269e0a3ca269..c030b318985a 100644 > --- a/arch/arm/boot/dts/microchip/sama7g5.dtsi > +++ b/arch/arm/boot/dts/microchip/sama7g5.dtsi > @@ -958,6 +958,30 @@ i2c9: i2c@600 { > }; > }; > > + flx10: flexcom@e2820000 { > + compatible = "atmel,sama5d2-flexcom"; My comment here was ignored: https://lore.kernel.org/all/20240214-robe-pregnancy-a1b056c9fe14@spud/ The SAMA7G5 has the same flexcom controller as SAMA5D2 MPU. https://github.com/torvalds/linux/blob/master/drivers/mfd/atmel-flexcom.c#L83 https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/mfd/atmel-flexcom.txt#L8
On 16/02/2024 06:58:10+0000, Mihai.Sain@microchip.com wrote: > > diff --git a/arch/arm/boot/dts/microchip/sama7g5.dtsi b/arch/arm/boot/dts/microchip/sama7g5.dtsi > > index 269e0a3ca269..c030b318985a 100644 > > --- a/arch/arm/boot/dts/microchip/sama7g5.dtsi > > +++ b/arch/arm/boot/dts/microchip/sama7g5.dtsi > > @@ -958,6 +958,30 @@ i2c9: i2c@600 { > > }; > > }; > > > > + flx10: flexcom@e2820000 { > > + compatible = "atmel,sama5d2-flexcom"; > > My comment here was ignored: > https://lore.kernel.org/all/20240214-robe-pregnancy-a1b056c9fe14@spud/ > > The SAMA7G5 has the same flexcom controller as SAMA5D2 MPU. > Still, it needs its own compatible plus a fallback to atmel,sama5d2-flexcom > https://github.com/torvalds/linux/blob/master/drivers/mfd/atmel-flexcom.c#L83 > https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/mfd/atmel-flexcom.txt#L8
On 16.02.2024 09:56, Alexandre Belloni wrote: > On 16/02/2024 06:58:10+0000, Mihai.Sain@microchip.com wrote: >>> diff --git a/arch/arm/boot/dts/microchip/sama7g5.dtsi b/arch/arm/boot/dts/microchip/sama7g5.dtsi >>> index 269e0a3ca269..c030b318985a 100644 >>> --- a/arch/arm/boot/dts/microchip/sama7g5.dtsi >>> +++ b/arch/arm/boot/dts/microchip/sama7g5.dtsi >>> @@ -958,6 +958,30 @@ i2c9: i2c@600 { >>> }; >>> }; >>> >>> + flx10: flexcom@e2820000 { >>> + compatible = "atmel,sama5d2-flexcom"; >> >> My comment here was ignored: >> https://lore.kernel.org/all/20240214-robe-pregnancy-a1b056c9fe14@spud/ >> >> The SAMA7G5 has the same flexcom controller as SAMA5D2 MPU. >> > > Still, it needs its own compatible plus a fallback to > atmel,sama5d2-flexcom I agree with this. Though, flexcom documentation is subject to YAML conversion (a patch has been re-posted these days [1] and *maybe* it will be integrated this time). And there are multiple SoC DTs that need to be updated with their own flexcom compatible (lan966x, sam9x60, sama7g5). To avoid conflicting with the work at [1] and postponing this series we may do the update after the [1] is done. Let me know your thoughts. Either way is fine by me. Thank you, Claudiu Beznea [1] https://patchwork.kernel.org/project/linux-arm-kernel/patch/20240214-sama5d2-flexcom-yaml-v1-1-5dedd0eba08e@microchip.com/ > >> https://github.com/torvalds/linux/blob/master/drivers/mfd/atmel-flexcom.c#L83 >> https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/mfd/atmel-flexcom.txt#L8 >
On Fri, Feb 16, 2024 at 10:24:13AM +0200, claudiu beznea wrote: > On 16.02.2024 09:56, Alexandre Belloni wrote: > > On 16/02/2024 06:58:10+0000, Mihai.Sain@microchip.com wrote: > >>> diff --git a/arch/arm/boot/dts/microchip/sama7g5.dtsi b/arch/arm/boot/dts/microchip/sama7g5.dtsi > >>> index 269e0a3ca269..c030b318985a 100644 > >>> --- a/arch/arm/boot/dts/microchip/sama7g5.dtsi > >>> +++ b/arch/arm/boot/dts/microchip/sama7g5.dtsi > >>> @@ -958,6 +958,30 @@ i2c9: i2c@600 { > >>> }; > >>> }; > >>> > >>> + flx10: flexcom@e2820000 { > >>> + compatible = "atmel,sama5d2-flexcom"; > >> > >> My comment here was ignored: > >> https://lore.kernel.org/all/20240214-robe-pregnancy-a1b056c9fe14@spud/ > >> > >> The SAMA7G5 has the same flexcom controller as SAMA5D2 MPU. > >> > > > > Still, it needs its own compatible plus a fallback to > > atmel,sama5d2-flexcom > > I agree with this. Though, flexcom documentation is subject to YAML > conversion (a patch has been re-posted these days [1] and *maybe* it will > be integrated this time). And there are multiple SoC DTs that need to be > updated with their own flexcom compatible (lan966x, sam9x60, sama7g5). > > To avoid conflicting with the work at [1] and postponing this series we may > do the update after the [1] is done. > > Let me know your thoughts. Either way is fine by me. I'd be inclined to say that if we are gonna take a shortcut here, then this patch should add a specific compatible so that when the yaml conversion goes through you'll get a warning about this being undocumented rather than silence. A resend on the flexcom patch is required though, the rebase was not done correctly, so maybe Balakrishnan could "atmel,sama7g5-flexcom" add with a fallback to "atmel,sama5d2-flexcom" while they're fixing it up? Cheers, Conor.
On 16.02.2024 11:35, Conor Dooley wrote: > On Fri, Feb 16, 2024 at 10:24:13AM +0200, claudiu beznea wrote: >> On 16.02.2024 09:56, Alexandre Belloni wrote: >>> On 16/02/2024 06:58:10+0000, Mihai.Sain@microchip.com wrote: >>>>> diff --git a/arch/arm/boot/dts/microchip/sama7g5.dtsi b/arch/arm/boot/dts/microchip/sama7g5.dtsi >>>>> index 269e0a3ca269..c030b318985a 100644 >>>>> --- a/arch/arm/boot/dts/microchip/sama7g5.dtsi >>>>> +++ b/arch/arm/boot/dts/microchip/sama7g5.dtsi >>>>> @@ -958,6 +958,30 @@ i2c9: i2c@600 { >>>>> }; >>>>> }; >>>>> >>>>> + flx10: flexcom@e2820000 { >>>>> + compatible = "atmel,sama5d2-flexcom"; >>>> >>>> My comment here was ignored: >>>> https://lore.kernel.org/all/20240214-robe-pregnancy-a1b056c9fe14@spud/ >>>> >>>> The SAMA7G5 has the same flexcom controller as SAMA5D2 MPU. >>>> >>> >>> Still, it needs its own compatible plus a fallback to >>> atmel,sama5d2-flexcom >> >> I agree with this. Though, flexcom documentation is subject to YAML >> conversion (a patch has been re-posted these days [1] and *maybe* it will >> be integrated this time). And there are multiple SoC DTs that need to be >> updated with their own flexcom compatible (lan966x, sam9x60, sama7g5). >> >> To avoid conflicting with the work at [1] and postponing this series we may >> do the update after the [1] is done. >> >> Let me know your thoughts. Either way is fine by me. > > I'd be inclined to say that if we are gonna take a shortcut here, then > this patch should add a specific compatible so that when the yaml > conversion goes through you'll get a warning about this being > undocumented rather than silence. All the flexcom nodes from all flexcom capable SoCs (including SAMA7G5) have the same compatible introduced by Mihai. I don't like the idea of updating only the DTSes, either update all DTSes and documentation or do it as it is already done (with sama5d2 compatible). > > A resend on the flexcom patch is required though, the rebase was not > done correctly, so maybe Balakrishnan could "atmel,sama7g5-flexcom" > add with a fallback to "atmel,sama5d2-flexcom" while they're fixing > it up? I agree, and DTSes should also be updated along with documentation. With this we can go forward with this patch and avoid conflicting with work that is currently in progress for flexcom. Thank you, Claudiu Beznea > > Cheers, > Conor.
On Mon, Feb 19, 2024 at 08:45:45PM +0200, claudiu beznea wrote: > > > On 16.02.2024 11:35, Conor Dooley wrote: > > On Fri, Feb 16, 2024 at 10:24:13AM +0200, claudiu beznea wrote: > >> On 16.02.2024 09:56, Alexandre Belloni wrote: > >>> On 16/02/2024 06:58:10+0000, Mihai.Sain@microchip.com wrote: > >>>>> diff --git a/arch/arm/boot/dts/microchip/sama7g5.dtsi b/arch/arm/boot/dts/microchip/sama7g5.dtsi > >>>>> index 269e0a3ca269..c030b318985a 100644 > >>>>> --- a/arch/arm/boot/dts/microchip/sama7g5.dtsi > >>>>> +++ b/arch/arm/boot/dts/microchip/sama7g5.dtsi > >>>>> @@ -958,6 +958,30 @@ i2c9: i2c@600 { > >>>>> }; > >>>>> }; > >>>>> > >>>>> + flx10: flexcom@e2820000 { > >>>>> + compatible = "atmel,sama5d2-flexcom"; > >>>> > >>>> My comment here was ignored: > >>>> https://lore.kernel.org/all/20240214-robe-pregnancy-a1b056c9fe14@spud/ > >>>> > >>>> The SAMA7G5 has the same flexcom controller as SAMA5D2 MPU. > >>>> > >>> > >>> Still, it needs its own compatible plus a fallback to > >>> atmel,sama5d2-flexcom > >> > >> I agree with this. Though, flexcom documentation is subject to YAML > >> conversion (a patch has been re-posted these days [1] and *maybe* it will > >> be integrated this time). And there are multiple SoC DTs that need to be > >> updated with their own flexcom compatible (lan966x, sam9x60, sama7g5). > >> > >> To avoid conflicting with the work at [1] and postponing this series we may > >> do the update after the [1] is done. > >> > >> Let me know your thoughts. Either way is fine by me. > > > > I'd be inclined to say that if we are gonna take a shortcut here, then > > this patch should add a specific compatible so that when the yaml > > conversion goes through you'll get a warning about this being > > undocumented rather than silence. > > All the flexcom nodes from all flexcom capable SoCs (including SAMA7G5) > have the same compatible introduced by Mihai. > > I don't like the idea of updating only the DTSes, either update all DTSes > and documentation or do it as it is already done (with sama5d2 compatible). > > > > > A resend on the flexcom patch is required though, the rebase was not > > done correctly, so maybe Balakrishnan could "atmel,sama7g5-flexcom" > > add with a fallback to "atmel,sama5d2-flexcom" while they're fixing > > it up? > > I agree, and DTSes should also be updated along with documentation. I'm biased, I'll almost never disagree with updating things to use soc-specific compatibles... > With this we can go forward with this patch and avoid conflicting with work > that is currently in progress for flexcom. I forgot to actually CC Balakrishnan, but Nicolas fortunately forwarded it to them. They're added now though to make sure they see this.
diff --git a/arch/arm/boot/dts/microchip/sama7g5.dtsi b/arch/arm/boot/dts/microchip/sama7g5.dtsi index 269e0a3ca269..c030b318985a 100644 --- a/arch/arm/boot/dts/microchip/sama7g5.dtsi +++ b/arch/arm/boot/dts/microchip/sama7g5.dtsi @@ -958,6 +958,30 @@ i2c9: i2c@600 { }; }; + flx10: flexcom@e2820000 { + compatible = "atmel,sama5d2-flexcom"; + reg = <0xe2820000 0x200>; + clocks = <&pmc PMC_TYPE_PERIPHERAL 48>; + #address-cells = <1>; + #size-cells = <1>; + ranges = <0x0 0xe2820000 0x800>; + status = "disabled"; + + i2c10: i2c@600 { + compatible = "microchip,sama7g5-i2c", "microchip,sam9x60-i2c"; + reg = <0x600 0x200>; + interrupts = <GIC_SPI 48 IRQ_TYPE_LEVEL_HIGH>; + #address-cells = <1>; + #size-cells = <0>; + clocks = <&pmc PMC_TYPE_PERIPHERAL 48>; + atmel,fifo-size = <32>; + dmas = <&dma0 AT91_XDMAC_DT_PERID(26)>, + <&dma0 AT91_XDMAC_DT_PERID(25)>; + dma-names = "tx", "rx"; + status = "disabled"; + }; + }; + flx11: flexcom@e2824000 { compatible = "atmel,sama5d2-flexcom"; reg = <0xe2824000 0x200>;