All of lore.kernel.org
 help / color / mirror / Atom feed
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] More select madness - keystone
Date: Wed, 8 Jan 2014 09:06:11 -0500	[thread overview]
Message-ID: <52CD5B53.6040704@ti.com> (raw)
In-Reply-To: <52CCD029.6090404@ti.com>

On Tuesday 07 January 2014 11:12 PM, Sekhar Nori wrote:
> On Friday 03 January 2014 01:07 AM, Santosh Shilimkar wrote:
>> On Thursday 02 January 2014 02:17 PM, Santosh Shilimkar wrote:
>>> On Thursday 02 January 2014 12:26 PM, Russell King - ARM Linux wrote:
>>>> warning: (ARCH_KEYSTONE && SPI_DAVINCI) selects TI_EDMA which has unmet direct dependencies (DMADEVICES && (ARCH_DAVINCI || ARCH_OMAP || ARCH_KEYSTONE))
>>>>
>>>> This results in the EDMA engine code not being built.  Yet another
>>>> example of why improper use of the "select" statement is bad news
>>>> and leads to broken configurations.
>>>>
>>> Thanks for reporting Russell. Will have a look.
>>>
>> Just to be clear for records, the select was introduced before
>> KEYSTONE support was enabled. As per git blame, it came via commit
>> b5f1433059 {spi: davici - make davinci select edma}.
> 
> I don't quite recall why this was needed and the commit description does
> not help. Anyway, this is not needed - at least with current code. I
> verified that the DaVinci SPI driver builds correctly with TI_EDMA
> switched off. I can send a revert.
> 
Please do...

> BTW, it looks like arch/arm/mach-keystone/Kconfig has a select for
> TI_EDMA as well and that needs to be removed too.
> 
I have patch to kill that. Will be posting that.

Regards,
Santosh

      reply	other threads:[~2014-01-08 14:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-02 17:26 [BUG] More select madness - keystone Russell King - ARM Linux
2014-01-02 19:17 ` Santosh Shilimkar
2014-01-02 19:37   ` Santosh Shilimkar
2014-01-08  4:12     ` Sekhar Nori
2014-01-08 14:06       ` Santosh Shilimkar [this message]

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=52CD5B53.6040704@ti.com \
    --to=santosh.shilimkar@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.