From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-kernel@vger.kernel.org,
Bibek BASU <bibek.basu@stericsson.com>,
Sascha Hauer <kernel@pengutronix.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Juergen Beisert <jbe@pengutronix.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Smartcard/SIM card subsystem, LDO regulator and signal modelling
Date: Wed, 18 May 2011 09:25:58 -0700 [thread overview]
Message-ID: <20110518162558.GA16414@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <BANLkTikAzjmVoNK20RHRkhHkn3YgSra6dA@mail.gmail.com>
On Wed, May 18, 2011 at 12:36:17PM +0200, Linus Walleij wrote:
> It's basically an LDO for powering a SIM card (which in turn is basically
> a smartcard), but apart from plain regulation also expose some other
> electrical properties of the interface to software:
> - Select pull-up resistance on some I/O lines
> - Select weak pull-down on some data lines
> - Select load capacitance limits on the data lines
> - Select whether to run in low impedance or transmission gate mode
> I think these will be mostly similar so what other SIM card controllers
> will need to have. All the stuff needs to have userspace interfaces
> since the stuff is usually controlled on behalf of another CPU
> running the modem (and also performing the actual traffic on
> the SIM data lines).
The above also sounds rather like the standard sort of stuff you get
with pin muxes - the pulls are certainly very common for random GPIO
or I2C use, for example. No real idea on the SIM interface itself.
next prev parent reply other threads:[~2011-05-18 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 10:36 Smartcard/SIM card subsystem, LDO regulator and signal modelling Linus Walleij
2011-05-18 16:25 ` Mark Brown [this message]
2011-05-18 17:03 ` Linus Walleij
2011-05-18 22:19 ` Mark Brown
2011-05-19 20:02 ` Linus Walleij
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=20110518162558.GA16414@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bibek.basu@stericsson.com \
--cc=catalin.marinas@arm.com \
--cc=jbe@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).