From: Marty Plummer <netz.kernel@gmail.com>
To: Andrey Utkin <andrey_utkin@fastmail.com>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: TW2866 i2c driver and solo6x10
Date: Thu, 22 Sep 2016 17:30:33 -0500 [thread overview]
Message-ID: <5873da5b-d402-6757-a7ab-16bdd9eed091@gmail.com> (raw)
In-Reply-To: <20160922221713.kvi3q4qcobye6m5b@acer>
[-- Attachment #1.1: Type: text/plain, Size: 858 bytes --]
On 09/22/2016 05:17 PM, Andrey Utkin wrote:
> So is the actual machine x86 or ARM?
> Do the tw28xx chips behind the bus (i2c as you said) show up in any way
> at all? Is something like i2c controller available? Or it's ARM and we
> should tell kernel how to "find" the i2c line by feeding correct
> devicetree to it?
>
This particular device is ARM. I can't be certain right now, as I've not
gotten to the point of handling the i2c bus; In the kernel module that
it currently uses it has hard-coded i2c addresses for each chip and does
a small for-loop to do the setup i2c stuffs. I could see about getting
the i2c bus running really quick and see if the various i2c tools
buildroot provides can see them, if that's helpful.
If you could provide a list of useful info and how to acquire it I'd be
more than willing to probe stuff for it.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-09-22 22:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <25e70ffb-147a-33f4-76cf-3435ab555520@gmail.com>
2016-08-03 21:35 ` TW2866 i2c driver and solo6x10 Marty Plummer
2016-08-03 22:05 ` Marty Plummer
2016-09-19 18:20 ` Andrey Utkin
2016-09-22 22:06 ` Marty Plummer
2016-09-22 22:17 ` Andrey Utkin
2016-09-22 22:30 ` Marty Plummer [this message]
2016-07-28 4:51 Marty Plummer
2016-08-03 19:28 ` Andrey Utkin
2016-08-03 20:26 ` Marty Plummer
2016-08-03 21:01 ` Andrey Utkin
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=5873da5b-d402-6757-a7ab-16bdd9eed091@gmail.com \
--to=netz.kernel@gmail.com \
--cc=andrey_utkin@fastmail.com \
--cc=linux-media@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