Hi Matti,
On Thu, Mar 20, 2025 at 10:35:35AM +0200, Matti Vaittinen wrote:
It appears that the concept of available firmware nodes is not really
applicable to the scenarios where a specific name is required from a
node.
As explained[1] by Sakari:
"OF only enumerates available nodes via the fwnode API, software nodes
don't have the concept but on ACPI I guess you could have a difference
in nodes where you have device sub-nodes that aren't available. Still,
these ACPI device nodes don't have meaningful names in this context
(they're 4-character object names) so you wouldn't use them like this
anyway."
Use the fwnode_for_each_child_node() instead of the
fwnode_for_each_available_child_node() In order to make it clearly
visible that the 'availability' of the nodes does not need to be
considered here.
Why not ? Node availability is a concept that exists in DT, and this
driver has only been tested on DT-based systems.
Why can't we keep the
code as-is ?