On Fri, Oct 27, 2017 at 10:21 PM, Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> wrote: > Commit fd9c963c5661 ("gpio: mb86s70: Return error if requesting an > already assigned gpio") adds code that infers from the state of the > GPIO Pin Function Register (PFR) whether a GPIO has been assigned > already. This assumes that the pin functions are set to 'peripheral' > when the driver is loaded, which is not guaranteed. Also, the GPIO > layer is perfectly capable of keeping track of which GPIOs have been > assigned already, so we shouldn't need this check in the first place. > > This reverts commit fd9c963c5661af3403e77e312c0d9941773b6c1b. > > Cc: Axel Lin <axel.lin@xxxxxxxxxx> > Cc: Linus Walleij <linus.walleij@xxxxxxxxxx> > Signed-off-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Patch applied with Axel's ACK. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html