View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001185 | fss5pv210_Linux | SPI | public | 2012-08-03 10:49 | 2014-01-28 11:42 |
| Reporter | Keller | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | resolved | Resolution | fixed | ||
| Product Version | armStoneA8-V1.1 | ||||
| Target Version | fss5pv210-V2.0 | Fixed in Version | fss5pv210-V2.0 | ||
| Summary | 0001185: Block I2C0 if SPI0 is running and vice versa | ||||
| Description | On armStoneA8, the lines for SPI0 (GPB[3:0]) are also connected to I2C0 (GPD1[1:0]) and interrupt capable I/Os (GPH[6], GPH[0]). To avoid short circuits between these pins, only one of the functions must be allowed to be active. So the other function must be blocked. | ||||
| Forum Link | |||||
|
|
To avoid activating the one while the other is already running, both devices request all their lines *and* the other lines as GPIOs. Then the second one that wants to initialize the device will fail. This also makes it impossible to export these I/Os through the /sys/class/gpio interface, so users won't interfere neither. In the current configuration, SPI0 is active and I2C0 not. |
