~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/Documentation/devicetree/bindings/sifive/sifive-blocks-ip-versioning.txt

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

  1 DT compatible string versioning for SiFive open-source IP blocks
  2 
  3 This document describes the version specification for DT "compatible"
  4 strings for open-source SiFive IP blocks.  HDL for these IP blocks
  5 can be found in this public repository:
  6 
  7 https://github.com/sifive/sifive-blocks
  8 
  9 IP block-specific DT compatible strings are contained within the HDL,
 10 in the form "sifive,<ip-block-name><integer version number>".
 11 
 12 An example is "sifive,uart0" from:
 13 
 14 https://github.com/sifive/sifive-blocks/blob/v1.0/src/main/scala/devices/uart/UART.scala#L43
 15 
 16 Until these IP blocks (or IP integration) support version
 17 auto-discovery, the maintainers of these IP blocks intend to increment
 18 the suffixed number in the compatible string whenever the software
 19 interface to these IP blocks changes, or when the functionality of the
 20 underlying IP blocks changes in a way that software should be aware of.
 21 
 22 Driver developers can use compatible string "match" values such as
 23 "sifive,uart0" to indicate that their driver is compatible with the
 24 register interface and functionality associated with the relevant
 25 upstream sifive-blocks commits.  It is expected that most drivers will
 26 match on these IP block-specific compatible strings.
 27 
 28 DT data authors, when writing data for a particular SoC, should
 29 continue to specify an SoC-specific compatible string value, such as
 30 "sifive,fu540-c000-uart".  This way, if SoC-specific
 31 integration-specific bug fixes or workarounds are needed, the kernel
 32 or other system software can match on this string to apply them.  The
 33 IP block-specific compatible string (such as "sifive,uart0") should
 34 then be specified as a subsequent value.
 35 
 36 An example of this style:
 37 
 38     compatible = "sifive,fu540-c000-uart", "sifive,uart0";

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php