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:06:34 -0500 [thread overview]
Message-ID: <57c69cbd-950e-ba01-5d6a-efdabe6f6d16@gmail.com> (raw)
In-Reply-To: <20160919182033.qaom5ji4k43jsu24@acer>
[-- Attachment #1.1: Type: text/plain, Size: 1388 bytes --]
On 09/19/2016 01:20 PM, Andrey Utkin wrote:
> I'm going to have quite constrained time for participation in this
> driver development, but still I think this is perspective project which
> is in line with trend of exposing internal details of complex media
> hardware for configuration by V4L2 framework. Also tw286x are used in
> both tw5864 and solo6x10 boards, and in both cases it could be
> controlled better from userspace.
> I think first thing to do is expose tw286x chips as i2c- (or more
> precisely SMBus-) controllable devices. I have accomplished that in some
> way for tw5864, and hopefully I'll manage that for solo6x10.
> But beyond that, I currently don't know.
> A senior mentor would be very appreciated :)
>
I do appreciate the assistance. In most of this I'm already in water
above my head for the most part, but I'm making progress. Currently have
a booting kernel (4.8-rc4) and usb support, taking a go at the gmac/phy
driver atm. Its mostly similar to an existing driver, but I'd like to
get it up and running since the primary use of this device is over the
network, so even if we did have proper v4l2 devices it would not be
available over the network. One other thing I'm slightly worried about
is the sii/sil9034 hdmi chip included. Apparently its rather tricky to
get a datasheet for this without a NDA due to the drm stuff built in.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-09-22 22:06 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 [this message]
2016-09-22 22:17 ` Andrey Utkin
2016-09-22 22:30 ` Marty Plummer
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=57c69cbd-950e-ba01-5d6a-efdabe6f6d16@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