From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: BALATON Zoltan <balaton@eik.bme.hu>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: Bernhard Beschow <shentey@gmail.com>,
Jamin Lin <jamin_lin@aspeedtech.com>
Subject: Re: [PATCH] hw/sd/sdhci: Set reset value of interrupt registers
Date: Thu, 6 Feb 2025 11:00:48 +0100 [thread overview]
Message-ID: <8cbad5be-e67b-46bd-9198-f7c90ad5ff56@linaro.org> (raw)
In-Reply-To: <20250115190422.5F0FA4E6030@zero.eik.bme.hu>
On 15/1/25 20:04, BALATON Zoltan wrote:
> The interrupt enable registers are not reset to 0 but some bits are
> enabled on reset. At least some U-Boot versions seem to expect this
> and not initialise these registers before expecting interrupts. The
> numbers in this patch match what QorIQ P1022 has on reset and fix
> U-Boot for this SoC and should not break other drivers that initialise
> (and thus overwrite) these reset values.
>
> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
> ---
> I've also noticed that the work around marked with an XXX comment near
> line 600 breaks the U-Boot I've tested so I need to disable it:
> if ((s->sdmasysad % boundary_chk) == 0) {
> - page_aligned = true;
> +// page_aligned = true;
> }
> What should this hack fix and could it be now removed or somehow
> restricted to cases where it's needed?
Cc'ing Jamin for
https://lore.kernel.org/qemu-devel/20241213031205.641009-2-jamin_lin@aspeedtech.com/
>
> hw/sd/sdhci.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/hw/sd/sdhci.c b/hw/sd/sdhci.c
> index 58375483e3..88eb0bfcb2 100644
> --- a/hw/sd/sdhci.c
> +++ b/hw/sd/sdhci.c
> @@ -303,6 +303,8 @@ static void sdhci_reset(SDHCIState *s)
> s->data_count = 0;
> s->stopped_state = sdhc_not_stopped;
> s->pending_insert_state = false;
> + s->norintstsen = 0x013f;
> + s->errintstsen = 0x117f;
I guess the problem is earlier:
/*
* Set all registers to 0. Capabilities/Version registers are not
cleared
* and assumed to always preserve their value, given to them during
* initialization
*/
memset(&s->sdmasysad, 0, (uintptr_t)&s->capareg -
(uintptr_t)&s->sdmasysad);
Not all registers have to be reset.
next prev parent reply other threads:[~2025-02-06 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 19:04 [PATCH] hw/sd/sdhci: Set reset value of interrupt registers BALATON Zoltan
2025-01-30 12:46 ` BALATON Zoltan
2025-02-06 10:00 ` Philippe Mathieu-Daudé [this message]
2025-02-06 12:49 ` BALATON Zoltan
2025-02-06 13:20 ` Philippe Mathieu-Daudé
2025-02-06 13:49 ` BALATON Zoltan
2025-02-06 15:05 ` Philippe Mathieu-Daudé
2025-02-09 12:10 ` Bernhard Beschow
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=8cbad5be-e67b-46bd-9198-f7c90ad5ff56@linaro.org \
--to=philmd@linaro.org \
--cc=balaton@eik.bme.hu \
--cc=jamin_lin@aspeedtech.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shentey@gmail.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;
as well as URLs for NNTP newsgroup(s).