linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Use xilinx video drivers in PCIe device
@ 2016-02-02 16:05 Franck Jullien
  2016-02-04  9:45 ` Laurent Pinchart
  0 siblings, 1 reply; 4+ messages in thread
From: Franck Jullien @ 2016-02-02 16:05 UTC (permalink / raw)
  To: linux-media

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.
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 ?

Thanks in advance,

Franck.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Use xilinx video drivers in PCIe device
  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
  0 siblings, 1 reply; 4+ messages in thread
From: Laurent Pinchart @ 2016-02-04  9:45 UTC (permalink / raw)
  To: Franck Jullien; +Cc: linux-media, Chris Kohn

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Use xilinx video drivers in PCIe device
  2016-02-04  9:45 ` Laurent Pinchart
@ 2016-02-08  7:40   ` Franck Jullien
  2016-02-08 11:14     ` Laurent Pinchart
  0 siblings, 1 reply; 4+ messages in thread
From: Franck Jullien @ 2016-02-08  7:40 UTC (permalink / raw)
  To: Laurent Pinchart; +Cc: linux-media, Chris Kohn

2016-02-04 10:45 GMT+01:00 Laurent Pinchart <laurent.pinchart@ideasonboard.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.
>

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.

Franck.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Use xilinx video drivers in PCIe device
  2016-02-08  7:40   ` Franck Jullien
@ 2016-02-08 11:14     ` Laurent Pinchart
  0 siblings, 0 replies; 4+ messages in thread
From: Laurent Pinchart @ 2016-02-08 11:14 UTC (permalink / raw)
  To: Franck Jullien; +Cc: linux-media, Chris Kohn

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2016-02-08 11:13 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).