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: Mon, 08 Feb 2016 13:14:10 +0200 [thread overview]
Message-ID: <3104943.upkGDP3not@avalon> (raw)
In-Reply-To: <CAJfOKBymfpRHx5XXLPP1+zAJ+N_C7bzW-pJTvj8S8uGWixNw0w@mail.gmail.com>
Hi Frank,
On Monday 08 February 2016 08:40:11 Franck Jullien wrote:
> 2016-02-04 10:45 GMT+01:00 Laurent Pinchart:
> > 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.
>
> I'm working on such a solution (DT framgent, or more precisely
> devitree dynamic feature).
> I'll keep you informed whenever I get something usable.
Thank you. If you're faced with design choices please feel free to pick our
brains at any time without waiting for a complete implementation.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2016-02-08 11:13 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
2016-02-08 7:40 ` Franck Jullien
2016-02-08 11:14 ` Laurent Pinchart [this message]
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=3104943.upkGDP3not@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.