All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Pandita, Vikram" <vikram.pandita@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
	Hugo Vincent <hugo.vincent@gmail.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Chikkature Rajashekar, Madhusudhan" <madhu.cr@ti.com>
Subject: Re: [PATCH] OMAP3: MMC: Add mux for pins
Date: Wed, 17 Jun 2009 14:39:32 -0700	[thread overview]
Message-ID: <878wjqy1yj.fsf@deeprootsystems.com> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC35608702F53D18C6@dbde02.ent.ti.com> (Vikram Pandita's message of "Thu\, 18 Jun 2009 00\:08\:01 +0530")

"Pandita, Vikram" <vikram.pandita@ti.com> writes:

>>-----Original Message-----
>>From: Kevin Hilman [mailto:khilman@deeprootsystems.com]
>>
>>>>If some pins are always needed, and don't have alternative pinouts, then
>>>>the common pins could be muxed in devices.c.
>>>
>>> This is the algo we can use for MMC pin muxing in that case:
>>>
>>> MMC1: No pin has mux clash
>>> 	Mux all 10 pins in devices.c
>>
>>Is this common across 34xx and 35xx?
>
> Yes this is common.
> Both are same OMAP3 marketed differently.

Yes, but they are in different packages, so I was curious if the pin
muxing is identical across the different packages.

Kevin

  reply	other threads:[~2009-06-17 21:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 22:41 [PATCH] OMAP3: MMC: Add mux for pins Vikram Pandita
2009-06-15  8:12 ` Tony Lindgren
2009-06-15 10:44   ` Hugo Vincent
2009-06-15 11:04     ` Tony Lindgren
2009-06-15 15:46       ` Madhusudhan
2009-06-16 14:56       ` Pandita, Vikram
2009-06-16 15:35         ` Kevin Hilman
2009-06-16 16:50           ` Pandita, Vikram
2009-06-17  8:12             ` Tony Lindgren
2009-06-17 17:44               ` Pandita, Vikram
2009-06-17 18:27                 ` Kevin Hilman
2009-06-17 18:38                   ` Pandita, Vikram
2009-06-17 21:39                     ` Kevin Hilman [this message]
2009-06-17 22:48                       ` Jon Hunter
2009-06-17 22:57                         ` Kevin Hilman
2009-06-17 23:25                           ` Pandita, Vikram
2009-06-18  0:08                             ` Jon Hunter
2009-06-18  5:04                               ` 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=878wjqy1yj.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=hugo.vincent@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=madhu.cr@ti.com \
    --cc=tony@atomide.com \
    --cc=vikram.pandita@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 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.