QUERY: How to handle SOC Configuration (Peripheral Multiplexing) in linux
Bill Gatliff
bgat at billgatliff.com
Mon Mar 15 08:55:38 EDT 2010
Viresh KUMAR wrote:
> Actually, different peripherals share IO Pads (PL_GPIOs) and GPIO lines. Sending
> patch for drivers to support this doesn't look a great idea to me. Further this
> may cause problems to users, for example: User have entered a inserted a module
> and by mistake or lack of knowledge, he disables already working IP. Now with
> Kconfig concept this is taken care of at the beginning only. User can't select
> peripherals which can't be enabled simultaneously.
>
Better to leave that knowledge out of the drivers and Kconfig, and just
let the system "blow up" at runtime if a bad combination is attempted.
Making the system any smarter than that leads to drivers that are really
difficult to reuse elsewhere.
The "blow up" scenario isn't usually literal, of course, and the problem
is almost always spotted very early in the development effort. So it
doesn't lead to problems. The alternatives do.
b.g.
--
Bill Gatliff
Embedded systems training and consulting
http://billgatliff.com
bgat at billgatliff.com
More information about the linux-arm-kernel
mailing list