[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200131144737.GA4948@willie-the-truck>
Date: Fri, 31 Jan 2020 14:47:38 +0000
From: Will Deacon <will@...nel.org>
To: Andrew Lunn <andrew@...n.ch>
Cc: Robin Murphy <robin.murphy@....com>,
Jon Nettleton <jon@...id-run.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Marc Zyngier <maz@...nel.org>,
Makarand Pawagi <makarand.pawagi@....com>,
Calvin Johnson <calvin.johnson@....com>, stuyoder@...il.com,
nleeder@...eaurora.org, Ioana Ciornei <ioana.ciornei@....com>,
Cristi Sovaiala <cristian.sovaiala@....com>,
Hanjun Guo <guohanjun@...wei.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Pankaj Bansal <pankaj.bansal@....com>,
Russell King <linux@...linux.org.uk>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Len Brown <lenb@...nel.org>,
Jason Cooper <jason@...edaemon.net>,
Andy Wang <Andy.Wang@....com>, Varun Sethi <V.Sethi@....com>,
Thomas Gleixner <tglx@...utronix.de>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Laurentiu Tudor <laurentiu.tudor@....com>,
Paul Yang <Paul.Yang@....com>,
"<netdev@...r.kernel.org>" <netdev@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Shameerali Kolothum Thodi
<shameerali.kolothum.thodi@...wei.com>,
Sudeep Holla <sudeep.holla@....com>
Subject: Re: [EXT] Re: [PATCH] bus: fsl-mc: Add ACPI support for fsl-mc
On Fri, Jan 31, 2020 at 03:29:06PM +0100, Andrew Lunn wrote:
> > > But by design SFP, SFP+, and QSFP cages are not fixed function network
> > > adapters. They are physical and logical devices that can adapt to
> > > what is plugged into them. How the devices are exposed should be
> > > irrelevant to this conversation it is about the underlying
> > > connectivity.
> >
> > Apologies - I was under the impression that SFP and friends were a
> > physical-layer thing and that a MAC in the SoC would still be fixed such
> > that its DMA and interrupt configuration could be statically described
> > regardless of what transceiver was plugged in (even if some configurations
> > might not use every interrupt/stream ID/etc.) If that isn't the case I shall
> > go and educate myself further.
>
> It gets interesting with QSFP cages. The Q is quad, there are 4 SERDES
> lanes. You can use them for 1x 40G link, or you can split them into 4x
> 10G links. So you either need one MAC or 4 MACs connecting to the
> cage, and this can change on the fly when a modules is ejected and
> replaced with another module. There are only one set of control pins
> for i2c, loss of signal, TX disable, module inserted. So where the
> interrupt/stream ID/etc are mapped needs some flexibility.
>
> There is also to some degree a conflict with hiding all this inside
> firmware. This is complex stuff. It is much better to have one core
> implementing in Linux plus some per hardware driver support, than
> having X firmware blobs, generally closed source, each with there own
> bugs which nobody can fix.
Devicetree to the rescue!
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?
Will
Powered by blists - more mailing lists