From: Paul Burton <paul.burton@mips.com>
To: Vinod <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: Paul Cercueil <paul@crapouillou.net>,
Ralf Baechle <ralf@linux-mips.org>,
James Hogan <jhogan@kernel.org>,
Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>,
Mathieu Malaterre <malat@debian.org>,
Daniel Silsby <dansilsby@gmail.com>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: [PATCH 02/14] dmaengine: dma-jz4780: Separate chan/ctrl registers
Date: Wed, 11 Jul 2018 16:27:15 -0700 [thread overview]
Message-ID: <20180711232715.djxrbgmcski5xtjp@pburton-laptop> (raw)
In-Reply-To: <20180711121655.GS3219@vkoul-mobl>
Hi Vinod,
On Wed, Jul 11, 2018 at 05:46:55PM +0530, Vinod wrote:
> > > > - jzdma->base = devm_ioremap_resource(dev, res);
> > > > - if (IS_ERR(jzdma->base))
> > > > - return PTR_ERR(jzdma->base);
> > > > + jzdma->chn_base = devm_ioremap_resource(dev, res);
> > > > + if (IS_ERR(jzdma->chn_base))
> > > > + return PTR_ERR(jzdma->chn_base);
> > > > +
> > > > + res = platform_get_resource(pdev, IORESOURCE_MEM, 1);
> > > > + if (!res) {
> > > > + dev_err(dev, "failed to get I/O memory\n");
> > > > + return -EINVAL;
> > > > + }
> > >
> > > okay and this breaks if you happen to get probed on older DT. I think DT
> > > is treated as ABI so you need to continue support older method while
> > > finding if DT has split resources
> >
> > See my response to PrasannaKumar. All the Ingenic-based boards do compile
> > the devicetree within the kernel, so I think it's still fine to add breaking
> > changes. I'll wait on @Rob to give his point of view on this, though.
> >
> > (It's not something hard to change, but I'd like to know what's the policy
> > in that case. I have other DT-breaking patches to submit)
>
> The policy is that DT is an ABI and should not break :)
I think in general that's a good policy to have for compatibility, but
if it's known for certain that the DT for all users of a driver is
always built into the kernel then I don't see why we shouldn't feel free
to change a binding. I agree with Paul that it'd be interesting to hear
the DT binding maintainers take on this.
Thanks,
Paul
next prev parent reply other threads:[~2018-07-11 23:27 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 12:32 [PATCH 00/14] dma-jz4780 improvements Paul Cercueil
2018-07-03 12:32 ` [PATCH 01/14] dmaengine: dma-jz4780: Avoid hardcoding number of channels Paul Cercueil
2018-07-04 16:28 ` PrasannaKumar Muralidharan
2018-07-05 18:26 ` Paul Cercueil
2018-07-07 7:34 ` PrasannaKumar Muralidharan
2018-07-07 11:01 ` Paul Cercueil
2018-07-09 16:59 ` Vinod
2018-07-10 15:29 ` Paul Cercueil
2018-07-11 12:14 ` Vinod
2018-07-03 12:32 ` [PATCH 02/14] dmaengine: dma-jz4780: Separate chan/ctrl registers Paul Cercueil
2018-07-03 16:53 ` Paul Burton
2018-07-05 18:23 ` Paul Cercueil
2018-07-04 16:35 ` PrasannaKumar Muralidharan
2018-07-05 21:45 ` Paul Cercueil
2018-07-07 7:27 ` PrasannaKumar Muralidharan
2018-07-09 17:03 ` Vinod
2018-07-10 15:36 ` Paul Cercueil
2018-07-11 12:16 ` Vinod
2018-07-11 23:13 ` Paul Cercueil
2018-07-11 23:27 ` Paul Burton [this message]
2018-07-16 21:28 ` Rob Herring
2018-07-03 12:32 ` [PATCH 03/14] dmaengine: dma-jz4780: Use 4-word descriptors Paul Cercueil
2018-07-04 16:40 ` PrasannaKumar Muralidharan
2018-07-03 12:32 ` [PATCH 04/14] dmaengine: dma-jz4780: Add support for the JZ4770 SoC Paul Cercueil
2018-07-09 17:10 ` Vinod
2018-07-10 15:41 ` Paul Cercueil
2018-07-03 12:32 ` [PATCH 05/14] dmaengine: dma-jz4780: Add support for the JZ4740 SoC Paul Cercueil
2018-07-04 16:52 ` PrasannaKumar Muralidharan
2018-07-09 17:12 ` Vinod
2018-07-16 21:33 ` Rob Herring
2018-07-17 11:00 ` Paul Cercueil
2018-07-17 15:34 ` Vinod
2018-07-17 17:40 ` Rob Herring
2018-07-18 5:27 ` Vinod
2018-07-03 12:32 ` [PATCH 06/14] dmaengine: dma-jz4780: Add support for the JZ4725B SoC Paul Cercueil
2018-07-04 16:55 ` PrasannaKumar Muralidharan
2018-07-09 17:14 ` Vinod
2018-07-10 15:45 ` Paul Cercueil
2018-07-11 12:18 ` Vinod
2018-07-11 23:13 ` Paul Cercueil
2018-07-03 12:32 ` [PATCH 07/14] dmaengine: dma-jz4780: Enable Fast DMA to the AIC Paul Cercueil
2018-07-04 17:00 ` PrasannaKumar Muralidharan
2018-07-03 12:32 ` [PATCH 08/14] dmaengine: dma-jz4780: Add missing residue DTC mask Paul Cercueil
2018-07-03 12:32 ` [PATCH 09/14] dmaengine: dma-jz4780: Simplify jz4780_dma_desc_residue() Paul Cercueil
2018-07-03 12:32 ` [PATCH 10/14] dmaengine: dma-jz4780: Set DTCn register explicitly Paul Cercueil
2018-07-03 12:32 ` [PATCH 11/14] dmaengine: dma-jz4780: Further residue status fix Paul Cercueil
2018-07-03 12:32 ` [PATCH 12/14] dmaengine: dma-jz4780: Use dma_set_residue() Paul Cercueil
2018-07-03 12:32 ` [PATCH 13/14] MIPS: JZ4780: DTS: Update DMA node to match driver changes Paul Cercueil
2018-07-03 12:32 ` [PATCH 14/14] MIPS: JZ4770: DTS: Add DMA nodes Paul Cercueil
2018-07-03 19:32 ` [PATCH 00/14] dma-jz4780 improvements Mathieu Malaterre
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=20180711232715.djxrbgmcski5xtjp@pburton-laptop \
--to=paul.burton@mips.com \
--cc=Zubair.Kakakhel@imgtec.com \
--cc=dansilsby@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=malat@debian.org \
--cc=mark.rutland@arm.com \
--cc=paul@crapouillou.net \
--cc=ralf@linux-mips.org \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.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