From: "Pali Rohár" <pali.rohar@gmail.com>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
Jarkko Nikula <jarkko.nikula@bitmer.com>,
Tony Lindgren <tony@atomide.com>,
Eduardo Valentin <edubezval@gmail.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
Nishanth Menon <nm@ti.com>, Sebastian Reichel <sre@kernel.org>,
Pavel Machek <pavel@ucw.cz>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
joerg Reisenweber <joerg@openmoko.org>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Nokia N900 sound driver and ECI GPIOs
Date: Mon, 2 Jan 2017 21:01:01 +0100 [thread overview]
Message-ID: <201701022101.01341@pali> (raw)
In-Reply-To: <20170102184945.m6maflaoihumd7nt@raspberrypi-2.musicnaut.iki.fi>
[-- Attachment #1: Type: Text/Plain, Size: 1213 bytes --]
On Monday 02 January 2017 19:49:45 Aaro Koskinen wrote:
> Hi,
>
> On Mon, Jan 02, 2017 at 09:44:32AM +0100, Pali Rohár wrote:
> > On Monday 02 January 2017 10:23:23 Peter Ujfalusi wrote:
> > > GPIO_182 is to select where to route the MIC line from the jack
> > > for the ECI core to handle (when the TVOUT is disabled).
> >
> > Yes, already figured out from schematic.
> >
> > > I have no idea what the
> > > gpio_178 should have been used for. It might be only needed for
> > > early protos but not in production devices?
> >
> > I do not know, reason why I'm asking.
>
> The schematic shows ECI(5:0), but only 3 are connected/used. There
> were 3 other GPIOs reserved but not used in the final product.
Are you sure that this is truth (maybe you have some information)? Or
you just looked at schematic and deduced this observation (as other
people too)?
Joerg already told us that RX51 schematic does not 100% match production
N900 and e.g. there is missing UART3 pins...
What we know that gpio 178 is *already* controlled and changed by
production Nokia kernel running on production N900 devices (as I wrote
in first email).
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2017-01-02 20:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 19:54 Nokia N900 sound driver and ECI GPIOs Pali Rohár
2017-01-01 22:36 ` Pavel Machek
2017-01-02 8:34 ` Peter Ujfalusi
2017-01-02 8:51 ` Pali Rohár
2017-01-02 12:53 ` Peter Ujfalusi
2017-01-02 12:58 ` Pali Rohár
2017-01-02 14:36 ` Peter Ujfalusi
2017-01-02 15:51 ` joerg Reisenweber
2017-01-02 17:02 ` Pali Rohár
2017-01-02 15:45 ` joerg Reisenweber
2017-01-02 9:01 ` Jarkko Nikula
2017-01-02 9:29 ` Pali Rohár
2017-01-02 9:33 ` Pavel Machek
2017-01-02 16:07 ` joerg Reisenweber
2017-01-02 8:23 ` Peter Ujfalusi
2017-01-02 8:44 ` Pali Rohár
2017-01-02 18:49 ` Aaro Koskinen
2017-01-02 20:01 ` Pali Rohár [this message]
2017-01-02 21:05 ` joerg Reisenweber
2017-01-04 22:27 ` Aaro Koskinen
2017-01-04 22:41 ` Pali Rohár
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=201701022101.01341@pali \
--to=pali.rohar@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=edubezval@gmail.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=jarkko.nikula@bitmer.com \
--cc=joerg@openmoko.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=pavel@ucw.cz \
--cc=peter.ujfalusi@ti.com \
--cc=sre@kernel.org \
--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 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).