From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/5] dma: Allow TI_EDMA selectable for ARCH_KEYSTONE
Date: Thu, 3 Oct 2013 20:33:59 +0530 [thread overview]
Message-ID: <20131003150359.GC16684@intel.com> (raw)
In-Reply-To: <524ACFAF.7020802@ti.com>
On Tue, Oct 01, 2013 at 09:35:43AM -0400, Santosh Shilimkar wrote:
> On Monday 30 September 2013 09:54 PM, Vinod Koul wrote:
> > On Mon, Sep 30, 2013 at 06:41:25PM -0400, Santosh Shilimkar wrote:
> >> Allow the TI_EDMA to be built for ARCH_KEYSTONE which also supports
> >> the EDMA IP.
> >>
> >> Cc: Vinod Koul <vinod.koul@intel.com>
> >>
> >> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> >> ---
> >> Vinod,
> >> I need your ack on this patch to carry $subject patch via arm-soc tree
> >> to avoid the unmet dependency warnings.
> > Sure, but too many dependency fixes have been popoing up for this part and this
> > IIRC is third patch! Something doesn't seem right, hopefully am wrong..
> >
> I think it mainly because EDMA support is just merged last cycle and few SOCs
> which use the EDMA trying to enable them now.
Okay btw is EDMA enabled in any of defconfigs. Having that will help us get
better test covergae in -next
>
> > I have a patch in my -next from Josh which selects TI_PRIV_EDMA for this...
> >
> I looked at your next patch which is fixing the TI_EDMA dependency.
> If you prefer to merge $subject patch via your tree, thats fine as well.
> Juts give me a stable branch targeted for 3.13 and I shall merge your branch
> and apply other patches on top of it.
Pls merge my fixes branch. I will send that to Linus in day or two...
> Since it was very trivial patch, I thought its easy to carry via arm-soc
> with your ack.
Sure, looks good to me
Acked-by: Vinod Koul <vinod.koul@intel.com>
>
> >>
> >> drivers/dma/Kconfig | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
> >> index 526ec77..b1dde16 100644
> >> --- a/drivers/dma/Kconfig
> >> +++ b/drivers/dma/Kconfig
> >> @@ -195,7 +195,7 @@ config SIRF_DMA
> >>
> >> config TI_EDMA
> >> bool "TI EDMA support"
> >> - depends on ARCH_DAVINCI || ARCH_OMAP
> >> + depends on ARCH_DAVINCI || ARCH_OMAP || ARCH_KEYSTONE
> >> select DMA_ENGINE
> >> select DMA_VIRTUAL_CHANNELS
> >> default n
> >> --
> >> 1.7.9.5
> >>
> >
>
--
next prev parent reply other threads:[~2013-10-03 15:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 22:41 [PATCH v2 0/5] ARM: keystone: Enable SPI and I2C support Santosh Shilimkar
2013-09-30 22:41 ` [PATCH v2 1/5] ARM: dts: keystone: Add i2c device nodes Santosh Shilimkar
2013-09-30 22:41 ` [PATCH v2 2/5] ARM: dts: keystone: Add the SPI nodes Santosh Shilimkar
2013-09-30 22:41 ` [PATCH v2 3/5] dma: Allow TI_EDMA selectable for ARCH_KEYSTONE Santosh Shilimkar
2013-10-01 1:54 ` Vinod Koul
2013-10-01 13:35 ` Santosh Shilimkar
2013-10-03 15:03 ` Vinod Koul [this message]
2013-10-03 15:57 ` Santosh Shilimkar
2013-10-03 15:11 ` Vinod Koul
2013-10-03 16:06 ` Santosh Shilimkar
2013-09-30 22:41 ` [PATCH v2 4/5] ARM: keystone: Select TI_EDMA to be able to enable SPI driver Santosh Shilimkar
2013-09-30 22:41 ` [PATCH v2 5/5] ARM: keystone: Enable I2C and SPI bus support Santosh Shilimkar
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=20131003150359.GC16684@intel.com \
--to=vinod.koul@intel.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.