public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: LW@KARO-electronics.de (Lothar Waßmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i.MX51: Full iomux support
Date: Wed, 15 Dec 2010 16:19:15 +0100	[thread overview]
Message-ID: <19720.56435.675373.277522@ipc1.ka-ro> (raw)
In-Reply-To: <20101215151528.GD29833@pengutronix.de>

Hi,

Sascha Hauer writes:
> On i.MX51 there are several pins which do not have a sel_input register
> associated (I2C) and so setting the SION bit becomes mandatory. On the
> other hand not all pins have a SION bit. I'm confused...
> 
sel_input has nothing to do with SION. sel_input is an additional
multiplexer that can route one of different pads for a given internal
function.
SION (according to the spec) enables the input path of a pad no matter
what function is chosen.


Lothar Wa?mann
-- 
___________________________________________________________

Ka-Ro electronics GmbH | Pascalstra?e 22 | D - 52076 Aachen
Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10
Gesch?ftsf?hrer: Matthias Kaussen
Handelsregistereintrag: Amtsgericht Aachen, HRB 4996

www.karo-electronics.de | info at karo-electronics.de
___________________________________________________________

  reply	other threads:[~2010-12-15 15:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15 14:01 [PATCH] i.MX51: Full iomux support Sascha Hauer
2010-12-15 14:01 ` [PATCH 1/2] MXC IOMUX-V3 replace struct pad_desc with bitmapped cookie (step 2) Sascha Hauer
2010-12-15 14:01 ` [PATCH 2/2] ARM i.MX51: Full iomux support Sascha Hauer
2010-12-15 14:29 ` [PATCH] " Arnaud Patard (Rtp)
2010-12-15 15:10   ` Lothar Waßmann
2010-12-15 15:23     ` Sascha Hauer
2010-12-15 15:37     ` Arnaud Patard (Rtp)
2010-12-27 17:47       ` Nguyen Dinh-R00091
2010-12-27 18:25       ` Nguyen Dinh-R00091
2010-12-28  7:38         ` Lothar Waßmann
2010-12-15 15:15   ` Sascha Hauer
2010-12-15 15:19     ` Lothar Waßmann [this message]
2010-12-15 16:12 ` Peter Horton

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=19720.56435.675373.277522@ipc1.ka-ro \
    --to=lw@karo-electronics.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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