From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Enrico Weigelt <lkml@metux.net>, I2C <linux-i2c@vger.kernel.org>,
linux-media <linux-media@vger.kernel.org>,
GPIO <linux-gpio@vger.kernel.org>
Cc: "Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Brad Love" <brad@nextdimension.cc>,
"Antti Palosaari" <crope@iki.fi>,
"Olli Salonen" <olli.salonen@iki.fi>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Jeffrey Hugo" <jeffrey.l.hugo@gmail.com>,
"Wolfram Sang" <wsa@the-dreams.de>,
"Simon Horman" <horms+renesas@verge.net.au>,
"Peter Korsgaard" <peter@korsgaard.com>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC] SW connection between DVB Transport Stream demuxer and I2C-based frontend
Date: Mon, 8 Jul 2019 17:03:55 +0200 [thread overview]
Message-ID: <79b9bd5e-be05-daa8-0d16-d84a383138a7@free.fr> (raw)
In-Reply-To: <b6abf5a2-3151-29e5-8eb7-c960580fd4ea@metux.net>
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 AFAIU ;-)
https://elixir.bootlin.com/linux/latest/source/drivers/media/dvb-frontends/si2168.c#L780
/* create mux i2c adapter for tuner */
dev->muxc = i2c_mux_alloc(client->adapter, &client->dev, 1, 0, I2C_MUX_LOCKED, si2168_select, si2168_deselect);
ret = i2c_mux_add_adapter(dev->muxc, 0, 0, 0);
/* this is the new internal i2c bus */
struct i2c_adapter *si2168_bus = dev->muxc->adapter[0];
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.
Regards.
WARNING: multiple messages have this Message-ID (diff)
From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Enrico Weigelt <lkml@metux.net>, I2C <linux-i2c@vger.kernel.org>,
linux-media <linux-media@vger.kernel.org>,
GPIO <linux-gpio@vger.kernel.org>
Cc: "Peter Korsgaard" <peter@korsgaard.com>,
"Jeffrey Hugo" <jeffrey.l.hugo@gmail.com>,
"Wolfram Sang" <wsa@the-dreams.de>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Brad Love" <brad@nextdimension.cc>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
"Antti Palosaari" <crope@iki.fi>,
"Simon Horman" <horms+renesas@verge.net.au>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Olli Salonen" <olli.salonen@iki.fi>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC] SW connection between DVB Transport Stream demuxer and I2C-based frontend
Date: Mon, 8 Jul 2019 17:03:55 +0200 [thread overview]
Message-ID: <79b9bd5e-be05-daa8-0d16-d84a383138a7@free.fr> (raw)
In-Reply-To: <b6abf5a2-3151-29e5-8eb7-c960580fd4ea@metux.net>
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 AFAIU ;-)
https://elixir.bootlin.com/linux/latest/source/drivers/media/dvb-frontends/si2168.c#L780
/* create mux i2c adapter for tuner */
dev->muxc = i2c_mux_alloc(client->adapter, &client->dev, 1, 0, I2C_MUX_LOCKED, si2168_select, si2168_deselect);
ret = i2c_mux_add_adapter(dev->muxc, 0, 0, 0);
/* this is the new internal i2c bus */
struct i2c_adapter *si2168_bus = dev->muxc->adapter[0];
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.
Regards.
WARNING: multiple messages have this Message-ID (diff)
From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Enrico Weigelt <lkml@metux.net>, I2C <linux-i2c@vger.kernel.org>,
linux-media <linux-media@vger.kernel.org>,
GPIO <linux-gpio@vger.kernel.org>
Cc: "Peter Korsgaard" <peter@korsgaard.com>,
"Jeffrey Hugo" <jeffrey.l.hugo@gmail.com>,
"Wolfram Sang" <wsa@the-dreams.de>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Brad Love" <brad@nextdimension.cc>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
"Antti Palosaari" <crope@iki.fi>,
"Simon Horman" <horms+renesas@verge.net.au>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Olli Salonen" <olli.salonen@iki.fi>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC] SW connection between DVB Transport Stream demuxer and I2C-based frontend
Date: Mon, 8 Jul 2019 17:03:55 +0200 [thread overview]
Message-ID: <79b9bd5e-be05-daa8-0d16-d84a383138a7@free.fr> (raw)
In-Reply-To: <b6abf5a2-3151-29e5-8eb7-c960580fd4ea@metux.net>
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 AFAIU ;-)
https://elixir.bootlin.com/linux/latest/source/drivers/media/dvb-frontends/si2168.c#L780
/* create mux i2c adapter for tuner */
dev->muxc = i2c_mux_alloc(client->adapter, &client->dev, 1, 0, I2C_MUX_LOCKED, si2168_select, si2168_deselect);
ret = i2c_mux_add_adapter(dev->muxc, 0, 0, 0);
/* this is the new internal i2c bus */
struct i2c_adapter *si2168_bus = dev->muxc->adapter[0];
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.
Regards.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-07-08 15:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 11:08 [RFC] SW connection between DVB Transport Stream demuxer and I2C-based frontend Marc Gonzalez
2019-07-08 11:08 ` Marc Gonzalez
2019-07-08 11:08 ` Marc Gonzalez
2019-07-08 14:44 ` Enrico Weigelt, metux IT consult
2019-07-08 14:44 ` Enrico Weigelt, metux IT consult
2019-07-08 14:44 ` Enrico Weigelt, metux IT consult
2019-07-08 15:03 ` Marc Gonzalez [this message]
2019-07-08 15:03 ` Marc Gonzalez
2019-07-08 15:03 ` Marc Gonzalez
2019-07-08 19:10 ` Enrico Weigelt, metux IT consult
2019-07-08 19:10 ` Enrico Weigelt, metux IT consult
2019-07-08 19:10 ` Enrico Weigelt, metux IT consult
2019-07-08 16:42 ` Marc Gonzalez
2019-07-08 16:42 ` Marc Gonzalez
2019-07-08 16:42 ` Marc Gonzalez
2019-07-08 19:58 ` Peter Rosin
2019-07-08 19:58 ` Peter Rosin
2019-07-08 19:58 ` Peter Rosin
2019-07-09 23:21 ` Jonathan Neuschäfer
2019-07-09 23:21 ` Jonathan Neuschäfer
2019-07-10 13:52 ` Marc Gonzalez
2019-07-10 13:52 ` Marc Gonzalez
2019-07-10 13:52 ` Marc Gonzalez
2019-07-10 15:07 ` Marc Gonzalez
2019-07-10 15:07 ` Marc Gonzalez
2019-07-10 15:07 ` Marc Gonzalez
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=79b9bd5e-be05-daa8-0d16-d84a383138a7@free.fr \
--to=marc.w.gonzalez@free.fr \
--cc=bjorn.andersson@linaro.org \
--cc=brad@nextdimension.cc \
--cc=crope@iki.fi \
--cc=horms+renesas@verge.net.au \
--cc=j.neuschaefer@gmx.net \
--cc=jeffrey.l.hugo@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lkml@metux.net \
--cc=mchehab@kernel.org \
--cc=olli.salonen@iki.fi \
--cc=peter@korsgaard.com \
--cc=wsa@the-dreams.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.