All of lore.kernel.org
 help / color / mirror / Atom feed
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv4 3/6] dmaengine: mv_xor: remove support for dmacap,* DT properties
Date: Wed, 19 Aug 2015 22:30:45 +0530	[thread overview]
Message-ID: <20150819170045.GK13546@localhost> (raw)
In-Reply-To: <20150727124405.53752fe2@free-electrons.com>

On Mon, Jul 27, 2015 at 12:44:05PM +0200, Thomas Petazzoni wrote:
> Vinod,
> 
> On Wed, 22 Jul 2015 10:46:53 +0530, Vinod Koul wrote:
> 
> > >  	xor01 {
> > >  	      interrupts = <52>;
> > > -	      dmacap,memcpy;
> > > -	      dmacap,xor;
> > > -	      dmacap,memset;
> > I maybe wrong but there was an assumption that DT properties, even if bad
> > are always there as they need to be treated as kernel ABI.
> > 
> > How will it work if someone has older DT implementation or older driver?
> 
> Supporting a new DT with an old kernel has never been part of the
> requirements of the DT ABI stability.
> 
> Supporting an old DT with a new kernel is the actual requirement. And
> the patch I'm proposing does not break this at all: a new kernel will
> simply ignore those dmacap,* properties from an old DT, and the driver
> automatically knows by itself what are the capabilities of the
> different XOR engines.
> 
> Therefore, there is no backward compatibility issue introduced by this
> patch.

Yes tht is correct

-- 
~Vinod

  reply	other threads:[~2015-08-19 17:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 14:28 [PATCHv4 0/6] dmaengine: mv_xor fixes and improvements Thomas Petazzoni
2015-07-08 14:28 ` [PATCHv4 1/6] dmaengine: mv_xor: fix big endian operation in register mode Thomas Petazzoni
2015-07-22  5:22   ` Vinod Koul
2015-07-08 14:28 ` [PATCHv4 2/6] dmaengine: mv_xor: add suspend/resume support Thomas Petazzoni
2015-07-22  5:10   ` Vinod Koul
2015-07-29  9:34     ` Thomas Petazzoni
2015-08-19 16:53       ` Vinod Koul
2015-07-08 14:28 ` [PATCHv4 3/6] dmaengine: mv_xor: remove support for dmacap, * DT properties Thomas Petazzoni
2015-07-22  5:16   ` [PATCHv4 3/6] dmaengine: mv_xor: remove support for dmacap,* " Vinod Koul
2015-07-22  5:18     ` Vinod Koul
2015-07-27 10:44     ` Thomas Petazzoni
2015-08-19 17:00       ` Vinod Koul [this message]
2015-08-19 17:02   ` Vinod Koul
2015-07-08 14:28 ` [PATCHv4 4/6] dmaengine: mv_xor: remove mv_xor_chan->current_type field Thomas Petazzoni
2015-08-19 17:04   ` Vinod Koul
2015-07-08 14:28 ` [PATCHv4 5/6] dmaengine: mv_xor: de-duplicate mv_chan_set_mode*() Thomas Petazzoni
2015-08-19 17:05   ` Vinod Koul
2015-07-08 14:28 ` [PATCHv4 6/6] dmaengine: mv_xor: optimize performance by using a subset of the XOR channels Thomas Petazzoni
2015-08-19 17:05   ` Vinod Koul
2015-07-08 15:37 ` [PATCHv4 0/6] dmaengine: mv_xor fixes and improvements Andrew Lunn

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=20150819170045.GK13546@localhost \
    --to=vinod.koul@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.