From: Tony Lindgren <tony@atomide.com>
To: "R, Sricharan" <r.sricharan@ti.com>
Cc: "Cousson, Benoit" <b-cousson@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 0/5] OMAP4: mux: Initialise OMAP4 mux pins.
Date: Fri, 19 Nov 2010 08:04:04 -0800 [thread overview]
Message-ID: <20101119160403.GQ9264@atomide.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB5930247388A41@dbde02.ent.ti.com>
* R, Sricharan <r.sricharan@ti.com> [101119 00:39]:
>
> Ok . This means that the pin muxing introduced
> would be applicable for omap 2 ,3 and 4 also, with the
> board file passing the respective data if they are different ?
Well the pin configuration stays board specific, but the code
to set the pads is same for all omap2/3/4.
Even if the signal names stay the same, the pad configuration
register value may be different if external pulls are used
instead of the internal ones.
Regards,
Tony
next prev parent reply other threads:[~2010-11-19 16:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 7:38 [PATCH 0/5] OMAP4: mux: Initialise OMAP4 mux pins sricharan
2010-11-15 7:38 ` [PATCH 1/5] OMAP4: hsmmc: Initialise the mmc " sricharan
2010-11-18 19:03 ` Tony Lindgren
2010-11-15 7:38 ` [PATCH 2/5] OMAP4: usb-musb: Initialise the usb " sricharan
2010-11-15 7:38 ` [PATCH 3/5] OMAP4: mcbsp: Initialise the mcbsp " sricharan
2010-11-15 7:38 ` [PATCH 4/5] OMAP4: board-4430sdp: Initialise the mcspi " sricharan
2010-11-15 7:38 ` [PATCH 5/5] OMAP4: serial: Initialise the uart " sricharan
2010-11-15 22:33 ` [PATCH 0/5] OMAP4: mux: Initialise OMAP4 " Cousson, Benoit
2010-11-18 19:06 ` Tony Lindgren
2010-11-18 21:06 ` Cousson, Benoit
2010-11-18 21:26 ` Tony Lindgren
2010-11-19 8:48 ` R, Sricharan
2010-11-19 16:04 ` Tony Lindgren [this message]
[not found] <1289886357-22821-1-git-send-email-r.sricharan@ti.com>
2010-11-16 6:15 ` R, Sricharan
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=20101119160403.GQ9264@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=r.sricharan@ti.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