From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Bernhard Beschow <shentey@gmail.com>
Subject: Re: [PATCH v2] hw/sd/sdhci: Set reset value of interrupt registers
Date: Tue, 11 Mar 2025 10:51:57 +0100 [thread overview]
Message-ID: <a6a2ddc4-dca5-4234-9254-eacea37efe47@linaro.org> (raw)
In-Reply-To: <0f3814d3-7c27-fd50-2ad3-b4d5344d9fc1@eik.bme.hu>
On 6/3/25 19:23, BALATON Zoltan wrote:
> On Mon, 3 Mar 2025, BALATON Zoltan wrote:
>> On Mon, 3 Mar 2025, Philippe Mathieu-Daudé wrote:
>>> Hi Zoltan,
>>>
>>> On 10/2/25 17:03, BALATON Zoltan wrote:
>>>> The interrupt enable registers are not reset to 0 on Freescale eSDHC
>>>> 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. Use existing vendor property for Freescale eSDHC and set
>>>> the reset value of the interrupt registers to match Freescale
>>>> documentation.
>>>>
>>>> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
>>>> ---
>>>> v2: Restrict to e500. Adding a reset method in a subclass does not
>>>> work because the common reset function is called directly on register
>>>> write from the guest but there's already provision for vendor specific
>>>> behaviour which can be used to restrict this to Freescale SoCs.
>>>>
>>>> hw/ppc/e500.c | 1 +
>>>> hw/sd/sdhci.c | 4 ++++
>>>> include/hw/sd/sdhci.h | 1 +
>>>> 3 files changed, 6 insertions(+)
> This patch wasn't in the pull request but I haven't seen an answer to
> this message either so was it missed or do you have furhter comments?
> Bernhard has a comment about naming of SDHCI_VENDOR_FSL but I think the
> already existing IMX name is what's wrong not the one added in this
> patch but I don't think that's really that confusing to worth further
> effort. We still have time as this can be considered a fix but I'd like
> this to not get forgotten so I bring it up again.
Patch queued, thanks.
prev parent reply other threads:[~2025-03-11 9:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 16:03 [PATCH v2] hw/sd/sdhci: Set reset value of interrupt registers BALATON Zoltan
2025-03-01 16:02 ` BALATON Zoltan
2025-03-03 8:03 ` Bernhard Beschow
2025-03-03 10:31 ` BALATON Zoltan
2025-03-03 10:58 ` Philippe Mathieu-Daudé
2025-03-03 11:07 ` BALATON Zoltan
2025-03-06 18:23 ` BALATON Zoltan
2025-03-08 18:20 ` Philippe Mathieu-Daudé
2025-03-11 9:51 ` Philippe Mathieu-Daudé [this message]
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=a6a2ddc4-dca5-4234-9254-eacea37efe47@linaro.org \
--to=philmd@linaro.org \
--cc=balaton@eik.bme.hu \
--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).