mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Felipe Balbi <felipe.balbi@linux.intel.com>,
	Vinod Koul <vinod.koul@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [RFC] DMA initialization for manually created devices
Date: Tue, 19 Apr 2016 08:14:07 -0400	[thread overview]
Message-ID: <1461068047.3765.97.camel@infradead.org> (raw)
In-Reply-To: <87bn55esm6.fsf@intel.com>

[-- Attachment #1: Type: text/plain, Size: 878 bytes --]

On Tue, 2016-04-19 at 14:38 +0300, Felipe Balbi wrote:
> 
> The reason for that I'm using a manually created platform_device and
> that misses dev->archdata which the underlying/parent PCI device has.

Typically we'd expect you to use the parent device for DMA, as in your
second option.

That said, we're exploring the option of moving the dma_ops to be a
first-class member of 'struct device' instead of hiding it in archdata,
and cleaning up the way that it gets initialised for newly-created
devices. And at that point we might end up letting it get inherited
from the parent so your original code *would* work... but I wouldn't
hold your breath for that.

Definitely *don't* mess around in archdata.

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@intel.com                              Intel Corporation


[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5691 bytes --]

  reply	other threads:[~2016-04-19 12:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19 11:38 Felipe Balbi
2016-04-19 12:14 ` David Woodhouse [this message]
2016-04-19 12:52   ` Felipe Balbi
2016-04-20 10:31     ` Felipe Balbi

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=1461068047.3765.97.camel@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=felipe.balbi@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®