From: Rob Landley <rob@landley.net>
To: Christoph Hellwig <hch@lst.de>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: dma_declare_coherent_memory and SuperH
Date: Mon, 28 Jun 2021 09:29:59 -0500 [thread overview]
Message-ID: <1141b20f-7cdf-1477-ef51-876226db7a37@landley.net> (raw)
In-Reply-To: <20210628134955.GA22559@lst.de>
On 6/28/21 8:49 AM, Christoph Hellwig wrote:
> On Mon, Jun 28, 2021 at 09:04:19AM -0500, Rob Landley wrote:
>> > Well, the replacement is to declare the device memory carveouts in the
>> > Device Tree.
>>
>> Your plan is to eliminate the ability for non-device-tree boards to do DMA?
>
> No. My hope is to kill dma_declarare_coherent, an API for board
> support files to declare device-specific regions to be used for
> coherent DMA.
Q) If I haven't got regression test hardware to make sure I properly converted
each of these entire boards to device tree, Is there anything else I can do to
help you remove this function from common code, such as inlining some portion of
this function?
A) You can convert the board to device tree.
Which part of this exchange have I misunderstood?
Rob
next prev parent reply other threads:[~2021-06-28 14:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 13:32 dma_declare_coherent_memory and SuperH Christoph Hellwig
2021-06-23 13:35 ` Geert Uytterhoeven
2021-06-23 13:36 ` John Paul Adrian Glaubitz
2021-06-26 22:36 ` Rob Landley
2021-06-26 22:38 ` Rob Landley
2021-06-28 13:38 ` Christoph Hellwig
2021-06-28 14:04 ` Rob Landley
2021-06-28 13:49 ` Christoph Hellwig
2021-06-28 14:29 ` Rob Landley [this message]
2021-06-28 16:33 ` Christoph Hellwig
2021-06-28 19:12 ` Geert Uytterhoeven
2021-06-28 19:47 ` Rob Landley
2021-06-27 3:08 ` Daniel Palmer
2021-06-27 8:33 ` John Paul Adrian Glaubitz
2021-06-28 8:57 ` Geert Uytterhoeven
2021-06-28 9:29 ` Daniel Palmer
2021-06-28 10:00 ` Geert Uytterhoeven
2021-06-28 14:29 ` Geert Uytterhoeven
2021-06-28 16:29 ` Christoph Hellwig
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=1141b20f-7cdf-1477-ef51-876226db7a37@landley.net \
--to=rob@landley.net \
--cc=dalias@libc.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.