From: Shawn Lin <shawn.lin@rock-chips.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Jaehoon Chung <jh80.chung@samsung.com>
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Shawn Lin <shawn.lin@rock-chips.com>
Subject: [PATCH 0/4] Refactoring to support per-instance configurable max segments for dw_mmc
Date: Thu, 9 Apr 2026 15:48:10 +0800 [thread overview]
Message-ID: <1775720894-97901-1-git-send-email-shawn.lin@rock-chips.com> (raw)
The first patch is a defensive fix that addresses a crash caused by
incorrect max segment numbers provided by host drivers. Patches 2
through 4 then perform a step-by-step refactoring of the dw_mmc
code to support per-instance configurable max segments, which host
drivers can utilize in the future.
Shawn Lin (4):
mmc: core: mmc: core: Add validation for host-provided max_segs
mmc: dw_mmc: Move misplaced comment
mmc: dw_mmc: Add desc_num field for clarity
mmc: dw_mmc: Convert descriptor ring buffer to per-instance
configurable
drivers/mmc/core/queue.c | 8 +++++++-
drivers/mmc/host/dw_mmc.c | 27 +++++++++++++--------------
drivers/mmc/host/dw_mmc.h | 4 +++-
3 files changed, 23 insertions(+), 16 deletions(-)
--
2.7.4
next reply other threads:[~2026-04-09 7:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 7:48 Shawn Lin [this message]
2026-04-09 7:48 ` [PATCH 1/4] mmc: core: mmc: core: Add validation for host-provided max_segs Shawn Lin
2026-04-09 7:48 ` [PATCH 2/4] mmc: dw_mmc: Move misplaced comment Shawn Lin
2026-04-09 7:48 ` [PATCH 3/4] mmc: dw_mmc: Add desc_num field for clarity Shawn Lin
2026-05-11 13:31 ` Ulf Hansson
2026-04-09 7:48 ` [PATCH 4/4] mmc: dw_mmc: Convert descriptor ring buffer to per-instance configurable Shawn Lin
2026-05-11 13:36 ` Ulf Hansson
2026-05-11 15:39 ` [PATCH 0/4] Refactoring to support per-instance configurable max segments for dw_mmc Ulf Hansson
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=1775720894-97901-1-git-send-email-shawn.lin@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
/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®