From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from galahad.ideasonboard.com ([185.26.127.97]:44562 "EHLO galahad.ideasonboard.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750910AbcBDJpQ (ORCPT ); Thu, 4 Feb 2016 04:45:16 -0500 From: Laurent Pinchart To: Franck Jullien Cc: linux-media@vger.kernel.org, Chris Kohn Subject: Re: Use xilinx video drivers in PCIe device Date: Thu, 04 Feb 2016 11:45:33 +0200 Message-ID: <1672061.k75230d3Eh@avalon> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-media-owner@vger.kernel.org List-ID: Hi Frank, On Tuesday 02 February 2016 17:05:06 Franck Jullien wrote: > Hi, > > I need to use a Xilinx video infrastructure on a PCIe board. > As far as I understand it, all Xilinx video drivers make use of the > device-tree for configuration. Correct. Those drivers target the Xilinx SoC FPGAs, no standalone FPGAs connected to an external CPU. > However, my idea is to create a MFD device to bind video drivers. That > would require Xilinx video drivers to check platform_data and continue > with device tree configuration if it is null or use platform data if > available. > > Do you think such a change in Xilinx drivers can be considered > upstream ? Is this the way to go ? Your use case is certainly valid, so I'm certainly open to supporting it in the drivers. I'm wondering whether your MFD decide driver could create a DT fragment to describe the IP cores topology. That way we could reuse the existing DT support in individual drivers. -- Regards, Laurent Pinchart