On Wed, May 20, 2015 at 10:24:15AM +0100, Catalin Marinas wrote:
> On Sat, May 16, 2015 at 01:59:00AM +0200, Rafael J. Wysocki wrote:
> > On Friday, May 15, 2015 04:23:11 PM Suravee Suthikulpanit wrote:
> > > +/**
> > > + * pci_dma_configure - Setup DMA configuration
> > > + * @pci_dev: ptr to pci_dev struct of the PCI device
> > > + *
> > > + * Function to update PCI devices's DMA configuration using the same
> > > + * info from the OF node or ACPI node of host bridge's parent (if any).
> > > + */
> > > +static void pci_dma_configure(struct pci_dev *pci_dev)
> > > +{
> > > + struct device *dev = &pci_dev->dev;
> > > + struct device *bridge = pci_get_host_bridge_device(pci_dev);
> > > + struct device *host = bridge->parent;
> > > + struct acpi_device *adev;
> > > +
> > > + if (!host)
> > > + return;
> > > +
> > > + if (acpi_disabled) {
> > > + of_dma_configure(dev, host->of_node);
> >
> > I'd rather do
> >
> > if (IS_ENABLED(CONFIG_OF) && host->of_node) {
> > of_dma_configure(dev, host->of_node);
>
> Nitpick: do we need the CONFIG_OF check? If disabled, I don't think
> anyone would set host->of_node.
Please ignore this, there is no point in checking host->of_node if
CONFIG_OF is disabled (I was just thinking from an arm64 perspective
where we always have CONFIG_OF enabled).
--
Catalin
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
