On Wed, May 25, 2016 at 10:20:34AM +0100, Mark Rutland wrote:
> On Tue, May 24, 2016 at 01:41:26PM -0700, Frank Rowand wrote:

> > The code and behavior is in the Linux kernel. It should be visible in
> > the documentation instead of being a big mystery of how it works.

> As above, I don't entirely agree. Mindlessly documenting existing Linux
> behaviour can have the unfortuante effect of moving people towards the
> wrong tool for the job.

Yes, this is exactly my concern - the articulated use case (which didn't
suprise me at all) is for using spidev which is itself not just Linux
specific but this particular version of Linux right now specific.  There
are lots of things that happen to work but are in fact terrible ideas
that leave messes for our future selves.  We need to distinguish between
things that are real, meaningful system descriptions and things that are
implementation details resulting from the rush to force everyone on to
DT.