1*4882a593SmuzhiyunLinux Devlink Documentation 2*4882a593Smuzhiyun=========================== 3*4882a593Smuzhiyun 4*4882a593Smuzhiyundevlink is an API to expose device information and resources not directly 5*4882a593Smuzhiyunrelated to any device class, such as chip-wide/switch-ASIC-wide configuration. 6*4882a593Smuzhiyun 7*4882a593SmuzhiyunInterface documentation 8*4882a593Smuzhiyun----------------------- 9*4882a593Smuzhiyun 10*4882a593SmuzhiyunThe following pages describe various interfaces available through devlink in 11*4882a593Smuzhiyungeneral. 12*4882a593Smuzhiyun 13*4882a593Smuzhiyun.. toctree:: 14*4882a593Smuzhiyun :maxdepth: 1 15*4882a593Smuzhiyun 16*4882a593Smuzhiyun devlink-dpipe 17*4882a593Smuzhiyun devlink-health 18*4882a593Smuzhiyun devlink-info 19*4882a593Smuzhiyun devlink-flash 20*4882a593Smuzhiyun devlink-params 21*4882a593Smuzhiyun devlink-region 22*4882a593Smuzhiyun devlink-resource 23*4882a593Smuzhiyun devlink-reload 24*4882a593Smuzhiyun devlink-trap 25*4882a593Smuzhiyun 26*4882a593SmuzhiyunDriver-specific documentation 27*4882a593Smuzhiyun----------------------------- 28*4882a593Smuzhiyun 29*4882a593SmuzhiyunEach driver that implements ``devlink`` is expected to document what 30*4882a593Smuzhiyunparameters, info versions, and other features it supports. 31*4882a593Smuzhiyun 32*4882a593Smuzhiyun.. toctree:: 33*4882a593Smuzhiyun :maxdepth: 1 34*4882a593Smuzhiyun 35*4882a593Smuzhiyun bnxt 36*4882a593Smuzhiyun ionic 37*4882a593Smuzhiyun ice 38*4882a593Smuzhiyun mlx4 39*4882a593Smuzhiyun mlx5 40*4882a593Smuzhiyun mlxsw 41*4882a593Smuzhiyun mv88e6xxx 42*4882a593Smuzhiyun netdevsim 43*4882a593Smuzhiyun nfp 44*4882a593Smuzhiyun sja1105 45*4882a593Smuzhiyun qed 46*4882a593Smuzhiyun ti-cpsw-switch 47