diff options
author | 2024-12-10 15:32:11 +0800 | |
---|---|---|
committer | 2024-12-18 15:57:59 +0100 | |
commit | 6ee5233a4c91fd0299c439b06d2d79bae54db4a3 (patch) | |
tree | 7154cf030b097f964c22f48763eeab35935dfa96 /scripts/gdb/linux/utils.py | |
parent | dt-bindings: mmc: mtk-sd: Document compatibles that need two register ranges (diff) | |
download | wireguard-linux-6ee5233a4c91fd0299c439b06d2d79bae54db4a3.tar.xz wireguard-linux-6ee5233a4c91fd0299c439b06d2d79bae54db4a3.zip |
mmc: mtk-sd: Limit getting top_base to SoCs that require it
Currently the mtk-sd driver tries to get and map the second register
base, named top_base in the code, regardless of whether the SoC model
actually has it or not. This produces confusing big error messages on
the platforms that don't need it:
mtk-msdc 11260000.mmc: error -EINVAL: invalid resource (null)
Limit it to the platforms that actually require it, based on their
device tree entries, and properly fail if it is missing.
Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Message-ID: <20241210073212.3917912-3-wenst@chromium.org>
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions