linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Claudiu.Beznea@microchip.com>
To: <Codrin.Ciubotariu@microchip.com>, <netdev@vger.kernel.org>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Cc: <Nicolas.Ferre@microchip.com>, <davem@davemloft.net>,
	<kuba@kernel.org>, <andrew@lunn.ch>, <f.fainelli@gmail.com>,
	<robh+dt@kernel.org>, <alexandre.belloni@bootlin.com>,
	<Ludovic.Desroches@microchip.com>
Subject: Re: [PATCH net-next v2 0/7] Add an MDIO sub-node under MACB
Date: Thu, 23 Jul 2020 07:51:48 +0000	[thread overview]
Message-ID: <8a78218a-9fbe-889d-8501-ad67ccb6e59b@microchip.com> (raw)
In-Reply-To: <7cab13f6-ac54-8f5c-c1bf-35e6c3b5d9db@microchip.com>



On 22.07.2020 14:38, Codrin Ciubotariu - M19940 wrote:
> On 22.07.2020 13:32, Claudiu Beznea - M18063 wrote:
>>
>>
>> On 21.07.2020 20:13, Codrin Ciubotariu wrote:
>>> Adding the PHY nodes directly under the Ethernet node became deprecated,
>>> so the aim of this patch series is to make MACB use an MDIO node as
>>> container for MDIO devices.
>>> This patch series starts with a small patch to use the device-managed
>>> devm_mdiobus_alloc(). In the next two patches we update the bindings and
>>> adapt macb driver to parse the device-tree PHY nodes from under an MDIO
>>> node. The last patches add the MDIO node in the device-trees of sama5d2,
>>> sama5d3, samad4 and sam9x60 boards.
>>>
>>
>> Tested this series on sama5d2_xplained in the following scenarios:
>>
>> 1/ PHY bindings from patch 4/7:
>> mdio {
>> 	#address-cells = <1>;
>> 	#size-cells = <0>;
>> 	ethernet-phy@1 {
>> 		reg = <0x1>;
>> 		interrupt-parent = <&pioA>;
>> 		interrupts = <PIN_PC9 IRQ_TYPE_LEVEL_LOW>;
>> };
>>
>> 2/ PHY bindings before this series:
>> ethernet-phy@1 {
>> 	reg = <0x1>;
>> 	interrupt-parent = <&pioA>;
>> 	interrupts = <PIN_PC9 IRQ_TYPE_LEVEL_LOW>;
>> };
>>
>> 3/ No PHY bindings at all.
>>
>> All 3 cases went OK.
>>
>> You can add:
>> Tested-by: Claudiu Beznea <claudiu.beznea@microchip.com>
>> Acked-by: Claudiu Beznea <claudiu.beznea@microchip.com>
> 
> Thank you very much Claudiu!
> There is still one more case in my mind. macb could be a fixed-link with 
> an MDIO DSA switch. While the macb would have a fixed connection with a 
> port from the DSA switch, the switch could be configured using macb's 
> MDIO. The dt would be something like:
> 
> macb {
> 	fixed-link {
> 		...
> 	};
> 	mdio {
> 		switch@0 {
> 			...
> 		};
> 	};
> };

Do you have a setup for testing this? At the moment I don't know a
configuration like this that macb is working with.

> 
> To support this, in patch 3/7 I should first check for the mdio node to 
> return of_mdiobus_register() and then check if it's a fixed-link to 
> return simple mdiobus_register(). I will address this in v3...> 
> Thanks and best regards,
> Codrin
> 
>>
>> Thank you,
>> Claudiu Beznea
>>
>>> Changes in v2:
>>>   - renamed patch 2/7 from "macb: bindings doc: use an MDIO node as a
>>>     container for PHY nodes" to "dt-bindings: net: macb: use an MDIO
>>>     node as a container for PHY nodes"
>>>   - added back a newline removed by mistake in patch 3/7
>>>
>>> Codrin Ciubotariu (7):
>>>    net: macb: use device-managed devm_mdiobus_alloc()
>>>    dt-bindings: net: macb: use an MDIO node as a container for PHY nodes
>>>    net: macb: parse PHY nodes found under an MDIO node
>>>    ARM: dts: at91: sama5d2: add an mdio sub-node to macb
>>>    ARM: dts: at91: sama5d3: add an mdio sub-node to macb
>>>    ARM: dts: at91: sama5d4: add an mdio sub-node to macb
>>>    ARM: dts: at91: sam9x60: add an mdio sub-node to macb
>>>
>>>   Documentation/devicetree/bindings/net/macb.txt | 15 ++++++++++++---
>>>   arch/arm/boot/dts/at91-sam9x60ek.dts           |  8 ++++++--
>>>   arch/arm/boot/dts/at91-sama5d27_som1.dtsi      | 16 ++++++++++------
>>>   arch/arm/boot/dts/at91-sama5d27_wlsom1.dtsi    | 17 ++++++++++-------
>>>   arch/arm/boot/dts/at91-sama5d2_ptc_ek.dts      | 13 ++++++++-----
>>>   arch/arm/boot/dts/at91-sama5d2_xplained.dts    | 12 ++++++++----
>>>   arch/arm/boot/dts/at91-sama5d3_xplained.dts    | 16 ++++++++++++----
>>>   arch/arm/boot/dts/at91-sama5d4_xplained.dts    | 12 ++++++++----
>>>   drivers/net/ethernet/cadence/macb_main.c       | 18 ++++++++++++------
>>>   9 files changed, 86 insertions(+), 41 deletions(-)
> 

  reply	other threads:[~2020-07-23  7:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 17:13 [PATCH net-next v2 0/7] Add an MDIO sub-node under MACB Codrin Ciubotariu
2020-07-21 17:13 ` [PATCH net-next v2 1/7] net: macb: use device-managed devm_mdiobus_alloc() Codrin Ciubotariu
2020-07-23 18:55   ` Florian Fainelli
2020-07-21 17:13 ` [PATCH net-next v2 2/7] dt-bindings: net: macb: use an MDIO node as a container for PHY nodes Codrin Ciubotariu
2020-07-23 17:51   ` Rob Herring
2020-07-23 18:56   ` Florian Fainelli
2020-07-21 17:13 ` [PATCH net-next v2 3/7] net: macb: parse PHY nodes found under an MDIO node Codrin Ciubotariu
2020-07-23 18:59   ` Florian Fainelli
2020-07-23 22:08     ` Codrin.Ciubotariu
2020-07-23 22:33       ` Florian Fainelli
2020-07-24  7:28     ` Claudiu.Beznea
2020-07-21 17:13 ` [PATCH net-next v2 4/7] ARM: dts: at91: sama5d2: add an mdio sub-node to macb Codrin Ciubotariu
2020-07-23 18:59   ` Florian Fainelli
2020-07-21 17:13 ` [PATCH net-next v2 5/7] ARM: dts: at91: sama5d3: " Codrin Ciubotariu
2020-07-23 19:00   ` Florian Fainelli
2020-07-21 17:13 ` [PATCH net-next v2 6/7] ARM: dts: at91: sama5d4: " Codrin Ciubotariu
2020-07-23 19:00   ` Florian Fainelli
2020-07-21 17:13 ` [PATCH net-next v2 7/7] ARM: dts: at91: sam9x60: " Codrin Ciubotariu
2020-07-23 19:00   ` Florian Fainelli
2020-07-22 10:32 ` [PATCH net-next v2 0/7] Add an MDIO sub-node under MACB Claudiu.Beznea
2020-07-22 11:38   ` Codrin.Ciubotariu
2020-07-23  7:51     ` Claudiu.Beznea [this message]
2020-07-23 13:18       ` Codrin.Ciubotariu

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=8a78218a-9fbe-889d-8501-ad67ccb6e59b@microchip.com \
    --to=claudiu.beznea@microchip.com \
    --cc=Codrin.Ciubotariu@microchip.com \
    --cc=Ludovic.Desroches@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@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).