linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [net-next: PATCH 0/8] Armada 7k/8k PP2 ACPI support
Date: Sun, 21 Jan 2018 17:13:19 +0100	[thread overview]
Message-ID: <20180121161319.GA8017@lunn.ch> (raw)
In-Reply-To: <20180121102700.GF27654@lahna.fi.intel.com>

> Right. So if you need to have some additional "parameters" with the
> connection, then I suppose you may want to go with the GenericSerialBus
> route. However, looking at the sample device tree description:
> 
>         davinci_mdio: ethernet at 5c030000 {
>                 compatible = "ti,davinci_mdio";
>                 reg = <0x5c030000 0x1000>;
>                 #address-cells = <1>;
>                 #size-cells = <0>;
> 
>                 reset-gpios = <&gpio2 5 GPIO_ACTIVE_LOW>;
>                 reset-delay-us = <2>;
> 
>                 ethphy0: ethernet-phy at 1 {
>                         reg = <1>;
>                 };
> 
>                 ethphy1: ethernet-phy at 3 {
>                         reg = <3>;
>                 };
>         };
> 
> would pretty much translate directly to this in ACPI if you don't need
> any additional attributes:
> 
> 	Device (ETH0) {
> 		Name (_ADR, /* PCI address of the NIC */)
> 
> 		Device (PHY0) {
> 			Name (_ADR, 1)
> 			...
> 		} 
> 
> 		Device (PHY1) {
> 			Name (_ADR, 3)
> 			...
> 		} 
> 	}
> 
> which looks pretty simple to me. You can also use _DSM and _DSD here to
> pass information (like the protocol number) for the PHY devices to Linux.

I'm not particularly worried about that simple case. Other than, i
don't want people to think that is all that is required. 

For a more full example, take a look at vf610-zii-dev-rev-b.dts. The
Freescale FEC Ethernet controller provides the base MDIO device,
mdio1. On top of this is an MDIO mux, using a few GPIO lines to
enable/disable 3 child MDIO busses. Each of these busses has an
Ethernet Switch. The Ethernet switch exports up to two MDIO busses,
and on these busses are Ethernet PHYs which are embedded inside the
switch. The Ethernet switches are also interrupt controllers, with the
PHYs having interrupt properties which point back to the interrupt
controller in the switch.

So i'm interested in an ACPI proposal which supports this board.

	   Andrew

  reply	other threads:[~2018-01-21 16:13 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18  9:17 [net-next: PATCH 0/8] Armada 7k/8k PP2 ACPI support Marcin Wojtas
2017-12-18  9:17 ` [net-next: PATCH 1/8] device property: Introduce fwnode_get_mac_address() Marcin Wojtas
2017-12-18  9:17 ` [net-next: PATCH 2/8] device property: Introduce fwnode_get_phy_mode() Marcin Wojtas
2017-12-18  9:17 ` [net-next: PATCH 3/8] mdio_bus: Introduce fwnode MDIO helpers Marcin Wojtas
2017-12-18  9:18 ` [net-next: PATCH 4/8] net: mvmdio: add ACPI support Marcin Wojtas
2017-12-18  9:18 ` [net-next: PATCH 5/8] net: mvpp2: simplify maintaining enabled ports' list Marcin Wojtas
2017-12-18  9:18 ` [net-next: PATCH 6/8] net: mvpp2: use device_*/fwnode_* APIs instead of of_* Marcin Wojtas
2017-12-18  9:18 ` [net-next: PATCH 7/8] net: mvpp2: handle PHY with its fwnode Marcin Wojtas
2017-12-18  9:18 ` [net-next: PATCH 8/8] net: mvpp2: enable ACPI support in the driver Marcin Wojtas
2017-12-18  9:40 ` [net-next: PATCH 0/8] Armada 7k/8k PP2 ACPI support Ard Biesheuvel
2017-12-18 15:49   ` Marcin Wojtas
2018-01-03 11:00   ` Graeme Gregory
2018-01-03 11:12     ` Marcin Wojtas
2018-01-03 12:47       ` Andrew Lunn
2018-01-03 13:13         ` Marcin Wojtas
2018-01-03 13:33           ` Andrew Lunn
2018-01-03 13:36             ` Marcin Wojtas
2018-01-04 16:09       ` Graeme Gregory
2018-01-04 16:20         ` Andrew Lunn
2018-01-08 14:45           ` Graeme Gregory
2018-01-08 14:53             ` Andrew Lunn
2018-01-08 15:14               ` Graeme Gregory
2018-01-08 15:42                 ` Andrew Lunn
2018-01-08 17:17                   ` Marcin Wojtas
2018-01-09 10:19                     ` Graeme Gregory
2018-01-09 10:22                       ` Marcin Wojtas
2018-01-09 13:00                         ` Andrew Lunn
2018-01-18 12:31                           ` Lorenzo Pieralisi
2018-01-18 13:00                             ` Andrew Lunn
2018-01-19 18:07                               ` Marcin Wojtas
2018-01-19 18:53                                 ` Andrew Lunn
2018-01-20 19:52                                 ` Mika Westerberg
2018-01-21  1:08                                   ` Andrew Lunn
2018-01-21 10:27                                     ` Mika Westerberg
2018-01-21 16:13                                       ` Andrew Lunn [this message]
2018-01-21 17:13                                         ` Ard Biesheuvel
2018-01-21 18:55                                           ` Andrew Lunn
2017-12-18 14:09 ` Rafael J. Wysocki
2017-12-19 18:48 ` David Miller
2017-12-19 18:59   ` Marcin Wojtas
2017-12-19 20:46     ` Andrew Lunn
2017-12-19 23:13       ` Marcin Wojtas
2017-12-21 19:21 ` Antoine Tenart

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=20180121161319.GA8017@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=linux-arm-kernel@lists.infradead.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).