From: Mohamed via Bugspray Bot <bugbot@kernel.org>
To: linux-mmc@vger.kernel.org, ulf.hansson@linaro.org
Subject: Unaligned access in drivers/mmc/host/sdhci-of-k1.c (arch:ariscv soc:spacemit k1)
Date: Fri, 05 Dec 2025 21:00:05 +0000 [thread overview]
Message-ID: <20251205-b220841c0-b1d85d237308@bugzilla.kernel.org> (raw)
Mohamed writes via Kernel.org Bugzilla:
There is an unaligned access in spacemit_sdhci_set_uhs_signaling that calls spacemit_sdhci_setbits(host, SDHCI_CTRL_VDD_180, SDHCI_HOST_CONTROL2);
As SDHCI_HOST_CONTROL2 0x3E the helper function spacemit_sdhci_setbits uses readl and writel functions,
ie.
/* All helper functions will update clr/set while preserve rest bits */
static inline void spacemit_sdhci_setbits(struct sdhci_host *host, u32 val, int reg)
{
sdhci_writel(host, sdhci_readl(host, reg) | val, reg);
}
So you get an unaligned access exception/panic/oops with cause 5 on the read.
To reproduce this you need to enable the emmc in the dtb as none of the boards have this enabled. It seems a bit strange that the commit message says that the emmc is working, as it is disabled in the emmc, yet there is working version based on 6.6 which does work. Obviously, it must be my mistake as the commit message cannot possibly lie and say that a driver is complete and working.
View: https://bugzilla.kernel.org/show_bug.cgi?id=220841#c0
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)
next reply other threads:[~2025-12-05 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 21:00 Mohamed via Bugspray Bot [this message]
2025-12-09 7:35 ` Unaligned access in drivers/mmc/host/sdhci-of-k1.c (arch:ariscv soc:spacemit k1) Adrian Hunter
2025-12-11 1:10 ` Yixun Lan
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=20251205-b220841c0-b1d85d237308@bugzilla.kernel.org \
--to=bugbot@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