Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755146Ab2JCPAe (ORCPT ); Wed, 3 Oct 2012 11:00:34 -0400 Received: from mail-ie0-f174.google.com ([209.85.223.174]:39002 "EHLO mail-ie0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754629Ab2JCPAd (ORCPT ); Wed, 3 Oct 2012 11:00:33 -0400 Date: Wed, 3 Oct 2012 11:00:58 -0400 From: Matt Porter To: Greg Kroah-Hartman , "Hans J. Koch" , Benoit Cousson , Paul Walmsley , Sekhar Nori Cc: Tony Lindgren , Russell King , Linux OMAP List , Linux Kernel Mailing List , Linux ARM Kernel List , Linux DaVinci Kernel List Subject: Re: [PATCH v2 0/7] uio_pruss cleanup and platform support Message-ID: <20121003150058.GB11180@beef> References: <1348861072-14507-1-git-send-email-mporter@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1348861072-14507-1-git-send-email-mporter@ti.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1102 Lines: 26 On Fri, Sep 28, 2012 at 03:37:45PM -0400, Matt Porter wrote: > Changes since v1: > - Replaced uio_pruss private SRAM API use with genalloc > - Added DA850 platform device and clock support > - Added DA850 L3 RAM gen_pool support > - Split out DT binding > > This series enables uio_pruss on both DA850 and AM33xx. The driver > previously was not enabled by any platform and the private SRAM API > was accessing an invalid SRAM bank for use on DA850. For AM33xx, > DT, pinctrl, and runtime PM support are added since AM33xx only > boots via DT. I'm dropping AM33xx/OMAP support from v3 for this series since the focus has turned to fixing Davinci SRAM to provide genalloc support and the associated use of that in the driver. I'll have a separate series with AM33xx support since dealing cleanly with external resets on OMAP is a bigger issue. -Matt -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/