Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Sat, 16 Jul 2022 20:17:32 +0200
From:   Andrew Lunn <andrew@lunn.ch>
To:     Sean Anderson <sean.anderson@seco.com>
Cc:     "David S . Miller" <davem@davemloft.net>,
        Jakub Kicinski <kuba@kernel.org>,
        Madalin Bucur <madalin.bucur@nxp.com>, netdev@vger.kernel.org,
        Paolo Abeni <pabeni@redhat.com>,
        Eric Dumazet <edumazet@google.com>,
        linux-arm-kernel@lists.infradead.org,
        Russell King <linux@armlinux.org.uk>,
        linux-kernel@vger.kernel.org,
        Alexandru Marginean <alexandru.marginean@nxp.com>,
        Heiner Kallweit <hkallweit1@gmail.com>,
        Vladimir Oltean <olteanv@gmail.com>
Subject: Re: [PATCH net-next v3 12/47] net: phy: aquantia: Add support for
 AQR115
Message-ID: <YtMAvHXuI76cTLAj@lunn.ch>
References: <20220715215954.1449214-1-sean.anderson@seco.com>
 <20220715215954.1449214-13-sean.anderson@seco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20220715215954.1449214-13-sean.anderson@seco.com>
Precedence: bulk

On Fri, Jul 15, 2022 at 05:59:19PM -0400, Sean Anderson wrote:
> This adds support for the AQR115 (which I have on my LS1046A RDB). I had a
> quick look over the registers, and it seems to be compatible with the
> AQR107. I couldn't find this oui anywhere, but that's what I have on my
> board. It's possible that NXP used a substitute here; I can't confirm
> the part number since there is a heatsink on top of the phy.

If i remember correctly, the OUI can be part of the provisioning for
Aquantia PHYs. And i think there is often per board provisioning,
specially for the SERDEs configuration. So aQuantia/Marvell probably
set this OUI, but maybe at NXP request.

Did you get the part number from the schematic? That should be enough
to confirm it is a AQR115.

> To avoid breaking <10G ethernet on the LS1046ARDB, we must add this
> vendor id as an exception to dpaa_phy_init. This will be removed once
> the DPAA driver is converted to phylink.

I suggest you split this into two. The PHY changes can be merged right
away, and is independent of the DPAA. Given the size of this patchset,
the more you can split it up into parallel submissions the better. So
please submit the PHY patches independent of the rest.

> Signed-off-by: Sean Anderson <sean.anderson@seco.com>

For the aquantia_main.c change only:

Reviewed-by: Andrew Lunn <andrew@lunn.ch>

    Andrew