From: Sricharan R <r.sricharan@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, Benoit Cousson <b-cousson@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
paul@pswan.com, linux-arm-kernel@lists.infradead.org
Subject: RE: [PATCH] omap2+: mux: Remove the use of IDLE flag.
Date: Wed, 9 Mar 2011 13:19:27 +0530 [thread overview]
Message-ID: <3454d5fcdc4f7fb8e8a5bcaffca95112@mail.gmail.com> (raw)
In-Reply-To: <20110308164033.GC26463@atomide.com>
Tony,
>-----Original Message-----
>From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
>owner@vger.kernel.org] On Behalf Of Tony Lindgren
>Sent: Tuesday, March 08, 2011 10:11 PM
>To: sricharan
>Cc: linux-omap@vger.kernel.org; b-cousson@ti.com;
santosh.shilimkar@ti.com;
>paul@pswan.com
>Subject: Re: [PATCH] omap2+: mux: Remove the use of IDLE flag.
>
>* sricharan <r.sricharan@ti.com> [110306 20:33]:
>> Currently OMAP_DEVICE_PAD_IDLE flag is used to mux pins
>> dynamically. This can be simplified by using the enabled
>> state variable of each pad. This also fixes the issue of
>> the static pads not getting muxed after idling and
>> disable/enable state transitions.
>
>Looks good, can you please repost one more time with linux-arm-kernel
>mailing list also Cc'd?
>
Ok sure. I have re posted this to the linux-arm-kernel list.
>Thanks,
>
>Tony
>--
>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
WARNING: multiple messages have this Message-ID (diff)
From: r.sricharan@ti.com (Sricharan R)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] omap2+: mux: Remove the use of IDLE flag.
Date: Wed, 9 Mar 2011 13:19:27 +0530 [thread overview]
Message-ID: <3454d5fcdc4f7fb8e8a5bcaffca95112@mail.gmail.com> (raw)
In-Reply-To: <20110308164033.GC26463@atomide.com>
Tony,
>-----Original Message-----
From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
>owner at vger.kernel.org] On Behalf Of Tony Lindgren
>Sent: Tuesday, March 08, 2011 10:11 PM
>To: sricharan
>Cc: linux-omap at vger.kernel.org; b-cousson at ti.com;
santosh.shilimkar at ti.com;
>paul at pswan.com
>Subject: Re: [PATCH] omap2+: mux: Remove the use of IDLE flag.
>
>* sricharan <r.sricharan@ti.com> [110306 20:33]:
>> Currently OMAP_DEVICE_PAD_IDLE flag is used to mux pins
>> dynamically. This can be simplified by using the enabled
>> state variable of each pad. This also fixes the issue of
>> the static pads not getting muxed after idling and
>> disable/enable state transitions.
>
>Looks good, can you please repost one more time with linux-arm-kernel
>mailing list also Cc'd?
>
Ok sure. I have re posted this to the linux-arm-kernel list.
>Thanks,
>
>Tony
>--
>To unsubscribe from this list: send the line "unsubscribe linux-omap" in
>the body of a message to majordomo at vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-03-09 7:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 4:35 [PATCH] omap2+: mux: Remove the use of IDLE flag sricharan
2011-03-08 16:40 ` Tony Lindgren
2011-03-09 7:49 ` Sricharan R [this message]
2011-03-09 7:49 ` Sricharan R
2011-03-09 11:49 ` Sricharan R
2011-03-09 11:49 ` Sricharan R
2011-03-09 20:32 ` [PATCH] omap2+: mux: Add macro for configuring static with omap_hwmod_mux_init (Re: [PATCH] omap2+: mux: Remove the use of IDLE flag) Tony Lindgren
2011-03-09 20:32 ` Tony Lindgren
2011-03-10 4:26 ` Sricharan R
2011-03-10 4:26 ` Sricharan R
2011-03-11 6:13 ` Sricharan R
2011-03-11 6:13 ` Sricharan R
2011-03-11 19:35 ` Tony Lindgren
2011-03-11 19:35 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2011-03-09 7:45 [PATCH] omap2+: mux: Remove the use of IDLE flag sricharan
2011-03-09 7:45 ` sricharan
2011-03-09 19:42 ` Tony Lindgren
2011-03-09 19:42 ` Tony Lindgren
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=3454d5fcdc4f7fb8e8a5bcaffca95112@mail.gmail.com \
--to=r.sricharan@ti.com \
--cc=b-cousson@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pswan.com \
--cc=santosh.shilimkar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.