linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Franck Jullien <franck.jullien@gmail.com>
Cc: linux-media@vger.kernel.org, Chris Kohn <christian.kohn@xilinx.com>
Subject: Re: Use xilinx video drivers in PCIe device
Date: Thu, 04 Feb 2016 11:45:33 +0200	[thread overview]
Message-ID: <1672061.k75230d3Eh@avalon> (raw)
In-Reply-To: <CAJfOKByVva72g_1kJyMKGFHr2Jz+Yo6BgZPp_EENj9m4vXOHBA@mail.gmail.com>

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


  reply	other threads:[~2016-02-04  9:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 16:05 Use xilinx video drivers in PCIe device Franck Jullien
2016-02-04  9:45 ` Laurent Pinchart [this message]
2016-02-08  7:40   ` Franck Jullien
2016-02-08 11:14     ` Laurent Pinchart

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=1672061.k75230d3Eh@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=christian.kohn@xilinx.com \
    --cc=franck.jullien@gmail.com \
    --cc=linux-media@vger.kernel.org \
    /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).