netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Heiner Kallweit <hkallweit1@gmail.com>,
	Madalin-cristian Bucur <madalin.bucur@nxp.com>,
	Shawn Guo <shawnguo@kernel.org>, Li Yang <leoyang.li@nxp.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>, Andrew Lunn <andrew@lunn.ch>,
	David Miller <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH net-next 2/2] net: phy: aquantia: add USXGMII support
Date: Wed, 22 May 2019 13:29:45 -0700	[thread overview]
Message-ID: <abdf67f6-3b7b-fab4-ed7c-779f5685ab58@gmail.com> (raw)
In-Reply-To: <e7a7c38c-ebe7-1cea-4099-3cf3a4483ac7@gmail.com>

On 5/22/19 1:18 PM, Heiner Kallweit wrote:
> On 22.05.2019 22:07, Florian Fainelli wrote:
>> On 5/22/19 12:58 PM, Heiner Kallweit wrote:
>>> So far we didn't support mode USXGMII, and in order to not break the
>>> two Freescale boards mode XGMII was accepted for the AQR107 family
>>> even though it doesn't support XGMII. Add USXGMII support to the
>>> Aquantia PHY driver and change the phy connection type for the two
>>> boards.
>>>
>>> As an additional note: Even though the handle is named aqr106
>>> there seem to be LS1046A boards with an AQR107.
>>>
>>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>>
>> You can probably split the DTS changes and the PHY driver changes into a
>> separate commits and just have the DTS changes come last? With that:
>>
> To split the patches I would have to do:
> 1. Add USXGMII support to Aquantia PHY driver
> 2. DTS changes
> 3. Don't accept XGMII any longer in Aquantia PHY driver
> This seemed to me to be too much overhead considering the very small
> change.
> 
> Just making the DTS changes a separate patch would break bisecting.

I fail to see how, you can't make use of "usxgmii" in DTS unless you
define that as as a valid phy-mode property value (patch #1), and you
can't have that possibly working until patch #2. Until then using
"xgmii" is still supported and going to work.

Once patch #3 which brings DTS lands in, you could possibly deprecate
"xgmii" in the Aquantia PHY driver (or rather issue a big warning).
-- 
Florian

  reply	other threads:[~2019-05-22 20:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22 19:56 [PATCH net-next 0/2] net: phy: add interface mode PHY_INTERFACE_MODE_USXGMII Heiner Kallweit
2019-05-22 19:57 ` [PATCH net-next 1/2] " Heiner Kallweit
2019-05-22 20:06   ` Florian Fainelli
2019-05-22 20:20     ` Heiner Kallweit
2019-05-22 19:58 ` [PATCH net-next 2/2] net: phy: aquantia: add USXGMII support Heiner Kallweit
2019-05-22 20:07   ` Florian Fainelli
2019-05-22 20:18     ` Heiner Kallweit
2019-05-22 20:29       ` Florian Fainelli [this message]
2019-05-22 20:58   ` Andrew Lunn
2019-05-23  4:08     ` Heiner Kallweit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=abdf67f6-3b7b-fab4-ed7c-779f5685ab58@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=hkallweit1@gmail.com \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=madalin.bucur@nxp.com \
    --cc=mark.rutland@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).