From: Chen-Yu Tsai <wenst@chromium.org>
To: Chaotian Jing <chaotian.jing@mediatek.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Wenbin Mei <wenbin.mei@mediatek.com>
Cc: Chen-Yu Tsai <wenst@chromium.org>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
Frank Wunderlich <frank-w@public-files.de>,
Andy-ld Lu <andy-ld.lu@mediatek.com>
Subject: [PATCH 0/2] mmc: mtk-sd: Limit second register range to SoCs requiring it
Date: Wed, 4 Dec 2024 17:28:51 +0800 [thread overview]
Message-ID: <20241204092855.1365638-1-wenst@chromium.org> (raw)
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
next reply other threads:[~2024-12-04 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 9:28 Chen-Yu Tsai [this message]
2024-12-04 9:28 ` [PATCH 1/2] dt-bindings: mmc: mtk-sd: Document compatibles that need two register ranges Chen-Yu Tsai
2024-12-04 10:33 ` Frank Wunderlich
2024-12-05 3:41 ` Chen-Yu Tsai
2024-12-09 10:14 ` AngeloGioacchino Del Regno
2024-12-04 9:28 ` [PATCH 2/2] mmc: mtk-sd: Limit getting top_base to SoCs that require it Chen-Yu Tsai
2024-12-09 10:14 ` AngeloGioacchino Del Regno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241204092855.1365638-1-wenst@chromium.org \
--to=wenst@chromium.org \
--cc=andy-ld.lu@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chaotian.jing@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=wenbin.mei@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®