On 08.07.19 13:08, Marc Gonzalez wrote: > The tuner (si2157) is not on the i2c5 bus, instead it is on a private > i2c bus *behind* si2168, which routes requests to the proper client. Should the si2168 make up it's own i2c controller ? --mtx -- Enrico Weigelt, metux IT consult Free software and Linux embedded engineering info@xxxxxxxxx -- +49-151-27565287
Re: [RFC] SW connection between DVB Transport Stream demuxer and I2C-based frontend
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [RFC] SW connection between DVB Transport Stream demuxer and I2C-based frontend
- From: "Enrico Weigelt, metux IT consult" <lkml@xxxxxxxxx>
- Date: Mon, 8 Jul 2019 16:44:00 +0200
- In-reply-to: <5e35b4fb-646d-6428-f372-ee47d7352cd6@free.fr>
- Organization: metux IT consult
- References: <5e35b4fb-646d-6428-f372-ee47d7352cd6@free.fr>
- User-agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1
- Follow-Ups:
- References:
- [RFC] SW connection between DVB Transport Stream demuxer and I2C-based frontend
- From: Marc Gonzalez
- [RFC] SW connection between DVB Transport Stream demuxer and I2C-based frontend
- Prev by Date: Re: [PATCH] gpio: tegra: fix debugfs compile error
- Next by Date: Re: [RFC] SW connection between DVB Transport Stream demuxer and I2C-based frontend
- Previous by thread: [RFC] SW connection between DVB Transport Stream demuxer and I2C-based frontend
- Next by thread: Re: [RFC] SW connection between DVB Transport Stream demuxer and I2C-based frontend
- Index(es):
 |