On Tue, Sep 13, 2016 at 02:38:35PM +0100, Robin Murphy wrote:
> > static int arm_smmu_match_node(struct device *dev, void *data)
> > {
> > - return dev->of_node == data;
> > + struct fwnode_handle *fwnode;
> > +
> > + fwnode = dev->of_node ? >of_node->fwnode : dev->fwnode;
> > +
> > +
On Tue, Sep 13, 2016 at 02:38:35PM +0100, Robin Murphy wrote:
> > static int arm_smmu_match_node(struct device *dev, void *data)
> > {
> > - return dev->of_node == data;
> > + struct fwnode_handle *fwnode;
> > +
> > + fwnode = dev->of_node ? >of_node->fwnode : dev->fwnode;
> > +
> > +
Hi Lorenzo,
On 09/09/16 15:23, Lorenzo Pieralisi wrote:
> The iommu_fwspec structure, used to hold per device iommu configuration
> data is not OF specific and therefore can be moved to a generic
> and OF independent compilation unit.
>
> In particular, the iommu_fwspec handling hinges on the
Hi Lorenzo,
On 09/09/16 15:23, Lorenzo Pieralisi wrote:
> The iommu_fwspec structure, used to hold per device iommu configuration
> data is not OF specific and therefore can be moved to a generic
> and OF independent compilation unit.
>
> In particular, the iommu_fwspec handling hinges on the
The iommu_fwspec structure, used to hold per device iommu configuration
data is not OF specific and therefore can be moved to a generic
and OF independent compilation unit.
In particular, the iommu_fwspec handling hinges on the device_node
pointer to identify the IOMMU device associated with the
The iommu_fwspec structure, used to hold per device iommu configuration
data is not OF specific and therefore can be moved to a generic
and OF independent compilation unit.
In particular, the iommu_fwspec handling hinges on the device_node
pointer to identify the IOMMU device associated with the
6 matches
Mail list logo
