Hi Nick, good to see all this stuff coming mainline, On Wed, Feb 02, 2022 at 10:52:50AM -0600, nick.hawkins@xxxxxxx wrote: > From: Nick Hawkins <nick.hawkins@xxxxxxx> > > GXP is the name of the HPE SoC. > This SoC is used to implement BMC features of HPE servers > (all ProLiant, Synergy, and many Apollo, and Superdome machines) > It does support many features including: > ARMv7 architecture, and it is based on a Cortex A9 core > Use an AXI bus to which > a memory controller is attached, as well as > multiple SPI interfaces to connect boot flash, > and ROM flash, a 10/100/1000 Mac engine which > supports SGMII (2 ports) and RMII > Multiple I2C engines to drive connectivity with a host infrastructure > A video engine which support VGA and DP, as well as > an hardware video encoder > Multiple PCIe ports > A PECI interface, and LPC eSPI > Multiple UART for debug purpose, and Virtual UART for host connectivity > A GPIO engine > This Patch Includes: > Documentation for device tree bindings > Device Tree Bindings > GXP Timer Support > GXP Architecture Support > > Signed-off-by: Nick Hawkins <nick.hawkins@xxxxxxx> > --- > .../bindings/display/hpe,gxp-thumbnail.txt | 21 + > .../devicetree/bindings/gpio/hpe,gxp-gpio.txt | 16 + ... All new bindings must be in the DT-schema format (yaml files). This enables a lot of syntax checks and validation. We are slowly migrating away from the .txt based bindings. Also, for new bindings please follow the guide lines listed in Documentation/devicetree/bindings/submitting-patches.rst Consider including the bindings with the drivers using the bindings so things have a more natural split. Sam
