From: Oleksij Rempel <o.rempel@pengutronix.de> To: Andrew Lunn <andrew@lunn.ch> Cc: "Marc Kleine-Budde" <mkl@pengutronix.de>, "Tony Lindgren" <tony@atomide.com>, linux-samsung-soc@vger.kernel.org, "Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>, bcm-kernel-feedback-list@broadcom.com, "Jakub Kicinski" <kuba@kernel.org>, devicetree@vger.kernel.org, "Nicolas Saenz Julienne" <nsaenz@kernel.org>, "Benoît Cousson" <bcousson@baylibre.com>, "Ray Jui" <rjui@broadcom.com>, "Sascha Hauer" <s.hauer@pengutronix.de>, "Rob Herring" <robh+dt@kernel.org>, linux-rpi-kernel@lists.infradead.org, linux-tegra@vger.kernel.org, "Florian Fainelli" <f.fainelli@gmail.com>, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, "Scott Branden" <sbranden@broadcom.com>, netdev@vger.kernel.org, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, kernel@pengutronix.de, "Shawn Guo" <shawnguo@kernel.org>, "David S. Miller" <davem@davemloft.net> Subject: Re: [PATCH v3 5/8] ARM: dts: exynos: fix ethernet node name for different odroid boards Date: Wed, 16 Feb 2022 07:15:29 +0100 [thread overview] Message-ID: <20220216061529.GA19299@pengutronix.de> (raw) In-Reply-To: <YgwTkr1UIGH6hgJ6@lunn.ch> On Tue, Feb 15, 2022 at 09:56:50PM +0100, Andrew Lunn wrote: > > > > - ethernet: usbether@2 { > > > > - compatible = "usb0424,9730"; > > > > + ethernet: ethernet@2 { > > > > + compatible = "usb424,9730"; > > > > > > The change of the compatible is not mentioned in the patch description. > > > Is this intentional? > > > > No, I forgot to mentione it. According to the USB schema 0 should be > > removed. So, this compatible was incorrect as well. With leading zero > > present yaml schema was not able to detect and validate this node. > > Does the current code not actually care about a leading 0? It will > match with or without it? It would be good to mention that as well in > the commit message, otherwise somebody like me is going to ask if this > breaks backwards compatibility, since normally compatible is an exact > string match. Current kernel code do not care about exact this compatibles. There is no driver matching against it. The USB Ethernet driver will take the node provided by the USB core drivers without validating the compatible against USB ID. See: drivers/usb/core/of.c drivers/usb/core/message.c:2093 On other hand, DT validations tools do care about it and this nodes was not detected automatically. I found it accidentally by grepping the sources. > And i actually think this is the sort of change which should be as a > patch of its own. If this causes a regression, a git bisect would then > tell you if it is the change of usbether -> ethernet, or 0424 to > 424. That is part of why we ask for lots of small changes. Sounds good, I'll update it. Regards, Oleksij -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
WARNING: multiple messages have this Message-ID (diff)
From: Oleksij Rempel <o.rempel@pengutronix.de> To: Andrew Lunn <andrew@lunn.ch> Cc: "Marc Kleine-Budde" <mkl@pengutronix.de>, "Tony Lindgren" <tony@atomide.com>, linux-samsung-soc@vger.kernel.org, "Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>, bcm-kernel-feedback-list@broadcom.com, "Jakub Kicinski" <kuba@kernel.org>, devicetree@vger.kernel.org, "Nicolas Saenz Julienne" <nsaenz@kernel.org>, "Benoît Cousson" <bcousson@baylibre.com>, "Ray Jui" <rjui@broadcom.com>, "Sascha Hauer" <s.hauer@pengutronix.de>, "Rob Herring" <robh+dt@kernel.org>, linux-rpi-kernel@lists.infradead.org, linux-tegra@vger.kernel.org, "Florian Fainelli" <f.fainelli@gmail.com>, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, "Scott Branden" <sbranden@broadcom.com>, netdev@vger.kernel.org, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, kernel@pengutronix.de, "Shawn Guo" <shawnguo@kernel.org>, "David S. Miller" <davem@davemloft.net> Subject: Re: [PATCH v3 5/8] ARM: dts: exynos: fix ethernet node name for different odroid boards Date: Wed, 16 Feb 2022 07:15:29 +0100 [thread overview] Message-ID: <20220216061529.GA19299@pengutronix.de> (raw) In-Reply-To: <YgwTkr1UIGH6hgJ6@lunn.ch> On Tue, Feb 15, 2022 at 09:56:50PM +0100, Andrew Lunn wrote: > > > > - ethernet: usbether@2 { > > > > - compatible = "usb0424,9730"; > > > > + ethernet: ethernet@2 { > > > > + compatible = "usb424,9730"; > > > > > > The change of the compatible is not mentioned in the patch description. > > > Is this intentional? > > > > No, I forgot to mentione it. According to the USB schema 0 should be > > removed. So, this compatible was incorrect as well. With leading zero > > present yaml schema was not able to detect and validate this node. > > Does the current code not actually care about a leading 0? It will > match with or without it? It would be good to mention that as well in > the commit message, otherwise somebody like me is going to ask if this > breaks backwards compatibility, since normally compatible is an exact > string match. Current kernel code do not care about exact this compatibles. There is no driver matching against it. The USB Ethernet driver will take the node provided by the USB core drivers without validating the compatible against USB ID. See: drivers/usb/core/of.c drivers/usb/core/message.c:2093 On other hand, DT validations tools do care about it and this nodes was not detected automatically. I found it accidentally by grepping the sources. > And i actually think this is the sort of change which should be as a > patch of its own. If this causes a regression, a git bisect would then > tell you if it is the change of usbether -> ethernet, or 0424 to > 424. That is part of why we ask for lots of small changes. Sounds good, I'll update it. Regards, Oleksij -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-02-16 6:15 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-15 8:09 [PATCH v3 1/8] dt-bindings: net: add schema for ASIX USB Ethernet controllers Oleksij Rempel 2022-02-15 8:09 ` Oleksij Rempel 2022-02-15 8:09 ` [PATCH v3 2/8] dt-bindings: net: add schema for Microchip/SMSC LAN95xx " Oleksij Rempel 2022-02-15 8:09 ` Oleksij Rempel 2022-02-15 8:09 ` [PATCH v3 3/8] dt-bindings: usb: ci-hdrc-usb2: fix node node for ethernet controller Oleksij Rempel 2022-02-15 8:09 ` Oleksij Rempel 2022-02-15 8:09 ` [PATCH v3 4/8] ARM: dts: bcm283x: fix ethernet node name Oleksij Rempel 2022-02-15 8:09 ` Oleksij Rempel 2022-02-15 21:01 ` Florian Fainelli 2022-02-15 21:01 ` Florian Fainelli 2022-02-16 7:16 ` Oleksij Rempel 2022-02-16 7:16 ` Oleksij Rempel 2022-02-15 8:09 ` [PATCH v3 5/8] ARM: dts: exynos: fix ethernet node name for different odroid boards Oleksij Rempel 2022-02-15 8:09 ` Oleksij Rempel 2022-02-15 8:12 ` Marc Kleine-Budde 2022-02-15 8:12 ` Marc Kleine-Budde 2022-02-15 8:16 ` Oleksij Rempel 2022-02-15 8:16 ` Oleksij Rempel 2022-02-15 20:56 ` Andrew Lunn 2022-02-15 20:56 ` Andrew Lunn 2022-02-16 6:15 ` Oleksij Rempel [this message] 2022-02-16 6:15 ` Oleksij Rempel 2022-02-15 8:28 ` Krzysztof Kozlowski 2022-02-15 8:28 ` Krzysztof Kozlowski 2022-02-15 8:09 ` [PATCH v3 6/8] ARM: dts: omap3/4/5: fix ethernet node name for different OMAP boards Oleksij Rempel 2022-02-15 8:09 ` Oleksij Rempel 2022-02-15 8:09 ` [PATCH v3 7/8] ARM: dts: tegra20/30: fix ethernet node name for different tegra boards Oleksij Rempel 2022-02-15 8:09 ` Oleksij Rempel 2022-02-15 8:09 ` [PATCH v3 8/8] arm64: dts: imx8mm-kontron: fix ethernet node name Oleksij Rempel 2022-02-15 8:09 ` Oleksij Rempel
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220216061529.GA19299@pengutronix.de \ --to=o.rempel@pengutronix.de \ --cc=andrew@lunn.ch \ --cc=bcm-kernel-feedback-list@broadcom.com \ --cc=bcousson@baylibre.com \ --cc=davem@davemloft.net \ --cc=devicetree@vger.kernel.org \ --cc=f.fainelli@gmail.com \ --cc=kernel@pengutronix.de \ --cc=krzysztof.kozlowski@canonical.com \ --cc=kuba@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=linux-rpi-kernel@lists.infradead.org \ --cc=linux-samsung-soc@vger.kernel.org \ --cc=linux-tegra@vger.kernel.org \ --cc=linux-usb@vger.kernel.org \ --cc=mkl@pengutronix.de \ --cc=netdev@vger.kernel.org \ --cc=nsaenz@kernel.org \ --cc=rjui@broadcom.com \ --cc=robh+dt@kernel.org \ --cc=s.hauer@pengutronix.de \ --cc=sbranden@broadcom.com \ --cc=shawnguo@kernel.org \ --cc=tony@atomide.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.