From: Michael Schmitz <schmitzmic@gmail.com>
To: Arnd Bergmann <arnd@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH v1 0/3] Converting m68k WD33C93 drivers to DMA API
Date: Thu, 30 Jun 2022 14:45:38 +1200 [thread overview]
Message-ID: <299b7b79-c8b9-46b8-8ae5-30ebd38e2c2c@gmail.com> (raw)
In-Reply-To: <CAK8P3a32A9eqQoOm9qyWV_XpQQnKyaEg5ULKyi1ZkDpn1onL5Q@mail.gmail.com>
Hi Arnd,
Am 30.06.2022 um 04:44 schrieb Arnd Bergmann:
> For simplicity, the normal bounce buffer could similarly use
> dma_alloc_coherent(), which will also result in an uncached
> buffer. If I read this correctly, this will also ensure that the buffer
No sure we can rule out calling dma_setup() in interrupt context.
> is within the DMA mask, so if ZONE_DMA is larger than the mask,
> it just returns NULL and you have to fall back to the chipram
> page, rather than checking the address and freeing the buffer.
Still need to check what ZONE_DMA is set to on Amiga.
Cheers,
Michael
>
> Arnd
>
next prev parent reply other threads:[~2022-06-30 2:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 1:16 [PATCH v1 0/3] Converting m68k WD33C93 drivers to DMA API Michael Schmitz
2022-06-29 1:16 ` [PATCH v1 1/3] scsi - a3000.c: convert " Michael Schmitz
2022-06-29 6:07 ` Arnd Bergmann
2022-06-29 1:16 ` [PATCH v1 2/3] scsi - a2091.c: " Michael Schmitz
2022-06-29 6:06 ` Arnd Bergmann
2022-06-29 7:26 ` Michael Schmitz
2022-06-29 15:55 ` Geert Uytterhoeven
2022-06-29 20:48 ` Michael Schmitz
2022-06-30 9:27 ` Geert Uytterhoeven
2022-06-30 19:42 ` Michael Schmitz
2022-06-29 1:16 ` [PATCH v1 3/3] scsi - gvp11.c: " Michael Schmitz
2022-06-29 6:02 ` Arnd Bergmann
2022-06-29 6:19 ` [PATCH v1 0/3] Converting " Arnd Bergmann
2022-06-29 7:36 ` Michael Schmitz
2022-06-29 8:20 ` Arnd Bergmann
2022-06-29 15:48 ` Geert Uytterhoeven
2022-06-29 16:44 ` Arnd Bergmann
2022-06-30 2:45 ` Michael Schmitz [this message]
2022-06-29 20:28 ` Michael Schmitz
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=299b7b79-c8b9-46b8-8ae5-30ebd38e2c2c@gmail.com \
--to=schmitzmic@gmail.com \
--cc=arnd@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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