[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160524172045.GN8206@sirena.org.uk>
Date: Tue, 24 May 2016 18:20:45 +0100
From: Mark Brown <broonie@...nel.org>
To: Christer Weinigel <christer@...nigel.se>
Cc: linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH] devicetree - document using aliases to set spi bus
number.
On Tue, May 24, 2016 at 06:39:20PM +0200, Christer Weinigel wrote:
> Document how to use devicetree aliases to assign a stable
> bus number to a spi bus.
Please submit patches using subject lines reflecting the style for the
subsystem. This makes it easier for people to identify relevant
patches.
> Not having used devicetree that much it was surprisingly hard to
> figure out how to assign a stable bus number to a spi bus. Add a
> simple example that shows how to do that.
I'm not sure this is something we want to support at all, I can't
immediately see anything that does this deliberately in the SPI code and
obviously the "bus number" is something of a Linux specific concept
which would need some explanation if we were going to document it. It's
something I'm struggling a bit to see a robust use case for that isn't
better served by parsing sysfs, what's the goal here?
> Mark Cced as the SPI maintainer. Or should trivial documentation
> fixes like this be addressed to someone else?
This is definitely *not* trivial but yes, in general you should CC
maintainers on things.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists