From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Icenowy Zheng <icenowy@aosc.io>,
linux-arm-kernel@lists.infradead.org,
Chen-Yu Tsai <wens@csie.org>,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com,
Icenowy Zheng <icenowy@aosc.xyz>,
dmaengine@vger.kernel.org
Subject: Re: [linux-sunxi] Re: [PATCH 1/2] dmaengine: sun6i: make gate bit in sun8i's DMA engines a common quirk
Date: Tue, 20 Jun 2017 10:45:17 +0200 [thread overview]
Message-ID: <20170620084517.giq3zhvbmhpx7pge@flea.lan> (raw)
In-Reply-To: <20170615035407.GM13020@localhost>
[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]
On Thu, Jun 15, 2017 at 09:24:08AM +0530, Vinod Koul wrote:
> On Wed, Jun 14, 2017 at 11:04:39AM +0200, Maxime Ripard wrote:
> > On Wed, Jun 14, 2017 at 02:15:29PM +0530, Vinod Koul wrote:
> > > > SoC info is in compatible, so there's no reason to make it a property.
> > >
> > > that's why it would need to be optional for the SoC's that needs these..
> >
> > There's nothing optional about that behaviour, it's mandatory for the
> > SoC that need it, and useless on the SoC that don't.
>
> And why should kernel put strings for each hw behaviour.
You will have strings in the kernel for each hw behaviour,
disregarding on whether you base the behaviour on the compatible or a
set of properties. In fact, you will have *much* more strings in the
kernel in the latter case.
> I am expecting DT to tell me if this SoC is a special case or not
> and kernel shall handle accordingly
How is this not the case here?
The DT tells you that this SoC is a special case through a compatible
already.
> > Plus, that would require changing the DT binding, which isn't
> > something we can do.
>
> Any reason why bindings can't change..? I though this was support for new
> SoC...
No, this is a rework of an existing code to support a new SoC. The
code is already there, and the binding too. It has been for 3 years.
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-06-20 8:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 12:33 [PATCH 0/2] Allwinner V3s DMA support Icenowy Zheng
2017-06-05 12:33 ` [PATCH 1/2] dmaengine: sun6i: make gate bit in sun8i's DMA engines a common quirk Icenowy Zheng
2017-06-05 13:15 ` [linux-sunxi] " Chen-Yu Tsai
2017-06-14 8:32 ` Vinod Koul
2017-06-14 8:32 ` Icenowy Zheng
2017-06-14 8:45 ` Vinod Koul
2017-06-14 8:46 ` [linux-sunxi] " Icenowy Zheng
2017-06-14 9:04 ` Maxime Ripard
2017-06-15 3:54 ` Vinod Koul
2017-06-15 3:53 ` Icenowy Zheng
2017-06-20 8:45 ` Maxime Ripard [this message]
2017-06-05 12:33 ` [PATCH 2/2] dmaengine: sun6i: support V3s SoC variant Icenowy Zheng
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=20170620084517.giq3zhvbmhpx7pge@flea.lan \
--to=maxime.ripard@free-electrons.com \
--cc=dmaengine@vger.kernel.org \
--cc=icenowy@aosc.io \
--cc=icenowy@aosc.xyz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--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
all inboxes | Powered by JetHome®