From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754879Ab0CYPU7 (ORCPT ); Thu, 25 Mar 2010 11:20:59 -0400 Received: from mail-bw0-f209.google.com ([209.85.218.209]:47302 "EHLO mail-bw0-f209.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754860Ab0CYPU5 (ORCPT ); Thu, 25 Mar 2010 11:20:57 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=PCIaY5nmtlok8Gxqf+Z0ulQ8lSAZ8Xoy79NP8adqk3Wc4totQHB62IWgMNynd5/HcA aJXDJFbIku2aaCBcMxKnTSSMdWYqBfJzDHnNjcvKZgJbKdU7XKXN91cQc0RZ84+aENGL URdy39/BGAJFnN3ZMZXrMvcnDI+N80i9puDtU= MIME-Version: 1.0 In-Reply-To: <1b68c6791003250517y4e2789baoe147e5982c363682@mail.gmail.com> References: <4BAAD5BB.7050101@samsung.com> <1b68c6791003242234h106d9530p12b5a046a906227e@mail.gmail.com> <63386a3d1003250130w6f34854ag2ca163799e9b7bed@mail.gmail.com> <1b68c6791003250517y4e2789baoe147e5982c363682@mail.gmail.com> Date: Thu, 25 Mar 2010 16:20:55 +0100 Message-ID: <63386a3d1003250820x3cf81000i9d27e95c755b9ca8@mail.gmail.com> Subject: Re: [PATCH v2] PL330: Add PL330 DMA controller driver From: Linus Walleij To: jassi brar Cc: Joonyoung Shim , dan.j.williams@intel.com, kyungmin.park@samsung.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Russell King - ARM Linux , Ben Dooks Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2010/3/25 jassi brar : > My approach is to write a separate PL330 core driver as the backend which > can be reused by any DMA API implementer driver. That will avoid > having two copies of the PL330 driver, among other benefits. Seems like a rather good approach. > And if this patch is accepted, there > _will_ exist two copies of the PL330 driver -- one in drivers/dma/pl330_dmac.c > and another in arch/arm/plat-samsung/. Only the former will be lying unused > until some other SoC vendor decided to use PL330, because S3C has come too > long a way to change its drivers to driver/dma/ API and modify DMA > drivers for every SoC. What's wrong with merging them later then? Refactoring FTW. > I have the pl330-core part almost ready, but i need time to implement > some _testable_ > implementation of the scheme. If maintainers want to see structure of > my code, I can > share it too, but I think I pretty much made it clear. Why not just post it on the list? I'm curious! Since I'm working on a PrimeCell DMA API I would love to look at PrimeCell DMA engine drivers. Yours, Linus Walleij