On 21/01/16 18:38, Mark Brown wrote:
On Thu, Jan 21, 2016 at 06:33:47PM +0000, Srinivas Kandagatla wrote:
This driver reuses pdev->id for spi bus numbers resulting in random
or very large bus numbering when used with device trees. pdev->id
is not the correct choice when using device trees. So add code to
What makes you say this, why is pdev->id not "correct"? It is worrying
if anything cares what number we pick.
Issue is that using pdev->id for bus number, as pdev->id does not get
populated in device tree cases.
The end users who are reading the schematics would not be able to map
the actual bus numbers on the schematics with the bus numbers allocated
using pdev->id. It add more confusion.
Without this patch the bus number allocated to this driver is 32766.
This does not really reflect the actual bus numbers on the boards
schematics.
get bus numbers via device tree aliases and if it fails then generate
a unique bus number.
The other question is even if this is a good idea why is it something
that should be open coded in individual drivers, if we want to change
the policy we should be consistent between drivers.
Device tree aliases seems used very much in many drivers.
The unique bus number scheme was actually inspired by the
driver/tty/serial/msm_serial.c
--srini
--
To unsubscribe from this list: send the line "unsubscribe linux-soc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
