Lines Matching +full:board +full:- +full:specific

1 .. SPDX-License-Identifier: GPL-2.0
16 - Board name, specified at depthcharge_ compile time. This is $(BOARD) below.
17 - Board revision number, determined at runtime (perhaps by reading GPIO
19 - SKU number, read from GPIO strappings at boot time. This is $(SKU) below.
23 - google,$(BOARD)-rev$(REV)-sku$(SKU)
24 - google,$(BOARD)-rev$(REV)
25 - google,$(BOARD)-sku$(SKU)
26 - google,$(BOARD)
31 Note that for some boards there may be extra board-specific logic to inject
35 find one that matches the most specific compatible. It will then look
37 matches the *second most* specific compatible, etc.
41 As an example, if we're on board "lazor", rev 4, SKU 0 and we have two device
44 - "google,lazor-rev5-sku0", "google,lazor-rev4-sku0", "qcom,sc7180"
45 - "google,lazor", "qcom,sc7180"
48 "google,lazor-rev4-sku0" was the second compatible listed in that device tree.
49 This is because it is a more specific compatible than "google,lazor".
52 match board or SKU revisions that are "close by". That is to say that
53 if depthcharge_ knows it's on "rev4" of a board but there is no "rev4"
56 In general when any significant changes are made to a board the board
63 supporting the newest revision(s) of a board omits the "-rev{REV}"
64 compatible strings. When this is done then if you get a new board