From: Mark Salter <msalter@redhat.com>
To: shuah.khan@hp.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
a-jacquiot@ti.com, linux-c6x-dev@linux-c6x.org,
LKML <linux-kernel@vger.kernel.org>,
shuahkhan@gmail.com
Subject: Re: [PATCH RFT RESEND linux-next] c6x: dma-mapping: support debug_dma_mapping_error
Date: Fri, 02 Nov 2012 16:15:25 -0400 [thread overview]
Message-ID: <1351887326.15973.35.camel@deneb.redhat.com> (raw)
In-Reply-To: <1351885999.3161.11.camel@lorien2>
On Fri, 2012-11-02 at 13:53 -0600, Shuah Khan wrote:
> On Fri, 2012-11-02 at 15:10 -0400, Mark Salter wrote:
> > On Fri, 2012-11-02 at 10:44 -0600, Shuah Khan wrote:
> > > On Fri, 2012-10-26 at 09:40 -0600, Shuah Khan wrote:
> > > > Add support for debug_dma_mapping_error() call to avoid warning from
> > > > debug_dma_unmap() interface when it checks for mapping error checked
> > > > status. Without this patch, device driver failed to check map error
> > > > warning is generated.
> > > >
> > > > Signed-off-by: Shuah Khan <shuah.khan@hp.com>
> > > > ---
> > > > arch/c6x/include/asm/dma-mapping.h | 1 +
> > > > 1 file changed, 1 insertion(+)
> >
> > > Would you like to this patch go through c6x arch tree or linux-next?
> > > Please let me know your preference.
> >
> > I tried to test this but I get a build error with CONFIG_DMA_API_DEBUG:
> >
> > /linux-next/lib/dma-debug.c: In function 'has_mapping_error':
> > /linux-next/lib/dma-debug.c:863:15: error: implicit declaration of function 'get_dma_ops' [-Werror=implicit-function-declaration]
> > /linux-next/lib/dma-debug.c:863:34: warning: initialization makes pointer from integer without a cast [enabled by default]
> >
> > C6X (along with some other architectures) doesn't have a get_dma_ops()
> > function defined.
>
> That is a problem I didn't think about. I did a check and looks like c6x
> and frv are the only ones that don't have get_dma_ops() defined. frv is
By my count, there are 14 architectures with get_dma_ops() and 14
without.
> in a different category as it doesn't use dma_debug interfaces. IN the
> case c6x, now with my change to add debug_dma_mapping_error(), we will
> start seeing warnings since dma_map_page() and dma_map_single() are
> debugged with a call to debug_dma_map_page() and the corresponding
> dma_mapping_error() interface doesn't call debug_dma_mapping_error()
> interface
>
> - Does adding get_dma_ops() make sense? Doesn't look like c6x exports
> dma_ops?
>
> Any other ideas?
I'm not sure. I don't know what get_dma_ops() does and it doesn't seem
to be documented anywhere.
next prev parent reply other threads:[~2012-11-02 20:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 23:01 [PATCH RFT] c6x: dma-mapping: support debug_dma_mapping_error Shuah Khan
2012-10-26 15:40 ` [PATCH RFT RESEND linux-next] " Shuah Khan
2012-11-02 16:44 ` Shuah Khan
2012-11-02 19:10 ` Mark Salter
2012-11-02 19:53 ` Shuah Khan
2012-11-02 20:15 ` Mark Salter [this message]
2012-11-02 20:26 ` Shuah Khan
2012-11-02 20:59 ` Mark Salter
2012-11-02 21:08 ` Shuah Khan
2012-11-15 17:45 ` Shuah Khan
2012-11-15 18:02 ` Mark Salter
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=1351887326.15973.35.camel@deneb.redhat.com \
--to=msalter@redhat.com \
--cc=a-jacquiot@ti.com \
--cc=akpm@linux-foundation.org \
--cc=linux-c6x-dev@linux-c6x.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shuah.khan@hp.com \
--cc=shuahkhan@gmail.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 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.