From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Marc Gonzalez <marc.w.gonzalez@free.fr>,
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 16:44:00 +0200 [thread overview]
Message-ID: <b6abf5a2-3151-29e5-8eb7-c960580fd4ea@metux.net> (raw)
In-Reply-To: <5e35b4fb-646d-6428-f372-ee47d7352cd6@free.fr>
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@metux.net -- +49-151-27565287
next prev parent reply other threads:[~2019-07-08 14:44 UTC|newest]
Thread overview: 9+ 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 14:44 ` Enrico Weigelt, metux IT consult [this message]
2019-07-08 15:03 ` Marc Gonzalez
2019-07-08 19:10 ` Enrico Weigelt, metux IT consult
2019-07-08 16:42 ` Marc Gonzalez
2019-07-08 19:58 ` Peter Rosin
2019-07-09 23:21 ` Jonathan Neuschäfer
2019-07-10 13:52 ` 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=b6abf5a2-3151-29e5-8eb7-c960580fd4ea@metux.net \
--to=lkml@metux.net \
--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=marc.w.gonzalez@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox