From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Pantelis Antoniou" <panto@antoniou-consulting.com>,
"Tony Lindgren" <tony@atomide.com>,
"Benoît Coussno" <b-cousson@ti.com>,
"Paul Walmsley" <paul@pwsan.com>,
"Sourav Poddar" <sourav.poddar@ti.com>,
"Russ Dill" <Russ.Dill@ti.com>, "Felipe Balbi" <balbi@ti.com>,
"Koen Kooi" <koen@circuitco.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] pdev: Fix platform device resource linking
Date: Tue, 6 Aug 2013 11:19:14 +0100 [thread overview]
Message-ID: <20130806101914.GH23053@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130806101527.GB29283@kroah.com>
On Tue, Aug 06, 2013 at 06:15:27PM +0800, Greg Kroah-Hartman wrote:
> On Tue, Aug 06, 2013 at 12:45:42PM +0300, Pantelis Antoniou wrote:
> > What would it take to move all this into driver core?
>
> What specifically would you move into there?
A variable to hold the streaming dma_mask, so that its in struct device
rather than having to be separate. Yes, we can keep the pointer in there
too, because that appears to convey meaning in the kernel today - whether
the device can do DMA or not.
A NULL dma_mask pointer already means it can't and dma_set_mask() always
fails. A non-NULL dma_mask pointer means the driver can use
dma_set_mask() to set an appropriate mask.
next prev parent reply other threads:[~2013-08-06 10:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1375775624-12250-1-git-send-email-panto@antoniou-consulting.com>
[not found] ` <1375775624-12250-6-git-send-email-panto@antoniou-consulting.com>
2013-08-06 9:33 ` [PATCH 5/5] arm: omap: Proper cleanups for omap_device Greg Kroah-Hartman
2013-08-06 9:37 ` Pantelis Antoniou
2013-08-06 10:14 ` Greg Kroah-Hartman
2013-08-06 13:37 ` Alexander Holler
2013-08-07 5:52 ` Greg Kroah-Hartman
2013-08-07 15:22 ` Alexander Holler
2013-08-07 7:44 ` Pantelis Antoniou
2013-08-07 16:15 ` Tony Lindgren
2013-08-07 16:23 ` Pantelis Antoniou
2013-08-08 7:25 ` Tony Lindgren
[not found] ` <1375775624-12250-2-git-send-email-panto@antoniou-consulting.com>
2013-08-06 9:36 ` [PATCH 1/5] pdev: Fix platform device resource linking Greg Kroah-Hartman
2013-08-06 9:45 ` Pantelis Antoniou
2013-08-06 10:15 ` Greg Kroah-Hartman
2013-08-06 10:19 ` Russell King - ARM Linux [this message]
2013-08-07 5:57 ` Greg Kroah-Hartman
2013-08-07 8:27 ` Russell King - ARM Linux
2013-08-06 10:27 ` Pantelis Antoniou
2013-08-07 5:56 ` Greg Kroah-Hartman
2013-08-07 7:37 ` Pantelis Antoniou
2013-08-07 17:13 ` Matt Porter
[not found] ` <1375775624-12250-4-git-send-email-panto@antoniou-consulting.com>
[not found] ` <87a9kt2vd8.fsf@linaro.org>
2013-08-08 9:23 ` [PATCH 3/5] omap: Properly handle resources for omap_devices Pantelis Antoniou
2013-08-09 15:16 ` Kevin Hilman
2013-08-09 15:32 ` Pantelis Antoniou
2013-08-09 16:35 ` Kevin Hilman
2013-08-09 18:08 ` Pantelis Antoniou
[not found] ` <1375775624-12250-5-git-send-email-panto@antoniou-consulting.com>
[not found] ` <87siyl19uk.fsf@linaro.org>
2013-08-08 9:29 ` [PATCH 4/5] omap: Avoid crashes in the case of hwmod misconfiguration Pantelis Antoniou
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=20130806101914.GH23053@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=Russ.Dill@ti.com \
--cc=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=koen@circuitco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=panto@antoniou-consulting.com \
--cc=paul@pwsan.com \
--cc=sourav.poddar@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).