aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/exported-sql-viewer.py
diff options
context:
space:
mode:
authorMartin Blumenstingl <martin.blumenstingl@googlemail.com>2019-05-11 19:45:34 +0200
committerKevin Hilman <khilman@baylibre.com>2019-05-21 10:58:40 -0700
commit890265c97941e10ea99203f082e0d108ed573999 (patch)
treeac0a2be08a2c7a064de7333d4397032ed45dd209 /tools/perf/scripts/python/exported-sql-viewer.py
parentarm64: dts: meson: u200: consistently order nodes (diff)
downloadlinux-dev-890265c97941e10ea99203f082e0d108ed573999.tar.xz
linux-dev-890265c97941e10ea99203f082e0d108ed573999.zip
arm64: dts: amlogic: remove ethernet-phy-idAAAA.BBBB compatible strings
The Ethernet PHY documentation (Documentation/devicetree/bindings/net/phy.txt) states that: If the PHY reports an incorrect ID (or none at all) then the "compatible" list may contain an entry with the correct PHY ID in the form: "ethernet-phy-idAAAA.BBBB" An older version of the documentation suggested that the compatible string can be used when the PHY ID is known. Remove the ethernet-phy-id compatible string and add a comment with the PHY ID instead. This is a no-op on boards which are shipped with the PHY that was listed (= all known cases). However, if a board manufacturer decides to ship a different PHY we will now load and use the correct driver because we ask the PHY to identify itself. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> Reviewed-by: Andrew Lunn <andrew@lunn.ch> Signed-off-by: Kevin Hilman <khilman@baylibre.com>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions