> .../bindings/display/hpe,gxp-thumbnail.txt| 21 +
> .../devicetree/bindings/gpio/hpe,gxp-gpio.txt | 16 +
> .../devicetree/bindings/i2c/hpe,gxp-i2c.txt | 19 +
> .../bindings/ipmi/hpegxp-kcs-bmc-cfg.txt | 13 +
> .../bindings/ipmi/hpegxp-kcs-bmc.txt | 21 +
Hi Nick
In
On Wed, Feb 02, 2022 at 06:14:57PM +, Verdun, Jean-Marie wrote:
> > This is far too big for a single patch. It needs to be broken into
> > functional chunks that can be reviewed individually. Each driver and
> > each device tree change along with it's accompanying code need to be
> > done in
On Wed, Feb 2, 2022 at 7:14 PM Verdun, Jean-Marie wrote:
>
> > This is far too big for a single patch. It needs to be broken into
> > functional chunks that can be reviewed individually. Each driver and
> > each device tree change along with it's accompanying code need to be
> > done in
> Maybe it does not look like, but this is actually a v2. Nick was asked
> to change the naming for the nodes already in v1. Unfortunately it did
> not happen, so we have vuart, spifi, vic and more.
> It is a waste of reviewers' time to ask them to perform the same review
> twice
On 02/02/2022 17:52, nick.hawk...@hpe.com wrote:
> From: Nick Hawkins
>
> 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
On 03/02/2022 15:29, Rob Herring wrote:
> On Wed, Feb 2, 2022 at 10:55 AM wrote:
>>
>> From: Nick Hawkins
>>
(...)
>> +
>> + vuart_a: vuart_a@80fd0200 {
>
> serial@...
Maybe it does not look like, but this is actually a v2. Nick was asked
to change the naming for the nodes already in
