mfd: Allow the board to choose any GPIO base for tps65010
If the board does not care where the TPS turns up, then specifiying the value -1 to get gpiolib to dynamically allocate the base for the chip is valid. Change the test to look for != 0, so that any boards specifying zero will not end up with gpio that they didn't want. Signed-off-by: Ben Dooks <ben@simtec.co.uk> Signed-off-by: Simtec Liunx Team <linux@simtec.co.uk> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
This commit is contained in:
parent
38a684963f
commit
8483699266
1 changed files with 1 additions and 1 deletions
|
@ -637,7 +637,7 @@ static int tps65010_probe(struct i2c_client *client,
|
||||||
tps, DEBUG_FOPS);
|
tps, DEBUG_FOPS);
|
||||||
|
|
||||||
/* optionally register GPIOs */
|
/* optionally register GPIOs */
|
||||||
if (board && board->base > 0) {
|
if (board && board->base != 0) {
|
||||||
tps->outmask = board->outmask;
|
tps->outmask = board->outmask;
|
||||||
|
|
||||||
tps->chip.label = client->name;
|
tps->chip.label = client->name;
|
||||||
|
|
Loading…
Reference in a new issue