On Wed, Sep 18, 2019 at 02:35:50PM -0400, Sven Van Asbroeck wrote: > Support device configuration by adding > > - an in-kernel driver config API, and > - a configfs-based userspace config ABI > > In short, drivers pick a subset from a set of standardized config > properties. This is exposed by the fieldbus core as configfs files. > Userspace may then configure the device by writing to these configfs > files, prior to enabling the device.
Why is a new way of doing configuration needed here? What does this provide that the current code doesn't already do? And have you looked at the recent configfs fixes to make sure this code still works with them? I can't test this so rebasing this on 5.4-rc1 would be good for you to do first. thanks, greg k-h
