From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Peter Rosin <peda@axentia.se>
Cc: "Peter Korsgaard" <peter@korsgaard.com>,
"Marc Gonzalez" <marc.w.gonzalez@free.fr>,
"Wolfram Sang" <wsa@the-dreams.de>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Brad Love" <brad@nextdimension.cc>,
"Jeffrey Hugo" <jeffrey.l.hugo@gmail.com>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
GPIO <linux-gpio@vger.kernel.org>,
"Antti Palosaari" <crope@iki.fi>, I2C <linux-i2c@vger.kernel.org>,
"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>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: [RFC] SW connection between DVB Transport Stream demuxer and I2C-based frontend
Date: Wed, 10 Jul 2019 01:21:44 +0200 [thread overview]
Message-ID: <20190709232144.GI22408@latitude> (raw)
In-Reply-To: <7d47a978-5307-a2c8-acc2-f29ce7567bd5@axentia.se>
[-- Attachment #1.1: Type: text/plain, Size: 944 bytes --]
On Mon, Jul 08, 2019 at 07:58:00PM +0000, 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 think you should be able to add something like this here:
>
> i2c-gate {
> #address-cells = <1>;
> #size-cells = <0>;
>
> tuner@60 {
> compatible = "silabs,si2157";
> reg = <0x60>;
> /* whatever else is needed */
> };
> };
>
> But in practice, I don't know if the si2157 driver understands that or
> if there is anything else that gets in the way. Totally untested...
So far, both drivers don't deal with devicetree at all, and there are no
bindings, so we have the chance to write the best bindings possible.
An i2c-gate subnode on the si2168 node looks good to me, FWIW.
Greetings,
Jonathan Neuschäfer
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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-09 23:22 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
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 [this message]
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=20190709232144.GI22408@latitude \
--to=j.neuschaefer@gmx.net \
--cc=bjorn.andersson@linaro.org \
--cc=brad@nextdimension.cc \
--cc=crope@iki.fi \
--cc=horms+renesas@verge.net.au \
--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=peda@axentia.se \
--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;
as well as URLs for NNTP newsgroup(s).