From: Andrew Lunn <andrew@lunn.ch> To: Will Deacon <will@kernel.org> Cc: Robin Murphy <robin.murphy@arm.com>, Jon Nettleton <jon@solid-run.com>, Ard Biesheuvel <ard.biesheuvel@linaro.org>, Marc Zyngier <maz@kernel.org>, Makarand Pawagi <makarand.pawagi@nxp.com>, Calvin Johnson <calvin.johnson@nxp.com>, stuyoder@gmail.com, nleeder@codeaurora.org, Ioana Ciornei <ioana.ciornei@nxp.com>, Cristi Sovaiala <cristian.sovaiala@nxp.com>, Hanjun Guo <guohanjun@huawei.com>, Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>, Pankaj Bansal <pankaj.bansal@nxp.com>, Russell King <linux@armlinux.org.uk>, ACPI Devel Maling List <linux-acpi@vger.kernel.org>, Len Brown <lenb@kernel.org>, Jason Cooper <jason@lakedaemon.net>, Andy Wang <Andy.Wang@arm.com>, Varun Sethi <V.Sethi@nxp.com>, Thomas Gleixner <tglx@linutronix.de>, linux-arm-kernel <linux-arm-kernel@lists.infradead.org>, Laurentiu Tudor <laurentiu.tudor@nxp.com>, Paul Yang <Paul.Yang@arm.com>, "<netdev@vger.kernel.org>" <netdev@vger.kernel.org>, "Rafael J. Wysocki" <rjw@rjwysocki.net>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>, Sudeep Holla <sudeep.holla@arm.com> Subject: Re: [EXT] Re: [PATCH] bus: fsl-mc: Add ACPI support for fsl-mc Date: Fri, 31 Jan 2020 16:09:29 +0100 [thread overview] Message-ID: <20200131150929.GB13902@lunn.ch> (raw) In-Reply-To: <20200131144737.GA4948@willie-the-truck> > Devicetree to the rescue! Yes, exactly. We have good, standardised descriptions for most of this in device tree. And phylink can handle SFP and SFP+. Nobody has worked on QSFP yet, since phylink has mostly been pushed by the embedded world and 40G is not yet popular in the embedded world. > Entertaining the use of ACPI without any firmware abstraction for this > hardware really feels like a square peg / round hole situation, so I'm > assuming somebody's telling you that you need it "FOAR ENTAPRYZE". Who > is it and can you tell them to bog off? The issues here is that SFPs are appearing in more and more server systems, replacing plain old copper Ethernet. If the boxes use off the shelf Mellanox or Intel PCIe cards, it is not an issue. But silicon vendors are integrating this into the SoC in the ARM way of doing things, memory mapped, spread over a number of controllers, not a single PCIe device. Maybe we need hybrid systems. Plain, old, simple, boring things like CPUs, serial ports, SATA, PCIe busses are described in ACPI. Complex interesting things are in DT. The hard thing is the interface between the two. DT having a phandle to an ACPI object, e.g a GPIO, interrupt or an i2c bus. Andrew
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch> To: Will Deacon <will@kernel.org> Cc: Calvin Johnson <calvin.johnson@nxp.com>, stuyoder@gmail.com, nleeder@codeaurora.org, Ioana Ciornei <ioana.ciornei@nxp.com>, Cristi Sovaiala <cristian.sovaiala@nxp.com>, Hanjun Guo <guohanjun@huawei.com>, Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>, Marc Zyngier <maz@kernel.org>, Pankaj Bansal <pankaj.bansal@nxp.com>, Jon Nettleton <jon@solid-run.com>, Russell King <linux@armlinux.org.uk>, ACPI Devel Maling List <linux-acpi@vger.kernel.org>, Len Brown <lenb@kernel.org>, Jason Cooper <jason@lakedaemon.net>, Andy Wang <Andy.Wang@arm.com>, Makarand Pawagi <makarand.pawagi@nxp.com>, Varun Sethi <V.Sethi@nxp.com>, Thomas Gleixner <tglx@linutronix.de>, linux-arm-kernel <linux-arm-kernel@lists.infradead.org>, Laurentiu Tudor <laurentiu.tudor@nxp.com>, Paul Yang <Paul.Yang@arm.com>, Ard Biesheuvel <ard.biesheuvel@linaro.org>, "<netdev@vger.kernel.org>" <netdev@vger.kernel.org>, "Rafael J. Wysocki" <rjw@rjwysocki.net>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>, Sudeep Holla <sudeep.holla@arm.com>, Robin Murphy <robin.murphy@arm.com> Subject: Re: [EXT] Re: [PATCH] bus: fsl-mc: Add ACPI support for fsl-mc Date: Fri, 31 Jan 2020 16:09:29 +0100 [thread overview] Message-ID: <20200131150929.GB13902@lunn.ch> (raw) In-Reply-To: <20200131144737.GA4948@willie-the-truck> > Devicetree to the rescue! Yes, exactly. We have good, standardised descriptions for most of this in device tree. And phylink can handle SFP and SFP+. Nobody has worked on QSFP yet, since phylink has mostly been pushed by the embedded world and 40G is not yet popular in the embedded world. > Entertaining the use of ACPI without any firmware abstraction for this > hardware really feels like a square peg / round hole situation, so I'm > assuming somebody's telling you that you need it "FOAR ENTAPRYZE". Who > is it and can you tell them to bog off? The issues here is that SFPs are appearing in more and more server systems, replacing plain old copper Ethernet. If the boxes use off the shelf Mellanox or Intel PCIe cards, it is not an issue. But silicon vendors are integrating this into the SoC in the ARM way of doing things, memory mapped, spread over a number of controllers, not a single PCIe device. Maybe we need hybrid systems. Plain, old, simple, boring things like CPUs, serial ports, SATA, PCIe busses are described in ACPI. Complex interesting things are in DT. The hard thing is the interface between the two. DT having a phandle to an ACPI object, e.g a GPIO, interrupt or an i2c bus. Andrew _______________________________________________ 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:[~2020-01-31 15:09 UTC|newest] Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-01-28 8:08 [PATCH] bus: fsl-mc: Add ACPI support for fsl-mc Makarand Pawagi 2020-01-28 8:08 ` Makarand Pawagi 2020-01-28 10:58 ` Marc Zyngier 2020-01-28 10:58 ` Marc Zyngier 2020-01-28 11:09 ` Lorenzo Pieralisi 2020-01-28 11:09 ` Lorenzo Pieralisi 2020-01-31 10:35 ` [EXT] " Makarand Pawagi 2020-01-31 10:35 ` Makarand Pawagi 2020-01-31 11:06 ` Lorenzo Pieralisi 2020-01-31 11:06 ` Lorenzo Pieralisi 2020-01-31 11:06 ` Marc Zyngier 2020-01-31 11:06 ` Marc Zyngier 2020-01-31 12:01 ` Ard Biesheuvel 2020-01-31 12:01 ` Ard Biesheuvel 2020-01-31 12:28 ` Jon Nettleton 2020-01-31 12:28 ` Jon Nettleton 2020-01-31 12:48 ` Robin Murphy 2020-01-31 12:48 ` Robin Murphy 2020-01-31 13:11 ` Jon Nettleton 2020-01-31 13:11 ` Jon Nettleton 2020-01-31 13:29 ` Ard Biesheuvel 2020-01-31 13:29 ` Ard Biesheuvel 2020-01-31 13:39 ` Robin Murphy 2020-01-31 13:39 ` Robin Murphy 2020-01-31 14:29 ` Andrew Lunn 2020-01-31 14:29 ` Andrew Lunn 2020-01-31 14:47 ` Will Deacon 2020-01-31 14:47 ` Will Deacon 2020-01-31 15:09 ` Andrew Lunn [this message] 2020-01-31 15:09 ` Andrew Lunn 2020-01-31 15:14 ` Jon Nettleton 2020-01-31 15:14 ` Jon Nettleton 2020-01-31 15:41 ` Andrew Lunn 2020-01-31 15:41 ` Andrew Lunn 2020-01-31 15:39 ` Russell King - ARM Linux admin 2020-01-31 15:39 ` Russell King - ARM Linux admin 2020-01-31 15:15 ` Russell King - ARM Linux admin 2020-01-31 15:15 ` Russell King - ARM Linux admin 2020-01-31 15:40 ` Jakub Kicinski 2020-01-31 15:40 ` Jakub Kicinski 2020-02-01 11:49 ` Russell King - ARM Linux admin 2020-02-01 11:49 ` Russell King - ARM Linux admin 2020-02-01 17:36 ` Jakub Kicinski 2020-02-01 17:36 ` Jakub Kicinski 2020-02-14 15:05 ` Pankaj Bansal 2020-02-14 15:05 ` Pankaj Bansal 2020-02-14 15:54 ` Marc Zyngier 2020-02-14 15:54 ` Marc Zyngier 2020-02-14 15:58 ` Pankaj Bansal 2020-02-14 15:58 ` Pankaj Bansal 2020-02-14 16:19 ` Lorenzo Pieralisi 2020-02-14 16:19 ` Lorenzo Pieralisi 2020-02-14 16:35 ` Pankaj Bansal 2020-02-14 16:35 ` Pankaj Bansal 2020-02-14 17:49 ` Lorenzo Pieralisi 2020-02-14 17:49 ` Lorenzo Pieralisi 2020-02-17 12:35 ` Pankaj Bansal 2020-02-17 12:35 ` Pankaj Bansal 2020-02-17 15:25 ` Lorenzo Pieralisi 2020-02-17 15:25 ` Lorenzo Pieralisi 2020-02-17 15:35 ` Marc Zyngier 2020-02-17 15:35 ` Marc Zyngier 2020-02-17 16:26 ` Lorenzo Pieralisi 2020-02-17 16:26 ` Lorenzo Pieralisi 2020-02-18 8:02 ` Pankaj Bansal (OSS) 2020-02-18 8:02 ` Pankaj Bansal (OSS) 2020-02-14 16:29 ` Robin Murphy 2020-02-14 16:29 ` Robin Murphy
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=20200131150929.GB13902@lunn.ch \ --to=andrew@lunn.ch \ --cc=Andy.Wang@arm.com \ --cc=Paul.Yang@arm.com \ --cc=V.Sethi@nxp.com \ --cc=ard.biesheuvel@linaro.org \ --cc=calvin.johnson@nxp.com \ --cc=cristian.sovaiala@nxp.com \ --cc=guohanjun@huawei.com \ --cc=ioana.ciornei@nxp.com \ --cc=jason@lakedaemon.net \ --cc=jon@solid-run.com \ --cc=laurentiu.tudor@nxp.com \ --cc=lenb@kernel.org \ --cc=linux-acpi@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=lorenzo.pieralisi@arm.com \ --cc=makarand.pawagi@nxp.com \ --cc=maz@kernel.org \ --cc=netdev@vger.kernel.org \ --cc=nleeder@codeaurora.org \ --cc=pankaj.bansal@nxp.com \ --cc=rjw@rjwysocki.net \ --cc=robin.murphy@arm.com \ --cc=shameerali.kolothum.thodi@huawei.com \ --cc=stuyoder@gmail.com \ --cc=sudeep.holla@arm.com \ --cc=tglx@linutronix.de \ --cc=will@kernel.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: 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.