All of lore.kernel.org
 help / color / mirror / Atom feed
From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] usb: musb: USB_TI_CPPI41_DMA requires dmaengine support
Date: Wed, 18 Nov 2015 13:27:32 -0600	[thread overview]
Message-ID: <87a8qbhzvf.fsf@saruman.tx.rr.com> (raw)
In-Reply-To: <CADYTM3baomio7+nFizOKFXMav7guow+=GsVaGExBWxQyn9t=2w@mail.gmail.com>


Hi,

Bin Liu <binmlist@gmail.com> writes:
> On Wed, Nov 18, 2015 at 10:18 AM, Arnd Bergmann <arnd@arndb.de> wrote:
>> The CPPI-4.1 driver selects TI_CPPI41, which is a dmaengine
>> driver and that may not be available when CONFIG_DMADEVICES
>> is not set:
>>
>> warning: (USB_TI_CPPI41_DMA) selects TI_CPPI41 which has unmet direct dependencies (DMADEVICES && ARCH_OMAP)
>>
>> This adds an extra dependency to avoid generating warnings in randconfig
>> builds. Ideally we'd remove the 'select' statement, but that has the
>> potential to break defconfig files.
>>
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>> Fixes: 411dd19c682d ("usb: musb: Kconfig: Select the DMA driver if DMA mode of MUSB is enabled")
>>
>> diff --git a/drivers/usb/musb/Kconfig b/drivers/usb/musb/Kconfig
>> index 1f2037bbeb0d..45c83baf675d 100644
>> --- a/drivers/usb/musb/Kconfig
>> +++ b/drivers/usb/musb/Kconfig
>> @@ -159,7 +159,7 @@ config USB_TI_CPPI_DMA
>>
>>  config USB_TI_CPPI41_DMA
>>         bool 'TI CPPI 4.1 (AM335x)'
>> -       depends on ARCH_OMAP
>> +       depends on ARCH_OMAP && DMADEVICES
>>         select TI_CPPI41
>
> I am not sure what the generic policy is, but instead of hiding
> USB_TI_CPPI41_DMA if DMADEVICES is disabled, I'd like to enable
> DMADEVICES if USB_TI_CPPI41_DMA is enabled, from user experience
> perspective.

that would mean "select DMADEVICES" and that's frowned upon.

-- 
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20151118/d0365a41/attachment.sig>

WARNING: multiple messages have this Message-ID (diff)
From: Felipe Balbi <balbi@ti.com>
To: Bin Liu <binmlist@gmail.com>, Arnd Bergmann <arnd@arndb.de>
Cc: <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] usb: musb: USB_TI_CPPI41_DMA requires dmaengine support
Date: Wed, 18 Nov 2015 13:27:32 -0600	[thread overview]
Message-ID: <87a8qbhzvf.fsf@saruman.tx.rr.com> (raw)
In-Reply-To: <CADYTM3baomio7+nFizOKFXMav7guow+=GsVaGExBWxQyn9t=2w@mail.gmail.com>

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


Hi,

Bin Liu <binmlist@gmail.com> writes:
> On Wed, Nov 18, 2015 at 10:18 AM, Arnd Bergmann <arnd@arndb.de> wrote:
>> The CPPI-4.1 driver selects TI_CPPI41, which is a dmaengine
>> driver and that may not be available when CONFIG_DMADEVICES
>> is not set:
>>
>> warning: (USB_TI_CPPI41_DMA) selects TI_CPPI41 which has unmet direct dependencies (DMADEVICES && ARCH_OMAP)
>>
>> This adds an extra dependency to avoid generating warnings in randconfig
>> builds. Ideally we'd remove the 'select' statement, but that has the
>> potential to break defconfig files.
>>
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>> Fixes: 411dd19c682d ("usb: musb: Kconfig: Select the DMA driver if DMA mode of MUSB is enabled")
>>
>> diff --git a/drivers/usb/musb/Kconfig b/drivers/usb/musb/Kconfig
>> index 1f2037bbeb0d..45c83baf675d 100644
>> --- a/drivers/usb/musb/Kconfig
>> +++ b/drivers/usb/musb/Kconfig
>> @@ -159,7 +159,7 @@ config USB_TI_CPPI_DMA
>>
>>  config USB_TI_CPPI41_DMA
>>         bool 'TI CPPI 4.1 (AM335x)'
>> -       depends on ARCH_OMAP
>> +       depends on ARCH_OMAP && DMADEVICES
>>         select TI_CPPI41
>
> I am not sure what the generic policy is, but instead of hiding
> USB_TI_CPPI41_DMA if DMADEVICES is disabled, I'd like to enable
> DMADEVICES if USB_TI_CPPI41_DMA is enabled, from user experience
> perspective.

that would mean "select DMADEVICES" and that's frowned upon.

-- 
balbi

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

  reply	other threads:[~2015-11-18 19:27 UTC|newest]

Thread overview: 20+ 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 16:18 ` Arnd Bergmann
2015-11-18 18:29 ` Bin Liu
2015-11-18 18:29   ` Bin Liu
2015-11-18 19:27   ` Felipe Balbi [this message]
2015-11-18 19:27     ` Felipe Balbi
2015-11-18 20:20     ` Bin Liu
2015-11-18 20:20       ` Bin Liu
2015-11-18 20:38       ` Felipe Balbi
2015-11-18 20:38         ` Felipe Balbi
2015-11-18 20:45         ` Bin Liu
2015-11-18 20:45           ` Bin Liu
2015-11-18 20:27   ` Arnd Bergmann
2015-11-18 20:27     ` Arnd Bergmann
2015-11-18 20:39     ` Bin Liu
2015-11-18 20:39       ` Bin Liu
2015-11-18 21:06       ` Arnd Bergmann
2015-11-18 21:06         ` Arnd Bergmann
2015-11-18 20:41     ` Felipe Balbi
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=87a8qbhzvf.fsf@saruman.tx.rr.com \
    --to=balbi@ti.com \
    --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 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.