1. 10 8月, 2015 5 次提交
  2. 13 6月, 2015 1 次提交
  3. 22 5月, 2015 1 次提交
    • C
      extcon: Use the unique id for external connector instead of string · 2a9de9c0
      Chanwoo Choi 提交于
      This patch uses the unique id to identify the type of external connector instead
      of string name. The string name have the many potential issues. So, this patch
      defines the 'extcon' enumeration which includes all supported external connector
      on EXTCON subsystem. If new external connector is necessary, the unique id of
      new connector have to be added in 'extcon' enumeration. There are current
      supported external connector in 'enum extcon' as following:
      
      enum extcon {
      	EXTCON_NONE		= 0x0,
      
      	/* USB external connector */
      	EXTCON_USB		= 0x1,
      	EXTCON_USB_HOST		= 0x2,
      
      	/* Charger external connector */
      	EXTCON_TA		= 0x10,
      	EXTCON_FAST_CHARGER	= 0x11,
      	EXTCON_SLOW_CHARGER	= 0x12,
      	EXTCON_CHARGE_DOWNSTREAM = 0x13,
      
      	/* Audio and video external connector */
      	EXTCON_LINE_IN		= 0x20,
      	EXTCON_LINE_OUT		= 0x21,
      	EXTCON_MICROPHONE	= 0x22,
      	EXTCON_HEADPHONE	= 0x23,
      
      	EXTCON_HDMI		= 0x30,
      	EXTCON_MHL		= 0x31,
      	EXTCON_DVI		= 0x32,
      	EXTCON_VGA		= 0x33,
      	EXTCON_SPDIF_IN		= 0x34,
      	EXTCON_SPDIF_OUT	= 0x35,
      	EXTCON_VIDEO_IN		= 0x36,
      	EXTCON_VIDEO_OUT	= 0x37,
      
      	/* Miscellaneous external connector */
      	EXTCON_DOCK		= 0x50,
      	EXTCON_JIG		= 0x51,
      	EXTCON_MECHANICAL	= 0x52,
      
      	EXTCON_END,
      };
      
      For example in extcon-arizona.c:
      To use unique id removes the potential issue about handling
      the inconsistent name of external connector with string.
      - Previously, use the string to register the type of arizona jack connector
      static const char *arizona_cable[] = {
      	"Mechanical",
      	"Microphone",
      	"Headphone",
      	"Line-out",
      };
      - Newly, use the unique id to register the type of arizona jack connector
      static const enum extcon arizona_cable[] = {
      	EXTCON_MECHANICAL,
      	EXTCON_MICROPHONE,
      	EXTCON_HEADPHONE,
      	EXTCON_LINE_OUT,
      
      	EXTCON_NONE,
      };
      
      And this patch modify the prototype of extcon_{get|set}_cable_state_() which
      uses the 'enum extcon id' instead of 'cable_index'. Because although one more
      extcon drivers support USB cable, each extcon driver might has the differnt
      'cable_index' for USB cable. All extcon drivers can use the unique id number
      for same external connector with modified extcon_{get|set}_cable_state_().
      
      - Previously, use 'cable_index' on these functions:
      extcon_get_cable_state_(struct extcon_dev*, int cable_index)
      extcon_set_cable_state_(struct extcon_dev*, int cable_index, bool state)
      
      -Newly, use 'enum extcon id' on these functions:
      extcon_get_cable_state_(struct extcon_dev*, enum extcon id)
      extcon_set_cable_state_(struct extcon_dev*, enum extcon id, bool state)
      
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Felipe Balbi <balbi@ti.com>
      Signed-off-by: NChanwoo Choi <cw00.choi@samsung.com>
      Acked-by: NRoger Quadros <rogerq@ti.com>
      Acked-by: NCharles Keepax <ckeepax@opensource.wolfsonmicro.com>
      Acked-by: NRamakrishna Pallala <ramakrishna.pallala@intel.com>
      Reviewed-by: NKrzysztof Kozlowski <k.kozlowski@samsung.com>
      [arnd: Report the build break about drivers/usb/phy/phy-tahvo.c after using the
      unique id for external connector insteadf of string]
      Reported-by: NArnd Bergmann <arnd@arndb.de>
      [dan.carpenter: Report the build warning of extcon_{set|get}_cable_state_()]
      Reported-by: NDan Carpenter <dan.carpenter@oracle.com>
      2a9de9c0
  4. 19 5月, 2015 4 次提交
  5. 04 3月, 2015 2 次提交
  6. 26 2月, 2015 1 次提交
  7. 20 10月, 2014 1 次提交
  8. 23 7月, 2014 2 次提交
    • C
      extcon: arizona: Get MICVDD against extcon device · 17271f60
      Charles Keepax 提交于
      Previously we would do a regulator get against the main Arizona device
      to obtain the MICVDD regulator. Arizona is an MFD device and normally
      MICVDD will be supplied by one of its children (the arizona-micsupp
      regulator). As devres destruction for the MFD device will run after all
      its children have been destroyed, the regulator will be destroyed before
      devres calls regulator_put. This causes a warning from both the
      destruction of the child node, as the regulator is still open, and from
      the put of the regulator as the regulator device has already been
      destroyed.
      
      A simple fix here is to get the regulator against the extcon device
      itself such that devres runs when the child is destroyed. This has the
      additional benefit that if for some reason the extcon driver is unloaded
      the regulator reference won't hang around until the MFD is unloaded.
      Signed-off-by: NCharles Keepax <ckeepax@opensource.wolfsonmicro.com>
      Signed-off-by: NChanwoo Choi <cw00.choi@samsung.com>
      17271f60
    • J
      extcon: Remove unnecessary OOM messages · 0a16ee63
      Jingoo Han 提交于
      The site-specific OOM messages are unnecessary, because they
      duplicate the MM subsystem generic OOM message. The following
      checkpatch warning is also removed.
      
        WARNING: Possible unnecessary 'out of memory' message
      Signed-off-by: NJingoo Han <jg1.han@samsung.com>
      [Acked by Charles Keepax for arizona part]
      Acked-by: NCharles Keepax <ckeepax@opensource.wolfsonmicro.com>
      Signed-off-by: NChanwoo Choi <cw00.choi@samsung.com>
      0a16ee63
  9. 16 6月, 2014 6 次提交
  10. 29 4月, 2014 1 次提交
  11. 24 4月, 2014 1 次提交
  12. 20 2月, 2014 1 次提交
  13. 07 1月, 2014 5 次提交
  14. 26 11月, 2013 1 次提交
  15. 27 9月, 2013 7 次提交
  16. 05 8月, 2013 1 次提交