From: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
"grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org"
<grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>,
"rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org"
<rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
"spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
<spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH V2] spi: tegra: add spi driver for SLINK controller
Date: Tue, 30 Oct 2012 15:14:51 +0000 [thread overview]
Message-ID: <20121030151451.GT4511@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <508F6906.7020704-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
On Tue, Oct 30, 2012 at 11:13:34AM +0530, Laxman Dewangan wrote:
> On Tuesday 30 October 2012 12:44 AM, Stephen Warren wrote:
> >I think it depends on DMAENGINE, not the specific driver now, doesn't it?
> Taking example from the mfd, we depends on particular driver, not
> from the core driver.
> I like to have this depends on Tegra20_apb_dma.
The reason MFDs do this is that the function drivers usually directly
reference the core driver in some way, for example by relying on data
structures it sets up. With DMA that should all be hidden behind the
dmaengine API.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"spi-devel-general@lists.sourceforge.net"
<spi-devel-general@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH V2] spi: tegra: add spi driver for SLINK controller
Date: Tue, 30 Oct 2012 15:14:51 +0000 [thread overview]
Message-ID: <20121030151451.GT4511@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <508F6906.7020704@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 573 bytes --]
On Tue, Oct 30, 2012 at 11:13:34AM +0530, Laxman Dewangan wrote:
> On Tuesday 30 October 2012 12:44 AM, Stephen Warren wrote:
> >I think it depends on DMAENGINE, not the specific driver now, doesn't it?
> Taking example from the mfd, we depends on particular driver, not
> from the core driver.
> I like to have this depends on Tegra20_apb_dma.
The reason MFDs do this is that the function drivers usually directly
reference the core driver in some way, for example by relying on data
structures it sets up. With DMA that should all be hidden behind the
dmaengine API.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-10-30 15:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 17:18 [PATCH V2] spi: tegra: add spi driver for SLINK controller Laxman Dewangan
2012-10-29 17:18 ` Laxman Dewangan
2012-10-29 17:18 ` Laxman Dewangan
[not found] ` <1351531104-1604-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-10-29 19:14 ` Stephen Warren
2012-10-29 19:14 ` Stephen Warren
[not found] ` <508ED5A5.3000703-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-10-30 5:43 ` Laxman Dewangan
2012-10-30 5:43 ` Laxman Dewangan
[not found] ` <508F6906.7020704-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-10-30 15:14 ` Mark Brown [this message]
2012-10-30 15:14 ` Mark Brown
2012-10-30 5:56 ` Laxman Dewangan
2012-10-30 5:56 ` Laxman Dewangan
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=20121030151451.GT4511@opensource.wolfsonmicro.com \
--to=broonie-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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.