This patch-set update the extcon core to resolve the ambiguous identification
method for each external connectors. So, first patch define the unique id
for each external connector to identify them by using common unique id on
various extcon device driver as following:
enum extcon {
EXTCON_NONE = 0x0, /* NONE */
/* USB external connector */
EXTCON_USB = 0x1, /* USB */
EXTCON_USB_HOST = 0x2, /* USB-HOST */
/* Charger external connector */
EXTCON_TA = 0x10, /* TA */
EXTCON_FAST_CHARGER = 0x11, /* FAST-CHARGER */
EXTCON_SLOW_CHARGER = 0x12, /* SLOW-CHARGER */
EXTCON_CHARGE_DOWNSTREAM= 0x13, /* CHARGE-DOWNSTREAM */
.....
};
And the second patch simplify the prototype of extcon notifier's register
and unregister function with the unique id. All extcon driver have to use
the unique id (enum extcon definition) when registering the notifier and
getting/setting the state of cable state.
: int extcon_{register|unregister}_notifier(struct extcon_dev *edev,
enum extcon id, struct notifier_block *nb)
In result, the extcon_{register|unregister}_interest() will be deprecated
by using the simply extcon_{register|unregister}_notifier().
Chanwoo Choi (2):
extcon: Use the unique id for external connector instead of string
extcon: Update the prototype of extcon_register_notifier() with enum extcon
drivers/extcon/extcon-arizona.c | 38 ++---
drivers/extcon/extcon-axp288.c | 24 ++-
drivers/extcon/extcon-max14577.c | 45 +++---
drivers/extcon/extcon-max77693.c | 95 ++++++------
drivers/extcon/extcon-max77843.c | 56 +++----
drivers/extcon/extcon-max8997.c | 59 +++-----
drivers/extcon/extcon-palmas.c | 22 +--
drivers/extcon/extcon-rt8973a.c | 40 ++---
drivers/extcon/extcon-sm5502.c | 32 ++--
drivers/extcon/extcon-usb-gpio.c | 32 +---
drivers/extcon/extcon.c | 257 +++++++++++++++++++--------------
include/linux/extcon.h | 109 +++++++-------
include/linux/extcon/extcon-adc-jack.h | 5 +-
13 files changed, 382 insertions(+), 432 deletions(-)
--
1.8.5.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
