Am 27.03.2017 um 07:33 schrieb Matthijs van Duin matthijsvanduin@gmail.com:
On 27 March 2017 at 07:20, H. Nikolaus Schaller hns@goldelico.com wrote:
Am 27.03.2017 um 04:18 schrieb Matthijs van Duin matthijsvanduin@gmail.com: I just noticed that your kernel called eMMC "mmc0" instead of "mmc1", that's confusing as hell. Please apply: https://github.com/mvduin/linux/tree/patch/of-alias
Has this been suggested upstream?
A patch along those lines has been periodically posted on linux-mmc and got rejected for bogus reasons. Basically the linux-mmc devs think that, since you don't have reliable numbering of storage devices on PCs (where typically they are enumerated on discoverable buses), everybody using embedded systems should therefore also suffer with unpredictable numbering of devices.
Or they say: define your own udev-rules.
Yes, I know... My last attempt was to get the pre-calibration for our tsc2007 driver upsream. Just 2 lines of code and *we* would be happy.
The argument was that it can be solved in user space. Yes, *I* can fix it in user space by hacks. And aTc for the Pyra. But as soon as someone else wants to use a different user space he/she has to reinvent the wheel. What I don't can and want to is to fork X11 and provide my own xinput server just to do the same as the two lines in kernel...
My patches (or similar ones) have been integrated in Robert Nelson's kernels since he does care about embedded users.
Note that i2c and spi do support DT-provided numbering, except the mcspi driver breaks it. I should perhaps try to upstream that patch, except of course people will complain since it breaks backward compatibility for people who currently hardcode spi device numbers in applications.
Yes, that is the same way of argumentation I had to fight with the tsc2007...
BR, Nikolaus