1. 22 2月, 2013 4 次提交
  2. 20 2月, 2013 2 次提交
  3. 19 2月, 2013 4 次提交
  4. 18 2月, 2013 1 次提交
  5. 17 2月, 2013 1 次提交
  6. 16 2月, 2013 5 次提交
  7. 15 2月, 2013 6 次提交
  8. 14 2月, 2013 7 次提交
  9. 13 2月, 2013 5 次提交
    • T
      ACPI: Remove the use of CONFIG_ACPI_CONTAINER_MODULE · 64fd7401
      Toshi Kani 提交于
      config ACPI_CONTAINER has been changed to bool (y/n), and its
      module option is no longer valid.  So, remove the use of
      CONFIG_ACPI_CONTAINER_MODULE.
      Signed-off-by: NToshi Kani <toshi.kani@hp.com>
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      64fd7401
    • G
      gpio: Make of_count_named_gpios() use new of_count_phandle_with_args() · e80beb27
      Grant Likely 提交于
      This patch replaces the horribly coded of_count_named_gpios() with a
      call to of_count_phandle_with_args() which is far more efficient. This
      also changes the return value of of_gpio_count() & of_gpio_named_count()
      from 'unsigned int' to 'int' so that it can return an error code. All
      the users of that function are fixed up to correctly handle a negative
      return value.
      
      v2: Split GPIO portion into a separate patch
      Tested-by: NAndreas Larsson <andreas@gaisler.com>
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      Cc: Linus Walleij <linus.walleij@linaro.org>
      Cc: Rob Herring <rob.herring@calxeda.com>
      e80beb27
    • G
      of: Create function for counting number of phandles in a property · bd69f73f
      Grant Likely 提交于
      This patch creates of_count_phandle_with_args(), a new function for
      counting the number of phandle+argument tuples in a given property. This
      is better than the existing method of parsing each phandle individually
      until parsing fails which is a horribly slow way to do the count.
      
      Tested on ARM using the selftest code.
      
      v3: - Rebased on top of selftest code cleanup patch
      v2: - fix bug where of_parse_phandle_with_args() could behave like _count_.
          - made of_gpio_named_count() into a static inline regardless of CONFIG_OF_GPIO
      Tested-by: NAndreas Larsson <andreas@gaisler.com>
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      Cc: Linus Walleij <linus.walleij@linaro.org>
      Cc: Rob Herring <rob.herring@calxeda.com>
      bd69f73f
    • M
      driver: net: ethernet: cpsw: dual emac interface implementation · d9ba8f9e
      Mugunthan V N 提交于
      The CPSW switch can act as Dual EMAC by segregating the switch ports
      using VLAN and port VLAN as per the TRM description in
      14.3.2.10.2 Dual Mac Mode
      
      Following CPSW components will be common for both the interfaces.
      * Interrupt source is common for both eth interfaces
      * Interrupt pacing is common for both interfaces
      * Hardware statistics is common for all the ports
      * CPDMA is common for both eth interface
      * CPTS is common for both the interface and it should not be enabled on
        both the interface as timestamping information doesn't contain port
        information.
      
      Constrains
      * Reserved VID of One port should not be used in other interface which will
        enable switching functionality
      * Same VID must not be used in both the interface which will enable switching
        functionality
      Signed-off-by: NMugunthan V N <mugunthanvnm@ti.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d9ba8f9e
    • S
      efi_pstore: Introducing workqueue updating sysfs · a93bc0c6
      Seiji Aguchi 提交于
      [Problem]
      efi_pstore creates sysfs entries, which enable users to access to NVRAM,
      in a write callback. If a kernel panic happens in an interrupt context,
      it may fail because it could sleep due to dynamic memory allocations during
      creating sysfs entries.
      
      [Patch Description]
      This patch removes sysfs operations from a write callback by introducing
      a workqueue updating sysfs entries which is scheduled after the write
      callback is called.
      
      Also, the workqueue is kicked in a just oops case.
      A system will go down in other cases such as panic, clean shutdown and emergency
      restart. And we don't need to create sysfs entries because there is no chance for
      users to access to them.
      
      efi_pstore will be robust against a kernel panic in an interrupt context with this patch.
      Signed-off-by: NSeiji Aguchi <seiji.aguchi@hds.com>
      Acked-by: NMatt Fleming <matt.fleming@intel.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      a93bc0c6
  10. 12 2月, 2013 3 次提交
  11. 11 2月, 2013 2 次提交
    • D
      net/802: Implement Multiple Registration Protocol (MRP) · febf018d
      David Ward 提交于
      Initial implementation of the Multiple Registration Protocol (MRP)
      from IEEE 802.1Q-2011, based on the existing implementation of the
      Generic Attribute Registration Protocol (GARP).
      Signed-off-by: NDavid Ward <david.ward@ll.mit.edu>
      Acked-by: NPatrick McHardy <kaber@trash.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      febf018d
    • A
      VSOCK: Introduce VM Sockets · d021c344
      Andy King 提交于
      VM Sockets allows communication between virtual machines and the hypervisor.
      User level applications both in a virtual machine and on the host can use the
      VM Sockets API, which facilitates fast and efficient communication between
      guest virtual machines and their host.  A socket address family, designed to be
      compatible with UDP and TCP at the interface level, is provided.
      
      Today, VM Sockets is used by various VMware Tools components inside the guest
      for zero-config, network-less access to VMware host services.  In addition to
      this, VMware's users are using VM Sockets for various applications, where
      network access of the virtual machine is restricted or non-existent.  Examples
      of this are VMs communicating with device proxies for proprietary hardware
      running as host applications and automated testing of applications running
      within virtual machines.
      
      The VMware VM Sockets are similar to other socket types, like Berkeley UNIX
      socket interface.  The VM Sockets module supports both connection-oriented
      stream sockets like TCP, and connectionless datagram sockets like UDP. The VM
      Sockets protocol family is defined as "AF_VSOCK" and the socket operations
      split for SOCK_DGRAM and SOCK_STREAM.
      
      For additional information about the use of VM Sockets, please refer to the
      VM Sockets Programming Guide available at:
      
      https://www.vmware.com/support/developer/vmci-sdk/Signed-off-by: NGeorge Zhang <georgezhang@vmware.com>
      Signed-off-by: NDmitry Torokhov <dtor@vmware.com>
      Signed-off-by: NAndy king <acking@vmware.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d021c344