1. 17 11月, 2012 1 次提交
  2. 18 10月, 2012 1 次提交
  3. 01 10月, 2012 1 次提交
  4. 22 9月, 2012 1 次提交
  5. 18 9月, 2012 1 次提交
  6. 20 8月, 2012 1 次提交
  7. 11 7月, 2012 1 次提交
  8. 06 7月, 2012 1 次提交
  9. 16 6月, 2012 2 次提交
    • P
      irqdomain: Simple NUMA awareness. · 5ca4db61
      Paul Mundt 提交于
      While common irqdesc allocation is node aware, the irqdomain code is not.
      
      Presently we observe a number of regressions/inconsistencies on
      NUMA-capable platforms:
      
      - Platforms using irqdomains with legacy mappings, where the
        irq_descs are allocated node-local and the irqdomain data
        structure is not.
      
      - Drivers implementing irqdomains will lose node locality
        regardless of the underlying struct device's node id.
      
      This plugs in NUMA node id proliferation across the various allocation
      callsites by way of_node_to_nid() node lookup. While of_node_to_nid()
      does the right thing for OF-capable platforms it doesn't presently handle
      the non-DT case. This is trivially dealt with by simply wraping in to
      numa_node_id() unconditionally.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Rob Herring <rob.herring@calxeda.com>
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      5ca4db61
    • G
      devicetree: add helper inline for retrieving a node's full name · efd68e72
      Grant Likely 提交于
      The pattern (np ? np->full_name : "<none>") is rather common in the
      kernel, but can also make for quite long lines.  This patch adds a new
      inline function, of_node_full_name() so that the test for a valid node
      pointer doesn't need to be open coded at all call sites.
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      Cc: Paul Mundt <lethal@linux-sh.org>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      efd68e72
  10. 15 6月, 2012 2 次提交
  11. 02 5月, 2012 1 次提交
  12. 18 4月, 2012 1 次提交
    • S
      dt: add property iteration helpers · c541adc6
      Stephen Warren 提交于
      This patch adds macros of_property_for_each_u32() and
      of_property_for_each_string(), which iterate over an array of values
      within a device-tree property. Usage is for example:
      
      struct property *prop;
      const __be32 *p;
      u32 u;
      of_property_for_each_u32(np, "propname", prop, p, u)
      	printk("U32 value: %x\n", u);
      
      struct property *prop;
      const char *s;
      of_property_for_each_string(np, "propname", prop, s)
      	printk("String value: %s\n", s);
      
      Based on work by Rob Herring <robherring2@gmail.com>
      
      Cc: Grant Likely <grant.likely@secretlab.ca>
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Acked-by: NRob Herring <rob.herring@calxeda.com>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      c541adc6
  13. 28 3月, 2012 1 次提交
  14. 15 3月, 2012 1 次提交
  15. 09 3月, 2012 1 次提交
    • G
      powerpc/eeh: Introduce EEH device · eb740b5f
      Gavin Shan 提交于
      Original EEH implementation depends on struct pci_dn heavily. However,
      EEH shouldn't depend on that actually because EEH needn't share much
      information with other PCI components. That's to say, EEH should have
      worked independently.
      
      The patch introduces struct eeh_dev so that EEH core components needn't
      be working based on struct pci_dn in future. Also, struct pci_dn, struct
      eeh_dev instances are created in dynamic fasion and the binding with EEH
      device, OF node, PCI device is implemented as well.
      
      The EEH devices are created after PHBs are detected and initialized, but
      PCI emunation hasn't started yet. Apart from that, PHB might be created
      dynamically through DLPAR component and the EEH devices should be creatd
      as well. Another case might be OF node is created dynamically by DR
      (Dynamic Reconfiguration), which has been defined by PAPR. For those OF
      nodes created by DR, EEH devices should be also created accordingly. The
      binding between EEH device and OF node is done while the EEH device is
      initially created.
      
      The binding between EEH device and PCI device should be done after PCI
      emunation is done. Besides, PCI hotplug also needs the binding so that
      the EEH devices could be traced from the newly coming PCI buses or PCI
      devices.
      Signed-off-by: NGavin Shan <shangw@linux.vnet.ibm.com>
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      eb740b5f
  16. 22 2月, 2012 1 次提交
  17. 16 2月, 2012 1 次提交
  18. 29 1月, 2012 1 次提交
  19. 28 12月, 2011 2 次提交
  20. 13 12月, 2011 1 次提交
    • G
      of: create of_phandle_args to simplify return of phandle parsing data · 15c9a0ac
      Grant Likely 提交于
      of_parse_phandle_with_args() needs to return quite a bit of data.  Rather
      than making each datum a separate **out_ argument, this patch creates
      struct of_phandle_args to contain all the returned data and reworks the
      user of the function.  This patch also enables of_parse_phandle_with_args()
      to return the device node pointer for the phandle node.
      
      This patch also ends up being fairly major surgery to
      of_parse_handle_with_args().  The existing structure didn't work well
      when extending to use of_phandle_args, and I discovered bugs during testing.
      I also took the opportunity to rename the function to be like the
      existing of_parse_phandle().
      
      v2: - moved declaration of of_phandle_args to fix compile on non-DT builds
          - fixed incorrect index in example usage
          - fixed incorrect return code handling for empty entries
      Reviewed-by: NShawn Guo <shawn.guo@freescale.com>
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      15c9a0ac
  21. 04 11月, 2011 1 次提交
  22. 01 11月, 2011 1 次提交
  23. 29 10月, 2011 2 次提交
  24. 24 10月, 2011 1 次提交
  25. 14 10月, 2011 1 次提交
  26. 05 10月, 2011 2 次提交
  27. 30 9月, 2011 1 次提交
  28. 23 9月, 2011 2 次提交
  29. 10 8月, 2011 1 次提交
  30. 04 8月, 2011 1 次提交
  31. 03 8月, 2011 1 次提交
  32. 02 8月, 2011 1 次提交
  33. 09 7月, 2011 1 次提交
  34. 07 7月, 2011 1 次提交