[RESEND PATCH v3 0/4] fpga: don't use drvdata in common code

Setting drvdata is fine for DT based devices which have one manager, bridge, or region device per platform device. However, PCIe based devices may have multiple FPGA mgr/bridge/regions under one PCIe device. Without these changes, PCIe-based solutions have to create an extra device for each child

Re: [PATCH v3 0/4] fpga: don't use drvdata in common code

On Fri, Feb 9, 2018 at 11:18 AM, Moritz Fischer wrote: > On Wed, Feb 07, 2018 at 03:05:26PM -0600, Alan Tull wrote: >> Setting drvdata is fine for DT based devices which have one manager, >> bridge, or region device per platform device. However, PCIe based >> devices may have multiple FPGA mgr/br

Re: [PATCH v3 0/4] fpga: don't use drvdata in common code

On Wed, Feb 07, 2018 at 03:05:26PM -0600, Alan Tull wrote: > Setting drvdata is fine for DT based devices which have one manager, > bridge, or region device per platform device. However, PCIe based > devices may have multiple FPGA mgr/bridge/regions under one PCIe > device. Without these changes,

[PATCH v3 0/4] fpga: don't use drvdata in common code

Setting drvdata is fine for DT based devices which have one manager, bridge, or region device per platform device. However, PCIe based devices may have multiple FPGA mgr/bridge/regions under one PCIe device. Without these changes, PCIe-based solutions have to create an extra device for each child