From: Mika Westerberg <mika.westerberg@intel.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.jf.intel.com>,
linux-kernel@vger.kernel.org,
spear-devel <spear-devel@list.st.com>,
Mika Westerberg <mika.westerberg@linux.jf.intel.com>
Subject: Re: [PATCH] dw_dmac: adjust slave_id accordingly to request line base
Date: Thu, 14 Feb 2013 12:17:09 +0200 [thread overview]
Message-ID: <20130214101709.GF20771@intel.com> (raw)
In-Reply-To: <20130214095738.GD27887@intel.com>
On Thu, Feb 14, 2013 at 03:27:38PM +0530, Vinod Koul wrote:
> Not in the CSRT parser. Once your plaform devices are created, you can add your
> own board handler for each platform device. This board code, using the
> data availble from CSRT can go ahead and do the translation and present the
> actual addresses to dmac.
> Would this be doable with ACPI5.
I'm not sure what you mean by own board handler?
AFAIK, the only platform specific code is under arch/x86/platform/* but we
don't have such thing for Lynxpoint and it should not be needed as we can
enumerate the devices from ACPI.
> Somehow I dont like the idea of DMA resource for request lines. DMA
> resources have specific meaning, perhpas IO resource maybe better idea.
Well, it's a DMA request line so we thought that IORESOURCE_DMA would suit
fine there and the drivers that use these are well aware of their usage.
Not sure about IORESOURCE_IO, it has also specific meaning and I don't
think DMA request lines fit there either :-(
next prev parent reply other threads:[~2013-02-14 10:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 11:04 [PATCH] dw_dmac: adjust slave_id accordingly to request line base Andy Shevchenko
2013-01-29 4:59 ` Viresh Kumar
2013-01-29 5:22 ` Mika Westerberg
2013-01-29 15:27 ` Viresh Kumar
2013-01-30 7:32 ` Andy Shevchenko
2013-01-30 8:01 ` Viresh Kumar
2013-01-30 8:07 ` Andy Shevchenko
2013-02-07 13:22 ` Shevchenko, Andriy
2013-02-12 15:56 ` Vinod Koul
2013-02-12 16:34 ` Andy Shevchenko
2013-02-12 15:53 ` Vinod Koul
2013-02-12 16:43 ` Mika Westerberg
2013-02-12 17:34 ` Vinod Koul
2013-02-12 19:02 ` Mika Westerberg
2013-02-14 9:57 ` Vinod Koul
2013-02-14 10:17 ` Mika Westerberg [this message]
2013-02-07 13:28 ` Viresh Kumar
2013-02-19 9:02 ` Andy Shevchenko
2013-02-19 22:17 ` Rafael J. Wysocki
2013-02-20 6:04 ` Vinod Koul
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=20130214101709.GF20771@intel.com \
--to=mika.westerberg@intel.com \
--cc=andriy.shevchenko@linux.jf.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.jf.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).