From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933453AbdLRJWi (ORCPT ); Mon, 18 Dec 2017 04:22:38 -0500 Received: from mail-lf0-f67.google.com ([209.85.215.67]:38303 "EHLO mail-lf0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933179AbdLRJSN (ORCPT ); Mon, 18 Dec 2017 04:18:13 -0500 X-Google-Smtp-Source: ACJfBoud3eFtt/c0pU6lrhIhMCyY9UHpX6YF+aWODj8XjBwEqaE/dgsjDCzthH5t53BOCoJGVu6xwA== From: Marcin Wojtas To: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org Cc: davem@davemloft.net, linux@arm.linux.org.uk, rafael.j.wysocki@intel.com, andrew@lunn.ch, f.fainelli@gmail.com, antoine.tenart@free-electrons.com, thomas.petazzoni@free-electrons.com, gregory.clement@free-electrons.com, ezequiel.garcia@free-electrons.com, nadavh@marvell.com, neta@marvell.com, ard.biesheuvel@linaro.org, mw@semihalf.com, jaz@semihalf.com, tn@semihalf.com Subject: [net-next: PATCH 0/8] Armada 7k/8k PP2 ACPI support Date: Mon, 18 Dec 2017 10:17:56 +0100 Message-Id: <1513588684-15647-1-git-send-email-mw@semihalf.com> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, This patchset introduces ACPI support in mvpp2 and mvmdio drivers. First three patches introduce fwnode helpers for obtaining PHY information from nodes and also MDIO fwnode API for registering the bus with its PHY/devices. Following patches update code of the mvmdio and mvpp2 drivers to support ACPI tables handling. The latter is done in 4 steps, as can be seen in the commits. For the details, please refer to the commit messages. Drivers operation was tested on top of the net-next branch with both DT and ACPI. Although for compatibility reasons with older platforms, the mvmdio driver keeps using of_ MDIO registering, new fwnode_ one proved to fully work with DT as well (tested on MacchiatoBin board). mvpp2/mvmdio driver can work with the ACPI representation, as exposed on a public branch: https://github.com/MarvellEmbeddedProcessors/edk2-open-platform/commits/marvell-armada-wip It was compiled together with the most recent Tianocore EDK2 revision. Please refer to the firmware build instruction on MacchiatoBin board: http://wiki.macchiatobin.net/tiki-index.php?page=Build+from+source+-+UEFI+EDK+II Above support configures 1G to use its PHY normally. 10G can work now only with the link interrupt mode. Somehow reading of the string property in fwnode_mdiobus_child_is_phy works only with DT and cannot cope with 10G PHY nodes as in: https://pastebin.com/3JnYpU0A Above root cause will be further checked. In the meantime I will appreciate any comments or remarks for the kernel patches. Best regards, Marcin Marcin Wojtas (8): device property: Introduce fwnode_get_mac_address() device property: Introduce fwnode_get_phy_mode() mdio_bus: Introduce fwnode MDIO helpers net: mvmdio: add ACPI support net: mvpp2: simplify maintaining enabled ports' list net: mvpp2: use device_*/fwnode_* APIs instead of of_* net: mvpp2: handle PHY with its fwnode net: mvpp2: enable ACPI support in the driver drivers/base/property.c | 52 +++-- drivers/net/ethernet/marvell/mvmdio.c | 42 +++- drivers/net/ethernet/marvell/mvpp2.c | 246 ++++++++++++-------- drivers/net/phy/mdio_bus.c | 218 +++++++++++++++++ include/linux/mdio.h | 3 + include/linux/property.h | 3 + 6 files changed, 454 insertions(+), 110 deletions(-) -- 2.7.4 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcin Wojtas Subject: [net-next: PATCH 0/8] Armada 7k/8k PP2 ACPI support Date: Mon, 18 Dec 2017 10:17:56 +0100 Message-ID: <1513588684-15647-1-git-send-email-mw@semihalf.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: thomas.petazzoni@free-electrons.com, andrew@lunn.ch, f.fainelli@gmail.com, linux@arm.linux.org.uk, ard.biesheuvel@linaro.org, jaz@semihalf.com, antoine.tenart@free-electrons.com, rafael.j.wysocki@intel.com, nadavh@marvell.com, neta@marvell.com, ezequiel.garcia@free-electrons.com, tn@semihalf.com, gregory.clement@free-electrons.com, mw@semihalf.com, davem@davemloft.net To: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org List-Id: netdev.vger.kernel.org Hi, This patchset introduces ACPI support in mvpp2 and mvmdio drivers. First three patches introduce fwnode helpers for obtaining PHY information from nodes and also MDIO fwnode API for registering the bus with its PHY/devices. Following patches update code of the mvmdio and mvpp2 drivers to support ACPI tables handling. The latter is done in 4 steps, as can be seen in the commits. For the details, please refer to the commit messages. Drivers operation was tested on top of the net-next branch with both DT and ACPI. Although for compatibility reasons with older platforms, the mvmdio driver keeps using of_ MDIO registering, new fwnode_ one proved to fully work with DT as well (tested on MacchiatoBin board). mvpp2/mvmdio driver can work with the ACPI representation, as exposed on a public branch: https://github.com/MarvellEmbeddedProcessors/edk2-open-platform/commits/marvell-armada-wip It was compiled together with the most recent Tianocore EDK2 revision. Please refer to the firmware build instruction on MacchiatoBin board: http://wiki.macchiatobin.net/tiki-index.php?page=Build+from+source+-+UEFI+EDK+II Above support configures 1G to use its PHY normally. 10G can work now only with the link interrupt mode. Somehow reading of the string property in fwnode_mdiobus_child_is_phy works only with DT and cannot cope with 10G PHY nodes as in: https://pastebin.com/3JnYpU0A Above root cause will be further checked. In the meantime I will appreciate any comments or remarks for the kernel patches. Best regards, Marcin Marcin Wojtas (8): device property: Introduce fwnode_get_mac_address() device property: Introduce fwnode_get_phy_mode() mdio_bus: Introduce fwnode MDIO helpers net: mvmdio: add ACPI support net: mvpp2: simplify maintaining enabled ports' list net: mvpp2: use device_*/fwnode_* APIs instead of of_* net: mvpp2: handle PHY with its fwnode net: mvpp2: enable ACPI support in the driver drivers/base/property.c | 52 +++-- drivers/net/ethernet/marvell/mvmdio.c | 42 +++- drivers/net/ethernet/marvell/mvpp2.c | 246 ++++++++++++-------- drivers/net/phy/mdio_bus.c | 218 +++++++++++++++++ include/linux/mdio.h | 3 + include/linux/property.h | 3 + 6 files changed, 454 insertions(+), 110 deletions(-) -- 2.7.4 From mboxrd@z Thu Jan 1 00:00:00 1970 From: mw@semihalf.com (Marcin Wojtas) Date: Mon, 18 Dec 2017 10:17:56 +0100 Subject: [net-next: PATCH 0/8] Armada 7k/8k PP2 ACPI support Message-ID: <1513588684-15647-1-git-send-email-mw@semihalf.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi, This patchset introduces ACPI support in mvpp2 and mvmdio drivers. First three patches introduce fwnode helpers for obtaining PHY information from nodes and also MDIO fwnode API for registering the bus with its PHY/devices. Following patches update code of the mvmdio and mvpp2 drivers to support ACPI tables handling. The latter is done in 4 steps, as can be seen in the commits. For the details, please refer to the commit messages. Drivers operation was tested on top of the net-next branch with both DT and ACPI. Although for compatibility reasons with older platforms, the mvmdio driver keeps using of_ MDIO registering, new fwnode_ one proved to fully work with DT as well (tested on MacchiatoBin board). mvpp2/mvmdio driver can work with the ACPI representation, as exposed on a public branch: https://github.com/MarvellEmbeddedProcessors/edk2-open-platform/commits/marvell-armada-wip It was compiled together with the most recent Tianocore EDK2 revision. Please refer to the firmware build instruction on MacchiatoBin board: http://wiki.macchiatobin.net/tiki-index.php?page=Build+from+source+-+UEFI+EDK+II Above support configures 1G to use its PHY normally. 10G can work now only with the link interrupt mode. Somehow reading of the string property in fwnode_mdiobus_child_is_phy works only with DT and cannot cope with 10G PHY nodes as in: https://pastebin.com/3JnYpU0A Above root cause will be further checked. In the meantime I will appreciate any comments or remarks for the kernel patches. Best regards, Marcin Marcin Wojtas (8): device property: Introduce fwnode_get_mac_address() device property: Introduce fwnode_get_phy_mode() mdio_bus: Introduce fwnode MDIO helpers net: mvmdio: add ACPI support net: mvpp2: simplify maintaining enabled ports' list net: mvpp2: use device_*/fwnode_* APIs instead of of_* net: mvpp2: handle PHY with its fwnode net: mvpp2: enable ACPI support in the driver drivers/base/property.c | 52 +++-- drivers/net/ethernet/marvell/mvmdio.c | 42 +++- drivers/net/ethernet/marvell/mvpp2.c | 246 ++++++++++++-------- drivers/net/phy/mdio_bus.c | 218 +++++++++++++++++ include/linux/mdio.h | 3 + include/linux/property.h | 3 + 6 files changed, 454 insertions(+), 110 deletions(-) -- 2.7.4