From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>,
Jarkko Nikula <jarkko.nikula@bitmer.com>,
Tony Lindgren <tony@atomide.com>,
Eduardo Valentin <edubezval@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Aaro Koskinen <aaro.koskinen@iki.fi>, Nishanth Menon <nm@ti.com>,
Sebastian Reichel <sre@kernel.org>,
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 16:36:38 +0200 [thread overview]
Message-ID: <a132c193-5c00-14cb-91bf-abb86eac01d6@ti.com> (raw)
In-Reply-To: <20170102125840.GD6728@pali>
On 01/02/2017 02:58 PM, Pali Rohár wrote:
> On Monday 02 January 2017 14:53:44 Peter Ujfalusi wrote:
>> On 01/02/2017 10:51 AM, Pali Rohár wrote:
>>> On Monday 02 January 2017 10:34:34 Peter Ujfalusi wrote:
>>>> On 01/02/2017 12:36 AM, Pavel Machek wrote:
>>>>> Are there multi-button headsets compatible with N900?
>>>>
>>>> Not sure if n900 is capable of handling ECI communication, n9 was. In n9
>>>> the PMIC/Audio chip had an ECI core integrated afaik
>>>
>>> In N9 it is handled by twl5030 chip? Is there documentation for that
>>> ECI/ACI part? N900 has twl4030 so we need some chip documentation for
>>> adding support for N900...
>>
>> n9 has twl5031 and the documentation is not public. But the kernel
>> source from Nokia have the driver under drivers/mfd/twl5031-aci.c It is
>> using the ECI stack to report the changes.
>> twl4030 and twl5030 does not have support for ECI, only twl5031.
>
> Ok, so Nokia N900's audio chip (twl4030) does not have support for ECI.
TLV320AIC34 (two of them) on n900 to be precise, n9 uses twl5031 and
tlv320dac33.
> But still as Jarkko wrote there could be an option to supports ECI via
> GPIO and ADC.
Yes, there is the option, but w/o documentation on the ECI protocol it
is not going to be easy. And I'm sure there were a (good) reason the
n900 does not support ECI. If it could be done in a stable way the
product would have support for it.
> And there is still mysterious gpio 178 (RX51_ECI_SWITCH_1_GPIO) which
> could help us?
Yeah, that is something I have no idea what it is for. It could be that
the schema is using different pin mode for it? It might worth looking at
the TRM on which pin the gpio_178 can go out and look for the possible
modes? Most likely waste of time...
>
--
Péter
next prev parent reply other threads:[~2017-01-02 14:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 19:54 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 [this message]
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
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=a132c193-5c00-14cb-91bf-abb86eac01d6@ti.com \
--to=peter.ujfalusi@ti.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=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--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
all inboxes | Powered by JetHome®