From: Christoph Hellwig <hch@lst.de>
To: Rob Landley <rob@landley.net>
Cc: Christoph Hellwig <hch@lst.de>,
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 15:38:58 +0200 [thread overview]
Message-ID: <20210628133858.GA21602@lst.de> (raw)
In-Reply-To: <1a55cf69-8fe1-dca0-68c7-f978567f9ca0@landley.net>
On Sat, Jun 26, 2021 at 05:36:08PM -0500, Rob Landley wrote:
> On 6/23/21 8:32 AM, Christoph Hellwig wrote:
> > Hi SuperH maintainers,
> >
> > I have a vague recollection that you were planning on dropping support
> > for non-devicetree platforms, is that still the case?
>
> We'd like to convert them, but have to rustle up test hardware for what _is_
> still available. (There was some motion towards this a year or so back, but it
> petered out because pandemic and everyone got distracted halfway through.)
>
> (We should definitely START by converting the r2d board qemu emulates. :)
>
> > The reason I'm asking is because all but one users of
> > dma_declare_coherent_memory are in the sh platform setup code, and
> > I'd really like to move towards killing this function off.
>
> Understood. Is there an easy "convert to this" I could do to those callers?
Well, the replacement is to declare the device memory carveouts in the
Device Tree.
next prev parent reply other threads:[~2021-06-28 13:39 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 [this message]
2021-06-28 14:04 ` Rob Landley
2021-06-28 13:49 ` Christoph Hellwig
2021-06-28 14:29 ` Rob Landley
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=20210628133858.GA21602@lst.de \
--to=hch@lst.de \
--cc=dalias@libc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rob@landley.net \
--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.