On 10/07/2019 15:52, Marc Gonzalez wrote:
> Your solution works great. It's refreshing to have stuff work
> out-of-the-box!
Arg! I spoke too soon. For some reason, si2157_init() is not being
called when it should. I'm trying to trace it down...
On 08/07/2019 21:58, Peter Rosin wrote:
> On 2019-07-08 13:08, Marc Gonzalez wrote:
>
>> PROBLEM #2
>>
>> 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.
>> For the time being, I don't know how to model
On Mon, Jul 08, 2019 at 07:58:00PM +, Peter Rosin wrote:
> On 2019-07-08 13:08, Marc Gonzalez wrote:
[...]
> > + dvb_demod: si2168@64 {
> > + compatible = "silabs,si2168";
> > + reg = <0x64>;
> > + reset-gpios = <&tlmm 84 GPIO_ACTIVE_LOW>;
>
>
> In principle, I
On 2019-07-08 13:08, Marc Gonzalez wrote:
> Hello everyone,
*snip*
Focusing on #2...
> PROBLEM #2
>
> 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.
> For the time being, I don't know how to model this
On 08.07.19 17:03, Marc Gonzalez wrote:
> One problem is that since the internal bus is "created" (declared?) at
> run-time,
> it doesn't seem possible to define it (or its client) in DT.
Maybe declare it nested inside the si2168 device ?
The driver then needs a piece of glue code for triggering
On 08/07/2019 13:08, Marc Gonzalez wrote:
> PROBLEM #1
>
> The media framework requires that the TSIF and demod be "tied" together,
> by calling dvb_register_frontend(). If I do that in tsif.c, then I need to
> get the frontend pointer from the demod at some point. There is no such
> callback pre
On 08/07/2019 16:44, Enrico Weigelt wrote:
> 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 its own i2c controller ?
It does
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 an
Hello everyone,
My first message(*) might have been too vague. Let me try explaining
the goal in a different way, using code this time. (Provided at the
end of this message.)
(*) https://www.spinics.net/lists/arm-kernel/msg739657.html
Background: I'm working with a SoC that provides a TSIF HW bl
