linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Rob Landley <rob@landley.net>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Rich Felker <dalias@libc.org>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: dma_declare_coherent_memory and SuperH
Date: Mon, 28 Jun 2021 21:12:58 +0200	[thread overview]
Message-ID: <CAMuHMdVT17ruQZKJXAahMvQQVMnJNoaSjHSuqat-CHOCV4hVaA@mail.gmail.com> (raw)
In-Reply-To: <20210628163312.GA29659@lst.de>

Hi Christoph,

On Mon, Jun 28, 2021 at 6:33 PM Christoph Hellwig <hch@lst.de> wrote:
> On Mon, Jun 28, 2021 at 09:29:59AM -0500, Rob Landley wrote:
> > > 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?
>
> The part that there is no easy way out without the device tree
> conversion.

So you keep this functionality around with DT.  Which means there's
some code to parse the DT, extract a region, and handle it?
I'm just wondering which terrible maintenance burden would be left by
making the handling function public, so the SH platform code can still call it?

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2021-06-28 19:13 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
2021-06-28 16:33           ` Christoph Hellwig
2021-06-28 19:12             ` Geert Uytterhoeven [this message]
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=CAMuHMdVT17ruQZKJXAahMvQQVMnJNoaSjHSuqat-CHOCV4hVaA@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=dalias@libc.org \
    --cc=hch@lst.de \
    --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 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).