02 Aug, 2017

1 commit


23 Jun, 2017

1 commit

  • The Devicetree Specification has superseded the ePAPR as the
    base specification for bindings. Update files in Documentation
    to reference the new document.

    First reference to ePAPR in Documentation/devicetree/bindings/arm/cci.txt
    is generic, remove it.

    Some files are not updated because there is no hypervisor chapter
    in the Devicetree Specification:
    Documentation/devicetree/bindings/powerpc/fsl/msi-pic.txt
    Documenation/virtual/kvm/api.txt
    Documenation/virtual/kvm/ppc-pv.txt

    Signed-off-by: Frank Rowand
    Signed-off-by: Rob Herring

    Frank Rowand
     

13 Dec, 2016

1 commit

  • Summarize the "hotpluggable" property of dt memory nodes.

    Link: http://lkml.kernel.org/r/1479160961-25840-6-git-send-email-arbab@linux.vnet.ibm.com
    Signed-off-by: Reza Arbab
    Cc: "Aneesh Kumar K.V"
    Cc: "H. Peter Anvin"
    Cc: Alistair Popple
    Cc: Aneesh Kumar K.V
    Cc: Balbir Singh
    Cc: Benjamin Herrenschmidt
    Cc: Bharata B Rao
    Cc: Frank Rowand
    Cc: Ingo Molnar
    Cc: Michael Ellerman
    Cc: Nathan Fontenot
    Cc: Paul Mackerras
    Cc: Rob Herring
    Cc: Stewart Smith
    Cc: Thomas Gleixner
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Reza Arbab
     

18 Mar, 2016

1 commit

  • Add a new pseudo-board, within the existing SH boards/machine-vectors
    framework, which does not represent any actual hardware but instead
    requires all hardware to be described by the device tree blob provided
    by the boot loader. Changes made are thus non-invasive and do not risk
    breaking support for legacy boards.

    New hardware, including the open-hardware J2 and associated SoC
    devices, will use device free from the outset. Legacy SH boards can
    transition to device tree once all their hardware has device tree
    bindings, driver support for device tree, and a dts file for the
    board.

    It is intented that, once all boards are supported in the new
    framework, the existing machine-vectors framework should be removed
    and the new device tree setup code integrated directly.

    Signed-off-by: Rich Felker

    Rich Felker
     

08 May, 2015

1 commit

  • Open firmware is already using the serial-number property for passing the
    device's serial number from the bootloader to the kernel. In addition, lshw
    already has support for scanning this property.

    The serial number is a string that somewhat represents the device's serial
    number. It might come from some form of storage (e.g. an eeprom) and be
    programmed at factory-time by the manufacturer or come from identification
    bits available in e.g. the SoC (note that the soc_id property in the SoC bus
    should hold a full account of those bits).

    The serial number is taken as-is from the bootloader, so it is up to the
    bootloader to define where the serial number comes from and what length it
    should be. Some use cases for the serial number require it to have a maximum
    length (e.g. for USB serial number) and some other cases imply more restrictions
    on what the serial number should look like (e.g. in Android, the ro.serialno
    property is usually a 16-bytes (plus one null byte) representation of a 64 bit
    number).

    Signed-off-by: Paul Kocialkowski
    Acked-by: Rob Herring
    Signed-off-by: Russell King

    Paul Kocialkowski
     

01 Apr, 2015

1 commit

  • Add a new section covering the Generic BMIPS machine type.

    Signed-off-by: Kevin Cernekee
    Cc: f.fainelli@gmail.com
    Cc: jaedon.shin@gmail.com
    Cc: abrestic@chromium.org
    Cc: tglx@linutronix.de
    Cc: jason@lakedaemon.net
    Cc: jogo@openwrt.org
    Cc: arnd@arndb.de
    Cc: computersforpeace@gmail.com
    Cc: linux-mips@linux-mips.org
    Cc: devicetree@vger.kernel.org
    Cc: linux-kernel@vger.kernel.org
    Patchwork: https://patchwork.linux-mips.org/patch/8849/
    Signed-off-by: Ralf Baechle

    Kevin Cernekee
     

27 Sep, 2014

1 commit

  • Recently we introduced the generic device tree infrastructure for couple of DMA
    bus parameter, dma-ranges and dma-coherent. Update the documentation so that
    its useful for future users.

    The "dma-ranges" property is intended to be used for describing the
    configuration of DMA bus RAM addresses and its offset w.r.t CPU addresses.

    The "dma-coherent" property is intended to be used for identifying devices
    supported coherent DMA operations.

    Cc: Arnd Bergmann
    Cc: Grant Likely
    Cc: Rob Herring
    Cc: Pawel Moll
    Cc: Mark Rutland
    Cc: Ian Campbell
    Cc: Kumar Gala
    Acked-by: Shawn Guo
    Signed-off-by: Grygorii Strashko
    Signed-off-by: Santosh Shilimkar
    Signed-off-by: Rob Herring

    Santosh Shilimkar
     

16 Jan, 2014

1 commit

  • The device_type property is deprecated for the flattened device tree and
    the value "ethernet-phy" has never been defined as having a useful
    meaning. Neither the kernel nor u-boot depend on it. It should never
    have appeared in PHY bindings. This patch removes all references to
    "ethernet-phy" as a device_type value from the documentation and the
    .dts files.

    This patch was generated mechanically with the following command and
    then verified by looking at the diff.

    sed -i '/"ethernet-phy"/d' `git grep -l '"ethernet-phy"'`

    Signed-off-by: Grant Likely
    Acked-by: Srinivas Kandagatla
    Cc: Rob Herring
    Cc: Pawel Moll
    Cc: Mark Rutland
    Cc: Ian Campbell
    Cc: Kumar Gala
    Cc: Florian Fainelli
    Cc: Benjamin Herrenschmidt

    Grant Likely
     

22 Feb, 2013

1 commit

  • After I came across a help text for SUNGEM mentioning a broken sun.com
    URL, I felt like fixing those up, as they are now pointing to oracle.com
    URLs.

    Signed-off-by: Christian Kujau
    Acked-by: David S. Miller
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Christian Kujau
     

20 May, 2012

1 commit

  • Numeric values in dts files can be specified in decimal and hex (the latter
    prefixed 0x). The current documentation is updated with this patch to prevent
    confusion about what is meant with values without "0x" (previously hex, now
    dec).

    Signed-off-by: Roland Stigge
    Acked-by: Rob Landley
    Signed-off-by: Grant Likely

    Roland Stigge
     

07 Mar, 2012

1 commit


23 May, 2011

1 commit


05 Apr, 2011

1 commit


24 Feb, 2011

1 commit

  • 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: Sebastian Andrzej Siewior
    Signed-off-by: Dirk Brandewie
    Acked-by: Grant Likely
    Cc: sodaville@linutronix.de
    Cc: devicetree-discuss@lists.ozlabs.org
    LKML-Reference:
    Signed-off-by: Thomas Gleixner

    Sebastian Andrzej Siewior
     

14 Feb, 2011

1 commit


01 Feb, 2011

2 commits


31 Jan, 2011

1 commit