On Wed, Apr 23, 2014 at 11:48 PM, Frank Rowand <frowand.l...@gmail.com> wrote: > On 4/23/2014 4:54 AM, Grant Likely wrote: >> On Tue, 22 Apr 2014 20:20:44 -0700, Greg Kroah-Hartman >> <gre...@linuxfoundation.org> wrote: >>> On Tue, Apr 22, 2014 at 06:25:25PM -0700, Frank Rowand wrote: >>>> Create some infrastructure to aid trouble shooting device tree related >>>> boot issues. >>>> >>>> Add a %driver_name file to each device tree node sysfs directory which has >>>> had >>>> a driver bound to it. This allows detecting device tree nodes which failed >>>> to be bound to any driver. >>> >>> Why is this needed, shouldn't there already be a "driver" symlink in >>> sysfs for these devices when a driver binds to them? The rest of the >>> driver model works that way, why is of devices any different? >>> >> >> Because it hasn't been added yet! I only just committed the change to >> convert device_nodes into kobjects in v3.14. The next step is to add >> driver symlinks. > > No need to add a "driver" symlink. The device directories in sysfs already > have a driver symlink.
Sorry, I meant of_node symlink. That is the bit I've been planning to add. g. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
