Hi Arnd, On 17/10/17 14:02, Rob Herring wrote: > On Thu, Sep 28, 2017 at 5:45 AM, Sudeep Holla <sudeep.holla@xxxxxxx> wrote: >> Since "/firmware" does not have its own "compatible" property as it's >> just collection of nodes representing firmware interface, it's sub-nodes >> are not populated during system initialization. >> >> Currently different firmware drivers search the /firmware/ node and >> populate the sub-node devices selectively. Instead we can populate >> the /firmware/ node during init to avoid more drivers continuing to >> populate the devices selectively. >> >> To generalize the solution this patch populates the /firmware/ node >> explicitly from of_platform_default_populate_init(). >> You had concernsin the past and I mentioned that firmware interface to user-space *has* to continue in /sys/firmware, but he platform_device management is internal to kernel. Can we proceed with this change at-least for qcom and meson firmware which are platform device already ? I can drop optee related changes. -- Regards, Sudeep -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
