From: Grant Likely <firstname.lastname@example.org> To: Andrew Lunn <email@example.com>, Andy Shevchenko <firstname.lastname@example.org> Cc: Florian Fainelli <email@example.com>, Dan Callaghan <firstname.lastname@example.org>, Jeremy Linton <email@example.com>, Calvin Johnson <firstname.lastname@example.org>, Russell King <email@example.com>, Jon <firstname.lastname@example.org>, Cristi Sovaiala <email@example.com>, Ioana Ciornei <firstname.lastname@example.org>, Madalin Bucur <email@example.com>, netdev <firstname.lastname@example.org>, "linux.cj" <email@example.com>, linux-acpi <firstname.lastname@example.org>, nd <email@example.com>, Rob Herring <Rob.Herring@arm.com> Subject: Re: [net-next PATCH v7 1/6] Documentation: ACPI: DSD: Document MDIO PHY Date: Fri, 25 Sep 2020 14:22:52 +0100 Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <20200731151444.GI1712415@lunn.ch> On 31/07/2020 16:14, Andrew Lunn wrote: >>>> DT can be used on x86, and i suspect it is a much easier path of least >>>> resistance. >>> >>> And you can easily overlay Device Tree to an existing system by using >>> either a full Device Tree overlay (dtbo) or using CONFIG_OF_DYNAMIC and >>> creating nodes on the fly. >> >> Why do you need DT on a system that runs without it and Linux has all >> means to extend to cover a lot of stuff DT provides for other types of >> firmware nodes? > > As i said, path of least resistance. It is here today, heavily used, > well understood by lots of network developers, has a very active > maintainer in the form of Rob Herring, and avoids 'showflakes' as > Florian likes to call it, so we are all sharing the same code, > providing a lot of testing and maintenance. > > Andrew Hi Andrew, I'm just coming into this thread now. With my alumni DT-maintainer had on I think that trying to use ACPI & DT on the same system is the worst of both worlds. Trying to do so makes the solution far more complicated than either an ACPI-only or DT-only approach. There is no good way for references between DT & ACPI nodes. I have serious doubts about the reliability of the dynamic DT code in the kernel. Perhaps most problematic is it excludes platform specific data from the ACPI description provided by firmware, which means platform-specific data needs to be shipped with the OS. Rather defeats the whole point of firmware providing the platform description. An ACPI solution is absolutely needed. Regarding this specific series, I think it is approximately the right approach. I have some specific concerns that I've talked with Calvin about and I'm going to post as replies to the individual patches. My most significant concern is the reference from the ACPI MAC node to the MDIO node, which makes little sense. The MAC should have a reference to the PHY node. There have been other issues raised in this thread. I'm going to go back and respond to a few of those points in separate emails, but as a larger issue I think there is a fair bit of misunderstanding on what ACPI does and does not do, and how much is expected to be standardized in ACPI specs. In the ACPI world the typical model is the firmware/platform vendor decides what data to put into the ACPI nodes that works for them, and then the OS just has to deal with it. Linux typically never gets a choice about what goes into ACPI nodes. Already, threads like this one are setting the bar *far* higher on ACPI schema than has ever been done before. I do think it is right to be asking for a common data model for describing PHY connections. Lining the model up with the DT PHY model is also valuable because we can use common code. I also think as first through the door, what gets accepted (after review) for the layerscape platforms here should become the defacto standard that other vendors are expected to adopt, and I have very high confidence that it will be acceptable because it follow the pattern already used in devicetree. Cheers, g.
next prev parent reply index Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-15 9:03 [net-next PATCH v7 0/6] ACPI support for dpaa2 MAC driver Calvin Johnson 2020-07-15 9:03 ` [net-next PATCH v7 1/6] Documentation: ACPI: DSD: Document MDIO PHY Calvin Johnson 2020-07-16 3:04 ` Florian Fainelli 2020-07-16 3:11 ` Andrew Lunn 2020-07-23 23:26 ` Jeremy Linton 2020-07-24 13:39 ` Andrew Lunn 2020-07-24 17:26 ` Jeremy Linton 2020-07-24 17:39 ` Florian Fainelli 2020-07-24 19:20 ` Andrew Lunn 2020-07-24 20:12 ` Andy Shevchenko 2020-07-24 20:13 ` Florian Fainelli 2020-07-24 20:20 ` Andy Shevchenko 2020-07-25 7:36 ` Calvin Johnson 2020-07-25 10:48 ` Andy Shevchenko 2020-07-24 21:06 ` Russell King - ARM Linux admin 2020-07-27 17:03 ` Sudeep Holla 2020-07-24 19:14 ` Andrew Lunn 2020-07-27 17:21 ` Sudeep Holla 2020-07-28 20:34 ` Andrew Lunn 2020-07-28 20:59 ` Russell King - ARM Linux admin 2020-07-28 21:26 ` Andy Shevchenko 2020-07-29 16:00 ` Rafael J. Wysocki 2020-07-31 15:08 ` Andrew Lunn 2020-07-27 17:32 ` Jon Nettleton [not found] ` <email@example.com> 2020-07-28 20:45 ` Andrew Lunn 2020-07-28 20:56 ` Florian Fainelli 2020-07-28 21:28 ` Andy Shevchenko 2020-07-28 21:40 ` Florian Fainelli 2020-07-31 15:14 ` Andrew Lunn 2020-09-25 13:22 ` Grant Likely [this message] 2020-07-28 22:30 ` Jeremy Linton 2020-07-29 0:39 ` Florian Fainelli 2020-07-29 2:53 ` Jeremy Linton 2020-07-29 3:16 ` Florian Fainelli 2020-07-29 8:43 ` Jon Nettleton 2020-07-29 9:39 ` Calvin Johnson 2020-09-25 13:34 ` Grant Likely 2020-09-26 4:30 ` Calvin Johnson 2020-09-29 5:17 ` Calvin Johnson 2020-09-29 13:43 ` Andrew Lunn 2020-09-29 13:55 ` Andy Shevchenko 2020-09-29 14:32 ` Andrew Lunn 2020-09-29 14:46 ` Andy Shevchenko 2020-09-29 15:06 ` Andrew Lunn 2020-09-29 15:29 ` Arnd Bergmann 2020-09-29 14:44 ` Arnd Bergmann 2020-09-29 14:59 ` Andrew Lunn 2020-09-29 15:59 ` Grant Likely 2020-09-29 15:53 ` Grant Likely 2020-09-29 16:04 ` Calvin Johnson 2020-07-15 9:03 ` [net-next PATCH v7 2/6] net: phy: introduce device_mdiobus_register() Calvin Johnson 2020-07-16 3:05 ` Florian Fainelli 2020-07-15 9:03 ` [net-next PATCH v7 3/6] net/fsl: use device_mdiobus_register() Calvin Johnson 2020-07-16 3:05 ` Florian Fainelli 2020-07-15 9:03 ` [net-next PATCH v7 4/6] net: phy: introduce phy_find_by_mdio_handle() Calvin Johnson 2020-07-16 3:06 ` Florian Fainelli 2020-07-15 9:03 ` [net-next PATCH v7 5/6] phylink: introduce phylink_fwnode_phy_connect() Calvin Johnson 2020-07-15 9:04 ` [net-next PATCH v7 6/6] net: dpaa2-mac: Add ACPI support for DPAA2 MAC driver Calvin Johnson 2020-09-25 13:39 ` [net-next PATCH v7 0/6] ACPI support for dpaa2 " Grant Likely 2020-09-26 4:34 ` Calvin Johnson 2020-07-25 14:23 Calvin Johnson 2020-07-25 14:23 ` [net-next PATCH v7 1/6] Documentation: ACPI: DSD: Document MDIO PHY Calvin Johnson
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 \ --firstname.lastname@example.org \ --email@example.com \ --cc=Rob.Herring@arm.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ /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: link
Linux-ACPI Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-acpi/0 linux-acpi/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-acpi linux-acpi/ https://lore.kernel.org/linux-acpi \ email@example.com public-inbox-index linux-acpi Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-acpi AGPL code for this site: git clone https://public-inbox.org/public-inbox.git