From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ocean.emcraft.com (ocean.emcraft.com [213.221.7.182]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 87530DDDDB for ; Fri, 14 Nov 2008 04:51:23 +1100 (EST) Message-ID: <491C68F3.3030102@emcraft.com> Date: Thu, 13 Nov 2008 20:50:43 +0300 From: Ilya Yanok MIME-Version: 1.0 To: Josh Boyer Subject: Re: [PATCH 11/11] ppc440spe-adma: ADMA driver for PPC440SP(e) systems References: <1226589364-5619-1-git-send-email-yanok@emcraft.com> <1226589364-5619-12-git-send-email-yanok@emcraft.com> <20081113160307.GB2299@yoda.jdub.homelinux.org> In-Reply-To: <20081113160307.GB2299@yoda.jdub.homelinux.org> Content-Type: text/plain; charset=ISO-8859-1 Cc: linux-raid@vger.kernel.org, linuxppc-dev@ozlabs.org, wd@denx.de, dzu@denx.de List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Josh Boyer wrote: > On Thu, Nov 13, 2008 at 06:16:04PM +0300, Ilya Yanok wrote: > >> Adds the platform device definitions and the architecture specific support >> routines for the ppc440spe adma driver. >> >> Any board equipped with PPC440SP(e) controller may utilize this driver. >> >> Signed-off-by: Yuri Tikhonov >> Signed-off-by: Ilya Yanok >> > > Before I really dig into reviewing this driver, I'm going to ask you as simple > question. This looks like a 1/2 completed port of an arch/ppc driver that uses > the device tree (incorrectly) to get the interrupt resources and that's about it. > Otherwise, it's just a straight up platform device driver. Is that correct? > Yep, that's correct. > If that is the case, I think the driver needs more work before it can be merged. > It should get the DCR and MMIO resources from the device tree as well. It should > be binding on compatible properties and not based on device tree paths. And it > should probably be an of_platform device driver. > Surely, you're right. I agree with you in that this driver isn't ready for merging. But it works so we'd like to publish it so interested people could use it and test it. Regards, Ilya.