public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Vinod Koul <vinod.koul@intel.com>,
	linux-kernel@vger.kernel.org,
	spear-devel <spear-devel@list.st.com>
Subject: Re: [RFC PATCH v0 0/2] dw_dmac: move to own folder and split
Date: Mon, 03 Jun 2013 16:23:12 +0300	[thread overview]
Message-ID: <1370265792.29283.260.camel@smile> (raw)
In-Reply-To: <CAKohpokWj4fNxc3AQPvKoogJRjGaMkeU6r7OvPCkE2Rrj+OcGw@mail.gmail.com>

On Mon, 2013-06-03 at 18:42 +0530, Viresh Kumar wrote: 
> On 3 June 2013 17:55, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:


> > In patch 2/2 I collect platform related code. I see a lot of #ifdefs
> > related to OF and ACPI. I would like to split it further and create
> > files like of.c and acpi.c. What do you think?
> 
> Naahh.. OF by itself doesn't mean anything here on this driver. It
> belongs to all the users that are using DT to enumerate it (Mostly
> ARM). And they are going to use platform_driver interface. So,
> code is well located currently too..

I got it.

> ACPI, I am not sure.. you need these routines in your pci stuff too?

No, ACPI is alike OF, it relies on platform driver.

> Keep it this way:
> - Keep all the common stuff across pci and platform in core.c
> - everything else in pci and platform files.

It seems it's kept in that way already.

Thanks for your comments!

I will resend patch series v1 w/o RFC and with PCI driver later (when it
will be ready). I will attach the missed patch to the series in case
Vinod doesn't apply it in time.


-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

      reply	other threads:[~2013-06-03 13:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-31 15:50 [RFC PATCH v0 0/2] dw_dmac: move to own folder and split Andy Shevchenko
2013-05-31 15:50 ` [RFC PATCH v0 1/2] dma: move dw_dmac driver to an own directory Andy Shevchenko
2013-06-03  4:55   ` Viresh Kumar
2013-06-03  8:24     ` Andy Shevchenko
2013-06-03  8:39       ` Viresh Kumar
2013-05-31 15:50 ` [RFC PATCH v0 2/2] dma: dw: split driver to library part and platform code Andy Shevchenko
2013-06-03  5:05 ` [RFC PATCH v0 0/2] dw_dmac: move to own folder and split Viresh Kumar
2013-06-03 12:25   ` Andy Shevchenko
2013-06-03 13:12     ` Viresh Kumar
2013-06-03 13:23       ` Andy Shevchenko [this message]

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=1370265792.29283.260.camel@smile \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spear-devel@list.st.com \
    --cc=vinod.koul@intel.com \
    --cc=viresh.kumar@linaro.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