From: "Raphaël Assénat" <raph@8d.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Premi, Sanjeev" <premi@ti.com>
Subject: Re: [PATCH v2] AM3505/3517 ZCN package support
Date: Thu, 07 Jul 2011 10:41:03 -0400 [thread overview]
Message-ID: <4E15C57F.9020402@8d.com> (raw)
In-Reply-To: <20110707141957.GG15815@atomide.com>
On 07/07/11 10:19 AM, Tony Lindgren wrote:
> * Raphaël Assénat <raph@8d.com> [110706 19:47]:
>> Fixes according to Sanjeev's comments in previous thread.
>>
>> ---
>> This patch adds support for the AM35xx ZCN package specific muxmodes.
>
> 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..
do you think we could merge this one?
[PATCH 5/5] am3505/3517: Various platform defines for UART4
http://marc.info/?l=linux-omap&m=130980816418020&w=4
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ël Assénat
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-07-07 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 16:52 [PATCH v2] AM3505/3517 ZCN package support Raphaël Assénat
2011-07-07 14:19 ` Tony Lindgren
2011-07-07 14:41 ` Raphaël Assénat [this message]
2011-07-07 15:35 ` Tony Lindgren
2011-07-08 17:11 ` Raphaël Assénat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E15C57F.9020402@8d.com \
--to=raph@8d.com \
--cc=linux-omap@vger.kernel.org \
--cc=premi@ti.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox