Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 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
  3. 20 9月, 2012 1 次提交
  5. 18 9月, 2012 1 次提交
  7. 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
  9. 12 7月, 2012 1 次提交
  11. 10 5月, 2012 1 次提交
  13. 02 5月, 2012 1 次提交
  15. 19 4月, 2012 1 次提交
  17. 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
  19. 09 1月, 2012 1 次提交
  21. 16 11月, 2011 1 次提交
  23. 07 10月, 2011 1 次提交
  25. 24 9月, 2011 1 次提交
  27. 23 8月, 2011 1 次提交
  29. 26 7月, 2011 2 次提交
  31. 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
  33. 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
  35. 13 5月, 2011 1 次提交
  37. 23 3月, 2011 1 次提交
  39. 22 3月, 2011 1 次提交
  41. 15 3月, 2011 1 次提交
  43. 04 2月, 2011 1 次提交
  45. 14 1月, 2011 1 次提交
  47. 15 11月, 2010 1 次提交
  49. 29 10月, 2010 1 次提交
  51. 27 10月, 2010 6 次提交
  53. 23 10月, 2010 2 次提交
    • D
      hpilo: Despecificate driver from iLO generation · 1ce873ab
      由 dann frazier 提交于 
      This driver supports iLO, iLO2 and iLO3. However, comments and Kconfig
reference only iLO and iLO2. Let's just call it "iLO" to avoid having to
update strings for each iLO generation. This is similar to the change made
to hpwdt in commit 36e3ff44.
Signed-off-by: Ndann frazier <dannf@hp.com>
Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      1ce873ab
    • M
      add Packet hub driver for Topcliff Platform controller hub · cf4ece53
      由 Masayuki Ohtak 提交于 
      Packet hub driver of Topcliff PCH

Topcliff PCH is the platform controller hub that is going to be used in
Intel's upcoming general embedded platform. All IO peripherals in
Topcliff PCH are actually devices sitting on AMBA bus. Packet hub is
a special converter device in Topcliff PCH that translate AMBA transactions
to PCI Express transactions and vice versa. Thus packet hub helps present
all IO peripherals in Topcliff PCH as PCIE devices to IA system.
Topcliff PCH has MAC address and Option ROM data.
These data are in SROM which is connected to PCIE bus.
Packet hub driver of Topcliff PCH can access MAC address and Option ROM data in
SROM via sysfs interface.
Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      cf4ece53
  55. 18 10月, 2010 1 次提交
  57. 06 10月, 2010 1 次提交
  59. 23 9月, 2010 1 次提交
  61. 23 8月, 2010 1 次提交
  63. 10 8月, 2010 2 次提交