On Fri, 24 Apr 2015 14:18:30 +1000 Stewart Smith <stewart@xxxxxxxxxxxxxxxxxx> wrote: > Jacek Anaszewski <j.anaszewski81@xxxxxxxxx> writes: > >> These device tree comes from out firmware ... which is immutable . > > > > How the firmware is related to kernel? These bindings are for > > kernel, not for the firmware. > > > > DT bindings are compiled to *.dtb file which is concatenated with > > zImage. During system boot device drivers are matched with DT > > bindings through 'compatible' property. A driver should have single > > matching DT node, i.e. no other driver can probe with the same DT > > node. This implies that the node should contain only the properties > > required for configuring the related device. > > For OPAL firmware on POWER, firmware hands kernel a flattened device > tree of the machine it's booting on. It's not added to kernel as the > kernels aren't board specific - they're generic. Is the DT node we are discussing used by some other drivers than the LED class driver? Or is it required in this form by other components of your platform? > https://github.com/open-power/skiboot/ is the firmware that generates > the device tree for booting under OPAL. > -- Best Regards, Jacek Anaszewski -- To unsubscribe from this list: send the line "unsubscribe linux-leds" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
