Currently the usage of a second register range for MediaTek's MMC
controller is seen only on a few platforms. However the driver tries
to grab the register base regardless, and then ignores any errors.
This makes all the other platforms that don't need it produce confusing
error messages.
Instead, make the driver only grab the register range for platforms that
actually require it, and correctly handle the error. Also fix up the
binding so that validation of the "reg" property is as strict as
possible.
Please take a look.
Thanks
ChenYu
Chen-Yu Tsai (2):
dt-bindings: mmc: mtk-sd: Document compatibles that need two register
ranges
mmc: mtk-sd: Limit getting top_base to SoCs that require it
Documentation/devicetree/bindings/mmc/mtk-sd.yaml | 9 ++++++++-
drivers/mmc/host/mtk-sd.c | 15 +++++++++++----
2 files changed, 19 insertions(+), 5 deletions(-)
--
2.47.0.338.g60cca15819-goog
