diff options
author | steven miao <realmz6@gmail.com> | 2010-09-17 03:03:17 +0000 |
---|---|---|
committer | Mike Frysinger <vapier@gentoo.org> | 2010-10-22 04:02:01 -0400 |
commit | 05bbec38dbafa60583be8347dea88919d48cc733 (patch) | |
tree | d172eb120912c9656357781d9f131a95a455bc99 /drivers/parisc/led.c | |
parent | a71159b96a210d3e4d9bd24dd21278aa29770e9d (diff) | |
download | blackbird-op-linux-05bbec38dbafa60583be8347dea88919d48cc733.tar.gz blackbird-op-linux-05bbec38dbafa60583be8347dea88919d48cc733.zip |
Blackfin: gpio: add peripheral group check
Many Blackfin parts group sets of pins into a single functional unit.
This means you cannot use different pins within a group for different
peripherals. Our resource conflict checking thus far has been limited
to individual pins, so if someone tried to grab a different pin from
the same group, it would be allowed while silently changing the other
pins in the same group.
One common example is the pin set PG12 - PG15 on BF51x parts. They
may either be used with SPI0 (1st function), or they may be used with
PTP/PWM/AMS3 (3rd function). Ideally, we'd like to use PG12 - PG14
for SPI0 while using PG15 with AMS3, but the hardware does not permit
this. In the past, the software would allow the pins to be requested
this way, but ultimately things like the Blackfin SPI driver would
stop working when the hardware rerouted to a different peripheral.
Signed-off-by: steven miao <realmz6@gmail.com>
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Diffstat (limited to 'drivers/parisc/led.c')
0 files changed, 0 insertions, 0 deletions