From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Simran Rai <ssimran@broadcom.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] dma: remove bad_dma_ops to fix build fail
Date: Mon, 13 Jun 2016 13:11:05 +0100 [thread overview]
Message-ID: <20160613121105.GA12857@sudip-tp> (raw)
In-Reply-To: <20160613115911.GG2282@sirena.org.uk>
On Mon, Jun 13, 2016 at 12:59:11PM +0100, Mark Brown wrote:
> On Mon, Jun 13, 2016 at 11:51:08AM +0100, Sudip Mukherjee wrote:
> > On Mon, Jun 13, 2016 at 10:29:34AM +0100, Mark Brown wrote:
>
> > > Right, we've got a couple of obscure architectures with no DMA support
> > > which are leading to a constant stream of patches like this that are
> > > being triggered by compile coverage stuff. In situations like this we
> > > very often provide stubs rather than having to handle this in lots of
> > > different places in the code.
>
> > Ok, I will do that. But I am seeing arch/m32r/include/asm/m32102.h is
> > defining the DMA Controller registers and also a MAX_DMA_ADDRESS is
> > defined in dma.h. Doesn't that mean that this arch is capable of DMA?
>
> Quite possibly, but they don't seem to implement the standard interfaces
> for generic code (this sort of thing is quite common for the less widely
> used architectures sadly).
If only I had a board to play with the DMA code. :(
I will go for the stub like you said.
Regards
Sudip
next prev parent reply other threads:[~2016-06-13 12:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 20:25 [PATCH] dma: remove bad_dma_ops to fix build fail Sudip Mukherjee
2016-06-12 21:32 ` Jerry Snitselaar
2016-06-13 7:41 ` Sudip Mukherjee
2016-06-13 9:29 ` Mark Brown
2016-06-13 10:51 ` Sudip Mukherjee
2016-06-13 11:59 ` Mark Brown
2016-06-13 12:11 ` Sudip Mukherjee [this message]
2016-06-13 7:59 ` Christoph Hellwig
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=20160613121105.GA12857@sudip-tp \
--to=sudipm.mukherjee@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ssimran@broadcom.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