summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2024-02-03 15:50:45 +0300
committerDavid S. Miller <davem@davemloft.net>2024-02-03 15:50:45 +0300
commitd6aa8e0aa605a6baba08220e4a83fa2619a4c4d7 (patch)
treea01b18cf0669e7bdc8bfb78c45300a6217c4b5b5 /tools/perf/scripts/python/export-to-sqlite.py
parent0eb1ec426cfcdac021c3f5c0c8fc1127047050e5 (diff)
parentf203c8c77c7616c099647636f4c67d59a45fe8a2 (diff)
downloadlinux-d6aa8e0aa605a6baba08220e4a83fa2619a4c4d7.tar.xz
Merge branch 'qca-phy-led-fixes'
Christian Marangi says: ==================== net: phy: qcom: qca808x: fixup qca808x LED This is a bit embarassing and totally my fault so sorry for that! While reworking the patch to phy_modify API, it was done a logic error and made the brightness_set function broken. It wasn't notice in last revisions test as the testing method was to verify if hw control was correctly working. Noticing this problem also made me notice an additional problem with the polarity. The introduced patch made the polarity configurable but I forgot to add the required code to enable Active High by default. (the PHY sets active low by default) This wasn't notice with hw control testing as the LED blink on traffic and polarity problem are not notice. It might be worth discussing if needed a change in implementation where the polarity function is always called but I think it's better this way where specific PHY apply fixup with the help of priv struct and on the config_init phase. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions