From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFT] arm64: dts: renesas: r8a77990: Add all MSIOF device nodes
Date: Thu, 6 Sep 2018 11:27:48 +0200 [thread overview]
Message-ID: <CAMuHMdXgAe=AO_B2DfP1jLi1omETocJQt=C6G+WBJKNqTEDvFQ@mail.gmail.com> (raw)
In-Reply-To: <20180906092507.lz2n3xw7ksbgpges@verge.net.au>
Hi Simon,
On Thu, Sep 6, 2018 at 11:25 AM Simon Horman <horms@verge.net.au> wrote:
> On Wed, Sep 05, 2018 at 08:52:56AM +0200, Geert Uytterhoeven wrote:
> > On Tue, Sep 4, 2018 at 10:23 PM Yoshihiro Kaneko <ykaneko0929@gmail.com> wrote:
> > > From: Takeshi Kihara <takeshi.kihara.df@renesas.com>
> > > This patch adds the device nodes for all MSIOF SPI controllers to
> > > the R8A77990 SoC.
> > >
> > > Signed-off-by: Takeshi Kihara <takeshi.kihara.df@renesas.com>
> > > Signed-off-by: Yoshihiro Kaneko <ykaneko0929@gmail.com>
> >
> > Thanks for your patch!
> >
> > Unfortunately this is a duplicate of
> > https://www.spinics.net/lists/devicetree/msg246988.html.
> >
> > Sorry for stepping on your toes, I added MSIOF support for Ebisu to investigate
> > MSIOF driver bugs.
>
> The DMA portions seem new.
Yes it is.
> Perhaps a new patch should be constructed that only adds those properties?
To be added after testing MSIOF DMA ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at 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
prev parent reply other threads:[~2018-09-06 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 20:22 [PATCH/RFT] arm64: dts: renesas: r8a77990: Add all MSIOF device nodes Yoshihiro Kaneko
2018-09-05 6:52 ` Geert Uytterhoeven
2018-09-06 9:25 ` Simon Horman
2018-09-06 9:27 ` Geert Uytterhoeven [this message]
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='CAMuHMdXgAe=AO_B2DfP1jLi1omETocJQt=C6G+WBJKNqTEDvFQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.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).