~ [ 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 ] ~

Diff markup

Differences between /Documentation/devicetree/bindings/sifive/sifive-blocks-ip-versioning.txt (Version linux-6.12-rc7) and /Documentation/devicetree/bindings/sifive/sifive-blocks-ip-versioning.txt (Version linux-4.11.12)


  1 DT compatible string versioning for SiFive ope    
  2                                                   
  3 This document describes the version specificat    
  4 strings for open-source SiFive IP blocks.  HDL    
  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 co    
 10 in the form "sifive,<ip-block-name><integer ve    
 11                                                   
 12 An example is "sifive,uart0" from:                
 13                                                   
 14 https://github.com/sifive/sifive-blocks/blob/v    
 15                                                   
 16 Until these IP blocks (or IP integration) supp    
 17 auto-discovery, the maintainers of these IP bl    
 18 the suffixed number in the compatible string w    
 19 interface to these IP blocks changes, or when     
 20 underlying IP blocks changes in a way that sof    
 21                                                   
 22 Driver developers can use compatible string "m    
 23 "sifive,uart0" to indicate that their driver i    
 24 register interface and functionality associate    
 25 upstream sifive-blocks commits.  It is expecte    
 26 match on these IP block-specific compatible st    
 27                                                   
 28 DT data authors, when writing data for a parti    
 29 continue to specify an SoC-specific compatible    
 30 "sifive,fu540-c000-uart".  This way, if SoC-sp    
 31 integration-specific bug fixes or workarounds     
 32 or other system software can match on this str    
 33 IP block-specific compatible string (such as "    
 34 then be specified as a subsequent value.          
 35                                                   
 36 An example of this style:                         
 37                                                   
 38     compatible = "sifive,fu540-c000-uart", "si    
                                                      

~ [ 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