mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-24 05:04:00 +08:00
8f1cc3b10e
Teach the mcp23s08 driver about a curious feature of these chips: up to
four of them can share the same chipselect, with the SPI signals wired in
parallel, by matching two bits in the first protocol byte against two
address lines on the chip.
This is handled by three software changes:
* Platform data now holds an array of per-chip structs, not
just one chip's address and pullup configuration.
* Probe() and remove() now use another level of structure,
wrapping an instance of the original structure for each
mcp23s08 chip sharing that chipselect.
* The HAEN bit is set, so that the hardware address bits can no
longer be ignored (boot firmware may not have enabled them).
The "one struct per chip" preserves the guts of the current code,
but platform_data will need minor changes.
OLD:
/* incorrect "slave" ID may not have mattered */
.slave = 3,
.pullups = BIT(3) | BIT(1) | BIT(0),
NEW:
/* slave address _must_ match chip's wiring */
.chip[3] = {
.is_present = true,
.pullups = BIT(3) | BIT(1) | BIT(0),
},
There's no change in how things _behave_ for spi_device nodes with a
single mcp23s08 chip. New multi-chip configurations assign GPIOs in
sequence, without holes. The spi_device just resembles a bigger
controller, but internally it has multiple gpio_chip instances.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
32 lines
919 B
C
32 lines
919 B
C
|
|
/* FIXME driver should be able to handle IRQs... */
|
|
|
|
struct mcp23s08_chip_info {
|
|
bool is_present; /* true iff populated */
|
|
u8 pullups; /* BIT(x) means enable pullup x */
|
|
};
|
|
|
|
struct mcp23s08_platform_data {
|
|
/* Four slaves (numbered 0..3) can share one SPI chipselect, and
|
|
* will provide 8..32 GPIOs using 1..4 gpio_chip instances.
|
|
*/
|
|
struct mcp23s08_chip_info chip[4];
|
|
|
|
/* "base" is the number of the first GPIO. Dynamic assignment is
|
|
* not currently supported, and even if there are gaps in chip
|
|
* addressing the GPIO numbers are sequential .. so for example
|
|
* if only slaves 0 and 3 are present, their GPIOs range from
|
|
* base to base+15.
|
|
*/
|
|
unsigned base;
|
|
|
|
void *context; /* param to setup/teardown */
|
|
|
|
int (*setup)(struct spi_device *spi,
|
|
int gpio, unsigned ngpio,
|
|
void *context);
|
|
int (*teardown)(struct spi_device *spi,
|
|
int gpio, unsigned ngpio,
|
|
void *context);
|
|
};
|