[RFC PATCH v2 1/4] dt-bindings: misc: Add bindings for misc. BMC control fields
Benjamin Herrenschmidt
benh at kernel.crashing.org
Fri Jul 20 14:56:13 AEST 2018
On Fri, 2018-07-20 at 09:37 +0930, Andrew Jeffery wrote:
> >
> > Andrew, can you start with a list that shows what you expect us to need
> > on our systems ?
> >
>
> Okay, our Witherspoon and Romulus platforms containing the ASPEED AST2500 currently need the following tuneables exposed:
>
> > From the SCU:
>
> - Debug UART enable
> - VGA DAC mux
> - VGA scratch registers 0-7
> - LPC SuperIO decode enable
> - VGA MMIO decode enable
>
> > From the LPC controller:
>
> - iLPC2AHB enable
> - SuperIO scratch registers 0x20-0x2f
>
> (The LPC controller is just as much of a collection of random bits as the SCU)
>
> Lastly, our Palmetto platform uses an AST2400 which has fewer features compared to the AST2500. Its tuneable list is the same as the above with the exception of "Debug UART enable".
>
> Tuneables that we may need to expose in the future include:
>
> > From the SCU:
>
> - PCI VID/DID for the BMC PCIe device
> - VGA device enable (may need to be disabled if the platform contains a discrete graphics processor)
Additionally there's a bunch of resigters controlling the mapping of
various MMIO regions of the BMC PCIe device to portions of the BMC
address space. I'm not sure what's the best way to handle that.
This specific set might require a dedicated device as a subnode of
the SCU in the DT that contains all the mappings as properties...
That or we consider them static enough and just whack it in u-boot.
> > From the LPC controller:
>
> - UART mux
>
> Alexander, Eugene, can you chime in with your platforms' needs?
>
> Cheers,
>
> Andrew
More information about the openbmc
mailing list