From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: "André Przywara" <andre.przywara@arm.com>
Cc: "Stefan Brüns" <stefan.bruens@rwth-aachen.de>,
linux-sunxi@googlegroups.com, "Chen-Yu Tsai" <wens@csie.org>,
devicetree@vger.kernel.org, dmaengine@vger.kernel.org,
"Vinod Koul" <vinod.koul@intel.com>,
"Rob Herring" <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] dmaengine: sun6i: Add support for Allwinner A64
Date: Fri, 8 Sep 2017 16:39:13 +0200 [thread overview]
Message-ID: <20170908143913.6ga64ssakvk2mjis@flea.lan> (raw)
In-Reply-To: <d3d32839-12a8-71fa-cfec-03055d64388d@arm.com>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
Hi,
On Mon, Sep 04, 2017 at 09:14:52AM +0100, André Przywara wrote:
> > And obviously, while maintaining the stability of the binding of those
> > hundreds properties.
> >
> > Or, you can base all this on the compatible, and be done with it once
> > and for all.
>
> What I am after is to cover SoCs which *don't* have differences in their
> register layout, for instance A83T, H3, A64, R40.
> In an ideal world we could have reused the H3 compatible string,
> adjusting the number of channels for each SoC in the DT.
>
> So I see that having a generic compatible name will not fly, as we now
> have differences which should not be modelled by DT properties.
> But I still think we should try to cover those non-register differences
> (number of channels) with a DT property, to allow reusing the existing
> driver code whenever possible. As is stands with this series, the R40
> support should just be a matter of:
> compatible = "allwinner,sun8i-r40-dma",
> "allwinner,sun50i-a64-dma";
I just suggested the exact same thing, and then saw your mail, so I
guess we have an agreement :)
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-09-08 14:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 23:36 [PATCH 0/3] dmaengine: Fix DMA on current allwinner SoCs, add A64 support Stefan Brüns
2017-08-30 23:36 ` [PATCH 1/3] dmaengine: sun6i: Correct DMA support on H3 Stefan Brüns
2017-08-31 14:51 ` Maxime Ripard
2017-09-01 3:04 ` Stefan Bruens
2017-09-01 13:35 ` Maxime Ripard
2017-09-01 14:42 ` Brüns, Stefan
2017-09-04 6:50 ` Maxime Ripard
2017-08-30 23:36 ` [PATCH 2/3] arm64: allwinner: a64: Add device node for DMA controller Stefan Brüns
2017-09-11 22:00 ` Rob Herring
2017-08-30 23:36 ` [PATCH 3/3] dmaengine: sun6i: Add support for Allwinner A64 Stefan Brüns
2017-08-31 11:44 ` Code Kipper
2017-08-31 14:52 ` Maxime Ripard
2017-08-31 16:35 ` [linux-sunxi] " Code Kipper
2017-09-01 0:31 ` Andre Przywara
2017-09-01 1:19 ` Stefan Bruens
2017-09-01 22:32 ` André Przywara
2017-09-02 0:38 ` Stefan Bruens
2017-09-02 2:02 ` Stefan Bruens
2017-09-03 23:14 ` André Przywara
2017-09-01 6:04 ` Maxime Ripard
2017-09-01 22:35 ` André Przywara
2017-09-04 7:04 ` Maxime Ripard
2017-09-04 8:14 ` André Przywara
2017-09-08 14:39 ` Maxime Ripard [this message]
2017-09-08 14:57 ` Andre Przywara
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=20170908143913.6ga64ssakvk2mjis@flea.lan \
--to=maxime.ripard@free-electrons.com \
--cc=andre.przywara@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=robh+dt@kernel.org \
--cc=stefan.bruens@rwth-aachen.de \
--cc=vinod.koul@intel.com \
--cc=wens@csie.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