On Thu, Jan 16, 2014 at 10:33:22AM +0530, Tushar Behera wrote: > In a multi-platform scenario, the hard-coded major/minor numbers in > serial drivers may conflict with each other. A typical scenario is > observed with amba-pl011 and samsung-uart drivers, both of these > drivers use same set of major/minor numbers. If both of these drivers > are enabled, probe of samsung-uart driver fails because the desired > node is busy. Why would both drivers ever be loaded at the same time? Don't they bind to different hardware devices, and as such, never will be in the same system? The driver shouldn't be registering it's tty devices if the hardware isn't present in the system, so how can this codepath ever happen? > The issue is fixed by adding a fallback in driver core, so that we can > use dynamic major number in case device node allocation fails for > hard-coded major/minor number. Did you test this out? You still get userspace breakage with it :( > Signed-off-by: Tushar Behera <tushar.behera@xxxxxxxxxx> > --- > Hi Greg, > > This is my second attempt at getting this fixed. Let me know if you are > okay with this. > > Initial approach to fix this problem was by forcing samsung-uart driver > to use dynamic major number, but it was rejected [1] because of possible > user-space breakage. "possible"? Heh, no, that should be "real". Sorry, but I think you are trying to fix a problem that never actually happens in real life, or in valid configurations... greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |