Re: [net-next: PATCH v2 4/5] net: mvpp2: use device_*/fwnode_* APIs instead of of_*

Hi Andrew, 2017-12-31 20:18 GMT+01:00 Andrew Lunn : > On Sun, Dec 31, 2017 at 12:58:39PM +0100, Marcin Wojtas wrote: > Hi Marcin > >> Because there is no equivalent for for_each_available_child_of_node(), >> use device_for_each_child_node() and check the port availability >>

Re: [net-next: PATCH v2 4/5] net: mvpp2: use device_*/fwnode_* APIs instead of of_*

On Sun, Dec 31, 2017 at 12:58:39PM +0100, Marcin Wojtas wrote: Hi Marcin > Because there is no equivalent for for_each_available_child_of_node(), > use device_for_each_child_node() and check the port availability > inside the mvpp2_port_probe() routine. Could device_each_available_child_node()

[net-next: PATCH v2 4/5] net: mvpp2: use device_*/fwnode_* APIs instead of of_*

OF functions can be used only for the driver using DT. As a preparation for introducing ACPI support in mvpp2 driver, use struct fwnode_handle in order to obtain properties from the hardware description. Because there is no equivalent for for_each_available_child_of_node(), use