All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: vinod.koul@intel.com, devicetree-discuss@lists.ozlabs.org,
	spear-devel@list.st.com, linux-kernel@vger.kernel.org,
	andriy.shevchenko@linux.intel.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2 2/3] dmaengine: dw_dmac: Enhance device tree support
Date: Fri, 12 Oct 2012 22:44:52 +0530	[thread overview]
Message-ID: <CAKohpokY9PVTVh6nvPdj9+v0iLeuCOWMmpgaEDqSqNBxqf13WQ@mail.gmail.com> (raw)
In-Reply-To: <20121012162057.GG12801@game.jcrosoft.org>

On 12 October 2012 21:50, Jean-Christophe PLAGNIOL-VILLARD
<plagnioj@jcrosoft.com> wrote:
>> >> - pass platform data via DT, non-DT way still takes precedence if both are used.
>> > why keep it  all platform are DT
>>
>> I would love to remove that, but not sure if somebody want's the non-DT
>> way too.
>>
>> I didn't wanted to get into fixing user SoCs of this driver.
> no drop it at the mailine if do not need it

But what's the harm in keeping it until we are sure, all users of it have
moved into DT? It is not adding any overhead for DT case. And this
is what most of the drivers today are doing, because not every platform
is DT compatible.

This driver is used in multiple architectures, not only ARM.

--
viresh

WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 2/3] dmaengine: dw_dmac: Enhance device tree support
Date: Fri, 12 Oct 2012 22:44:52 +0530	[thread overview]
Message-ID: <CAKohpokY9PVTVh6nvPdj9+v0iLeuCOWMmpgaEDqSqNBxqf13WQ@mail.gmail.com> (raw)
In-Reply-To: <20121012162057.GG12801@game.jcrosoft.org>

On 12 October 2012 21:50, Jean-Christophe PLAGNIOL-VILLARD
<plagnioj@jcrosoft.com> wrote:
>> >> - pass platform data via DT, non-DT way still takes precedence if both are used.
>> > why keep it  all platform are DT
>>
>> I would love to remove that, but not sure if somebody want's the non-DT
>> way too.
>>
>> I didn't wanted to get into fixing user SoCs of this driver.
> no drop it at the mailine if do not need it

But what's the harm in keeping it until we are sure, all users of it have
moved into DT? It is not adding any overhead for DT case. And this
is what most of the drivers today are doing, because not every platform
is DT compatible.

This driver is used in multiple architectures, not only ARM.

--
viresh

  reply	other threads:[~2012-10-12 17:14 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12 14:31 [PATCH V2 1/3] dmaengine: dw_dmac: Update documentation style comments for dw_dma_platform_data Viresh Kumar
2012-10-12 14:31 ` Viresh Kumar
2012-10-12 14:31 ` [PATCH V2 2/3] dmaengine: dw_dmac: Enhance device tree support Viresh Kumar
2012-10-12 14:31   ` Viresh Kumar
2012-10-12 14:50   ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-12 14:50     ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-12 14:55     ` Viresh Kumar
2012-10-12 14:55       ` Viresh Kumar
2012-10-12 16:20       ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-12 16:20         ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-12 17:14         ` Viresh Kumar [this message]
2012-10-12 17:14           ` Viresh Kumar
2012-10-12 14:58   ` Andy Shevchenko
2012-10-12 14:58     ` Andy Shevchenko
2012-10-12 15:18     ` Viresh Kumar
2012-10-12 15:18       ` Viresh Kumar
2012-10-12 15:53       ` Andy Shevchenko
2012-10-12 15:53         ` Andy Shevchenko
2012-10-12 15:55         ` Viresh Kumar
2012-10-12 15:55           ` Viresh Kumar
2012-10-15  3:29     ` Viresh Kumar
2012-10-15  3:29       ` Viresh Kumar
2012-10-15  7:35       ` Andy Shevchenko
2012-10-15  7:35         ` Andy Shevchenko
2012-10-12 14:31 ` [PATCH V2 3/3] ARM: SPEAr13xx: Pass DW DMAC platform data from DT Viresh Kumar
2012-10-12 14:31   ` Viresh Kumar
2012-10-12 14:48   ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-12 14:48     ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-12 14:48     ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-12 14:52     ` Viresh Kumar
2012-10-12 14:52       ` Viresh Kumar
2012-10-12 16:21       ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-12 16:21         ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-12 17:12         ` Viresh Kumar
2012-10-12 17:12           ` Viresh Kumar
2012-10-13  6:44           ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-13  6:44             ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-13  8:48             ` Viresh Kumar
2012-10-13  8:48               ` Viresh Kumar
2012-10-13 12:22               ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-13 12:22                 ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-13 12:22                 ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-13 14:08                 ` Viresh Kumar
2012-10-13 14:08                   ` Viresh Kumar
2012-10-13 14:10                   ` Viresh Kumar
2012-10-13 14:10                     ` Viresh Kumar
2012-10-14 10:01                     ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-14 10:01                       ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-14 10:01                       ` Jean-Christophe PLAGNIOL-VILLARD
2012-10-15  3:21                       ` Viresh Kumar
2012-10-15  3:21                         ` Viresh Kumar

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=CAKohpokY9PVTVh6nvPdj9+v0iLeuCOWMmpgaEDqSqNBxqf13WQ@mail.gmail.com \
    --to=viresh.kumar@linaro.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plagnioj@jcrosoft.com \
    --cc=spear-devel@list.st.com \
    --cc=vinod.koul@intel.com \
    /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.