summaryrefslogtreecommitdiff
path: root/Documentation/extcon/porting-android-switch-class
diff options
context:
space:
mode:
authorMyungJoo Ham <myungjoo.ham@samsung.com>2012-04-20 09:16:26 +0400
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-04-20 20:24:03 +0400
commitbde68e60b18208978c50c6fb9bdf29826d2887f3 (patch)
tree62b48807d48c2454c374bede680c9e9c6cf71a0d /Documentation/extcon/porting-android-switch-class
parent806d9dd71ff52ef09764585baaeec23afbb98560 (diff)
downloadlinux-bde68e60b18208978c50c6fb9bdf29826d2887f3.tar.xz
Extcon: support mutually exclusive relation between cables.
There could be cables that t recannot be attaches simulatenously. Extcon device drivers may express such information via mutually_exclusive in struct extcon_dev. For example, for an extcon device with 16 cables (bits 0 to 15 are available), if mutually_exclusive = { 0x7, 0xC0, 0x81, 0 }, then, the following attachments are prohibitted. {0, 1} {0, 2} {1, 2} {6, 7} {0, 7} and every attachment set that are superset of one of the above. For the detail, please refer to linux/include/linux/extcon.h. The concept is suggested by NeilBrown <neilb@suse.de> Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com> -- Changes from V5: - Updated sysfs format Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/extcon/porting-android-switch-class')
0 files changed, 0 insertions, 0 deletions