From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] usb: musb: USB_TI_CPPI41_DMA requires dmaengine support
Date: Wed, 18 Nov 2015 22:06:36 +0100 [thread overview]
Message-ID: <4749121.AD5OMAAsPq@wuerfel> (raw)
In-Reply-To: <CADYTM3bwZhLWyL_D+jFwQTDGHT3VBoQdxaPjaex7YZU=POLO+A@mail.gmail.com>
On Wednesday 18 November 2015 14:39:10 Bin Liu wrote:
> > Ideally we should remove the 'select TI_CPPI41' here as well, but
> > what we could do instead is to make that a silent symbol and remove
> > the prompt so it always gets enabled implicitly when USB_TI_CPPI41_DMA
> > and DMADEVICES are both enabled.
>
> But what if DMADEVICES was disabled and USB_TI_CPPI41_DMA was enabled?
> I would think I had CPPI fully enabled for MUSB, but it didn't because
> TI_CPPI41 was disabled.
That would cause a runtime failure, just like any other configuration
that does not enable all the hardware you want to use.
> I would think this patch is the test option so far, we might have to
> document somewhere that to dmaengine has to be enabled to use MUSB
> CPPI, but I am not sure where the best place is to document...
There are hundreds of device drivers that use dmaengines as a
backend, we don't normally document this, just like we don't
document the fact that you need to enable the right gpio, irqchip,
timer, clock etc drivers for your platform.
Arnd
next prev parent reply other threads:[~2015-11-18 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 16:18 [PATCH] usb: musb: USB_TI_CPPI41_DMA requires dmaengine support Arnd Bergmann
2015-11-18 18:29 ` Bin Liu
2015-11-18 19:27 ` Felipe Balbi
2015-11-18 20:20 ` Bin Liu
2015-11-18 20:38 ` Felipe Balbi
2015-11-18 20:45 ` Bin Liu
2015-11-18 20:27 ` Arnd Bergmann
2015-11-18 20:39 ` Bin Liu
2015-11-18 21:06 ` Arnd Bergmann [this message]
2015-11-18 20:41 ` 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=4749121.AD5OMAAsPq@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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).