summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorEugen Hristev <eugen.hristev@collabora.com>2023-08-14 12:39:30 +0300
committerVinod Koul <vkoul@kernel.org>2023-08-22 19:28:10 +0530
commit188a447b20f83b58f89413aaa811d7f1dc247638 (patch)
treeae093b61fb464471289febe8736a867cf12e46a1 /tools/perf/scripts/python/export-to-sqlite.py
parentffc1786c3f4174b9e44a537cb1cecb7ba6b756ff (diff)
dt-bindings: phy: mediatek,tphy: allow simple nodename pattern
The pattern for the nodename only allows t-phy@... , however, for the case when the t-phy has no `reg` and only `ranges` (basically when the t-phy is just a parent node), dtc will throw this warning: Warning (unit_address_vs_reg): /t-phy@1a243000: node has a unit name, but no reg or ranges property For a node like this: sata_phy: t-phy@1a243000 { ranges; sata_port: sata-phy@1a243000 { reg = <0 0x1a243000 0 0x0100>; }; }; it is normal that the parent node 't-phy' would be without any address, as in: sata_phy: t-phy { ranges; sata_port: sata-phy@1a243000 { reg = <0 0x1a243000 0 0x0100>; }; }; because being just a holder it does not have its own reg. However the binding does not allow such a name for the t-phy, so with this patch, making the `@[0-9a-f]+` part optional, such node is possible. Signed-off-by: Eugen Hristev <eugen.hristev@collabora.com> Acked-by: Conor Dooley <conor.dooley@microchip.com> Link: https://lore.kernel.org/r/20230814093931.9298-1-eugen.hristev@collabora.com Signed-off-by: Vinod Koul <vkoul@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions