1. 19 12月, 2013 1 次提交
  2. 17 10月, 2013 1 次提交
  3. 27 9月, 2013 1 次提交
  4. 25 6月, 2013 1 次提交
    • J
      build some drivers only when compile-testing · 4bb16672
      Jiri Slaby 提交于
      Some drivers can be built on more platforms than they run on. This is
      a burden for users and distributors who package a kernel. They have to
      manually deselect some (for them useless) drivers when updating their
      configs via oldconfig. And yet, sometimes it is even impossible to
      disable the drivers without patching the kernel.
      
      Introduce a new config option COMPILE_TEST and make all those drivers
      to depend on the platform they run on, or on the COMPILE_TEST option.
      Now, when users/distributors choose COMPILE_TEST=n they will not have
      the drivers in their allmodconfig setups, but developers still can
      compile-test them with COMPILE_TEST=y.
      
      Now the drivers where we use this new option:
      * PTP_1588_CLOCK_PCH: The PCH EG20T is only compatible with Intel Atom
        processors so it should depend on x86.
      * FB_GEODE: Geode is 32-bit only so only enable it for X86_32.
      * USB_CHIPIDEA_IMX: The OF_DEVICE dependency will be met on powerpc
        systems -- which do not actually support the hardware via that
        method.
      * INTEL_MID_PTI: It is specific to the Penwell type of Intel Atom
        device.
      
      [v2]
      * remove EXPERT dependency
      
      [gregkh - remove chipidea portion, as it's incorrect, and also doesn't
       apply to my driver-core tree]
      Signed-off-by: NJiri Slaby <jslaby@suse.cz>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Jeff Mahoney <jeffm@suse.com>
      Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
      Cc: linux-usb@vger.kernel.org
      Cc: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
      Cc: linux-geode@lists.infradead.org
      Cc: linux-fbdev@vger.kernel.org
      Cc: Richard Cochran <richardcochran@gmail.com>
      Cc: netdev@vger.kernel.org
      Cc: Ben Hutchings <ben@decadent.org.uk>
      Cc: "Keller, Jacob E" <jacob.e.keller@intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      4bb16672
  5. 06 6月, 2013 1 次提交
  6. 30 4月, 2013 1 次提交
    • P
      misc: generic on-chip SRAM allocation driver · 4984c6f5
      Philipp Zabel 提交于
      This driver requests and remaps a memory region as configured in the
      device tree.  It serves memory from this region via the genalloc API.  It
      optionally enables the SRAM clock.
      
      Other drivers can retrieve the genalloc pool from a phandle pointing to
      this drivers' device node in the device tree.
      
      The allocation granularity is hard-coded to 32 bytes for now, to make the
      SRAM driver useful for the 6502 remoteproc driver.  There is overhead for
      bigger SRAMs, where only a much coarser allocation granularity is needed:
      At 32 bytes minimum allocation size, a 256 KiB SRAM needs a 1 KiB bitmap
      to track allocations.
      
      [akpm@linux-foundation.org: fix Kconfig text, make sram_init static]
      Signed-off-by: NPhilipp Zabel <p.zabel@pengutronix.de>
      Reviewed-by: NShawn Guo <shawn.guo@linaro.org>
      Acked-by: NGrant Likely <grant.likely@secretlab.ca>
      Tested-by: NMichal Simek <monstr@monstr.eu>
      Cc: Dong Aisheng <dong.aisheng@linaro.org>
      Cc: Fabio Estevam <fabio.estevam@freescale.com>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Cc: Huang Shijie <shijie8@gmail.com>
      Cc: Javier Martin <javier.martin@vista-silicon.com>
      Cc: Matt Porter <mporter@ti.com>
      Cc: Michal Simek <monstr@monstr.eu>
      Cc: Paul Gortmaker <paul.gortmaker@windriver.com>
      Cc: Rob Herring <rob.herring@calxeda.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      4984c6f5
  7. 24 4月, 2013 1 次提交
    • A
      misc: mark spear13xx-pcie-gadget as broken · 98097858
      Arnd Bergmann 提交于
      This driver was merged in 2.6.38 but never actually compiled because
      it depends on the <mach/pcie.h> header that has not made it into the
      kernel. Starting with Linux-3.10, this results in "allyesconfig"
      build errors, since spear13xx can now be enabled with the default
      "multiplatform" platform on ARM. Let's mark it as broken for now.
      If it doesn't get fixed, we can drop it completely.
      
      Cc: Pratyush Anand <pratyush.anand@st.com>
      Cc: Randy Dunlap <randy.dunlap@oracle.com>
      Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
      Cc: Viresh Kumar <viresh.kumar@st.com>
      Cc: Shiraz Hashim <shiraz.hashim@st.com>
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      98097858
  8. 26 3月, 2013 1 次提交
  9. 05 3月, 2013 1 次提交
  10. 19 1月, 2013 1 次提交
    • J
      tty: Added a CONFIG_TTY option to allow removal of TTY · 4f73bc4d
      Joe Millenbach 提交于
      The option allows you to remove TTY and compile without errors. This
      saves space on systems that won't support TTY interfaces anyway.
      bloat-o-meter output is below.
      
      The bulk of this patch consists of Kconfig changes adding "depends on
      TTY" to various serial devices and similar drivers that require the TTY
      layer.  Ideally, these dependencies would occur on a common intermediate
      symbol such as SERIO, but most drivers "select SERIO" rather than
      "depends on SERIO", and "select" does not respect dependencies.
      
      bloat-o-meter output comparing our previous minimal to new minimal by
      removing TTY.  The list is filtered to not show removed entries with awk
      '$3 != "-"' as the list was very long.
      
      add/remove: 0/226 grow/shrink: 2/14 up/down: 6/-35356 (-35350)
      function                                     old     new   delta
      chr_dev_init                                 166     170      +4
      allow_signal                                  80      82      +2
      static.__warned                              143     142      -1
      disallow_signal                               63      62      -1
      __set_special_pids                            95      94      -1
      unregister_console                           126     121      -5
      start_kernel                                 546     541      -5
      register_console                             593     588      -5
      copy_from_user                                45      40      -5
      sys_setsid                                   128     120      -8
      sys_vhangup                                   32      19     -13
      do_exit                                     1543    1526     -17
      bitmap_zero                                   60      40     -20
      arch_local_irq_save                          137     117     -20
      release_task                                 674     652     -22
      static.spin_unlock_irqrestore                308     260     -48
      Signed-off-by: NJoe Millenbach <jmillenbach@gmail.com>
      Reviewed-by: NJamey Sharp <jamey@minilop.net>
      Reviewed-by: NJosh Triplett <josh@joshtriplett.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      4f73bc4d
  11. 18 1月, 2013 1 次提交
  12. 09 1月, 2013 1 次提交
  13. 24 12月, 2012 1 次提交
  14. 20 9月, 2012 1 次提交
  15. 18 9月, 2012 1 次提交
  16. 23 7月, 2012 1 次提交
    • T
      pwm: Conflict with legacy PWM API · eac7a92f
      Thierry Reding 提交于
      In order to avoid duplicate symbols with legacy PWM API implementations,
      the new PWM framework needs to conflict with any of the existing legacy
      implementations. This is done in two ways: for implementations provided
      by drivers, a conflict is added to the driver to ensure it will have to
      be ported to the PWM subsystem before it can coexist with other PWM
      providers. For architecture-specific code, the conflict is added to the
      PWM symbol to avoid confusion when a previously picked platform or
      machine can no longer be selected because of the PWM subsystem being
      included.
      Signed-off-by: NThierry Reding <thierry.reding@avionic-design.de>
      eac7a92f
  17. 12 7月, 2012 1 次提交
  18. 10 5月, 2012 1 次提交
  19. 02 5月, 2012 1 次提交
  20. 19 4月, 2012 1 次提交
  21. 25 1月, 2012 1 次提交
    • F
      drivers: misc: Remove MISC_DEVICES config option · 7c5763b8
      Fabio Estevam 提交于
      MISC_DEVICES option alone does not select any kernel code and can cause dependency build warnings, such as:
      
      warning: (KS8851 && AX88796_93CX6 && RTL8180 && RTL8187 && ADM8211 && RT2400PCI && RT2500PCI && RT61PCI && RT2800PCI && R8187SE) selects EEPROM_93CX6 which has unmet direct dependencies (MISC_DEVICES)
      
      As the current drivers/misc/Kconfig stands, it is only possible to select the drivers below if MISC_DEVICES option is selected:
      
      source "drivers/misc/c2port/Kconfig"
      source "drivers/misc/eeprom/Kconfig"
      source "drivers/misc/cb710/Kconfig"
      source "drivers/misc/iwmc3200top/Kconfig"
      source "drivers/misc/ti-st/Kconfig"
      source "drivers/misc/lis3lv02d/Kconfig"
      source "drivers/misc/carma/Kconfig"
      source "drivers/misc/altera-stapl/Kconfig"
      
      So remove MISC_DEVICES option so that nothing is dependant on it.
      Signed-off-by: NFabio Estevam <fabio.estevam@freescale.com>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      7c5763b8
  22. 09 1月, 2012 1 次提交
  23. 16 11月, 2011 1 次提交
  24. 07 10月, 2011 1 次提交
  25. 24 9月, 2011 1 次提交
  26. 23 8月, 2011 1 次提交
  27. 26 7月, 2011 2 次提交
  28. 19 5月, 2011 1 次提交
    • I
      misc: Add CARMA DATA-FPGA Access Driver · c186f0e1
      Ira Snyder 提交于
      This driver allows userspace to access the data processing FPGAs on the
      OVRO CARMA board. It has two modes of operation:
      
      1) random access
      
      This allows users to poke any DATA-FPGA registers by using mmap to map
      the address region directly into their memory map.
      
      2) correlation dumping
      
      When correlating, the DATA-FPGA's have special requirements for getting
      the data out of their memory before the next correlation. This nominally
      happens at 64Hz (every 15.625ms). If the data is not dumped before the
      next correlation, data is lost.
      
      The data dumping driver handles buffering up to 1 second worth of
      correlation data from the FPGAs. This lowers the realtime scheduling
      requirements for the userspace process reading the device.
      Signed-off-by: NIra W. Snyder <iws@ovro.caltech.edu>
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      c186f0e1
  29. 14 5月, 2011 1 次提交
    • J
      Intel PTI implementaiton of MIPI 1149.7. · 0b61d2ac
      J Freyensee 提交于
      The PTI (Parallel Trace Interface) driver directs
      trace data routed from various parts in the system out
      through an Intel Penwell PTI port and out of the mobile
      device for analysis with a debugging tool (Lauterbach or Fido).
      Though n_tracesink and n_tracerouter line discipline drivers
      are used to extract modem tracing data to the PTI driver
      and other parts of an Intel mobile solution, the PTI driver
      can be used independent of n_tracesink and n_tracerouter.
      
      You should select this driver if the target kernel is meant for
      an Intel Atom (non-netbook) mobile device containing a MIPI
      P1149.7 standard implementation.
      Signed-off-by: NJ Freyensee <james_p_freyensee@linux.intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      0b61d2ac
  30. 13 5月, 2011 1 次提交
  31. 23 3月, 2011 1 次提交
  32. 22 3月, 2011 1 次提交
  33. 15 3月, 2011 1 次提交
  34. 04 2月, 2011 1 次提交
  35. 14 1月, 2011 1 次提交
  36. 15 11月, 2010 1 次提交
  37. 29 10月, 2010 1 次提交
  38. 27 10月, 2010 2 次提交