1. 22 7月, 2014 3 次提交
  2. 12 7月, 2014 1 次提交
  3. 11 6月, 2014 1 次提交
  4. 13 5月, 2014 1 次提交
  5. 12 5月, 2014 1 次提交
    • A
      phy: kona2: use 'select GENERIC_PHY' in Kconfig · 3fc03f3d
      Arnd Bergmann 提交于
      All other phy drivers use 'select', while this one is
      the only one to use 'depends on'. This is not a bug, just
      slightly inconsistent, so let's change it to do things the
      same way as everyone else.
      
      We may also want to turn GENERIC_PHY into a silent option
      that only ever gets turned on if another driver needs it.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Cc: Kishon Vijay Abraham I <kishon@ti.com>
      Cc: Matt Porter <mporter@linaro.org>
      Cc: Felipe Balbi <balbi@ti.com>
      Signed-off-by: NKishon Vijay Abraham I <kishon@ti.com>
      3fc03f3d
  6. 25 4月, 2014 1 次提交
  7. 09 3月, 2014 3 次提交
  8. 08 3月, 2014 2 次提交
  9. 06 3月, 2014 1 次提交
  10. 04 3月, 2014 1 次提交
  11. 03 3月, 2014 2 次提交
  12. 02 3月, 2014 2 次提交
  13. 25 2月, 2014 1 次提交
  14. 19 2月, 2014 2 次提交
  15. 16 2月, 2014 1 次提交
    • H
      phy-core: Don't allow building phy-core as a module · 6d36b6f3
      Hans de Goede 提交于
      include/phy/phy.h has stub code in there for when building without the
      phy-core enabled. This is useful for generic drivers such as ahci-platform,
      ehci-platoform and ohci-platform which have support for driving an optional
      phy passed to them through the devicetree.
      
      Since on some boards this phy functionality is not needed, being able to
      disable the phy subsystem without needing a lot of #ifdef magic in the
      driver using it is quite useful.
      
      However this breaks when the module using the phy subsystem is build-in and
      the phy-core is not, which leads to the build failing with missing symbol
      errors in the linking stage of the zImage.
      
      Which leads to gems such as this being added to the Kconfig for achi_platform:
      
      	depends on GENERIC_PHY || !GENERIC_PHY
      
      Rather then duplicating this code in a lot of places using the phy-core,
      I believe it is better to simply not allow the phy-core to be built as a
      module. The phy core is quite small and has no external dependencies, so
      always building it in when enabling it should not be an issue.
      Signed-off-by: NHans de Goede <hdegoede@redhat.com>
      Acked-by: NAndrew Lunn <andrew@lunn.ch>
      Acked-by: NRoger Quadros <rogerq@ti.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      6d36b6f3
  16. 16 1月, 2014 1 次提交
  17. 25 12月, 2013 1 次提交
  18. 24 12月, 2013 1 次提交
  19. 11 12月, 2013 1 次提交
  20. 17 10月, 2013 2 次提交
  21. 28 9月, 2013 3 次提交