From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Biju <biju.das.au@gmail.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Biju Das <biju.das.jz@bp.renesas.com>,
linux-mmc@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH v3 0/2] Enable 64-bit polling mode for R-Car Gen3 and RZ/G2+ family
Date: Fri, 29 Aug 2025 12:26:48 +0200 [thread overview]
Message-ID: <aLGAaKYucaW1vPCg@shikoro> (raw)
In-Reply-To: <CAMuHMdWOMpZo0fVASyDV+XTLmh-o0ozqfF4Za_sPiydsh6LOfw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
> I believe some of the SoCs that do not support 64-bit accesses, do
> support 32-bit accesses. Do you think it would be worthwhile adding
> support for that, too?
We have that already? Check the context after the chunk added to
tmio_mmc_core.c:
if (host->pdata->flags & TMIO_MMC_32BIT_DATA_PORT) {
u32 data = 0;
u32 *buf32 = (u32 *)buf;
...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-08-29 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 16:46 [PATCH v3 0/2] Enable 64-bit polling mode for R-Car Gen3 and RZ/G2+ family Biju
2025-07-30 16:46 ` [PATCH v3 1/2] mmc: tmio: Add 64-bit read/write support for SD_BUF0 in polling mode Biju
2025-07-30 16:46 ` [PATCH v3 2/2] mmc: renesas_sdhi: Enable 64-bit " Biju
2025-08-18 10:55 ` [PATCH v3 0/2] Enable 64-bit polling mode for R-Car Gen3 and RZ/G2+ family Ulf Hansson
2025-08-29 9:51 ` Geert Uytterhoeven
2025-08-29 10:26 ` Wolfram Sang [this message]
2025-08-29 11:04 ` Geert Uytterhoeven
2025-08-29 11:24 ` Wolfram Sang
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=aLGAaKYucaW1vPCg@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=biju.das.au@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--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;
as well as URLs for NNTP newsgroup(s).