summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/gecko.py
diff options
context:
space:
mode:
authorChen-Yu Tsai <wenst@chromium.org>2023-09-13 11:44:56 +0300
committerAngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>2023-12-11 13:13:05 +0300
commit9a8014b1d4d2b1ffc53a844e07dfdd814b70dad0 (patch)
tree4eef8920afed59c4945e3349fd44473157a68e62 /tools/perf/scripts/python/gecko.py
parente97c618234d930469a080051c20d4261d27de34b (diff)
downloadlinux-9a8014b1d4d2b1ffc53a844e07dfdd814b70dad0.tar.xz
arm64: dts: mediatek: mt6358: Merge ldo_vcn33_* regulators
The ldo_vcn33_bt and ldo_vcn33_wifi regulators are actually the same regulator, having the same voltage setting and output pin. There are simply two enable bits that are ORed together to enable the regulator. Having two regulators representing the same output pin is misleading from a design matching standpoint, and also error-prone in driver implementations. Now that the bindings have these two merged, merge them in the device tree as well. Neither vcn33 regulators are referenced in upstream device trees. As far as hardware designs go, none of the Chromebooks using MT8183 w/ MT6358 use this output. Signed-off-by: Chen-Yu Tsai <wenst@chromium.org> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Diffstat (limited to 'tools/perf/scripts/python/gecko.py')
0 files changed, 0 insertions, 0 deletions