From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933557Ab1JDTzI (ORCPT ); Tue, 4 Oct 2011 15:55:08 -0400 Received: from mail-wy0-f174.google.com ([74.125.82.174]:38956 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933403Ab1JDTzG (ORCPT ); Tue, 4 Oct 2011 15:55:06 -0400 MIME-Version: 1.0 X-Originating-IP: [93.172.135.251] In-Reply-To: <87botwk4gw.fsf@ti.com> References: <1316948337-7924-1-git-send-email-ohad@wizery.com> <1316948337-7924-3-git-send-email-ohad@wizery.com> <87sjni9aql.fsf@ti.com> <87botwk4gw.fsf@ti.com> From: Ohad Ben-Cohen Date: Tue, 4 Oct 2011 21:54:44 +0200 Message-ID: Subject: Re: [RFC 2/5] ARM: OMAP: omap_device: add a method to set iommu private archdata To: Kevin Hilman Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Laurent Pinchart , Joerg Roedel , iommu@lists.linux-foundation.org, Arnd Bergmann , linux-kernel@vger.kernel.org, Cousson Benoit , Tony Lindgren , Grant Likely , Hiroshi DOYU 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 On Tue, Oct 4, 2011 at 8:15 PM, Kevin Hilman wrote: > The approach is OK with me, but I'm a bit torn about whether or not to > merge this since the need for this should go away when converting to DT. I guess it will still take some time until our boards are fully functional with DT, so I think we should regard this as an interim solution. Without this patch, a huge deal of code consolidation and generalization is gated (namely - generic iommu and dma api, and everything that depends on it, e.g. rpmsg/remoteproc). > Is anyone working on IOMMU DT description? Unless Benoit is, I'll happily pick this up. > I guess if I do merge this, we can also clean this up significantly > after all devices are converted to DT. Sure. > Unless it has other dependencies on Benoit's further DT patches, you can > base this on my for_3.2/omap_device-2 branch which includes Benoit's > alloc changes. Ok, thanks a lot ! Ohad. From mboxrd@z Thu Jan 1 00:00:00 1970 From: ohad@wizery.com (Ohad Ben-Cohen) Date: Tue, 4 Oct 2011 21:54:44 +0200 Subject: [RFC 2/5] ARM: OMAP: omap_device: add a method to set iommu private archdata In-Reply-To: <87botwk4gw.fsf@ti.com> References: <1316948337-7924-1-git-send-email-ohad@wizery.com> <1316948337-7924-3-git-send-email-ohad@wizery.com> <87sjni9aql.fsf@ti.com> <87botwk4gw.fsf@ti.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tue, Oct 4, 2011 at 8:15 PM, Kevin Hilman wrote: > The approach is OK with me, but I'm a bit torn about whether or not to > merge this since the need for this should go away when converting to DT. I guess it will still take some time until our boards are fully functional with DT, so I think we should regard this as an interim solution. Without this patch, a huge deal of code consolidation and generalization is gated (namely - generic iommu and dma api, and everything that depends on it, e.g. rpmsg/remoteproc). > Is anyone working on IOMMU DT description? Unless Benoit is, I'll happily pick this up. > I guess if I do merge this, we can also clean this up significantly > after all devices are converted to DT. Sure. > Unless it has other dependencies on Benoit's further DT patches, you can > base this on my for_3.2/omap_device-2 branch which includes Benoit's > alloc changes. Ok, thanks a lot ! Ohad.