1. 21 11月, 2016 1 次提交
    • L
      mfd: qcom-pm8xxx: Clean up PM8XXX namespace · 40a3a0f2
      Linus Walleij 提交于
      The Kconfig and file naming for the PM8xxx driver is totally
      confusing:
      
      - Kconfig options MFD_PM8XXX and MFD_PM8921_CORE, some in-kernel
        users depending on or selecting either at random.
      - A driver file named pm8921-core.c even if it is indeed
        used by the whole PM8xxx family of chips.
      - An irqchip named pm8xxx since it was (I guess) realized that
        the driver was generic for all pm8xxx PMICs.
      
      As I may want to add support for PM8901 this is starting to get
      really messy. Fix this situation by:
      
      - Remove the MFD_PM8921_CORE symbol and rely solely on MFD_PM8XXX
        and convert all users, including LEDs Kconfig and ARM defconfigs
        for qcom and multi_v7 to use that single symbol.
      - Renaming the driver to qcom-pm8xxx.c to fit along the two
        other qcom* prefixed drivers.
      - Rename functions withing the driver from 8921 to 8xxx to
        indicate it is generic.
      - Just drop the =m config from the pxa_defconfig, I have no clue
        why it is even there, it is not a Qualcomm platform. (Possibly
        older Kconfig noise from saveconfig.)
      
      Cc: Stephen Boyd <sboyd@codeaurora.org>
      Cc: Neil Armstrong <narmstrong@baylibre.com>
      Cc: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      Reviewed-by: NAndy Gross <andy.gross@linaro.org>
      Acked-by: NBjorn Andersson <bjorn.andersson@linaro.org>
      Acked-by: NJacek Anaszewski <j.anaszewski@samsung.com>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NLee Jones <lee.jones@linaro.org>
      40a3a0f2
  2. 19 9月, 2016 1 次提交
  3. 15 9月, 2016 1 次提交
  4. 02 9月, 2016 1 次提交
  5. 19 8月, 2016 1 次提交
  6. 17 8月, 2016 1 次提交
  7. 09 8月, 2016 2 次提交
  8. 11 7月, 2016 2 次提交
  9. 04 7月, 2016 1 次提交
  10. 27 6月, 2016 1 次提交
  11. 20 6月, 2016 1 次提交
  12. 17 6月, 2016 4 次提交
  13. 06 6月, 2016 3 次提交
  14. 01 6月, 2016 2 次提交
  15. 30 5月, 2016 5 次提交
  16. 18 5月, 2016 1 次提交
    • A
      ARM: exynos: don't select keyboard driver · 8a6f71cc
      Arnd Bergmann 提交于
      The samsung-keypad driver is implicitly selected by ARCH_EXYNOS4 (why?),
      but this fails if CONFIG_INPUT is a loadable module:
      
      drivers/input/built-in.o: In function `samsung_keypad_remove':
      drivers/input/keyboard/samsung-keypad.c:461: undefined reference to `input_unregister_device'
      drivers/input/built-in.o: In function `samsung_keypad_irq':
      drivers/input/keyboard/samsung-keypad.c:137: undefined reference to `input_event'
      drivers/input/built-in.o: In function `samsung_keypad_irq':
      include/linux/input.h:389: undefined reference to `input_event'
      drivers/input/built-in.o: In function `samsung_keypad_probe':
      drivers/input/keyboard/samsung-keypad.c:358: undefined reference to `devm_input_allocate_device'
      drivers/input/built-in.o:(.debug_addr+0x34): undefined reference to `input_set_capability'
      
      This removes the 'select' as suggested by Krzysztof Kozlowski and
      instead enables the driver from the defconfig files.
      
      The problem does not happen on mainline kernels, as we don't normally
      build built-in input drivers when CONFIG_INPUT=m, but I am experimenting
      with a patch to change this, and the samsung keypad driver showed up
      as one example that was silently broken before.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Link: https://lkml.org/lkml/2016/2/14/55Signed-off-by: NKrzysztof Kozlowski <k.kozlowski@samsung.com>
      8a6f71cc
  17. 10 5月, 2016 1 次提交
  18. 30 4月, 2016 1 次提交
  19. 27 4月, 2016 5 次提交
  20. 26 4月, 2016 1 次提交
  21. 22 4月, 2016 1 次提交
  22. 15 4月, 2016 1 次提交
  23. 14 4月, 2016 2 次提交