| commit | 2302fa41f66e1a1cfe1171b9dd798cdfba751b1f | [log] [tgz] |
|---|---|---|
| author | Jian Zhang <zhangjian.3032@bytedance.com> | Thu Mar 21 23:58:13 2024 +0800 |
| committer | Jian Zhang <zhangjian.3032@bytedance.com> | Fri Mar 22 10:41:49 2024 +0800 |
| tree | 7101a1e3e93f38770206feeb31ae4c6f45abdbd0 | |
| parent | 636a6d42d6ae5186528a06bb324f0d5f9df0b928 [diff] |
i2c: add tree.py to parse i2c bus info to tree The i2c topo is so complex if there are many i2c buses and muxes, it's hard to understand the i2c bus info from the output of "i2cdetect -l". This patch adds a python script to parse the i2c bus info to a tree, which is easy to understand. ps: maybe add a tree view to the i2ctools, but it's not easy to me. Example: ``` ssh user@<ip> "i2cdetect -l" | python tree.py root ├── i2c-4 │ ├── i2c-16 │ │ ├── i2c-129 │ │ ├── i2c-130 │ │ ├── i2c-131 │ │ └── i2c-132 │ ├── i2c-17 │ │ ├── i2c-113 │ │ ├── i2c-114 │ │ ├── i2c-115 │ │ ├── i2c-116 │ │ ├── i2c-117 │ │ ├── i2c-118 │ │ ├── i2c-119 │ │ └── i2c-120 │ ├── i2c-18 │ │ ├── i2c-105 │ │ ├── i2c-106 │ │ ├── i2c-107 │ │ ├── i2c-108 .... ``` Change-Id: Ia434b093c7ccff80ea52ad7416bcda609890cecd Signed-off-by: Jian Zhang <zhangjian.3032@bytedance.com>
The goal of this repository is to collect the two-minute hacks you write to automate interactions with OpenBMC systems.
It's highly likely the scripts don't meet your needs - they could be undocumented, dysfunctional or utterly broken. Please help us improve!
Then this repository aims to be the default destination for your otherwise un-homed scripts. As such we are setting the bar for submission pretty low, and we aim to make the process as easy as possible.
Please use gerrit for all patches to this repository:
Do note that you will need to be party to the OpenBMC CLA before your contributions can be accepted. See Gerrit Setup and CLA for more information.
So long as your patches look sane with a cursory glance you can expect them to be applied. We may push back in the event that similar tools already exist or there are egregious issues.
We don't ask for much, but you need to give us at least a Signed-off-by, use SPDX markers in your source files and put your work under an Apache 2.0 compatible license.
There's no standard way to install the scripts housed here, and adding parts of the repository to your PATH might be a bit of a dice-roll. We may also move or remove scripts from time to time as part of housekeeping. It's probably best to copy things out if you need stability.