Message ID | 20230603200243.243878-22-varshini.rajendran@microchip.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:994d:0:b0:3d9:f83d:47d9 with SMTP id k13csp1828872vqr; Sat, 3 Jun 2023 13:15:00 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4rKHS4FjiTKmHr9FPlFBFQtY3Jh5KqGanJ2HAfka8iTI1pr8zj9jl+deDW233AshUgibcq X-Received: by 2002:a05:6358:7e88:b0:123:5d3c:5a36 with SMTP id o8-20020a0563587e8800b001235d3c5a36mr9917614rwn.24.1685823299766; Sat, 03 Jun 2023 13:14:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1685823299; cv=none; d=google.com; s=arc-20160816; b=iuyN/TDACtWLzm5n5zx/GaMqkd2UGgKQW41kqFmN1zxQtk7oy+UhGpADHTP8BP1ksF sgQq3DggwNPeG+m3AlaVjyqU0rO1v6x55J+X120RnlFRv16u4Pwqpl6io6hSLzarQ77X NLX5+Ic+xOwJ0ruIF17jyeRTQEv5KX+0rL58fJyhhR+0zNhqWlbaK6PqlTqeRAUkB1fm LKPaf4gqiaejc9jEP2g4LipP6jAypHni0JMNAT7qdAVbCyJE28ZdJsm4oWpyKACkG38c /w0YYAa1weTKSSX9luYLEt2Wdr4S4PHjW1o6AkXbkvnapQ8RB14P2zOCzpgeXeSAsSe9 HmQQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=3JilCyF71ezLJze8fqjJ0sZoMBaC3u+GKA3y5vuwlFQ=; b=w+Sm4zCAiGLtM6v0mo61mU+yQlt0rbJQihadTmz0Cd5Lxf6OuoNtLBw/T/WgQhBXEl Ke9HfYyc/nKYrBx/Jw7JBHB7EBld3rsVsjLa+be9o8pKLBQdrNvedxdtCnvj1CFaLGXP Yhy3lJBtshYp8EqVZ1+ioznAvVlze0MNKoBlBgT9ZYavIa/l9rMIZAq2VlK3xj0fi4XD BKxwLmLDKjYkpcbJvI/mR0aYVgvtAin7TBjtHrNbcj4eE+8Io94jBzo6xdHFMSgJBM41 wnOe3cI3grrBpPdheZcG1s55OqXySe/boHb8grTDAW0PcSVjpe4WKJNcTB7gmq74Srwx P0Mw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@microchip.com header.s=mchp header.b=pj61gaq8; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=microchip.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id na18-20020a17090b4c1200b00256df359e79si3373205pjb.33.2023.06.03.13.14.44; Sat, 03 Jun 2023 13:14:59 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@microchip.com header.s=mchp header.b=pj61gaq8; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=microchip.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231874AbjFCUJK (ORCPT <rfc822;stefanalexe802@gmail.com> + 99 others); Sat, 3 Jun 2023 16:09:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51552 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231881AbjFCUIq (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Sat, 3 Jun 2023 16:08:46 -0400 Received: from esa.microchip.iphmx.com (esa.microchip.iphmx.com [68.232.153.233]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B53FDE6F; Sat, 3 Jun 2023 13:07:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=microchip.com; i=@microchip.com; q=dns/txt; s=mchp; t=1685822875; x=1717358875; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=ZuPBRofcCh4+XxwWxNtafOL6nLRGQWKw7s1CYB0iMX4=; b=pj61gaq8411KE5xN35inJlgBXphmAOIFeGI4RupHoaAnDl/f+kHpAZey Bo9yYbE1ZwYXR0cw40odgOMXmfr8t5G4pchzDIVA645+kMC/uLbmqvcVq ip/7oDMSelhecGICjYMY2jEYu5NiJYdGyUfkSp+5SHOFqJDbjXTCIc4lu 9+eVAsqctR/LDsB8gQpVYF5gvIfzT+uXDwPJsCixhWjaNI/Uh7vcjpgFV uDJVmXlBHo0+UO06vYfrrcjsgapRGnOGDCvWy9Ra0raDGUFvzRPkAtOmp HouTib/VuZCG23iaPQ5zyjoY2d0gm2SbmMSbm/d00R+dGzCkW94sRjmfh w==; X-IronPort-AV: E=Sophos;i="6.00,216,1681196400"; d="scan'208";a="228308098" X-Amp-Result: SKIPPED(no attachment in message) Received: from unknown (HELO email.microchip.com) ([170.129.1.10]) by esa1.microchip.iphmx.com with ESMTP/TLS/AES256-SHA256; 03 Jun 2023 13:07:41 -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.21; Sat, 3 Jun 2023 13:07:41 -0700 Received: from che-lt-i67070.amer.actel.com (10.10.115.15) by chn-vm-ex04.mchp-main.com (10.10.85.152) with Microsoft SMTP Server id 15.1.2507.21 via Frontend Transport; Sat, 3 Jun 2023 13:07:27 -0700 From: Varshini Rajendran <varshini.rajendran@microchip.com> To: <tglx@linutronix.de>, <maz@kernel.org>, <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>, <nicolas.ferre@microchip.com>, <alexandre.belloni@bootlin.com>, <claudiu.beznea@microchip.com>, <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>, <gregkh@linuxfoundation.org>, <linux@armlinux.org.uk>, <mturquette@baylibre.com>, <sboyd@kernel.org>, <sre@kernel.org>, <broonie@kernel.org>, <varshini.rajendran@microchip.com>, <arnd@arndb.de>, <gregory.clement@bootlin.com>, <sudeep.holla@arm.com>, <balamanikandan.gunasundar@microchip.com>, <mihai.sain@microchip.com>, <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <netdev@vger.kernel.org>, <linux-usb@vger.kernel.org>, <linux-clk@vger.kernel.org>, <linux-pm@vger.kernel.org> CC: <Hari.PrasathGE@microchip.com>, <cristian.birsan@microchip.com>, <durai.manickamkr@microchip.com>, <manikandan.m@microchip.com>, <dharma.b@microchip.com>, <nayabbasha.sayed@microchip.com>, <balakrishnan.s@microchip.com> Subject: [PATCH 21/21] net: macb: add support for gmac to sam9x7 Date: Sun, 4 Jun 2023 01:32:43 +0530 Message-ID: <20230603200243.243878-22-varshini.rajendran@microchip.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20230603200243.243878-1-varshini.rajendran@microchip.com> References: <20230603200243.243878-1-varshini.rajendran@microchip.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Spam-Status: No, score=-4.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_PASS,SPF_NONE,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1767713852608888282?= X-GMAIL-MSGID: =?utf-8?q?1767713852608888282?= |
Series |
Add support for sam9x7 SoC family
|
|
Commit Message
Varshini Rajendran
June 3, 2023, 8:02 p.m. UTC
From: Nicolas Ferre <nicolas.ferre@microchip.com> Add support for GMAC in sam9x7 SoC family Signed-off-by: Varshini Rajendran <varshini.rajendran@microchip.com> Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com> --- drivers/net/ethernet/cadence/macb_main.c | 1 + 1 file changed, 1 insertion(+)
Comments
On 03/06/2023 22:02, Varshini Rajendran wrote: > From: Nicolas Ferre <nicolas.ferre@microchip.com> > > Add support for GMAC in sam9x7 SoC family > > Signed-off-by: Varshini Rajendran <varshini.rajendran@microchip.com> > Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com> > --- > drivers/net/ethernet/cadence/macb_main.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/net/ethernet/cadence/macb_main.c b/drivers/net/ethernet/cadence/macb_main.c > index 29a1199dad14..609c8e9305ba 100644 > --- a/drivers/net/ethernet/cadence/macb_main.c > +++ b/drivers/net/ethernet/cadence/macb_main.c > @@ -4913,6 +4913,7 @@ static const struct of_device_id macb_dt_ids[] = { > { .compatible = "microchip,mpfs-macb", .data = &mpfs_config }, > { .compatible = "microchip,sama7g5-gem", .data = &sama7g5_gem_config }, > { .compatible = "microchip,sama7g5-emac", .data = &sama7g5_emac_config }, > + { .compatible = "microchip,sam9x7-gem", .data = &sama7g5_gem_config }, These are compatible, aren't they? Why do you need new entry? Best regards, Krzysztof
On 05/06/2023 at 08:42, Krzysztof Kozlowski wrote: > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe > > On 03/06/2023 22:02, Varshini Rajendran wrote: >> From: Nicolas Ferre <nicolas.ferre@microchip.com> >> >> Add support for GMAC in sam9x7 SoC family >> >> Signed-off-by: Varshini Rajendran <varshini.rajendran@microchip.com> >> Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com> >> --- >> drivers/net/ethernet/cadence/macb_main.c | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/drivers/net/ethernet/cadence/macb_main.c b/drivers/net/ethernet/cadence/macb_main.c >> index 29a1199dad14..609c8e9305ba 100644 >> --- a/drivers/net/ethernet/cadence/macb_main.c >> +++ b/drivers/net/ethernet/cadence/macb_main.c >> @@ -4913,6 +4913,7 @@ static const struct of_device_id macb_dt_ids[] = { >> { .compatible = "microchip,mpfs-macb", .data = &mpfs_config }, >> { .compatible = "microchip,sama7g5-gem", .data = &sama7g5_gem_config }, >> { .compatible = "microchip,sama7g5-emac", .data = &sama7g5_emac_config }, >> + { .compatible = "microchip,sam9x7-gem", .data = &sama7g5_gem_config }, > > These are compatible, aren't they? Why do you need new entry? The hardware itself is different, even if the new features are not supported yet in the macb driver. The macb driver will certainly evolve in order to add these features so we decided to match a new compatible string all the way to the driver. Best regards, Nicolas
On Mon, Jun 5, 2023, at 14:07, Nicolas Ferre wrote: > On 05/06/2023 at 08:42, Krzysztof Kozlowski wrote: >>> >>> diff --git a/drivers/net/ethernet/cadence/macb_main.c b/drivers/net/ethernet/cadence/macb_main.c >>> index 29a1199dad14..609c8e9305ba 100644 >>> --- a/drivers/net/ethernet/cadence/macb_main.c >>> +++ b/drivers/net/ethernet/cadence/macb_main.c >>> @@ -4913,6 +4913,7 @@ static const struct of_device_id macb_dt_ids[] = { >>> { .compatible = "microchip,mpfs-macb", .data = &mpfs_config }, >>> { .compatible = "microchip,sama7g5-gem", .data = &sama7g5_gem_config }, >>> { .compatible = "microchip,sama7g5-emac", .data = &sama7g5_emac_config }, >>> + { .compatible = "microchip,sam9x7-gem", .data = &sama7g5_gem_config }, >> >> These are compatible, aren't they? Why do you need new entry? > > The hardware itself is different, even if the new features are not > supported yet in the macb driver. > The macb driver will certainly evolve in order to add these features so > we decided to match a new compatible string all the way to the driver. It sounds like you can still drop this patch though, and only add a specific entry here after the .data field is actually different when those features get added. The important bit for now is to have the specific string in the binding and in the dtb, along with the fallback for I assume "microchip,sama7g5-gem". Arnd
On 05/06/2023 14:07, Nicolas Ferre wrote: > On 05/06/2023 at 08:42, Krzysztof Kozlowski wrote: >> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe >> >> On 03/06/2023 22:02, Varshini Rajendran wrote: >>> From: Nicolas Ferre <nicolas.ferre@microchip.com> >>> >>> Add support for GMAC in sam9x7 SoC family >>> >>> Signed-off-by: Varshini Rajendran <varshini.rajendran@microchip.com> >>> Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com> >>> --- >>> drivers/net/ethernet/cadence/macb_main.c | 1 + >>> 1 file changed, 1 insertion(+) >>> >>> diff --git a/drivers/net/ethernet/cadence/macb_main.c b/drivers/net/ethernet/cadence/macb_main.c >>> index 29a1199dad14..609c8e9305ba 100644 >>> --- a/drivers/net/ethernet/cadence/macb_main.c >>> +++ b/drivers/net/ethernet/cadence/macb_main.c >>> @@ -4913,6 +4913,7 @@ static const struct of_device_id macb_dt_ids[] = { >>> { .compatible = "microchip,mpfs-macb", .data = &mpfs_config }, >>> { .compatible = "microchip,sama7g5-gem", .data = &sama7g5_gem_config }, >>> { .compatible = "microchip,sama7g5-emac", .data = &sama7g5_emac_config }, >>> + { .compatible = "microchip,sam9x7-gem", .data = &sama7g5_gem_config }, >> >> These are compatible, aren't they? Why do you need new entry? > > The hardware itself is different, even if the new features are not > supported yet in the macb driver. > The macb driver will certainly evolve in order to add these features so > we decided to match a new compatible string all the way to the driver. You claim to be fully compatible with sama7g5-gem, so adding new features does not warrant not-reusing old match entry now. Best regards, Krzysztof
diff --git a/drivers/net/ethernet/cadence/macb_main.c b/drivers/net/ethernet/cadence/macb_main.c index 29a1199dad14..609c8e9305ba 100644 --- a/drivers/net/ethernet/cadence/macb_main.c +++ b/drivers/net/ethernet/cadence/macb_main.c @@ -4913,6 +4913,7 @@ static const struct of_device_id macb_dt_ids[] = { { .compatible = "microchip,mpfs-macb", .data = &mpfs_config }, { .compatible = "microchip,sama7g5-gem", .data = &sama7g5_gem_config }, { .compatible = "microchip,sama7g5-emac", .data = &sama7g5_emac_config }, + { .compatible = "microchip,sam9x7-gem", .data = &sama7g5_gem_config }, { .compatible = "xlnx,zynqmp-gem", .data = &zynqmp_config}, { .compatible = "xlnx,zynq-gem", .data = &zynq_config }, { .compatible = "xlnx,versal-gem", .data = &versal_config},