From: Vinod Koul <vinod.koul@intel.com>
To: Arnd Bergmann <arnd@arndb.de>, Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: ksummit-discuss@lists.linuxfoundation.org,
Dave Airlie <airlied@linux.ie>,
"Nikula, Jani" <jani.nikula@linux.intel.com>,
Grant Likely <grant.likely@linaro.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] (group) maintainership models
Date: Tue, 2 Aug 2016 10:16:09 +0530 [thread overview]
Message-ID: <20160802044609.GS9681@localhost> (raw)
In-Reply-To: <23532527.pWCIkcecbr@wuerfel>
On Mon, Aug 01, 2016 at 04:10:29PM +0200, Arnd Bergmann wrote:
> On Monday, August 1, 2016 10:36:01 AM CEST Laurent Pinchart wrote:
> > On Monday 01 Aug 2016 08:56:30 Arnd Bergmann wrote:
> > > On Sunday, July 31, 2016 11:27:53 PM CEST Vinod Koul wrote:
> > > > On Thu, Jul 28, 2016 at 10:44:23AM +0200, Arnd Bergmann wrote:
> > > > > config FOO
> > > > >
> > > > > bool "foo driver" if COMPILE_TEST && !ARCH_FOO
> > > > > default ARCH_FOO
> > > > > depends on GPIOLIB && I2C && OF && WHATEVER
> > > > >
> > > > > This becomes a silent always-on symbol if the platform is used,
> > > > > and user-selectable on every other platform with COMPILE_TEST.
> > > >
> > > > Yeah this seems a bit more better. I am perhaps thinking to add top
> > > > level arch dependency if required. I will try this out on DMAengine to
> > > > start with and ease my build tests
> > >
> > > Sounds good. Let me know if you end up having to add a 'depends on ARM'
> > > dependency anywhere, as that might indicate that we are doing something
> > > different on ARM that should be done in a more generic way.
> >
> > OMAP DMA comes to mind, we still depend on the implementation provided by
> > arch/arm/plat-omap/dma.c.
>
> That's a dependency on MACH_OMAP instead of ARM though, which is a bit
> different.
>
> (Getting offtopic and) speaking of this one, is anyone working
> on converting the last four or five drivers to the dmaengine framework?
Rather lets' move this conversation to dmaengine list?
> drivers/media/platform/omap/omap_vout_vrfb.c
> drivers/mtd/onenand/omap2.c
> drivers/usb/gadget/udc/omap_udc.c
> drivers/usb/musb/tusb6010_omap.c
> (and a bit of drivers/video/fbdev/omap/omapfb_main.c)
Peter?
>
> I guess we could improve build coverage by moving
> arch/arm/plat-omap/dma.c into drivers/dma/omap-dma.c, but that
> has the disadvantage of exposing a nonstandard interface from
> somewhere inside of the dmaengine subsystem.
yeah that won't be nice. I think we should get these removed... We have omap
as well as edma driver in dmaengine.
--
~Vinod
next prev parent reply other threads:[~2016-08-02 4:38 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 12:11 Daniel Vetter
2016-07-22 20:02 ` Darren Hart
2016-07-25 5:57 ` Daniel Vetter
2016-07-26 16:22 ` Darren Hart
2016-07-28 22:13 ` Bjorn Helgaas
2016-07-26 16:45 ` Olof Johansson
2016-07-27 3:04 ` Vinod Koul
2016-07-27 5:34 ` Wolfram Sang
2016-07-27 7:53 ` Arnd Bergmann
2016-07-27 12:57 ` Vinod Koul
2016-07-27 14:22 ` Mark Brown
2016-07-27 17:15 ` Vinod Koul
2016-07-28 8:44 ` Arnd Bergmann
2016-07-28 23:48 ` Alexandre Belloni
2016-07-29 0:06 ` Stephen Rothwell
2016-07-31 17:57 ` Vinod Koul
2016-08-01 6:56 ` Arnd Bergmann
2016-08-01 7:36 ` Laurent Pinchart
2016-08-01 14:10 ` Arnd Bergmann
2016-08-02 4:46 ` Vinod Koul [this message]
2016-08-02 6:48 ` Peter Ujfalusi
2016-08-02 7:27 ` Arnd Bergmann
2016-08-02 8:29 ` Peter Ujfalusi
2016-08-02 8:33 ` Laurent Pinchart
2016-08-02 9:49 ` Tony Lindgren
2016-08-02 8:41 ` Russell King - ARM Linux
2016-08-02 9:21 ` Laurent Pinchart
2016-08-02 9:27 ` Russell King - ARM Linux
2016-09-02 10:46 ` Vinod Koul
2016-09-02 17:25 ` Linus Torvalds
2016-09-02 20:06 ` Arnd Bergmann
2016-09-02 20:26 ` Linus Torvalds
2016-09-02 20:43 ` Julia Lawall
2016-09-02 20:50 ` Linus Torvalds
2016-09-02 22:16 ` Benjamin Herrenschmidt
2016-09-03 14:02 ` Michael Ellerman
2016-09-02 23:35 ` Arnd Bergmann
2016-09-04 17:45 ` Geert Uytterhoeven
2016-09-04 17:59 ` Linus Torvalds
2016-09-03 0:07 ` Mark Brown
2016-07-27 12:59 ` Daniel Vetter
2016-07-27 13:03 ` Daniel Vetter
2016-08-01 14:42 ` Jani Nikula
2016-09-07 5:03 Leon Romanovsky
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=20160802044609.GS9681@localhost \
--to=vinod.koul@intel.com \
--cc=airlied@linux.ie \
--cc=arnd@arndb.de \
--cc=grant.likely@linaro.org \
--cc=jani.nikula@linux.intel.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=peter.ujfalusi@ti.com \
--cc=torvalds@linux-foundation.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