From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?UmFwaGHDq2wgQXNzw6luYXQ=?= Subject: Re: [PATCH v2] AM3505/3517 ZCN package support Date: Thu, 07 Jul 2011 10:41:03 -0400 Message-ID: <4E15C57F.9020402@8d.com> References: <4E1492C0.8060900@8d.com> <20110707141957.GG15815@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from roc.holo.8d.com ([64.254.227.115]:46597 "EHLO roc.holo.8d.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756637Ab1GGOlG (ORCPT ); Thu, 7 Jul 2011 10:41:06 -0400 In-Reply-To: <20110707141957.GG15815@atomide.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Tony Lindgren Cc: "linux-omap@vger.kernel.org" , "Premi, Sanjeev" On 07/07/11 10:19 AM, Tony Lindgren wrote: > * Rapha=C3=ABl Ass=C3=A9nat [110706 19:47]: >> Fixes according to Sanjeev's comments in previous thread. >> >> --- >> This patch adds support for the AM35xx ZCN package specific muxmodes= =2E >=20 > Thanks for doing this. Still it's quite a few lines of data.. So > I suggest that we just plan on doing the mux data for v3.2 merge > window in device tree format. I'm planning on working on that after > v3.1 merge window and should be able to generate it for am3505 > using your patch. Ok, looking forward to testing this. > Otherwise we'll be patching something that will be disappearing > quite soon anyways. I agree. At least in the meantime my problem is fixed by this patch. This is unrelated to this thread but..=20 do you think we could merge this one?=20 [PATCH 5/5] am3505/3517: Various platform defines for UART4 http://marc.info/?l=3Dlinux-omap&m=3D130980816418020&w=3D4 It does not depend on the other patches in this set so it can be applied individually. And those definitions will be needed later when full am35xx support is implemented anyway. Best regards, Rapha=C3=ABl Ass=C3=A9nat -- To unsubscribe from this list: send the line "unsubscribe linux-omap" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html