Skip to content
Snippets Groups Projects
  1. Jul 10, 2011
  2. May 23, 2011
  3. May 19, 2011
  4. May 10, 2011
  5. Apr 04, 2011
  6. Mar 31, 2011
  7. Mar 26, 2011
  8. Mar 22, 2011
  9. Mar 21, 2011
  10. Mar 20, 2011
    • Meador Inge's avatar
      powerpc: Document the Open PIC device tree binding · a99eff39
      Meador Inge authored
      
      This binding documents several properties that have been in use for quite
      some time, and adds one new property 'pic-no-reset', which controls the
      runtime initialization behavior of the PIC.  More specifically, the presence
      of 'pic-no-reset' mandates that the PIC shall not be reset during runtime
      initialization and that any initialization related to interrupt sources
      shall be limited to sources explicitly referenced in the device tree.  This
      functionality is useful in AMP systems where multiple OSes are sharing the
      PIC and the reinitialization of the PIC can interfere with OSes that are
      already up and running.
      
      The interrupt specifier definition is based off of Stuart Yoder's FSL MPIC
      binding.
      
      Signed-off-by: default avatarMeador Inge <meador_inge@mentor.com>
      Cc: Grant Likely <grant.likely@secretlab.ca>
      Cc: Stuart Yoder <stuart.yoder@freescale.com>
      Cc: Hollis Blanchard <hollis_blanchard@mentor.com>
      Signed-off-by: default avatarBenjamin Herrenschmidt <benh@kernel.crashing.org>
      a99eff39
  11. Mar 16, 2011
  12. Mar 15, 2011
  13. Mar 01, 2011
  14. Feb 28, 2011
  15. Feb 23, 2011
    • Sebastian Andrzej Siewior's avatar
      rtc: cmos: Add OF bindings · 3bcbaf6e
      Sebastian Andrzej Siewior authored
      
      This allows to load the OF driver based informations from the device
      tree. Systems without BIOS may need to perform some initialization.
      PowerPC creates a PNP device from the OF information and performs this
      kind of initialization in their private PCI quirk. This looks more
      generic.
      
      This patch also avoids registering the platform RTC driver on X86 if
      we have a device tree blob. Otherwise we would setup the device based
      on the hardcoded information in arch/x86 rather than the device tree
      based one.
      
      [ tglx: Changed "int of_have_populated_dt()" to bool as recommended by
              Grant ]
      
      Signed-off-by: default avatarSebastian Andrzej Siewior <bigeasy@linutronix.de>
      Signed-off-by: default avatarDirk Brandewie <dirk.brandewie@gmail.com>
      Acked-by: default avatarGrant Likely <grant.likely@secretlab.ca>
      Cc: sodaville@linutronix.de
      Cc: devicetree-discuss@lists.ozlabs.org
      Cc: rtc-linux@googlegroups.com
      Cc: Alessandro Zummo <a.zummo@towertech.it>
      LKML-Reference: <1298405266-1624-12-git-send-email-bigeasy@linutronix.de>
      Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
      3bcbaf6e
    • Sebastian Andrzej Siewior's avatar
      x86: dtb: Add a device tree for CE4100 · df2634f4
      Sebastian Andrzej Siewior authored
      
      History:
      v1..v2:
      - dropped device_type except for cpu & pci. I have the compatible string
        for pci so I can drop the device_type once it is possible
      - I lowercased all compatible types. I will need to resend some patches
        which have upper case intel
      - The cpu had the same compatible string as the soc node. So I added to
        the soc node -immr for internel memory mapped registers.
      - I added generic names for all parts.
      - I reworked the i2c bars matching the way you suggested. I added a
        compatible node for the PCI device which only the PCI ids in its
        compatible string. The bars (each represents a complete i2c
        controller) have a "intel,ce4100-i2c-controller" compatible node. It
        is not used by the driver.
        The driver is probed via PCI ids (by the pci subsystem not OF) and
        matches the bar address against the ressource in the child node. Once
        there is a hit the node is attached.
      - The SPI driver is also probed via pci. However I also attached a
        compatible property based on PCI ids
      
      v2..v3:
      - intel,ce4100-immr become intel,ce4100-cp. cp stands for core
        peripherals. The Atom data sheet talks here about ACPI devices. Since
        we don't have ACPI this does not apply here.
      - The interrupt map is gone. There are now plenty of device nodes.
      - The "unit address string" got fixed, it uses not DD,V format.
      
      v3..v4:
      - added descriptions for compatible nodes introduced here:
        - intel,ce4100-ioapic
        - intel,ce4100-lapic
        - intel,ce4100-hpet
        - intel,ce4100
        - intel,ce4100-cp
        - intel,ce4100-pci
      - added a description about I2C controller magic.
      - Added gpio-controller and gpio-cells property to gpio devices. Those
        properties are not (yet) used.
      
      Signed-off-by: default avatarSebastian Andrzej Siewior <bigeasy@linutronix.de>
      Signed-off-by: default avatarDirk Brandewie <dirk.brandewie@gmail.com>
      Acked-by: default avatarGrant Likely <grant.likely@secretlab.ca>
      Cc: sodaville@linutronix.de
      Cc: devicetree-discuss@lists.ozlabs.org
      LKML-Reference: <1298405266-1624-4-git-send-email-bigeasy@linutronix.de>
      Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
      df2634f4
    • Sebastian Andrzej Siewior's avatar
      x86: Add device tree support · da6b737b
      Sebastian Andrzej Siewior authored
      
      This patch adds minimal support for device tree on x86. The device
      tree blob is passed to the kernel via setup_data which requires at
      least boot protocol 2.09.
      
      Memory size, restricted memory regions, boot arguments are gathered
      the traditional way so things like cmd_line are just here to let the
      code compile.
      
      The current plan is use the device tree as an extension and to gather
      information which can not be enumerated and would have to be hardcoded
      otherwise. This includes things like 
         - which devices are on this I2C/SPI bus?
         - how are the interrupts wired to IO APIC?
         - where could my hpet be?
      
      Signed-off-by: default avatarSebastian Andrzej Siewior <bigeasy@linutronix.de>
      Signed-off-by: default avatarDirk Brandewie <dirk.brandewie@gmail.com>
      Acked-by: default avatarGrant Likely <grant.likely@secretlab.ca>
      Cc: sodaville@linutronix.de
      Cc: devicetree-discuss@lists.ozlabs.org
      LKML-Reference: <1298405266-1624-3-git-send-email-bigeasy@linutronix.de>
      Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
      da6b737b
  16. Feb 22, 2011
  17. Feb 15, 2011
  18. Feb 14, 2011
  19. Jan 31, 2011
Loading