pinctrl: assume map table entries can't have a NULL name field
authorStephen Warren <swarren@nvidia.com>
Fri, 2 Mar 2012 01:48:33 +0000 (18:48 -0700)
committerLinus Walleij <linus.walleij@linaro.org>
Fri, 2 Mar 2012 15:20:54 +0000 (16:20 +0100)
commit110e4ec5a1cfe20190e7f8c2b8b4eef369de3c99
tree2e20b44478f47069ac19f0ef9f5a92bee7576bdd
parent46919ae63d4820e76724beb655274ce143f0da0b
pinctrl: assume map table entries can't have a NULL name field

pinctrl_register_mappings() already requires that every mapping table
entry have a non-NULL name field.

Logically, this makes sense too; drivers should always request a specific
named state so they know what they're getting. Relying on getting the
first mentioned state in the mapping table is error-prone, and a nasty
special case to implement, given that a given the mapping table may define
multiple states for a device.

Remove a small part of the documentation that talked about optionally
requesting a specific state; it's mandatory now.

Signed-off-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Dong Aisheng <dong.aisheng@linaro.org>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Documentation/pinctrl.txt
arch/arm/mach-u300/core.c
drivers/pinctrl/core.c
drivers/tty/serial/sirfsoc_uart.c