On Mon, Jul 23, 2018 at 11:16:08PM +0100, Robin Murphy wrote: > When an explicit DMA limit is described by firmware, we need to remember > it regardless of how drivers might subsequently update their devices' > masks. The new bus_dma_mask field does that. > > CC: Lorenzo Pieralisi <lorenzo.pieralisi@xxxxxxx> > CC: Hanjun Guo <hanjun.guo@xxxxxxxxxx> > CC: Sudeep Holla <sudeep.holla@xxxxxxx> > Signed-off-by: Robin Murphy <robin.murphy@xxxxxxx> > --- > drivers/acpi/arm64/iort.c | 1 + > 1 file changed, 1 insertion(+) Acked-by: Lorenzo Pieralisi <lorenzo.pieralisi@xxxxxxx> > diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/arm64/iort.c > index 4a66896e2aa3..bc51cff5505e 100644 > --- a/drivers/acpi/arm64/iort.c > +++ b/drivers/acpi/arm64/iort.c > @@ -1014,6 +1014,7 @@ void iort_dma_setup(struct device *dev, u64 *dma_addr, u64 *dma_size) > * Limit coherent and dma mask based on size > * retrieved from firmware. > */ > + dev->bus_dma_mask = mask; > dev->coherent_dma_mask = mask; > *dev->dma_mask = mask; > } > -- > 2.17.1.dirty > -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
