From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Enrico Weigelt, metux IT consult" Subject: Re: [RFC] SW connection between DVB Transport Stream demuxer and I2C-based frontend Date: Mon, 8 Jul 2019 21:10:20 +0200 Message-ID: References: <5e35b4fb-646d-6428-f372-ee47d7352cd6@free.fr> <79b9bd5e-be05-daa8-0d16-d84a383138a7@free.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <79b9bd5e-be05-daa8-0d16-d84a383138a7@free.fr> Content-Language: en-US List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Marc Gonzalez , I2C , linux-media , GPIO Cc: Peter Korsgaard , Jeffrey Hugo , Wolfram Sang , Linus Walleij , Brad Love , =?UTF-8?Q?Jonathan_Neusch=c3=a4fer?= , Bjorn Andersson , Antti Palosaari , Simon Horman , Mauro Carvalho Chehab , Olli Salonen , Linux ARM List-Id: linux-i2c@vger.kernel.org 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 device probing on that bus. (so, it really needs to provide a full blown i2c driver ?) --mtx -- Enrico Weigelt, metux IT consult Free software and Linux embedded engineering info@metux.net -- +49-151-27565287