From: joerg Reisenweber <joerg@openmoko.org>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
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>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Nokia N900 sound driver and ECI GPIOs
Date: Mon, 02 Jan 2017 22:05:39 +0100 [thread overview]
Message-ID: <2036063.jAbaHqGlp2@saturn> (raw)
In-Reply-To: <201701022101.01341@pali>
[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]
On Mon 02 January 2017 21:01:01 Pali Rohár wrote:
> On Monday 02 January 2017 19:49:45 Aaro Koskinen wrote:
> > 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...
We found this, see https://irclog.whitequark.org/neo900/2017-01-01 (has a lot
of possibly useful references/links)
The question is if pin AA3 aka GPIO_178 is actually NotConnected in N900 or
it's just an omission in schematics and there's actually some more 'stealth
hardware' in N900 that doesn't show up in docs, just like the testpoint UART
console http://wiki.maemo.org/N900_Hardware_Hacking#Debug_ports which also are
missing in schematics.
> 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).
I could use one of the unpopulated N900 PCB and solder a wire to the OMAP AA3
pad, then try to make sure it's not connected to anything, or if it is then
find out about the details of this.
But I'm reluctant to do this, since it's an error prone and (in case of N/C)
not verifiable procedure, so I'd appreciate any further info, whether from
historical anecdote or from sourcecode review and conclusions, regarding that.
cheers
jOERG
--
() ascii ribbon campaign
/\
against html e-mail - against proprietary attachments
http://www.georgedillon.com/web/html_email_is_evil.shtml
http://www.nonhtmlmail.org/campaign.html
http://www.georgedillon.com/web/html_email_is_evil_still.shtml
http://www.gerstbach.at/2004/ascii/ (German)
[-- 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 21:07 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
2017-01-02 21:05 ` joerg Reisenweber [this message]
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=2036063.jAbaHqGlp2@saturn \
--to=joerg@openmoko.org \
--cc=aaro.koskinen@iki.fi \
--cc=edubezval@gmail.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=jarkko.nikula@bitmer.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=pali.rohar@gmail.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).